Re: ACPI 6.4 Could not convert 1 to 4 panic

[Mark Kettenis]

> From: 
> Date: Sun, 6 Nov 2022 11:29:47 +1100
> 
> > -Original Message-
> > From: Mark Kettenis 
> > Sent: Saturday, 5 November 2022 8:44 PM
> > To: ja...@tubnor.net
> > Cc: bugs@openbsd.org
> > Subject: Re: ACPI 6.4 Could not convert 1 to 4 panic
> > 
> > > From: 
> > > Date: Sat, 5 Nov 2022 18:47:23 +1100
> > 
> > Hi Jason,
> > 
> > Can you send us the acpidump output (all the files in
> /var/db/acpi) for this > machine?
> 
> No problems. Let me know if there is anything else I can help with. Cheers!

Still trying to get some context here as the ACPI standard explicitly
describes what conversions are allowed.

Could you boot a normal kernel (i.e. not a ramdisk kernel) without
Mikhail's diff and show me the output?  A screen image is ok.

Thanks,

Mark

Re: Ldomctl generates defective config after OBSD 6.3 on T1000.

[Stefan Sperling]

On Fri, Nov 11, 2022 at 06:46:31PM +, Andrew Grillet wrote:
> I was unable to compile and test the diff - compile times exceeded a week
> on a T1000, and
> then I took ill.
> 
> I now confirm that this problems is present on 7.2 and appears to affect my
> T5120 as well.
> I can create configs with OBSD 6.3 which are bootable on T1000, T2000 and
> T5120.
> All later releases, including 7.2 corrupt the device tree in a similar way.

I can confirm that ldoms are broken on T1000 at least. OpenBSD 7.1 did run
fine on my T1000, hosting several ldom guests. Though I don't remember when
I last updated the firmware's ldom config. Once I regenerated the config it
came back in a state where ldom guests would no longer start up.

I briefly considered debugging it but in the end I gave up on running this
machine. It swallows almost 150W and yields worse performance than a raspberry
pi in return. I've moved my VMs to vmm(4) on amd64 instead.