I think the hangs were actually CAUSED by the messages
being printked. If I make those go away, it stops
getting unhappy. (I suspect repeatedly printk-ing
stuff from the middle of the scsi layer with
interrupts disabled and other fun stuff occuring is
not a good thing. Delays something or
More data:
I changed QLOGICFC_REQ_QUEUE_LEN from 127 to 255, and
the lockup hasn't happened again yet, in circumstances
that fairly reliably reproduced it before. (Could
just mean I have to hit it harder.)
BUT: I am still getting those "no handle slots, this
should not happen" messages.
More data:
I changed QLOGICFC_REQ_QUEUE_LEN from 127 to 255, and
the lockup hasn't happened again yet, in circumstances
that fairly reliably reproduced it before. (Could
just mean I have to hit it harder.)
BUT: I am still getting those "no handle slots, this
should not happen" messages.
I think the hangs were actually CAUSED by the messages
being printked. If I make those go away, it stops
getting unhappy. (I suspect repeatedly printk-ing
stuff from the middle of the scsi layer with
interrupts disabled and other fun stuff occuring is
not a good thing. Delays something or
I've got a 20 drive raid0 set up off of two asus fiber
channel controllers using the qlogicfc.c driver. (I
think it's a variant of ISP2200.) Dual pentium 866
SMP machine, apparently stable under NT. Half a gig
of ram, booting off of a different drive (hanging off
of an LSI1010 scsi controller
I've got a 20 drive raid0 set up off of two asus fiber
channel controllers using the qlogicfc.c driver. (I
think it's a variant of ISP2200.) Dual pentium 866
SMP machine, apparently stable under NT. Half a gig
of ram, booting off of a different drive (hanging off
of an LSI1010 scsi controller
6 matches
Mail list logo
