https://bugzilla.kernel.org/show_bug.cgi?id=13594 Cláudio Martins <ctpm@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ctpm@xxxxxxxxxx --- Comment #9 from Cláudio Martins <ctpm@xxxxxxxxxx> 2010-04-03 22:07:47 --- Hello, I'd like to point out that this bug is still present on kernel version 2.6.34-rc3-00163-g5e11611. I'm using a Supermicro enclosure with a SAS backplane and 16 SATA 1.5TB drives (ST31500341AS). The onboard controller, as reported by lspci: 05:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08) At boot time the mptsas kernel driver reports: scsi4 : ioc0: LSISAS1068E B3, FwRev=011a0000h, Ports=1, MaxQ=478, IRQ=16 Smartmontools is version 5.38-2+lenny1 (v5.38 from Debian Lenny) While generating I/O in the disks, I can easily make all I/O stall for several minutes and even kick drives out of an MD Array by running "smartctl -a /dev/sdX" repeatedly on several drives. During the stall, the kernel logged the following messages: mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) mptscsih: ioc0: attempting task abort! (sc=ffff8802b57aa100) sd 4:0:10:0: [sdk] CDB: ATA command pass through(16): 85 08 0e 00 d5 00 01 00 09 00 4f 00 c2 00 b0 00 mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) mptscsih: ioc0: task abort: SUCCESS (sc=ffff8802b57aa100) mptscsih: ioc0: attempting task abort! (sc=ffff8802b57aa100) sd 4:0:10:0: [sdk] CDB: Test Unit Ready: 00 00 00 00 00 00 mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) mptscsih: ioc0: task abort: SUCCESS (sc=ffff8802b57aa100) mptscsih: ioc0: attempting task abort! (sc=ffff8802be35ec00) sd 4:0:10:0: [sdk] CDB: Write(10): 2a 00 96 27 78 00 00 04 00 00 mptscsih: ioc0: task abort: SUCCESS (sc=ffff8802be35ec00) mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) mptscsih: ioc0: attempting task abort! (sc=ffff8802be35eb00) sd 4:0:10:0: [sdk] CDB: Write(10): 2a 00 96 27 7c 00 00 04 00 00 mptscsih: ioc0: task abort: SUCCESS (sc=ffff8802be35eb00) mptscsih: ioc0: attempting task abort! (sc=ffff8802be35eb00) sd 4:0:10:0: [sdk] CDB: Test Unit Ready: 00 00 00 00 00 00 mptbase: ioc0: LogInfo(0x31130000): Originator={PL}, Code={IO Not Yet Executed}, SubCode(0x0000) mptscsih: ioc0: task abort: SUCCESS (sc=ffff8802be35eb00) mptscsih: ioc0: attempting target reset! (sc=ffff8802b57aa100) sd 4:0:10:0: [sdk] CDB: ATA command pass through(16): 85 08 0e 00 d5 00 01 00 09 00 4f 00 c2 00 b0 00 mptscsih: ioc0: target reset: FAILED (sc=ffff8802b57aa100) mptscsih: ioc0: attempting bus reset! (sc=ffff8802b57aa100) sd 4:0:10:0: [sdk] CDB: ATA command pass through(16): 85 08 0e 00 d5 00 01 00 09 00 4f 00 c2 00 b0 00 mptscsih: ioc0: bus reset: SUCCESS (sc=ffff8802b57aa100) mptscsih: ioc0: attempting task abort! (sc=ffff8802b57aa100) sd 4:0:10:0: [sdk] CDB: Test Unit Ready: 00 00 00 00 00 00 mptbase: ioc0: LogInfo(0x31130000): Originator={PL}, Code={IO Not Yet Executed}, SubCode(0x0000) mptscsih: ioc0: task abort: SUCCESS (sc=ffff8802b57aa100) mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) mptscsih: ioc0: attempting task abort! (sc=ffff8802be35eb00) sd 4:0:10:0: [sdk] CDB: Test Unit Ready: 00 00 00 00 00 00 mptbase: ioc0: LogInfo(0x31130000): Originator={PL}, Code={IO Not Yet Executed}, SubCode(0x0000) mptscsih: ioc0: task abort: SUCCESS (sc=ffff8802be35eb00) mptscsih: ioc0: attempting host reset! (sc=ffff8802b57aa100) mptbase: ioc0: Initiating recovery mptscsih: ioc0: host reset: SUCCESS (sc=ffff8802b57aa100) end_request: I/O error, dev sdb, sector 3903551 md: super_written gets error=-5, uptodate=0 raid1: Disk failure on sdb1, disabling device. raid1: Operation continuing on 1 devices. end_request: I/O error, dev sda, sector 3903551 md: super_written gets error=-5, uptodate=0 RAID1 conf printout: --- wd:1 rd:2 disk 0, wo:0, o:1, dev:sda1 disk 1, wo:1, o:0, dev:sdb1 RAID1 conf printout: --- wd:1 rd:2 disk 0, wo:0, o:1, dev:sda1 -------------- I have this hardware available for a few weeks, so I am willing to help with any tests, diagnostic operations, patches or firmware, that you might have. Any help with this is appreciated, since the fact that drives are being kicked from MD arrays, makes Smartmontools use quite difficult. Thanks in advance for your help. Best regards Cláudio -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.-- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
