Most recent kernel where this bug did not occur: unknown Distribution:Fedora Core 3 Hardware Environment:Intel Pentium III S, QLogic QLA12160 PCI to SCSI Host Adapter, Dell PowerVault 110T Ultrium Software Environment: Problem Description: When performing long scsi operations, such as tape rewinds or seeks, the command fails. Sample syslog entry: Mar 19 21:48:40 sibyl kernel: scsi(0): Resetting Cmnd=0xe850bce0, Handle=0x00000002, action=0x0 Mar 19 21:48:40 sibyl kernel: qla1280_mailbox_command: Command failed, mailbox0 = 0x0015, mailbox_out0 = 0x4005, istatus = 0x6000 Mar 19 21:48:40 sibyl kernel: m0 4005, m1 8600, m2 0000, m3 0001 Mar 19 21:48:40 sibyl kernel: m4 00f9, m5 0006, m6 0000, m7 0000 Mar 19 21:48:40 sibyl kernel: scsi(0:1:6:0): Unable to abort command! Mar 19 21:48:40 sibyl kernel: scsi(0): Resetting Cmnd=0xe850bce0, Handle=0x00000002, action=0x2 Mar 19 21:48:40 sibyl kernel: scsi(0:1:6:0): Queueing device reset command. Mar 19 21:48:53 sibyl kernel: scsi(0): Resetting Cmnd=0xe850bce0, Handle=0x00000001, action=0x0 Mar 19 21:48:57 sibyl kernel: scsi(0): Resetting Cmnd=0xe850bce0, Handle=0x00000001, action=0x3 Mar 19 21:48:57 sibyl kernel: qla1280(0:1): Issuing BUS DEVICE RESET Steps to reproduce: 1. Create a tape with lots of data. There needs to be enough so that a rewind or a seek will take more than 30seconds. 2. Seek to end of tape. I used "mt fsf 5" (because I had 5 partitions dumped to the tape) but "mt eod" might do. Note the the tape appears to seek correctly, but the command fails. Seeking one tape file at a time ("mt fsf 1") works for me but that presumably depends on the size of the tape file. "mt rewind" from the end of the tape fails in a similar way to a long seek. Examine syslog.
Created attachment 7648 [details] A patch to qla1280.c. The command sent to the card was using a 30second timeout regardless of the timeout requested in the scsi command passed down from higher levels.
I have just been made aware of this patch by mkp - being the current owner of the driver, it would have worked a little faster if I had been CC'ed :) At first glance it looks like the patch is good, but I would like to just check it before I push it to James. Cheers, Jes
The status of this problem could be changed to VERIFIED, as I see the patch is included in 2.6.19-rc1. Right?
Patch is in 2.6.19.