[5247] in linux-scsi channel archive
Re: Lockup with new Mylex/BusLogic 2.0.15 driver.
daemon@ATHENA.MIT.EDU (Leonard N. Zubkoff)
Mon Nov 30 23:09:15 1998
Date: Mon, 30 Nov 1998 14:14:26 -0800
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: flood@evcom.net
CC: linux-scsi@vger.rutgers.edu
In-reply-to: <19981130170551.A22794@evcom.net> (message from Floody on Mon, 30
Nov 1998 17:05:51 -0500)
Date: Mon, 30 Nov 1998 17:05:51 -0500
From: Floody <flood@evcom.net>
Greetings.
I am experiencing a lockup using the new BusLogic 2.0.15 driver present in the
2.0.36 kernel. 2.0.14 from 2.0.35 works like a champ, and has for many moons.
My controller is the BT958UW.
The box in question is a PII-266, 128M EDO. The only other cards in the box
are a fairly generic SVGA PCI card and a DE500BA NIC (also PCI). At boot, the
driver properly detects the host adapter, displays it's information, and then
locks hard after "scsi : 1 host." No attached scsi device information is
displayed. My BusLogic driver is compiled statically, rather than as a
module.
There is *very* little difference between the 2.0.14 and 2.0.15 versions of the
BusLogic driver. I suggest you try using the 2.0.14 driver in kernel 2.0.36,
and the 2.0.15 driver in 2.0.35 to see which combination causes the lossage. I
suspect some other change in 2.0.36 is causing the problem.
Leonard
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
