On Mon, Nov 30, 1998 at 02:14:26PM -0800, Leonard N. Zubkoff wrote: > Date: Mon, 30 Nov 1998 17:05:51 -0500 > From: Floody <[EMAIL PROTECTED]> > > 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 I just tested the 2.0.36+2.0.14 combination. I used the exact same kernel configuration as before, simply replacing BusLogic.(c|h) with the 2.0.14 versions. After a clean recompile and install, the box booted with no problem and appeared to operate normally. Reversed the process, putting the original 2.0.15 BusLogic.(c|h) in place, recompile, install, and get the same hang after the host adapter is found. I haven't tried the 2.0.35+2.0.15 combination yet, I'll do that tomorrow and get back to you with the results. -- "I look around me .. and all I see are surfaces .. without depth." - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
