Re: Follow up: 40p boot failure with QEMU
Mark Cave-Ayland <[email protected]> Tue, 28 Aug 2018 07:51:20 +0100
| Newsgroups | gmane.os.netbsd.ports.prep |
|---|---|
| Message-ID | <[email protected]> |
On 28/08/18 07:03, Mark Cave-Ayland wrote: > On 27/08/18 18:18, Martin Husemann wrote: > >> On Mon, Aug 27, 2018 at 05:00:45PM +0100, Mark Cave-Ayland wrote: >>> presumably is enough to reorder the initialisation process so that this >>> now works? >> >> Correct - I have commited the patch to -current. Can you test a daily >> build tomorrow and report back, so I can request pullup? > > Awesome, thanks Martin! I had a quick look at the -current builds but > couldn't see (yet) an ISO for NetBSD/prep - do I just need to wait a bit > longer? Never mind, I was looking in the wrong folder and managed to find the -current ISO at https://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201808272010Z/images/NetBSD-8.99.24-prep.iso. So the good news is that it doesn't panic anymore during the interrupt fixup, but there's a new panic right at the end which doesn't occur without the "IBM PPS Model 6015" in the residual data model name: >> NetBSD/prep BOOT, Revision 1.9 (Mon Aug 27 17:47:48 UTC 2018) siop_scsi_request: timeout siop_scsi_request: timeout siop_scsi_request: timeout (lots cut) Boot: Loading sd(0,0,0)netbsd sd(0,0,0): No such file or directory open sd(0,0,0)netbsd: No such file or directory Boot: Loading sd(0,0,0)onetbsd sd(0,0,0): No such file or directory open sd(0,0,0)onetbsd: No such file or directory Boot: Loading in() No such device - Configured devices are: sd in memory kernel 4580772+121596=0x47c3c4 start=0x100000 [ 1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, [ 1.0000000] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, [ 1.0000000] 2018 The NetBSD Foundation, Inc. All rights reserved. [ 1.0000000] Copyright (c) 1982, 1986, 1989, 1991, 1993 [ 1.0000000] The Regents of the University of California. All rights reserved. [ 1.0000000] NetBSD 8.99.24 (INSTALL) #0: Mon Aug 27 17:47:48 UTC 2018 [ 1.0000000] [email protected]:/usr/src/sys/arch/prep/compile/INSTALL [ 1.0000000] Model: IBM PPS Model 6015 [ 1.0000000] total memory = 128 MB [ 1.0000000] avail memory = 119 MB [ 1.0000000] mainbus0 (root) [ 1.0000000] cpu0 at mainbus0: 604 (Revision 1.3), ID 0 (primary) [ 1.0000000] cpu0: HID0 0xc084<ICE,DCE,SGE,BHT>, powersave: 1 [ 1.0000000] cpu0: 0.00 MHz Couldn't find PNP data for bus 0 devfunc 0x0 [ 1.0000000] pnpbus0 at mainbus0 [ 1.0000000] pci0 at mainbus0 bus 0: indirect configuration space access [ 1.0000000] pchb0 at pci0 dev 0 function 0 [ 1.0000000] pchb0: vendor 1057 product 4801 (rev. 0x00) [ 1.0000000] siop0 at pci0 dev 1 function 0: Symbios Logic 53c810 (fast scsi) [ 1.0000000] siop0: couldn't map interrupt [ 1.0000000] vendor 1234 product 1111 (VGA display, revision 0x02) at pci0 dev 2 function 0 not configured [ 1.0000000] pcn0 at pci0 dev 3 function 0: AMD PCnet-PCI Ethernet [ 1.0000000] pcn0: Am79c970A PCnet-PCI II rev 0, Ethernet address 52:54:00:12:34:56 [ 1.0000000] pcn0: unable to map interrupt [ 1.0000000] pcib0 at pci0 dev 11 function 0: vendor 8086 product 0484 (rev. 0x03) [ 1.0000000] isa0 at pcib0 [ 1.0000000] com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo [ 1.0000000] com0: console [ 1.0000000] com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo [ 1.0000000] pckbc0 at isa0 port 0x60-0x64 [ 1.0000000] pckbd0 at pckbc0 (kbd slot) [ 1.0000000] pckbc0: using irq 1 for kbd slot [ 1.0000000] wskbd0 at pckbd0 (mux ignored) [ 1.0000000] vmmask 10000000 schedmask 10000000 highmask 70000000 [ 1.8298914] WARNING: 3 errors while detecting hardware; check system log. [ 1.8599024] boot device: mainbus0 [ 1.8898394] root on md0a dumps on md0b [ 1.9899750] root file system type: ffs [ 2.0199375] kern.module.path=/stand/prep/8.99.24/modules [ 2.0300605] WARNING: no TOD clock present [ 2.0300605] WARNING: using filesystem time [ 2.0370838] WARNING: CHECK AND RESET THE DATE! [ 3.5907378] trap: pid 2.1 (sh): kernel PGM trap @ 0 (SRR1=0x89032) [ 3.5907378] panic: trap [ 3.6007618] dumpsys: TBD [ 3.6007618] rebooting... Anyone know what "kernel PGM trap @ 0" means? Is it a NULL pointer reference? ATB, Mark.