Re: regression problem with Maxtor disk
Lieven Marchand wrote: Tejun Heo <[EMAIL PROTECTED]> writes: It seems klogd clipped some messages. Can you please turn on printk timestamp, enlarge printk log buffersize and post the result of 'dmesg' after errors? [ 34.576963] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 34.586151] ata1.00: ATA-7: Maxtor 7H500F0, HA431DN0, max UDMA/133 [ 34.586191] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 34.602085] ata1.00: configured for UDMA/133 .. [ 48.994556] ata1: timeout waiting for ADMA IDLE, stat=0x440 [ 49.147577] ata1: failed to read log page 10h (errno=-2) [ 49.149046] ata1.00: exception Emask 0x1 SAct 0xff SErr 0x0 action 0x0 [ 49.149086] ata1.00: (CPB resp_flags 0x11: CMD error) [ 49.149129] ata1.00: cmd 61/06:00:bc:bf:df/00:00:16:00:00/40 tag 0 cdb 0x0 data 3072 out [ 49.149131] res 51/04:00:16:00:00/04:00:16:00:00/40 Emask 0x1 (device error) [ 49.149234] ata1.00: cmd 61/04:08:c4:bf:df/00:00:16:00:00/40 tag 1 cdb 0x0 data 2048 out [ 49.149236] res 51/04:00:16:00:00/04:00:16:00:00/40 Emask 0x1 (device error) [ 49.149338] ata1.00: cmd 61/02:10:d6:bf:df/00:00:16:00:00/40 tag 2 cdb 0x0 data 1024 out [ 49.149340] res 51/04:00:16:00:00/04:00:16:00:00/40 Emask 0x1 (device error) [ 49.149443] ata1.00: cmd 61/04:18:dc:bf:df/00:00:16:00:00/40 tag 3 cdb 0x0 data 2048 out [ 49.149445] res 51/04:00:16:00:00/04:00:16:00:00/40 Emask 0x1 (device error) [ 49.149547] ata1.00: cmd 61/02:20:e8:bf:df/00:00:16:00:00/40 tag 4 cdb 0x0 data 1024 out [ 49.149549] res 51/04:00:16:00:00/04:00:16:00:00/40 Emask 0x1 (device error) [ 49.149652] ata1.00: cmd 61/02:28:f2:bf:df/00:00:16:00:00/40 tag 5 cdb 0x0 data 1024 out [ 49.149653] res 51/04:00:16:00:00/04:00:16:00:00/40 Emask 0x1 (device error) [ 49.149756] ata1.00: cmd 61/04:30:fa:bf:df/00:00:16:00:00/40 tag 6 cdb 0x0 data 2048 out [ 49.149758] res 51/04:00:16:00:00/04:00:16:00:00/40 Emask 0x1 (device error) [ 49.149860] ata1.00: cmd 61/02:38:04:c0:df/00:00:16:00:00/40 tag 7 cdb 0x0 data 1024 out [ 49.149862] res 51/04:00:16:00:00/04:00:16:00:00/40 Emask 0x1 (device error) [ 49.175045] ata1.00: configured for UDMA/133 [ 49.175095] ata1: EH complete [ 49.175145] ata1: timeout waiting for ADMA LEGACY clear and IDLE, stat=0x440 [ 49.175237] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [ 49.175285] sd 0:0:0:0: [sda] Write Protect is off [ 49.175323] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 49.175334] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA I'm not sure exactly what the controller asserting CMD error on the CPB means (I don't think either Jeff or NVIDIA ever let out that particular bit of info), but presumably some kind of FIS error. It seems like the drive is not responding after this point, everything times out. Likely model "Maxtor 7H500F0" and firmware "HA431DN0" needs to be added to the NCQ blacklist. I think this is a similar symptom to some other Maxtor disks which seem to wedge up when NCQ is used.. [ 79.155040] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x17 next cpb idx 0x0 [ 79.155098] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x2 [ 79.155136] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0 [ 79.155174] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x0 [ 79.155212] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x0 [ 79.155250] ata1: CPB 4: ctl_flags 0x1f, resp_flags 0x0 [ 79.155288] ata1: CPB 5: ctl_flags 0x1f, resp_flags 0x0 [ 79.155326] ata1: CPB 6: ctl_flags 0x1f, resp_flags 0x0 [ 79.155364] ata1: CPB 7: ctl_flags 0x1f, resp_flags 0x0 [ 79.155402] ata1: CPB 8: ctl_flags 0x1f, resp_flags 0x0 [ 79.155440] ata1: CPB 9: ctl_flags 0x1f, resp_flags 0x0 [ 79.155478] ata1: CPB 10: ctl_flags 0x1f, resp_flags 0x0 [ 79.155517] ata1: CPB 11: ctl_flags 0x1f, resp_flags 0x0 [ 79.15] ata1: CPB 12: ctl_flags 0x1f, resp_flags 0x0 [ 79.155593] ata1: CPB 13: ctl_flags 0x1f, resp_flags 0x0 [ 79.155631] ata1: CPB 14: ctl_flags 0x1f, resp_flags 0x0 [ 79.155669] ata1: CPB 15: ctl_flags 0x1f, resp_flags 0x0 [ 79.155708] ata1: CPB 16: ctl_flags 0x1f, resp_flags 0x0 [ 79.155746] ata1: CPB 17: ctl_flags 0x1f, resp_flags 0x0 [ 79.155784] ata1: CPB 18: ctl_flags 0x1f, resp_flags 0x0 [ 79.155828] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 79.155873] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 79.155917] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x2 frozen [ 79.155971] ata1.00: cmd 61/02:00:02:c1:df/00:00:16:00:00/40 tag 0 cdb 0x0 data 1024 out [ 79.155973] res 40/00:00:16:00:00/04:00:16:00:00/40 Emask 0x4 (timeout) [ 79.156075] ata1.00: cmd 61/04:08:fa:bf:df/00:00:16:00:00/40 tag 1 cdb 0x0 data 2048 out [ 79.156077] res 40/00:00:16:00:00/04:00:16:00:00/40 Emask 0x4 (timeout) [
Re: regression problem with Maxtor disk
Tejun Heo <[EMAIL PROTECTED]> writes: > It seems klogd clipped some messages. Can you please turn on printk > timestamp, enlarge printk log buffersize and post the result of 'dmesg' > after errors? [ 33.587986] libata version 2.21 loaded. [ 33.592361] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 21 [ 33.592411] ACPI: PCI Interrupt :00:0a.0[A] -> Link [APCH] -> GSI 21 (level, low) -> IRQ 18 [ 33.592508] PCI: Setting latency timer of device :00:0a.0 to 64 [ 33.592516] forcedeth: using HIGHDMA [ 33.64] hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) [ 33.633558] Uniform CD-ROM driver Revision: 3.20 [ 33.638683] hdb: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66) [ 34.109811] eth0: forcedeth.c: subsystem: 01695:1010 bound to :00:0a.0 [ 34.109949] sata_nv :00:07.0: version 3.4 [ 34.110368] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 20 [ 34.110414] ACPI: PCI Interrupt :00:07.0[A] -> Link [APSI] -> GSI 20 (level, low) -> IRQ 19 [ 34.110509] sata_nv :00:07.0: Using ADMA mode [ 34.110587] PCI: Setting latency timer of device :00:07.0 to 64 [ 34.110849] scsi0 : sata_nv [ 34.110922] scsi1 : sata_nv [ 34.110973] ata1: SATA max UDMA/133 cmd 0xf883e480 ctl 0xf883e4a0 bmdma 0x0001cc00 irq 19 [ 34.111026] ata2: SATA max UDMA/133 cmd 0xf883e580 ctl 0xf883e5a0 bmdma 0x0001cc08 irq 19 [ 34.129549] usb 2-1: new high speed USB device using ehci_hcd and address 2 [ 34.322380] usb 2-1: configuration #1 chosen from 1 choice [ 34.336790] Initializing USB Mass Storage driver... [ 34.560984] usb 2-2: new high speed USB device using ehci_hcd and address 3 [ 34.576963] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 34.586151] ata1.00: ATA-7: Maxtor 7H500F0, HA431DN0, max UDMA/133 [ 34.586191] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 34.602085] ata1.00: configured for UDMA/133 [ 34.695412] usb 2-2: configuration #1 chosen from 1 choice [ 34.932499] usb 2-4: new high speed USB device using ehci_hcd and address 4 [ 35.068325] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 35.116969] ata2.00: ATA-7: MAXTOR STM3320820AS, 3.AAE, max UDMA/133 [ 35.117010] ata2.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 35.147355] usb 2-4: configuration #1 chosen from 1 choice [ 35.149712] scsi2 : SCSI emulation for USB Mass Storage devices [ 35.149993] usb-storage: device found at 2 [ 35.149995] usb-storage: waiting for device to settle before scanning [ 35.150009] scsi3 : SCSI emulation for USB Mass Storage devices [ 35.150201] usb-storage: device found at 3 [ 35.150203] usb-storage: waiting for device to settle before scanning [ 35.150216] scsi4 : SCSI emulation for USB Mass Storage devices [ 35.150406] usbcore: registered new interface driver usb-storage [ 35.150447] USB Mass Storage support registered. [ 35.150491] usb-storage: device found at 4 [ 35.150493] usb-storage: waiting for device to settle before scanning [ 35.183534] ata2.00: configured for UDMA/133 [ 35.183676] scsi 0:0:0:0: Direct-Access ATA Maxtor 7H500F0 HA43 PQ: 0 ANSI: 5 [ 35.183734] ata1: bounce limit 0x, segment boundary 0x, hw segs 61 [ 35.184076] scsi 1:0:0:0: Direct-Access ATA MAXTOR STM332082 3.AA PQ: 0 ANSI: 5 [ 35.184130] ata2: bounce limit 0x, segment boundary 0x, hw segs 61 [ 35.184627] ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 23 [ 35.184668] ACPI: PCI Interrupt :00:08.0[A] -> Link [APSJ] -> GSI 23 (level, low) -> IRQ 16 [ 35.184764] sata_nv :00:08.0: Using ADMA mode [ 35.184843] PCI: Setting latency timer of device :00:08.0 to 64 [ 35.184933] scsi5 : sata_nv [ 35.184996] scsi6 : sata_nv [ 35.185050] ata3: SATA max UDMA/133 cmd 0xf88a0480 ctl 0xf88a04a0 bmdma 0x0001b800 irq 16 [ 35.185102] ata4: SATA max UDMA/133 cmd 0xf88a0580 ctl 0xf88a05a0 bmdma 0x0001b808 irq 16 [ 35.651571] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 35.660568] ata3.00: ATA-7: Maxtor 6B300S0, BANC1980, max UDMA/133 [ 35.660608] ata3.00: 586114704 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 35.676553] ata3.00: configured for UDMA/133 [ 35.987125] ata4: SATA link down (SStatus 0 SControl 300) [ 35.987235] scsi 5:0:0:0: Direct-Access ATA Maxtor 6B300S0 BANC PQ: 0 ANSI: 5 [ 35.987289] ata3: bounce limit 0x, segment boundary 0x, hw segs 61 [ 36.023244] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [ 36.023297] sd 0:0:0:0: [sda] Write Protect is off [ 36.023336] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 36.023347] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 36.023439] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [ 36.023484] sd 0:0:0:0: [sda] Write Protect is off [ 36.023522] sd 0:0:0:0: [sda] Mode Sense: 0
Re: regression problem with Maxtor disk
Robert Hancock <[EMAIL PROTECTED]> writes: > It looks like there are some lines missing from this log, there should > be a line before the "res" lines indicating what the failed command > was.. There isn't. I snipped some irrelevant stuff but nothing about a command. The full log is appended. > My guess, though, is that NCQ is somehow busted on this drive, as is > known to be the case with a number of other Maxtor disks.. Aug 11 10:27:51 black kernel: sata_nv :00:07.0: Using ADMA mode Aug 11 10:27:51 black kernel: scsi3 : sata_nv Aug 11 10:27:51 black kernel: scsi4 : sata_nv Aug 11 10:27:51 black kernel: ata1: SATA max UDMA/133 cmd 0xf8840480 ctl 0xf88404a0 bmdma 0x0001cc00 irq 19 Aug 11 10:27:51 black kernel: ata2: SATA max UDMA/133 cmd 0xf8840580 ctl 0xf88405a0 bmdma 0x0001cc08 irq 19 Aug 11 10:27:51 black kernel: hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) Aug 11 10:27:51 black kernel: Uniform CD-ROM driver Revision: 3.20 Aug 11 10:27:51 black kernel: hdb: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66) Aug 11 10:27:51 black kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 11 10:27:51 black kernel: ata1.00: ATA-7: MAXTOR STM3320820AS, 3.AAE, max UDMA/133 Aug 11 10:27:51 black kernel: ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32) Aug 11 10:27:51 black kernel: ata1.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 11 10:27:51 black kernel: ata2.00: ATA-7: Maxtor 7H500F0, HA431DN0, max UDMA/133 Aug 11 10:27:51 black kernel: ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: scsi 3:0:0:0: Direct-Access ATA MAXTOR STM332082 3.AA PQ: 0 ANSI: 5 Aug 11 10:27:51 black kernel: ata1: bounce limit 0x, segment boundary 0x, hw segs 61 Aug 11 10:27:51 black kernel: scsi 4:0:0:0: Direct-Access ATA Maxtor 7H500F0 HA43 PQ: 0 ANSI: 5 Aug 11 10:27:51 black kernel: ata2: bounce limit 0x, segment boundary 0x, hw segs 61 Aug 11 10:27:51 black kernel: ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 23 Aug 11 10:27:51 black kernel: ACPI: PCI Interrupt :00:08.0[A] -> Link [APSJ] -> GSI 23 (level, low) -> IRQ 16 Aug 11 10:27:51 black kernel: sata_nv :00:08.0: Using ADMA mode Aug 11 10:27:51 black kernel: scsi5 : sata_nv Aug 11 10:27:51 black kernel: scsi6 : sata_nv Aug 11 10:27:51 black kernel: ata3: SATA max UDMA/133 cmd 0xf88de480 ctl 0xf88de4a0 bmdma 0x0001b800 irq 16 Aug 11 10:27:51 black kernel: ata4: SATA max UDMA/133 cmd 0xf88de580 ctl 0xf88de5a0 bmdma 0x0001b808 irq 16 Aug 11 10:27:51 black kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 11 10:27:51 black kernel: ata3.00: ATA-7: Maxtor 6Y200M0, YAR51HW0, max UDMA/133 Aug 11 10:27:51 black kernel: ata3.00: 398297088 sectors, multi 16: LBA48 Aug 11 10:27:51 black kernel: ata3.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 11 10:27:51 black kernel: ata4.00: ATA-7: Maxtor 6B300S0, BANC1980, max UDMA/133 Aug 11 10:27:51 black kernel: ata4.00: 586114704 sectors, multi 16: LBA48 NCQ (depth 31/32) Aug 11 10:27:51 black kernel: ata4.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: scsi 5:0:0:0: Direct-Access ATA Maxtor 6Y200M0 YAR5 PQ: 0 ANSI: 5 Aug 11 10:27:51 black kernel: ata3: bounce limit 0x, segment boundary 0x, hw segs 61 Aug 11 10:27:51 black kernel: scsi 6:0:0:0: Direct-Access ATA Maxtor 6B300S0 BANC PQ: 0 ANSI: 5 Aug 11 10:27:51 black kernel: ata4: bounce limit 0x, segment boundary 0x, hw segs 61 Aug 11 10:27:51 black kernel: sd 3:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) Aug 11 10:27:51 black kernel: sd 3:0:0:0: [sda] Write Protect is off Aug 11 10:27:51 black kernel: sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 11 10:27:51 black kernel: sd 3:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) Aug 11 10:27:51 black kernel: sd 3:0:0:0: [sda] Write Protect is off Aug 11 10:27:51 black kernel: sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 11 10:27:51 black kernel: sda: sda1 Aug 11 10:27:51 black kernel: sd 3:0:0:0: [sda] Attached SCSI disk Aug 11 10:27:51 black kernel: sd 4:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Aug 11 10:27:51 black kernel: sd 4:0:0:0: [sdb] Write Protect is off Aug 11 10:27:51 black kernel: sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Aug 11 10:27:51 black kernel: sd 4:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Aug 11 10:27:51 black kernel: sd 4:0:0:0: [sdb] Write Protect is off Aug 11 10:27:51 black kernel: sd 4:0:0:0: [sdb] Write cac
Re: regression problem with Maxtor disk
Lieven Marchand wrote: > Robert Hancock <[EMAIL PROTECTED]> writes: > >> It looks like there are some lines missing from this log, there should >> be a line before the "res" lines indicating what the failed command >> was.. > > There isn't. I snipped some irrelevant stuff but nothing about a > command. The full log is appended. It seems klogd clipped some messages. Can you please turn on printk timestamp, enlarge printk log buffersize and post the result of 'dmesg' after errors? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: regression problem with Maxtor disk
Tejun Heo wrote: [cc'ing Robert Hancock and quoting the whole message for him] Lieven Marchand wrote: Hi, the following drive Aug 12 12:26:15 black kernel: Vendor: ATA Model: Maxtor 7H500F0Rev: HA43 Aug 12 12:26:15 black kernel: Type: Direct-Access ANSI SCSI revision: 05 works fine under 2.6.18 and crashes the boot procedure under 2.6.22. Occasionally the boot continues but most of the times the kernel crashes with an error message of a corrupt cpu context. I've added the logs of a succesful boot here. When such a boot succeeds, the system is noticeably slower than under 2.6.18. Aug 11 10:27:51 black kernel: scsi 4:0:0:0: Direct-Access ATA Maxtor 7H 500F0 HA43 PQ: 0 ANSI: 5 Aug 11 10:27:51 black kernel: ata2: bounce limit 0x, segment bou ndary 0x, hw segs 61 Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x440 Aug 11 10:27:51 black kernel: res 51/04:00:00:00:00/04:00:00:00:00/40 E mask 0x1 (device error) Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: ata2: EH complete Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x440 Aug 11 10:27:51 black kernel: res 51/04:00:00:00:00/04:00:00:00:00/40 E mask 0x1 (device error) Aug 11 10:27:51 black last message repeated 2 times Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: ata2: EH complete Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and ID LE, stat=0x440 Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400 Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, stat=0x400 Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/04:00:00:00:00/40 E mask 0x4 (timeout) Aug 11 10:27:51 black last message repeated 2 times Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 E mask 0x4 (timeout) Aug 11 10:27:51 black kernel: ata2: soft resetting port Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: ata2: EH complete Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and ID LE, stat=0x400 Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400 Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, stat=0x400 Aug 11 10:27:51 black kernel: ata2.00: NCQ disabled due to excessive errors Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/04:00:00:00:00/40 E mask 0x4 (timeout) Aug 11 10:27:51 black last message repeated 2 times Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 E mask 0x4 (timeout) Aug 11 10:27:51 black kernel: ata2: soft resetting port Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: ata2: EH complete Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and ID LE, stat=0x400 Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400 Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, stat=0x400 Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/04:00:00:00:00/40 E mask 0x4 (timeout) Aug 11 10:27:51 black kernel: ata2: soft resetting port Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 Aug 11 10:27:51 black kernel: ata2: EH complete It looks like there are some lines missing from this log, there should be a line before the "res" lines indicating what the failed command was.. My guess, though, is that NCQ is somehow busted on this drive, as is known to be the case with a number of other Maxtor disks.. - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: regression problem with Maxtor disk
[cc'ing Robert Hancock and quoting the whole message for him] Lieven Marchand wrote: > Hi, > > the following drive > > Aug 12 12:26:15 black kernel: Vendor: ATA Model: Maxtor 7H500F0 > Rev: > HA43 > Aug 12 12:26:15 black kernel: Type: Direct-Access > ANSI > SCSI revision: 05 > > works fine under 2.6.18 and crashes the boot procedure under > 2.6.22. Occasionally the boot continues but most of the times the > kernel crashes with an error message of a corrupt cpu context. > > I've added the logs of a succesful boot here. When such a boot > succeeds, the system is noticeably slower than under 2.6.18. > > Aug 11 10:27:51 black kernel: scsi 4:0:0:0: Direct-Access ATA Maxtor > 7H > 500F0 HA43 PQ: 0 ANSI: 5 > Aug 11 10:27:51 black kernel: ata2: bounce limit 0x, segment > bou > ndary 0x, hw segs 61 > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x440 > Aug 11 10:27:51 black kernel: res > 51/04:00:00:00:00/04:00:00:00:00/40 E > mask 0x1 (device error) > Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 > Aug 11 10:27:51 black kernel: ata2: EH complete > > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x440 > Aug 11 10:27:51 black kernel: res > 51/04:00:00:00:00/04:00:00:00:00/40 E > mask 0x1 (device error) > Aug 11 10:27:51 black last message repeated 2 times > Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 > Aug 11 10:27:51 black kernel: ata2: EH complete > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and > ID > LE, stat=0x440 > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400 > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, > stat=0x400 > Aug 11 10:27:51 black kernel: res > 40/00:00:00:00:00/04:00:00:00:00/40 E > mask 0x4 (timeout) > Aug 11 10:27:51 black last message repeated 2 times > Aug 11 10:27:51 black kernel: res > 40/00:00:00:00:00/00:00:00:00:00/00 E > mask 0x4 (timeout) > Aug 11 10:27:51 black kernel: ata2: soft resetting port > Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 > SControl > 300) > Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 > Aug 11 10:27:51 black kernel: ata2: EH complete > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and > ID > LE, stat=0x400 > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400 > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, > stat=0x400 > Aug 11 10:27:51 black kernel: ata2.00: NCQ disabled due to excessive errors > Aug 11 10:27:51 black kernel: res > 40/00:00:00:00:00/04:00:00:00:00/40 E > mask 0x4 (timeout) > Aug 11 10:27:51 black last message repeated 2 times > Aug 11 10:27:51 black kernel: res > 40/00:00:00:00:00/00:00:00:00:00/00 E > mask 0x4 (timeout) > Aug 11 10:27:51 black kernel: ata2: soft resetting port > Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 > SControl > 300) > Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 > Aug 11 10:27:51 black kernel: ata2: EH complete > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and > ID > LE, stat=0x400 > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400 > Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, > stat=0x400 > Aug 11 10:27:51 black kernel: res > 40/00:00:00:00:00/04:00:00:00:00/40 E > mask 0x4 (timeout) > Aug 11 10:27:51 black kernel: ata2: soft resetting port > Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 > SControl > 300) > Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133 > Aug 11 10:27:51 black kernel: ata2: EH complete > - > To unsubscribe from this list: send the line "unsubscribe linux-ide" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: regression problem with Maxtor disk
I think, it's sata_nv driver problem. I have same bug too. MB: ASUS A8N SLI Deluxe (nforce4 sli + sil3114) Power: FSP Epsilon 700W /dev/disk/by-id/scsi-SATA_Maxtor_6B200M0_B404ZB9H /dev/disk/by-id/scsi-SATA_SAMSUNG_HD401LJS0HVJ1CP105426 /dev/disk/by-id/scsi-SATA_WDC_WD3200JD-00_WD-WCAMR1623763 /dev/disk/by-id/scsi-SATA_WDC_WD3200JS-00_WD-WCAPD1127756 /dev/disk/by-id/scsi-SATA_WDC_WD3200JS-00_WD-WCAPD2176538 /dev/disk/by-id/scsi-SATA_WDC_WD3200JS-60_WD-WCAPD2515626 /dev/disk/by-id/scsi-SATA_WDC_WD3200KS-00_WD-WCAPD2510753 /dev/disk/by-id/scsi-SATA_WDC_WD3200KS-00_WD-WCAPD3248212 When I try to copy files from one HDD to another, i have freeses and low speed. There are soft and hard resets here and regression from UDMA/133 to PIO. 2.6.18 (HD400LJ): Aug 13 03:16:52 bobr kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x58 action 0x2 Aug 13 03:16:52 bobr kernel: ata4.00: (BMDMA stat 0x20) Aug 13 03:16:52 bobr kernel: ata4.00: tag 0 cmd 0x35 Emask 0x10 stat 0x51 err 0x84 (ATA bus error) Aug 13 03:16:53 bobr kernel: ata4: soft resetting port Aug 13 03:16:53 bobr kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 13 03:16:53 bobr kernel: ata4.00: configured for UDMA/100 Aug 13 03:16:53 bobr kernel: ata4: EH complete Aug 13 03:16:53 bobr kernel: SCSI device sdd: 625142448 512-byte hdwr sectors (320073 MB) Aug 13 03:16:53 bobr kernel: sdd: Write Protect is off Aug 13 03:16:54 bobr kernel: sdd: Mode Sense: 00 3a 00 00 Aug 13 03:16:54 bobr kernel: SCSI device sdd: drive cache: write back Aug 13 03:17:28 bobr kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x18 action 0x2 frozen Aug 13 03:17:28 bobr kernel: ata4.00: (BMDMA stat 0x21) Aug 13 03:17:28 bobr kernel: ata4.00: tag 0 cmd 0x35 Emask 0x4 stat 0x40 err 0x0 (timeout) Aug 13 03:17:35 bobr kernel: ata4: port is slow to respond, please be patient Aug 13 03:17:59 bobr kernel: ata4: port failed to respond (30 secs) Aug 13 03:17:59 bobr kernel: ata4: soft resetting port Aug 13 03:17:59 bobr kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 13 03:17:59 bobr kernel: ata4.00: configured for UDMA/100 Aug 13 03:17:59 bobr kernel: ata4: EH complete Aug 13 03:18:00 bobr kernel: SCSI device sdd: 625142448 512-byte hdwr sectors (320073 MB) Aug 13 03:18:00 bobr kernel: sdd: Write Protect is off Aug 13 03:18:00 bobr kernel: sdd: Mode Sense: 00 3a 00 00 Aug 13 03:18:00 bobr kernel: SCSI device sdd: drive cache: write back 2.6.23-rc2 (HD401LJ NCQ BLACKLISTED!!!): Aug 12 23:39:54 bobr kernel: ata5: timeout waiting for ADMA IDLE, stat=0x440 Aug 12 23:39:54 bobr kernel: ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x38 action 0x2 Aug 12 23:39:54 bobr kernel: ata5.00: CPB resp_flags 0x11: , CMD error Aug 12 23:39:54 bobr kernel: ata5.00: cmd 25/00:d0:f9:6c:b9/00:01:17:00:00/e0 tag 0 cdb 0x0 data 237568 in Aug 12 23:39:54 bobr kernel: res 51/84:df:ea:6d:b9/84:00:17:00:00/e0 Emask 0x10 (ATA bus error) Aug 12 23:39:54 bobr kernel: ata5: soft resetting port Aug 12 23:39:55 bobr kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Aug 12 23:39:55 bobr kernel: ata5.00: configured for UDMA/133 Aug 12 23:39:55 bobr kernel: ata5: EH complete Aug 12 23:39:55 bobr kernel: sd 4:0:0:0: [sde] 781422768 512-byte hardware sectors (400088 MB) Aug 12 23:39:55 bobr kernel: sd 4:0:0:0: [sde] Write Protect is off Aug 12 23:39:55 bobr kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00 Aug 12 23:39:56 bobr kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 12 23:40:46 bobr kernel: t. Dev: usb-:00:02.0-6/input0, Type: 2, Code: 1, Value: 1 Aug 12 23:40:47 bobr kernel: ata5: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0 Aug 12 23:40:47 bobr kernel: ata5: CPB 0: ctl_flags 0xd, resp_flags 0x0 Aug 12 23:40:47 bobr kernel: ata5: timeout waiting for ADMA IDLE, stat=0x400 Aug 12 23:40:47 bobr kernel: ata5: timeout waiting for ADMA LEGACY, stat=0x400 Aug 12 23:40:47 bobr kernel: ata5: limiting SATA link speed to 1.5 Gbps Aug 12 23:40:47 bobr kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Aug 12 23:40:47 bobr kernel: ata5.00: cmd 25/00:00:79:76:a3/00:02:17:00:00/e0 tag 0 cdb 0x0 data 262144 in Aug 12 23:40:47 bobr kernel: res 40/00:8f:ba:10:a0/84:01:17:00:00/e0 Emask 0x4 (timeout) Aug 12 23:40:47 bobr kernel: ata5: hard resetting port Aug 12 23:40:47 bobr kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 12 23:40:47 bobr kernel: ata5.00: configured for UDMA/133 Aug 12 23:40:47 bobr kernel: ata5: EH complete Aug 12 23:40:47 bobr kernel: sd 4:0:0:0: [sde] 781422768 512-byte hardware sectors (400088 MB) Aug 12 23:40:48 bobr kernel: sd 4:0:0:0: [sde] Write Protect is off Aug 12 23:40:48 bobr kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00 Aug 12 23:40:48 bobr kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
