Re: Odd panic

1999-11-27 Thread Mike Smith
> 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 f

Re: Odd panic

1999-11-27 Thread Bob Bishop
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]

Re: Odd panic

1999-11-27 Thread Poul-Henning Kamp
In message , 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 >

Re: Odd panic

1999-11-27 Thread Bob Bishop
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

Re: Odd panic

1999-11-27 Thread Poul-Henning Kamp
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 , Bob Bishop writes: >Hi, > >cvsup at Sat Nov 27 04:02:41 GMT 1999

Odd panic

1999-11-27 Thread Bob Bishop
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: Fied Direct Access SCSI-2 device da0: 40.000MB/s transf