Re: GENERIC 5.1.2 panics on 7248/120
Andy Ruhl <[email protected]> Fri, 20 Jul 2012 07:43:32 -0700
| Newsgroups | gmane.os.netbsd.ports.prep |
|---|---|
| Message-ID | <CAJcb3fq-y6RrVV8d0k6ZbWC07Wqz23BGzoqq3YKuGHaTw3Gz-g@mail.gmail.com> |
On Fri, Jul 20, 2012 at 3:35 AM, Hisanobu Tomari <[email protected]> wrote: > Hello, > > I recently got an IBM 7248/120 computer and was happy to find NetBSD > support it. NetBSD was successfully installed on the machine using > network booting. However the GENERIC kernel panics during boot. > > I'll try building custom kernel on another machine, and I'd like to know > if there are suggestions on what options to turn on/off. > > Thanks in advance. > > Here's the console output: > > Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, > 2005, > 2006, 2007, 2008, 2009, 2010, 2011, 2012 > The NetBSD Foundation, Inc. All rights reserved. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > NetBSD 5.1.2 (GENERIC) #0: Thu Feb 2 20:16:46 UTC 2012 > > [email protected]:/home/builds/ab/netbsd-5-1-2-RELEASE/prep/201202021012Z-obj/home/builds/ab/netbsd-5-1-2-RELEASE/src/sys/arch/prep/compile/GENERIC > Model: IBM PPS Model 7248 (E) > total memory = 32768 KB > avail memory = 26284 KB > mainbus0 (root) > cpu0 at mainbus0: 604 (Revision 3.4), ID 0 (primary) > cpu0: HID0 c084<ICE,DCE,SGE,BHT>, powersave: 1 > cpu0: 121.21 MHz > pnpbus0 at mainbus0 > wdc0 at pnpbus0: port 0x1f0-0x1f7 0x3f6, irq 13, DMA 6 > atabus0 at wdc0 channel 0 > wdc1 at pnpbus0: port 0x170-0x177 0x376, irq 13, DMA 7 > atabus1 at wdc1 channel 0 > we2 at pnpbus0: port 0x300-0x31f, iomem 0xe8000-0xebfff, irq 11 > we2: WD8013EBT Ethernet (16-bit) > Š : Ethernet address 00:20:35:56:87:4f > fdc0 at pnpbus0: port 0x3f0-0x3f5 0x3f7, irq 6, DMA 2 > mcclock0 at pnpbus0: port 0x70-0x71, irq 8: mc146818 compatible > time-of-day clock > nvram0 at pnpbus0: port 0x74-0x75 0x76 > pci0 at mainbus0 bus 0: indirect configuration space access > pchb0 at pci0 dev 0 function 0 > pchb0: Motorola MPC105 "Eagle" Host Bridge (rev. 0x24) > pchb0: L2 cache: 512K, write-through mode > pcib0 at pci0 dev 11 function 0: IBM Fire Coral ISA Bridge w/PnP (rev. > 0x03) > pcn0 at pci0 dev 12 function 0: AMD PCnet-PCI Ethernet > pcn0: Am79c970A PCnet-PCI II rev 6, Ethernet address 08:00:5a:f8:a1:d2 > pcn0: interrupting at irq 15 > pcn0: 10base5, 10base5-FDX, 10baseT, 10baseT-FDX, auto, auto-FDX > vga0 at pci0 dev 14 function 0: S3 86C864-1 ("Vision864") (rev. 0x00) > wsdisplay0 at vga0 kbdmux 1 > drm at vga0 not configured > siop0 at pci0 dev 16 function 0: Symbios Logic 53c810 (fast scsi) > siop0: interrupting at irq 15 > scsibus0 at siop0: 8 targets, 8 luns per target > isa0 at pcib0 > lpt0 at isa0 port 0x3bc-0x3bf irq 7 > com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo > com0: console > com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo > pckbc0 at isa0 port 0x60-0x64 > pckbd0 at pckbc0 (kbd slot) > pckbc0: using irq 1 for kbd slot > wskbd0 at pckbd0 mux 1 > pms0 at pckbc0 (aux slot) > pckbc0: using irq 12 for aux slot > wsmouse0 at pms0 mux 0 > attimer0 at isa0 port 0x40-0x43: AT Timer > pcppi0 at isa0 port 0x61 > isabeep0 at pcppi0 > attimer0: attached to pcppi0 > biomask 800033e netmask 800033e ttymask 800033e > scsibus0: waiting 2 seconds for devices to settle... > fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec > st0 at scsibus0 target 0 lun 0: <CONNER, CTT8000-S, 1.17> tape removable > st0: drive empty > st0: sync (200.00ns offset 8), 8-bit (5.000MB/s) transfers > cd0 at scsibus0 target 3 lun 0: <IBM, CDRM00203\000\000\000\000\000!K, > 8B08> cdrom removable > cd0: sync (100.00ns offset 8), 8-bit (10.000MB/s) transfers > sd0 at scsibus0 target 6 lun 0: <IBM, DCAS-32160 !#, S69D> disk fixed > sd0: 2063 MB, 8188 cyl, 3 head, 172 sec, 512 bytes/sect x 4226725 > sectors > sd0: sync (100.00ns offset 8), 8-bit (10.000MB/s) transfers, tagged > queueing > Kernelized RAIDframe activated > trap: kernel read DSI trap @ 0x20800a30 by 0x2fd084 (DSISR 0x40000000, > err=14), lr 0x2fd068 > panic: trap > Stopped in pid 0.1 (system) at netbsd:cpu_Debugger+0x10: lwz > r0, r1, 0 > x14 > db> bt > 0x00577c10: at panic+0x210 > 0x00577c60: at trap+0x108 > 0x00577cf0: kernel DSI read trap @ 0x20800a30 by turnstile_block+0x150: > srr1=0x9 > 032 > r1=0x577db0 cr=0x44882228 xer=0 ctr=0x2ea6b0 > dsisr=0x40000000 > 0x00577db0: at turnstile_block+0xd8 > 0x00577de0: at rw_vector_enter+0x1e4 > 0x00577e40: at prop_dictionary_get+0x2c > 0x00577e70: at gen_fwpath+0x40 > 0x00577ea0: at cpu_rootconf+0x330 > 0x00577ee0: at main+0x1fc > 0x00577f30: at 0x1000f0 > db> I'm no kernel hacker, but it looks like it's the kernel probing hardware and it ran into a problem. The way I used to solve stuff like this was to build a kernel and comment out everything that wasn't necessary to boot, and then start adding things back in a few at a time until it panics again. Modern machines can build a kernel in minutes (or less), so it's not a huge deal. You might also look online to find a NetBSD dmesg from a similar machine to see what piece of hardware shows up just after raidframe starts. I haven't booted my prep machine for years. It's just sitting there. One of these days I will boot it again. I also had to netboot mine. Andy