Qlogic 1080 controller+Quantum Atlas 10K...

Kelledin (kelledin+LKML@skarpsey.dyndns.org)
Wed, 4 Dec 2002 23:41:37 -0600


I just spent half a day trying to coax this combo to work on
kernel 2.4.18. The kernel boots, the qla1280 driver probes the
bus, it identifies the drive...and that's the last good word I
get from it. After that, it ends up repeatedly trying to reset
the bus, then gives up and decides there are no devices
attached. Since the root FS is on the Quantum drive, this
obviously causes the kernel to punt.

I'm not actually able to catch all the messages, obviously, but
the general gist is something like this:

----------
scsi0 channel 0 : resetting for second half of retries
SCSI bus is being reset for host 0 channel 0
scsi0 : device driver called scsi_done() for a synchronous
reset
[note: this is bad driver behavior since what, 2.1?]
SCSI disk error: host 0 channel 0 id 0 lun 0 return code =
27070002
[this gets repeated many times.]
----------

The drive works on a different controller, so that's not the
problem (but the other controller is horribly mismatched for the
drive's performance class--it's an ncr53c810!!! :( )

The controller works with a different drive attached, so that's
not the problem (but the other drive is too small to be useful).

I can take the drive, controller, and cable to an x86 box, get
into FASTutil, and do a full sector check on the disk with no
problem--so the hardware is apparently working fine. I've tried
jumpering the controller for manual termination, jumpering the
drive to force single-ended operation, and various combinations,
all to no effect.

(By the way, I flashed the controller to the latest BIOS/firmware
while it was in the x86 box--it didn't help, but I figured it
wouldn't hurt.)

So now it's down to the kernel...any ideas here? At the very
least, I'd like to know what return code "27070002" means...

-- 
Kelledin
"If a server crashes in a server farm and no one pings it, does 
it still cost four figures to fix?"

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/