> On Thu, 11 Nov 1999, Alan Cox wrote:
>
> > > Well... The kernel boots, the ibmmca SCSI-driver starts probing drives,
> > > and BOOM, it panics... Same panic every time, too.
> >
> > Ok
> >
> > > IBM MCA SCSI: ERROR - command error!
> > > Last SCSI-command=0x0, ldn=6, host=0.
> >
> > TEST_UNIT_READY for device id 6. Is that a disk or a cdrom ?
> >
> > > Last SCB Address (LSW)......: 4b50
> > > Last SCB Address (MSW)......: fe
> >
> > and the SCB addr looks believable.
>
> /proc/scsi/scsi
>
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: IBM Model: WDS-3200 !J Rev: S560
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 05 Lun: 00
> Vendor: FUJITSU Model: M2694ES-512 Rev: 812A
> Type: Direct-Access ANSI SCSI revision: 02
>
>
> No CD's as far as eyes can see. In fact, none of my computers has one.
> (Kind of stinks, really.)
>
> I'm doing some tests to find out what kernel was the first to bug out.
As a followup to my own post, here's some results:
v2.3.17 -- Works
v2.3.18 -- Works
v2.3.19 -- Works
v2.3.20 -- Works
v2.3.21 -- Doesn't compile
v2.3.22 -- Works ... Ehmm... Oops:ed om me on reboot, but still...
v2.3.23 -- Panic on boot
v2.3.24 -- Panic on boot
v2.3.25 -- Panic on boot
v2.3.26 -- Panic on boot
Works only specifies that it works fine to boot; I haven't done any
extensive testing.
Now there's only the "small" quest of finding what differs between
v2.3.22 that boots, and v2.3.23 that panics...
I haven't tried v2.3.27 yet, but I wouldn't hold my hopes too high
that it would work.
/David
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/