Re: Status of openbsd/macppc port?
On 17/08/18 14:27, Mark Kettenis wrote: >> Obviously I can't categorically state that QEMU's emulation is perfect, >> but it can now reliably run all of Linux, MacOS, NetBSD and FreeBSD in >> my local tests which makes me suspect that OpenBSD is trying to do >> something different here. > > Runs fairly stable as long as there is enough RAM. There is an > (unknown) pmap bug that causes memory corruption as soon as the > machine starts swapping. Right, I wonder if this is related to the invalid memory accesses I'm seeing in QEMU? Fortunately it's fairly easy to boot different images within the VM, so let's go backwards in time... OpenBSD 6.1 - Boots to userspace, but hangs quickly at the installer shell OpenBSD 6.0 - Hangs on boot just after the USB controller initialises OpenBSD 5.9 - Boots to userspace, but hangs quickly at the installer shell (qemu console logs attempt to execute a NULL opcode, so looks like we're jumping off somewhere strange?) OpenBSD 5.8 - Hangs on boot just after the USB controller initialises (qemu console logs an attempt to execute an invalid/unsupported opcode: 00 - 1c - 17 - 0a (004ad5f8) 1) OpenBSD 5.7 - Lots of "mac_intr_establish called, not yet inited" warnings in the kernel dmesg output - However it boots to userspace and the installer shell seems stable OpenBSD 5.6 - Panics with a stack smash warning: OpenBSD 5.6 (RAMDISK) #163: Fri Aug 8 09:05:59 MDT 2014 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/RAMDISK real mem = 1073741824 (1024MB) avail mem = 1029210112 (981MB) warning: no entropy supplied by boot loader mainbus0 at root: model PowerMac3,1 cpu0 at mainbus0: 7400 (Revision 0x209): 900 MHz: L2 cache not enabled mem at mainbus0 not configured mpcpcibr0 at mainbus0 pci: uni-north pci0 at mpcpcibr0 bus 0 panic: smashed stack in ofw_enumerate_pcibus Stopped at Debugger+0x10: lwz r0,36(r1) 00a00ae4: end+0x561cc fp a00ac0 nfp a00ae0 001ee6dc: panic+0xe0 fp a00ae0 nfp a00b40 001e235c: __stack_smash_handler+0x18 fp a00b40 nfp a00b60 0037ea18: ofw_enumerate_pcibus+0x1b0 fp a00b60 nfp a00bc0 0031bc90: pciattach+0xf0 fp a00bc0 nfp a00bf0 001e3e50: config_attach+0x1f0 fp a00bf0 nfp a00c40 0037dc0c: mpcpcibrattach+0x3b0 fp a00c40 nfp a00d60 001e3e50: config_attach+0x1f0 fp a00d60 nfp a00db0 003095f0: dbdma_flush+0x4d8 fp a00db0 nfp a00e90 001e3e50: config_attach+0x1f0 fp a00e90 nfp a00ee0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb> trace 00a00ae4: end+0x561cc fp a00ac0 nfp a00ae0 001ee6dc: panic+0xe0 fp a00ae0 nfp a00b40 001e235c: __stack_smash_handler+0x18 fp a00b40 nfp a00b60 0037ea18: ofw_enumerate_pcibus+0x1b0 fp a00b60 nfp a00bc0 0031bc90: pciattach+0xf0 fp a00bc0 nfp a00bf0 001e3e50: config_attach+0x1f0 fp a00bf0 nfp a00c40 0037dc0c: mpcpcibrattach+0x3b0 fp a00c40 nfp a00d60 001e3e50: config_attach+0x1f0 fp a00d60 nfp a00db0 003095f0: dbdma_flush+0x4d8 fp a00db0 nfp a00e90 001e3e50: config_attach+0x1f0 fp a00e90 nfp a00ee0 002f63ec: cpu_configure+0x24 fp a00ee0 nfp a00f00 001c525c: main+0x3f0 fp a00f00 nfp a00f40 001001bc: kernel_text+0xa8 fp a00f40 nfp 0 ddb> ps PID PPID PGRPUID S FLAGS WAIT COMMAND *0 -1 0 0 7 0x10200swapper ddb> OpenBSD 5.5 - Lots of "mac_intr_establish called, not yet inited" warnings in the kernel dmesg output - Panics on boot when initialising USB: uhub0 at usb0 "Apple OHCI root hub" rev 1.00/1.00 addr 1 panic: trap type 600 at 2cf4a0 (mtx_enter+0x28) lr 2cf490 Stopped at Debugger+0x10: lwz r0,20(r1) 00fc: tlbdsmsize+0x14 fp 94ba70 nfp 94ba80 001cec40: panic+0xd0 fp 94ba80 nfp 94bae0 002ce8cc: trap+0x184 fp 94bae0 nfp 94bb60 00100900: ddblow+0x1ac fp 94bb60 nfp 94bc10 002cf48c: mtx_enter+0x14 fp 94bc10 nfp 94bc20 001c4a50: config_attach+0x200 fp 94bc20 nfp 94bc60 00351018: mpcpcibrattach+0x3b0 fp 94bc60 nfp 94bd80 001c4a40: config_attach+0x1f0 fp 94bd80 nfp 94bdc0 002e4af0: mb_matchname+0x4e8 fp 94bdc0 nfp 94beb0 001c4a40: config_attach+0x1f0 fp 94beb0 nfp 94bef0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb> trace 00fc: tlbdsmsize+0x14 fp 94ba70 nfp 94ba80 001cec40: panic+0xd0 fp 94ba80 nfp 94bae0 002ce8cc: trap+0x184 fp 94bae0 nfp 94bb60 00100900: ddblow+0x1ac fp 94bb60 nfp 94bc10 002cf48c: mtx_enter+0x14 fp 94bc10 nfp 94bc20 001c4a50: config_attach+0x200 fp 94bc20 nfp 94bc60 00351018: mpcpcibrattach+0x3b0 fp 94bc60 nfp 94bd80 001c4a40: config_attach+0x1f0 fp 94bd80 nfp 94bdc0 002e4af0: mb_matchname+0x4e8 fp 94bdc0 nfp 94beb0 001c4a40: config_attach+0x1f0 fp 94beb0 nfp 94bef0 002d1d9c: cpu_configure+0x24 fp 94bef0 nfp 94bf00 001a7314: main+0x3cc fp 94bf00 nfp 94bf40 001001bc: kernel_text+0xa8 fp 94bf40 nfp 0 ddb> ps PID PPID PGRPUID S FLAGS WAIT COMMAND *0 -1 0 0 7
Re: Status of openbsd/macppc port?
> On Aug 17, 2018, at 8:37 AM, Solene Rapenne wrote: > > The sad state is that less and less > ports are running on them. > The last package count for 6.3 shows macppc had the most packages after amd64 and i386. Can you share examples of ports you’re missing? I’d be interested to look at anything that’s not working (and doesn’t take 3 weeks to build). ps. numpy on macppc was broken for a short period of time which took out part of the tree, but that is fixed as far as i know. see this thread: https://marc.info/?t=15321658432=1=2
Re: Status of openbsd/macppc port?
> From: Mark Cave-Ayland > Date: Fri, 17 Aug 2018 12:15:10 +0100 > > Hi all, > > I was just wondering what is the current state of the openbsd/macppc > port? As part of my recent work on qemu-system-ppc I now have a patch > that can boot OpenBSD macppc under the New World (-M mac99,via=pmu) > machine but I'm seeing quite a bit of instability in OpenBSD compared to > all my other test OSs. > > For those that are interested I have included screenshots below: > > OpenBSD 6.3 > - Hangs just after USB detection > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.3.png > > OpenBSD 6.2 > - Panics just after USB detection > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.2.png > > OpenBSD 6.1 > - Boots all the way to the installer but causes qemu-system-ppc to > terminate fairly easily after pressing a few keys with "qemu: fatal: > ERROR: instruction should not need address translation" > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.1.png > > Note I also get a constant stream of messages on the console related to > OpenPIC: > > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > etc. > > > Obviously I can't categorically state that QEMU's emulation is perfect, > but it can now reliably run all of Linux, MacOS, NetBSD and FreeBSD in > my local tests which makes me suspect that OpenBSD is trying to do > something different here. Runs fairly stable as long as there is enough RAM. There is an (unknown) pmap bug that causes memory corruption as soon as the machine starts swapping.
Re: Status of openbsd/macppc port?
Mark Cave-Ayland wrote: > On 17/08/18 13:55, Solene Rapenne wrote: > > > I'm using the macppc port since 6.1 to -current and apart failing > > harware I don't have any issue while playing Doom or rebuilind ports :) > > Hmmm. 6.1 is the latest version that I can boot to userspace, even if it > faults quickly after a few keypresses (QEMU is generally really strict > on invalid memory accesses which is basically what I see, but once the > access is tracked down it would be possible to fix it). > > I'd be interested to know if you are able to at least boot a 6.3 > installation CDROM on the Mac Mini to the installer without hanging, > which is probably the closest match to what I'm doing on real hardware. > > > ATB, > > Mark. This is interesting as I never used a CDROM for installation, I don't have a burner anymore and I'm not sure that the cdrom reader still work but boot from PXE.
Re: Status of openbsd/macppc port?
On Fri, Aug 17, 2018 at 8:48 AM, Mark Cave-Ayland wrote: > On 17/08/18 13:34, Jonathan Gray wrote: > >> On Fri, Aug 17, 2018 at 12:15:10PM +0100, Mark Cave-Ayland wrote: >>> Hi all, >>> >>> I was just wondering what is the current state of the openbsd/macppc >>> port? As part of my recent work on qemu-system-ppc I now have a patch >>> that can boot OpenBSD macppc under the New World (-M mac99,via=pmu) >>> machine but I'm seeing quite a bit of instability in OpenBSD compared to >>> all my other test OSs. >>> >>> For those that are interested I have included screenshots below: >>> >>> OpenBSD 6.3 >>> - Hangs just after USB detection >>> - https://www.ilande.co.uk/tmp/qemu/openbsd-6.3.png >>> >>> OpenBSD 6.2 >>> - Panics just after USB detection >>> - https://www.ilande.co.uk/tmp/qemu/openbsd-6.2.png >>> >>> OpenBSD 6.1 >>> - Boots all the way to the installer but causes qemu-system-ppc to >>> terminate fairly easily after pressing a few keys with "qemu: fatal: >>> ERROR: instruction should not need address translation" >>> - https://www.ilande.co.uk/tmp/qemu/openbsd-6.1.png >>> >>> Note I also get a constant stream of messages on the console related to >>> OpenPIC: >>> >>> qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f >>> qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f >>> qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f >>> qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f >>> qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c >>> qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c >>> qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c >>> etc. >>> >>> >>> Obviously I can't categorically state that QEMU's emulation is perfect, >>> but it can now reliably run all of Linux, MacOS, NetBSD and FreeBSD in >>> my local tests which makes me suspect that OpenBSD is trying to do >>> something different here. >> >> Builds are done natively on real hardware (xserves). Your work on >> qemu-system-ppc would be improved by being able to compare to a real >> machine while it is still possible to find some that work. You could >> search bugs@ but I don't believe any of those problems have been reported >> running on actual macppc machines. > > Thanks for information. I guess there is a difference between being able > to build and run the guest OS - for example do the builds get regularly > tested on any Sawtooth-type PowerMac3,1 machines (which is effectively > what QEMU is trying to emulate)? > Hi Mark, I regularly run macppc. Here's my dmesg from a PowerMac10,2 which is a Mac Mini G4 and where I do all my ports building: http://dickman.org/openbsd/dmesg/dmesg.macppc I also have other macppc hardware which runs quite well. The only problem case is my G5 where the hard drive does not get detected. Hope this helps.
Re: Status of openbsd/macppc port?
On 17/08/18 13:55, Solene Rapenne wrote: > I'm using the macppc port since 6.1 to -current and apart failing > harware I don't have any issue while playing Doom or rebuilind ports :) Hmmm. 6.1 is the latest version that I can boot to userspace, even if it faults quickly after a few keypresses (QEMU is generally really strict on invalid memory accesses which is basically what I see, but once the access is tracked down it would be possible to fix it). I'd be interested to know if you are able to at least boot a 6.3 installation CDROM on the Mac Mini to the installer without hanging, which is probably the closest match to what I'm doing on real hardware. ATB, Mark.
Re: Status of openbsd/macppc port?
Mark Cave-Ayland wrote: > On 17/08/18 13:37, Solene Rapenne wrote: > > Mark Cave-Ayland wrote: > >> Hi all, > >> > >> I was just wondering what is the current state of the openbsd/macppc > >> port? As part of my recent work on qemu-system-ppc I now have a patch > >> that can boot OpenBSD macppc under the New World (-M mac99,via=pmu) > >> machine but I'm seeing quite a bit of instability in OpenBSD compared to > >> all my other test OSs. > > > Hello > > > > I can't help you much with your qemu issue but I can confirm you that > > the OpenBSD macppc port works really well as I use 2 macppc devices (an > > mac mini and a powerbook) often. The sad state is that less and less > > ports are running on them. > > Thanks for the response Solene. Can I ask which version of > openbsd/macppc you are currently running? > > > ATB, > > Mark. I'm using the macppc port since 6.1 to -current and apart failing harware I don't have any issue while playing Doom or rebuilind ports :)
Re: Status of openbsd/macppc port?
On 17/08/18 13:37, Solene Rapenne wrote: > Mark Cave-Ayland wrote: >> Hi all, >> >> I was just wondering what is the current state of the openbsd/macppc >> port? As part of my recent work on qemu-system-ppc I now have a patch >> that can boot OpenBSD macppc under the New World (-M mac99,via=pmu) >> machine but I'm seeing quite a bit of instability in OpenBSD compared to >> all my other test OSs. > Hello > > I can't help you much with your qemu issue but I can confirm you that > the OpenBSD macppc port works really well as I use 2 macppc devices (an > mac mini and a powerbook) often. The sad state is that less and less > ports are running on them. Thanks for the response Solene. Can I ask which version of openbsd/macppc you are currently running? ATB, Mark.
Re: Status of openbsd/macppc port?
On 17/08/18 13:34, Jonathan Gray wrote: > On Fri, Aug 17, 2018 at 12:15:10PM +0100, Mark Cave-Ayland wrote: >> Hi all, >> >> I was just wondering what is the current state of the openbsd/macppc >> port? As part of my recent work on qemu-system-ppc I now have a patch >> that can boot OpenBSD macppc under the New World (-M mac99,via=pmu) >> machine but I'm seeing quite a bit of instability in OpenBSD compared to >> all my other test OSs. >> >> For those that are interested I have included screenshots below: >> >> OpenBSD 6.3 >> - Hangs just after USB detection >> - https://www.ilande.co.uk/tmp/qemu/openbsd-6.3.png >> >> OpenBSD 6.2 >> - Panics just after USB detection >> - https://www.ilande.co.uk/tmp/qemu/openbsd-6.2.png >> >> OpenBSD 6.1 >> - Boots all the way to the installer but causes qemu-system-ppc to >> terminate fairly easily after pressing a few keys with "qemu: fatal: >> ERROR: instruction should not need address translation" >> - https://www.ilande.co.uk/tmp/qemu/openbsd-6.1.png >> >> Note I also get a constant stream of messages on the console related to >> OpenPIC: >> >> qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f >> qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f >> qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f >> qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f >> qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c >> qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c >> qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c >> etc. >> >> >> Obviously I can't categorically state that QEMU's emulation is perfect, >> but it can now reliably run all of Linux, MacOS, NetBSD and FreeBSD in >> my local tests which makes me suspect that OpenBSD is trying to do >> something different here. > > Builds are done natively on real hardware (xserves). Your work on > qemu-system-ppc would be improved by being able to compare to a real > machine while it is still possible to find some that work. You could > search bugs@ but I don't believe any of those problems have been reported > running on actual macppc machines. Thanks for information. I guess there is a difference between being able to build and run the guest OS - for example do the builds get regularly tested on any Sawtooth-type PowerMac3,1 machines (which is effectively what QEMU is trying to emulate)? FWIW from the screenshots above the "bad IRQs" being complained about above can be show to be macgpio1 (IRQ 47) and ohci0 (IRQ 28). Is there anything special about these interrupts at all, e.g. edge vs. level triggering? ATB, Mark.
Re: Status of openbsd/macppc port?
Mark Cave-Ayland wrote: > Hi all, > > I was just wondering what is the current state of the openbsd/macppc > port? As part of my recent work on qemu-system-ppc I now have a patch > that can boot OpenBSD macppc under the New World (-M mac99,via=pmu) > machine but I'm seeing quite a bit of instability in OpenBSD compared to > all my other test OSs. > > For those that are interested I have included screenshots below: > > OpenBSD 6.3 > - Hangs just after USB detection > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.3.png > > OpenBSD 6.2 > - Panics just after USB detection > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.2.png > > OpenBSD 6.1 > - Boots all the way to the installer but causes qemu-system-ppc to > terminate fairly easily after pressing a few keys with "qemu: fatal: > ERROR: instruction should not need address translation" > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.1.png > > Note I also get a constant stream of messages on the console related to > OpenPIC: > > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > etc. > > > Obviously I can't categorically state that QEMU's emulation is perfect, > but it can now reliably run all of Linux, MacOS, NetBSD and FreeBSD in > my local tests which makes me suspect that OpenBSD is trying to do > something different here. > > > ATB, > > Mark. Hello I can't help you much with your qemu issue but I can confirm you that the OpenBSD macppc port works really well as I use 2 macppc devices (an mac mini and a powerbook) often. The sad state is that less and less ports are running on them.
Re: Status of openbsd/macppc port?
On Fri, Aug 17, 2018 at 12:15:10PM +0100, Mark Cave-Ayland wrote: > Hi all, > > I was just wondering what is the current state of the openbsd/macppc > port? As part of my recent work on qemu-system-ppc I now have a patch > that can boot OpenBSD macppc under the New World (-M mac99,via=pmu) > machine but I'm seeing quite a bit of instability in OpenBSD compared to > all my other test OSs. > > For those that are interested I have included screenshots below: > > OpenBSD 6.3 > - Hangs just after USB detection > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.3.png > > OpenBSD 6.2 > - Panics just after USB detection > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.2.png > > OpenBSD 6.1 > - Boots all the way to the installer but causes qemu-system-ppc to > terminate fairly easily after pressing a few keys with "qemu: fatal: > ERROR: instruction should not need address translation" > - https://www.ilande.co.uk/tmp/qemu/openbsd-6.1.png > > Note I also get a constant stream of messages on the console related to > OpenPIC: > > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c > etc. > > > Obviously I can't categorically state that QEMU's emulation is perfect, > but it can now reliably run all of Linux, MacOS, NetBSD and FreeBSD in > my local tests which makes me suspect that OpenBSD is trying to do > something different here. Builds are done natively on real hardware (xserves). Your work on qemu-system-ppc would be improved by being able to compare to a real machine while it is still possible to find some that work. You could search bugs@ but I don't believe any of those problems have been reported running on actual macppc machines.
Status of openbsd/macppc port?
Hi all, I was just wondering what is the current state of the openbsd/macppc port? As part of my recent work on qemu-system-ppc I now have a patch that can boot OpenBSD macppc under the New World (-M mac99,via=pmu) machine but I'm seeing quite a bit of instability in OpenBSD compared to all my other test OSs. For those that are interested I have included screenshots below: OpenBSD 6.3 - Hangs just after USB detection - https://www.ilande.co.uk/tmp/qemu/openbsd-6.3.png OpenBSD 6.2 - Panics just after USB detection - https://www.ilande.co.uk/tmp/qemu/openbsd-6.2.png OpenBSD 6.1 - Boots all the way to the installer but causes qemu-system-ppc to terminate fairly easily after pressing a few keys with "qemu: fatal: ERROR: instruction should not need address translation" - https://www.ilande.co.uk/tmp/qemu/openbsd-6.1.png Note I also get a constant stream of messages on the console related to OpenPIC: qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f qemu-system-ppc: openpic_iack: bad raised IRQ 47 ctpr 8 ivpr 0x4047002f qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c qemu-system-ppc: openpic_iack: bad raised IRQ 28 ctpr 8 ivpr 0x4045001c etc. Obviously I can't categorically state that QEMU's emulation is perfect, but it can now reliably run all of Linux, MacOS, NetBSD and FreeBSD in my local tests which makes me suspect that OpenBSD is trying to do something different here. ATB, Mark.
