Odd panic
Hi, cvsup at Sat Nov 27 04:02:41 GMT 1999, looks like it went in the middle of starting up SCSI devices. This box is not SMP and has a 2940UW, my SMP -current box with a plain 2940 doesn't do this. ... da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DCAS-34330W S65A Fied Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2b da1 at ahc0 bus 0 target 1 lun 0 da1: IBM DDRS-34560D DC1B Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) fault code = supervisor read, page not present instruction pointer = 0x8:0xc01658e6 stack pointer = 0x10:0xc03a6f3c frame pointer = 0x10:0xc03a6f3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enable, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = none kernel: type 12 trap, code=0 Stopped at devsw+0x6 cmpl $0, 0x2c(%eax) db -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Odd panic
Bob, can you try to locate the symbols around 0xc01658e6 in your kernel ? Also, when you end in the debugger, always type "trace" so we get a stacktrace to look at. Poul-Henning In message l03020906b465beae21a8@[194.32.164.2], Bob Bishop writes: Hi, cvsup at Sat Nov 27 04:02:41 GMT 1999, looks like it went in the middle of starting up SCSI devices. This box is not SMP and has a 2940UW, my SMP -current box with a plain 2940 doesn't do this. ... da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DCAS-34330W S65A Fied Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2b da1 at ahc0 bus 0 target 1 lun 0 da1: IBM DDRS-34560D DC1B Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) fault code = supervisor read, page not present instruction pointer= 0x8:0xc01658e6 stack pointer = 0x10:0xc03a6f3c frame pointer = 0x10:0xc03a6f3c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enable, resume, IOPL = 0 current process= 0 (swapper) interrupt mask = none kernel: type 12 trap, code=0 Stopped at devsw+0x6 cmpl $0, 0x2c(%eax) db -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Odd panic
Hi, can you try to locate the symbols around 0xc01658e6 in your kernel ? I mistranscribed that (really must get serial consoles sorted out), in fact it's: c0165e80 T devsw Also, when you end in the debugger, always type "trace" so we get a stacktrace to look at. Yes, sorry, got called for dinner at an inopportune moment ;-) devsw() at devsw+0x6 vfs_mountroot_try(c0391092,c02c531c) at vfs_mountroot_try+0xe9 vfs_mountroot(0,3a4c00,3ab000,0,c011d5e6) at vfs_mountroot+0x5a mi_startup(c03a6fb4,b0246,ffe,3ab000,c017ada1) at mi_startup+0x70 begin() at begin+0x4b Also, further back in the log there's a "setrootbyname failed". -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Odd panic
In message l03020907b465d314ed05@[194.32.164.2], Bob Bishop writes: devsw() at devsw+0x6 vfs_mountroot_try(c0391092,c02c531c) at vfs_mountroot_try+0xe9 vfs_mountroot(0,3a4c00,3ab000,0,c011d5e6) at vfs_mountroot+0x5a mi_startup(c03a6fb4,b0246,ffe,3ab000,c017ada1) at mi_startup+0x70 begin() at begin+0x4b Also, further back in the log there's a "setrootbyname failed". Somehow, and there are a fair number of ways this could happen, you ended up without a root device. What is in your /etc/fstab for the root fs ? Is your /boot up to date ? -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Odd panic
Hi, At 7:54 pm +0100 27/11/99, Poul-Henning Kamp wrote: [...] What is in your /etc/fstab for the root fs ? That was it: I was still running on /dev/sd*, looks like that just stopped working. Thanks -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Odd panic
Hi, At 7:54 pm +0100 27/11/99, Poul-Henning Kamp wrote: [...] What is in your /etc/fstab for the root fs ? That was it: I was still running on /dev/sd*, looks like that just stopped working. Thanks A week or two back, actually. But you should have received a more civilised failure than the one you did. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
