* decoding PMP errors with Marvel SATA controller
@ 2011-06-26 7:08 Marc MERLIN
2011-06-26 9:03 ` Tejun Heo
0 siblings, 1 reply; 23+ messages in thread
From: Marc MERLIN @ 2011-06-26 7:08 UTC (permalink / raw)
To: tj, linux-ide
Howdy
I have a dual sil PMP which has been working well enough, and recently moved
to a new Motherboard.
I had to switch my sil3128 to a sil3132 (PCI-X to PCIe) and it seems to work
ok.
I was however trying to switch to a Marvell card that's supposed to be
faster, but I get errors like these on it:
I think my cables are ok since they work with the sil3132.
I also notice that the real error seems to be with the PMP itself
(ata9.15 SError: { BadCRC Handshk } ) and that the rest is just noise.
Is my Marvell card somewhat bad or incompatible with my PMP?
I have 2.6.39.1
gargamel kernel: sata_mv 0000:02:00.0: version 1.28
gargamel kernel: sata_mv 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
gargamel kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
gargamel kernel: sata_mv 0000:02:00.0: setting latency timer to 64
gargamel kernel: scsi8 : sata_mv
gargamel kernel: scsi9 : sata_mv
gargamel kernel: scsi10 : sata_mv
gargamel kernel: scsi11 : sata_mv
gargamel kernel: ata9: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb822000 irq 16
gargamel kernel: ata10: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb824000 irq 16
gargamel kernel: ata11: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb826000 irq 16
gargamel kernel: ata12: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb828000 irq 16
gargamel kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
gargamel kernel: ata10.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
Mmmh, dmesg also shows this (9.15 is my other PMP plugged into the same card):
Is the card bad, is it possibly a driver issue, or could it still be a sata cable issue?
kernel: ata9.00: qc timeout (cmd 0xec)
kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
kernel: ata9.15: hard resetting link
kernel: ata9.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: ------------[ cut here ]------------
kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44()
kernel: Hardware name: System Product Name
kernel: Modules linked in: usbserial pci_hotplug processor thermal_sys wmi parport_pc hwmon button parport r8169 rtc_core snd rtc_lib i2c_i801 xhci_hcd ehci_hcd soundcore sata_mv snd_page_alloc evdev pcspkr iTCO_wdt iTCO_vendor_support intel_agp intel_gtt tpm_tis agpgart usbcore
kernel: Pid: 1642, comm: scsi_eh_8 Not tainted 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2
kernel: Call Trace:
kernel: [<c0133599>] warn_slowpath_common+0x60/0x75
kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13
kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44
kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d
kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156
kernel: [<f84b150b>] mv_qc_issue+0x441/0x44d [sata_mv]
kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7
kernel: [<c014b5bb>] ? up+0x2b/0x2f
kernel: [<c036309d>] ata_qc_issue+0x30b/0x329
kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0
kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde
kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66
kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18
kernel: [<c037213a>] sata_pmp_read+0x66/0x9d
kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65
kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150
kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42
kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204
kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a
kernel: [<f84b0f41>] ? mv_port_start+0x19f/0x19f [sata_mv]
kernel: [<f84b0c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv]
kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150
kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa
kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e
kernel: [<f84b0bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv]
kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522
kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd
kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f
kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d
kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507
kernel: [<c012750b>] ? complete+0x34/0x3e
kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d
kernel: [<c01476c0>] kthread+0x64/0x69
kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119
kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd
This is the error that happens a lot with the sata_mv card, but not the sil24 one:
ata9.15: exception Emask 0x100 SAct 0x0 SErr 0x600000 action 0x6 frozen
ata9.15: edma_err_cause=02320080 pp_flags=00000007, EDMA self-disable
ata9.15: SError: { BadCRC Handshk }
ata9.00: exception Emask 0x100 SAct 0x2 SErr 0x0 action 0x6 frozen
ata9.00: failed command: READ FPDMA QUEUED
ata9.00: cmd 60/78:08:e7:0f:b8/02:00:01:00:00/40 tag 1 ncq 323584 in
res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.00: status: { DRDY }
ata9.01: exception Emask 0x100 SAct 0x8 SErr 0x0 action 0x6 frozen
ata9.01: failed command: READ FPDMA QUEUED
ata9.01: cmd 60/80:18:df:0f:b8/02:00:01:00:00/40 tag 3 ncq 327680 in
res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.01: status: { DRDY }
ata9.02: exception Emask 0x100 SAct 0x1 SErr 0x0 action 0x6 frozen
ata9.02: failed command: READ FPDMA QUEUED
ata9.02: cmd 60/80:00:df:0f:b8/02:00:01:00:00/40 tag 0 ncq 327680 in
res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.02: status: { DRDY }
ata9.03: exception Emask 0x100 SAct 0x74 SErr 0x0 action 0x6 frozen
ata9.03: failed command: WRITE FPDMA QUEUED
ata9.03: cmd 61/08:10:d7:0f:b8/00:00:01:00:00/40 tag 2 ncq 4096 out
res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.03: status: { DRDY }
ata9.03: failed command: WRITE FPDMA QUEUED
ata9.03: cmd 61/88:20:3f:0c:b8/03:00:01:00:00/40 tag 4 ncq 462848 out
res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.03: status: { DRDY }
ata9.03: failed command: WRITE FPDMA QUEUED
ata9.03: cmd 61/08:28:c7:0f:b8/00:00:01:00:00/40 tag 5 ncq 4096 out
res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.03: status: { DRDY }
ata9.03: failed command: WRITE FPDMA QUEUED
ata9.03: cmd 61/08:30:cf:0f:b8/00:00:01:00:00/40 tag 6 ncq 4096 out
res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.03: status: { DRDY }
ata9.04: exception Emask 0x100 SAct 0x80 SErr 0x0 action 0x6 frozen
ata9.04: failed command: READ FPDMA QUEUED
ata9.04: cmd 60/80:38:df:0f:b8/02:00:01:00:00/40 tag 7 ncq 327680 in
res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.04: status: { DRDY }
ata9.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata9.15: exception Emask 0x100 SAct 0x0 SErr 0x600000 action 0x6 frozen
ata9.15: edma_err_cause=02320080 pp_flags=00000007, EDMA self-disable
ata9.15: SError: { BadCRC Handshk }
ata9.00: exception Emask 0x100 SAct 0x11110611 SErr 0x0 action 0x6 frozen
ata9.00: failed command: READ FPDMA QUEUED
ata9.00: cmd 60/08:00:17:de:b8/00:00:01:00:00/40 tag 0 ncq 4096 in
res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.00: status: { DRDY }
ata9.00: failed command: READ FPDMA QUEUED
ata9.00: cmd 60/08:20:1f:de:b8/00:00:01:00:00/40 tag 4 ncq 4096 in
res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.00: status: { DRDY }
ata9.00: failed command: READ FPDMA QUEUED
ata9.00: cmd 60/98:48:7f:da:b8/03:00:01:00:00/40 tag 9 ncq 471040 in
res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.00: status: { DRDY }
ata9.00: failed command: READ FPDMA QUEUED
ata9.00: cmd 60/08:50:27:de:b8/00:00:01:00:00/40 tag 10 ncq 4096 in
res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error)
ata9.00: status: { DRDY }
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: decoding PMP errors with Marvel SATA controller 2011-06-26 7:08 decoding PMP errors with Marvel SATA controller Marc MERLIN @ 2011-06-26 9:03 ` Tejun Heo 2011-06-26 17:38 ` Mark Lord 0 siblings, 1 reply; 23+ messages in thread From: Tejun Heo @ 2011-06-26 9:03 UTC (permalink / raw) To: Marc MERLIN; +Cc: linux-ide, Larry Li, hbailey, mlord (cc'ing Marvell ppl and Mark and quoting whole body for them) On Sun, Jun 26, 2011 at 12:08:20AM -0700, Marc MERLIN wrote: > Howdy > > I have a dual sil PMP which has been working well enough, and recently moved > to a new Motherboard. > > I had to switch my sil3128 to a sil3132 (PCI-X to PCIe) and it seems to work > ok. > I was however trying to switch to a Marvell card that's supposed to be > faster, but I get errors like these on it: > > I think my cables are ok since they work with the sil3132. > I also notice that the real error seems to be with the PMP itself > (ata9.15 SError: { BadCRC Handshk } ) and that the rest is just noise. > > Is my Marvell card somewhat bad or incompatible with my PMP? > > I have 2.6.39.1 > > gargamel kernel: sata_mv 0000:02:00.0: version 1.28 > gargamel kernel: sata_mv 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > gargamel kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx > gargamel kernel: sata_mv 0000:02:00.0: setting latency timer to 64 > gargamel kernel: scsi8 : sata_mv > gargamel kernel: scsi9 : sata_mv > gargamel kernel: scsi10 : sata_mv > gargamel kernel: scsi11 : sata_mv > gargamel kernel: ata9: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb822000 irq 16 > gargamel kernel: ata10: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb824000 irq 16 > gargamel kernel: ata11: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb826000 irq 16 > gargamel kernel: ata12: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb828000 irq 16 > > gargamel kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > gargamel kernel: ata10.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 > > Mmmh, dmesg also shows this (9.15 is my other PMP plugged into the same card): > > Is the card bad, is it possibly a driver issue, or could it still be a sata cable issue? > > kernel: ata9.00: qc timeout (cmd 0xec) > kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) > kernel: ata9.15: hard resetting link > kernel: ata9.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > kernel: ------------[ cut here ]------------ > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() > kernel: Hardware name: System Product Name > kernel: Modules linked in: usbserial pci_hotplug processor thermal_sys wmi parport_pc hwmon button parport r8169 rtc_core snd rtc_lib i2c_i801 xhci_hcd ehci_hcd soundcore sata_mv snd_page_alloc evdev pcspkr iTCO_wdt iTCO_vendor_support intel_agp intel_gtt tpm_tis agpgart usbcore > kernel: Pid: 1642, comm: scsi_eh_8 Not tainted 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > kernel: Call Trace: > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 > kernel: [<f84b150b>] mv_qc_issue+0x441/0x44d [sata_mv] > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 > kernel: [<c014b5bb>] ? up+0x2b/0x2f > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a > kernel: [<f84b0f41>] ? mv_port_start+0x19f/0x19f [sata_mv] > kernel: [<f84b0c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e > kernel: [<f84b0bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 > kernel: [<c012750b>] ? complete+0x34/0x3e > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > kernel: [<c01476c0>] kthread+0x64/0x69 > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd > > This is the error that happens a lot with the sata_mv card, but not the sil24 one: > > ata9.15: exception Emask 0x100 SAct 0x0 SErr 0x600000 action 0x6 frozen > ata9.15: edma_err_cause=02320080 pp_flags=00000007, EDMA self-disable > ata9.15: SError: { BadCRC Handshk } > ata9.00: exception Emask 0x100 SAct 0x2 SErr 0x0 action 0x6 frozen > ata9.00: failed command: READ FPDMA QUEUED > ata9.00: cmd 60/78:08:e7:0f:b8/02:00:01:00:00/40 tag 1 ncq 323584 in > res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.00: status: { DRDY } > ata9.01: exception Emask 0x100 SAct 0x8 SErr 0x0 action 0x6 frozen > ata9.01: failed command: READ FPDMA QUEUED > ata9.01: cmd 60/80:18:df:0f:b8/02:00:01:00:00/40 tag 3 ncq 327680 in > res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.01: status: { DRDY } > ata9.02: exception Emask 0x100 SAct 0x1 SErr 0x0 action 0x6 frozen > ata9.02: failed command: READ FPDMA QUEUED > ata9.02: cmd 60/80:00:df:0f:b8/02:00:01:00:00/40 tag 0 ncq 327680 in > res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.02: status: { DRDY } > ata9.03: exception Emask 0x100 SAct 0x74 SErr 0x0 action 0x6 frozen > ata9.03: failed command: WRITE FPDMA QUEUED > ata9.03: cmd 61/08:10:d7:0f:b8/00:00:01:00:00/40 tag 2 ncq 4096 out > res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.03: status: { DRDY } > ata9.03: failed command: WRITE FPDMA QUEUED > ata9.03: cmd 61/88:20:3f:0c:b8/03:00:01:00:00/40 tag 4 ncq 462848 out > res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.03: status: { DRDY } > ata9.03: failed command: WRITE FPDMA QUEUED > ata9.03: cmd 61/08:28:c7:0f:b8/00:00:01:00:00/40 tag 5 ncq 4096 out > res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.03: status: { DRDY } > ata9.03: failed command: WRITE FPDMA QUEUED > ata9.03: cmd 61/08:30:cf:0f:b8/00:00:01:00:00/40 tag 6 ncq 4096 out > res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.03: status: { DRDY } > ata9.04: exception Emask 0x100 SAct 0x80 SErr 0x0 action 0x6 frozen > ata9.04: failed command: READ FPDMA QUEUED > ata9.04: cmd 60/80:38:df:0f:b8/02:00:01:00:00/40 tag 7 ncq 327680 in > res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.04: status: { DRDY } > ata9.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen > ata9.15: exception Emask 0x100 SAct 0x0 SErr 0x600000 action 0x6 frozen > ata9.15: edma_err_cause=02320080 pp_flags=00000007, EDMA self-disable > ata9.15: SError: { BadCRC Handshk } > ata9.00: exception Emask 0x100 SAct 0x11110611 SErr 0x0 action 0x6 frozen > ata9.00: failed command: READ FPDMA QUEUED > ata9.00: cmd 60/08:00:17:de:b8/00:00:01:00:00/40 tag 0 ncq 4096 in > res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.00: status: { DRDY } > ata9.00: failed command: READ FPDMA QUEUED > ata9.00: cmd 60/08:20:1f:de:b8/00:00:01:00:00/40 tag 4 ncq 4096 in > res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.00: status: { DRDY } > ata9.00: failed command: READ FPDMA QUEUED > ata9.00: cmd 60/98:48:7f:da:b8/03:00:01:00:00/40 tag 9 ncq 471040 in > res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.00: status: { DRDY } > ata9.00: failed command: READ FPDMA QUEUED > ata9.00: cmd 60/08:50:27:de:b8/00:00:01:00:00/40 tag 10 ncq 4096 in > res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) > ata9.00: status: { DRDY } This sounds a lot like another recent PMP problem we had with marvell. It could be that FIS-based switching doesn't work quite as well for some reason. Thanks. -- tejun ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: decoding PMP errors with Marvel SATA controller 2011-06-26 9:03 ` Tejun Heo @ 2011-06-26 17:38 ` Mark Lord 2011-06-27 0:06 ` Marc MERLIN 2011-06-29 3:41 ` Marc MERLIN 0 siblings, 2 replies; 23+ messages in thread From: Mark Lord @ 2011-06-26 17:38 UTC (permalink / raw) To: Tejun Heo; +Cc: Marc MERLIN, linux-ide, Larry Li, hbailey On 11-06-26 05:03 AM, Tejun Heo wrote: > (cc'ing Marvell ppl and Mark and quoting whole body for them) > > On Sun, Jun 26, 2011 at 12:08:20AM -0700, Marc MERLIN wrote: >> Howdy >> >> I have a dual sil PMP which has been working well enough, and recently moved >> to a new Motherboard. >> >> I had to switch my sil3128 to a sil3132 (PCI-X to PCIe) and it seems to work >> ok. >> I was however trying to switch to a Marvell card that's supposed to be >> faster, but I get errors like these on it: >> >> I think my cables are ok since they work with the sil3132. >> I also notice that the real error seems to be with the PMP itself >> (ata9.15 SError: { BadCRC Handshk } ) and that the rest is just noise. >> >> Is my Marvell card somewhat bad or incompatible with my PMP? >> >> I have 2.6.39.1 >> >> gargamel kernel: sata_mv 0000:02:00.0: version 1.28 >> gargamel kernel: sata_mv 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 >> gargamel kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx >> gargamel kernel: sata_mv 0000:02:00.0: setting latency timer to 64 >> gargamel kernel: scsi8 : sata_mv >> gargamel kernel: scsi9 : sata_mv >> gargamel kernel: scsi10 : sata_mv >> gargamel kernel: scsi11 : sata_mv >> gargamel kernel: ata9: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb822000 irq 16 >> gargamel kernel: ata10: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb824000 irq 16 >> gargamel kernel: ata11: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb826000 irq 16 >> gargamel kernel: ata12: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb828000 irq 16 >> >> gargamel kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> gargamel kernel: ata10.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 >> >> Mmmh, dmesg also shows this (9.15 is my other PMP plugged into the same card): >> >> Is the card bad, is it possibly a driver issue, or could it still be a sata cable issue? >> >> kernel: ata9.00: qc timeout (cmd 0xec) >> kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) >> kernel: ata9.15: hard resetting link >> kernel: ata9.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> kernel: ------------[ cut here ]------------ >> kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() >> kernel: Hardware name: System Product Name >> kernel: Modules linked in: usbserial pci_hotplug processor thermal_sys wmi parport_pc hwmon button parport r8169 rtc_core snd rtc_lib i2c_i801 xhci_hcd ehci_hcd soundcore sata_mv snd_page_alloc evdev pcspkr iTCO_wdt iTCO_vendor_support intel_agp intel_gtt tpm_tis agpgart usbcore >> kernel: Pid: 1642, comm: scsi_eh_8 Not tainted 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 >> kernel: Call Trace: >> kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 >> kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 >> kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 >> kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d >> kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 >> kernel: [<f84b150b>] mv_qc_issue+0x441/0x44d [sata_mv] >> kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 >> kernel: [<c014b5bb>] ? up+0x2b/0x2f >> kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 >> kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 >> kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde >> kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 >> kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 >> kernel: [<c037213a>] sata_pmp_read+0x66/0x9d >> kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 >> kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 >> kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 >> kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 >> kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a >> kernel: [<f84b0f41>] ? mv_port_start+0x19f/0x19f [sata_mv] >> kernel: [<f84b0c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] >> kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 >> kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa >> kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e >> kernel: [<f84b0bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] >> kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 >> kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd >> kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f >> kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d >> kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 >> kernel: [<c012750b>] ? complete+0x34/0x3e >> kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d >> kernel: [<c01476c0>] kthread+0x64/0x69 >> kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 >> kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd >> >> This is the error that happens a lot with the sata_mv card, but not the sil24 one: >> >> ata9.15: exception Emask 0x100 SAct 0x0 SErr 0x600000 action 0x6 frozen >> ata9.15: edma_err_cause=02320080 pp_flags=00000007, EDMA self-disable >> ata9.15: SError: { BadCRC Handshk } >> ata9.00: exception Emask 0x100 SAct 0x2 SErr 0x0 action 0x6 frozen >> ata9.00: failed command: READ FPDMA QUEUED >> ata9.00: cmd 60/78:08:e7:0f:b8/02:00:01:00:00/40 tag 1 ncq 323584 in >> res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.00: status: { DRDY } >> ata9.01: exception Emask 0x100 SAct 0x8 SErr 0x0 action 0x6 frozen >> ata9.01: failed command: READ FPDMA QUEUED >> ata9.01: cmd 60/80:18:df:0f:b8/02:00:01:00:00/40 tag 3 ncq 327680 in >> res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.01: status: { DRDY } >> ata9.02: exception Emask 0x100 SAct 0x1 SErr 0x0 action 0x6 frozen >> ata9.02: failed command: READ FPDMA QUEUED >> ata9.02: cmd 60/80:00:df:0f:b8/02:00:01:00:00/40 tag 0 ncq 327680 in >> res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.02: status: { DRDY } >> ata9.03: exception Emask 0x100 SAct 0x74 SErr 0x0 action 0x6 frozen >> ata9.03: failed command: WRITE FPDMA QUEUED >> ata9.03: cmd 61/08:10:d7:0f:b8/00:00:01:00:00/40 tag 2 ncq 4096 out >> res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.03: status: { DRDY } >> ata9.03: failed command: WRITE FPDMA QUEUED >> ata9.03: cmd 61/88:20:3f:0c:b8/03:00:01:00:00/40 tag 4 ncq 462848 out >> res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.03: status: { DRDY } >> ata9.03: failed command: WRITE FPDMA QUEUED >> ata9.03: cmd 61/08:28:c7:0f:b8/00:00:01:00:00/40 tag 5 ncq 4096 out >> res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.03: status: { DRDY } >> ata9.03: failed command: WRITE FPDMA QUEUED >> ata9.03: cmd 61/08:30:cf:0f:b8/00:00:01:00:00/40 tag 6 ncq 4096 out >> res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.03: status: { DRDY } >> ata9.04: exception Emask 0x100 SAct 0x80 SErr 0x0 action 0x6 frozen >> ata9.04: failed command: READ FPDMA QUEUED >> ata9.04: cmd 60/80:38:df:0f:b8/02:00:01:00:00/40 tag 7 ncq 327680 in >> res 40/00:2c:c7:0f:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.04: status: { DRDY } >> ata9.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen >> ata9.15: exception Emask 0x100 SAct 0x0 SErr 0x600000 action 0x6 frozen >> ata9.15: edma_err_cause=02320080 pp_flags=00000007, EDMA self-disable >> ata9.15: SError: { BadCRC Handshk } >> ata9.00: exception Emask 0x100 SAct 0x11110611 SErr 0x0 action 0x6 frozen >> ata9.00: failed command: READ FPDMA QUEUED >> ata9.00: cmd 60/08:00:17:de:b8/00:00:01:00:00/40 tag 0 ncq 4096 in >> res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.00: status: { DRDY } >> ata9.00: failed command: READ FPDMA QUEUED >> ata9.00: cmd 60/08:20:1f:de:b8/00:00:01:00:00/40 tag 4 ncq 4096 in >> res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.00: status: { DRDY } >> ata9.00: failed command: READ FPDMA QUEUED >> ata9.00: cmd 60/98:48:7f:da:b8/03:00:01:00:00/40 tag 9 ncq 471040 in >> res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.00: status: { DRDY } >> ata9.00: failed command: READ FPDMA QUEUED >> ata9.00: cmd 60/08:50:27:de:b8/00:00:01:00:00/40 tag 10 ncq 4096 in >> res 40/00:1c:6f:da:b8/00:00:01:00:00/40 Emask 0x100 (unknown error) >> ata9.00: status: { DRDY } > > This sounds a lot like another recent PMP problem we had with marvell. > It could be that FIS-based switching doesn't work quite as well for > some reason. This all *used* to work with sata_mv. But I also recently noticed my sata_mv cards no longer work with the 4-port Marvell PMP here, and that combo definitely did work when I finished with it all (back around 2.6.29 or so). Since sata_mv itself hasn't changed (much) since then, the problem is likely in the libata core somewhere. I'd guess that maybe in the reset/probe code. I'm rather distracted here right now with broken internet connectivity, and hunting for new providers etc., so not likely to dig around on it. Perhaps Marc MERLIN could retest with an older kernel, say 2.6.32 or 2.6.29 even, and see what happens with those. Hopefully it will work there for him, and we'll have a starting point to bisect the issue. Cheers -- Mark Lord Real-Time Remedies Inc. mlord@pobox.com ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: decoding PMP errors with Marvel SATA controller 2011-06-26 17:38 ` Mark Lord @ 2011-06-27 0:06 ` Marc MERLIN 2011-06-27 1:29 ` Mark Lord 2011-06-29 3:41 ` Marc MERLIN 1 sibling, 1 reply; 23+ messages in thread From: Marc MERLIN @ 2011-06-27 0:06 UTC (permalink / raw) To: Mark Lord; +Cc: Tejun Heo, linux-ide, Larry Li, hbailey Speaking of which, what sata chips are recommended nowadays for PMP outside sil24 cards? On Sun, Jun 26, 2011 at 01:38:38PM -0400, Mark Lord wrote: > > This sounds a lot like another recent PMP problem we had with marvell. > > It could be that FIS-based switching doesn't work quite as well for > > some reason. > > This all *used* to work with sata_mv. > But I also recently noticed my sata_mv cards no longer work with the > 4-port Marvell PMP here, and that combo definitely did work when I > finished with it all (back around 2.6.29 or so). I also used it but it was back 2-3 years ago now. I think it even worked back in 2.6.18. > I'm rather distracted here right now with broken internet connectivity, > and hunting for new providers etc., so not likely to dig around on it. > > Perhaps Marc MERLIN could retest with an older kernel, > say 2.6.32 or 2.6.29 even, and see what happens with those. > Hopefully it will work there for him, and we'll have a starting > point to bisect the issue. So it's a bit difficult for me to get too much data on this since it's a production system and downtime does come at somewhat of a premium. However, if whoever may be able to work on it and see what broke (because it almost works, I see all the drives on my PMP and I can read data somewhat, I just get a lot of somewhat scary errors now) lets me know, if he/she has no way to test him/herself, I'll see what I can do to help out and get to replicate this with older kernels on either that server, or maybe another machine I would have to build for it (trying repeatedly on production data, even with backups, not so good :) ). Thanks for the answer, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: decoding PMP errors with Marvel SATA controller 2011-06-27 0:06 ` Marc MERLIN @ 2011-06-27 1:29 ` Mark Lord 2011-06-27 1:58 ` Hubert Bailey 0 siblings, 1 reply; 23+ messages in thread From: Mark Lord @ 2011-06-27 1:29 UTC (permalink / raw) To: Marc MERLIN; +Cc: Tejun Heo, linux-ide, Larry Li, hbailey On 11-06-26 08:06 PM, Marc MERLIN wrote: > Speaking of which, what sata chips are recommended nowadays for PMP outside > sil24 cards? Well, sata_mv cards were once *the* best cards going for PMP. Nowadays though, none of the chipsets I have here work with all of the PMPs I have here. JMicron are the most common eSATA chips on motherboards, but even they have PMP troubles with Linux (but not with Windows). So.. dunno. -- Mark Lord Real-Time Remedies Inc. mlord@pobox.com ^ permalink raw reply [flat|nested] 23+ messages in thread
* RE: decoding PMP errors with Marvel SATA controller 2011-06-27 1:29 ` Mark Lord @ 2011-06-27 1:58 ` Hubert Bailey 2011-07-06 20:55 ` Tim Small 0 siblings, 1 reply; 23+ messages in thread From: Hubert Bailey @ 2011-06-27 1:58 UTC (permalink / raw) To: 'Mark Lord', Marc MERLIN Cc: Tejun Heo, linux-ide@vger.kernel.org, Larry Li Mark, Typically the biggest issues are with the PMPs that have internal RAID controllers. These parts do not follow the SATA spec when they are not in RAID mode. -----Original Message----- From: Mark Lord [mailto:mlord@pobox.com] Sent: Sunday, June 26, 2011 8:29 PM To: Marc MERLIN Cc: Tejun Heo; linux-ide@vger.kernel.org; Larry Li; Hubert Bailey Subject: Re: decoding PMP errors with Marvel SATA controller On 11-06-26 08:06 PM, Marc MERLIN wrote: > Speaking of which, what sata chips are recommended nowadays for PMP > outside > sil24 cards? Well, sata_mv cards were once *the* best cards going for PMP. Nowadays though, none of the chipsets I have here work with all of the PMPs I have here. JMicron are the most common eSATA chips on motherboards, but even they have PMP troubles with Linux (but not with Windows). So.. dunno. -- Mark Lord Real-Time Remedies Inc. mlord@pobox.com ----- No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1388 / Virus Database: 1513/3728 - Release Date: 06/26/11 ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: decoding PMP errors with Marvel SATA controller 2011-06-27 1:58 ` Hubert Bailey @ 2011-07-06 20:55 ` Tim Small 0 siblings, 0 replies; 23+ messages in thread From: Tim Small @ 2011-07-06 20:55 UTC (permalink / raw) To: Hubert Bailey Cc: 'Mark Lord', Marc MERLIN, Tejun Heo, linux-ide@vger.kernel.org, Larry Li On 27/06/11 02:58, Hubert Bailey wrote: > Typically the biggest issues are with the PMPs that have internal RAID controllers. These parts do not follow the SATA spec when they are not in RAID mode. > FWIW, the errors and performance issues which I have been seeing with the 88SE91xx are with a SiI 3726 - which is AFAIK the most common PMP chip, and has no RAID features... Cheers, Tim. -- South East Open Source Solutions Limited Registered in England and Wales with company number 06134732. Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309 ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: decoding PMP errors with Marvel SATA controller 2011-06-26 17:38 ` Mark Lord 2011-06-27 0:06 ` Marc MERLIN @ 2011-06-29 3:41 ` Marc MERLIN 2011-06-29 3:53 ` Mark Lord 1 sibling, 1 reply; 23+ messages in thread From: Marc MERLIN @ 2011-06-29 3:41 UTC (permalink / raw) To: Mark Lord; +Cc: Tejun Heo, linux-ide, Larry Li, hbailey On Sun, Jun 26, 2011 at 01:38:38PM -0400, Mark Lord wrote: > This all *used* to work with sata_mv. > But I also recently noticed my sata_mv cards no longer > work with the 4-port Marvell PMP here, and that combo > definitely did work when I finished with it all > (back around 2.6.29 or so). > > Since sata_mv itself hasn't changed (much) since then, > the problem is likely in the libata core somewhere. > I'd guess that maybe in the reset/probe code. > > I'm rather distracted here right now with broken internet connectivity, > and hunting for new providers etc., so not likely to dig around on it. > > Perhaps Marc MERLIN could retest with an older kernel, Well, I don't know what to say. A friend lent me another sata_mv card and just to get another baseline I tried my original card again, and it just started working. Yet, I tried it 4 different times before, moved it from one slot to the other one, changed the sata cables just in case, and nothing would help. The one thing I did since last time, however, was to update the motherboard bios. I'm now wondering if that did not solve some subtle problem which was causing issues with the sata_mv card and not the sata_sil24. So it seems it was a false alarm after all, I'll report back if I have problems again, but it looks like it's working solidly and for what it's worth with 5 drives and software raid 5, I can both read and write files at about 115MB/s, which isn't too shabby :) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: decoding PMP errors with Marvel SATA controller 2011-06-29 3:41 ` Marc MERLIN @ 2011-06-29 3:53 ` Mark Lord 2011-06-29 5:03 ` Marc MERLIN 0 siblings, 1 reply; 23+ messages in thread From: Mark Lord @ 2011-06-29 3:53 UTC (permalink / raw) To: Marc MERLIN; +Cc: Tejun Heo, linux-ide, Larry Li, hbailey On 11-06-28 11:41 PM, Marc MERLIN wrote: .. > So it seems it was a false alarm after all, I'll report back if I have > problems again, but it looks like it's working solidly and for what it's > worth with 5 drives and software raid 5, I can both read and write files > at about 115MB/s, which isn't too shabby :) Mmm.. power everything OFF, wait a few seconds, then power on and verify that it all still works. Thanks -- Mark Lord Real-Time Remedies Inc. mlord@pobox.com ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: decoding PMP errors with Marvel SATA controller 2011-06-29 3:53 ` Mark Lord @ 2011-06-29 5:03 ` Marc MERLIN 2011-06-29 15:07 ` sata_mv WARNING: at drivers/ata/libata-sff.c:1322 Marc MERLIN 0 siblings, 1 reply; 23+ messages in thread From: Marc MERLIN @ 2011-06-29 5:03 UTC (permalink / raw) To: Mark Lord; +Cc: Tejun Heo, linux-ide, Larry Li, hbailey On Tue, Jun 28, 2011 at 11:53:37PM -0400, Mark Lord wrote: > On 11-06-28 11:41 PM, Marc MERLIN wrote: > .. > > So it seems it was a false alarm after all, I'll report back if I have > > problems again, but it looks like it's working solidly and for what it's > > worth with 5 drives and software raid 5, I can both read and write files > > at about 115MB/s, which isn't too shabby :) > > Mmm.. power everything OFF, wait a few seconds, > then power on and verify that it all still works. Yep, it does (even powered off the power supply to the MB that isn't truly off otherwise). I've backed away slowly, sealed the cabinet it's in, and will leave things running :) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: sata_mv WARNING: at drivers/ata/libata-sff.c:1322 2011-06-29 5:03 ` Marc MERLIN @ 2011-06-29 15:07 ` Marc MERLIN 2011-06-29 16:03 ` Mark Lord 0 siblings, 1 reply; 23+ messages in thread From: Marc MERLIN @ 2011-06-29 15:07 UTC (permalink / raw) To: Mark Lord; +Cc: Tejun Heo, linux-ide, Larry Li, hbailey On Tue, Jun 28, 2011 at 10:03:41PM -0700, Marc MERLIN wrote: > On Tue, Jun 28, 2011 at 11:53:37PM -0400, Mark Lord wrote: > > On 11-06-28 11:41 PM, Marc MERLIN wrote: > > .. > > > So it seems it was a false alarm after all, I'll report back if I have > > > problems again, but it looks like it's working solidly and for what it's > > > worth with 5 drives and software raid 5, I can both read and write files > > > at about 115MB/s, which isn't too shabby :) > > > > Mmm.. power everything OFF, wait a few seconds, > > then power on and verify that it all still works. > > Yep, it does (even powered off the power supply to the MB that isn't truly > off otherwise). Mmh, although the card works fine now, I did notice 3 libata-sff errors in my boot log. Once boot is finished, there are no more errors. The card is: 02:00.0 SCSI storage controller: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II (rev 02) >From the errors, should I try swapping the card considering it otherwise works fine after boot, or is the problem elsewhere? Can the 3 warnings just be ignored, or are they important? So I suppose this is also why my kernel gets tainted? kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 kernel: sata_mv 0000:02:00.0: version 1.28 kernel: sata_mv 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx kernel: sata_mv 0000:02:00.0: setting latency timer to 64 kernel: scsi8 : sata_mv kernel: scsi9 : sata_mv kernel: scsi10 : sata_mv kernel: scsi11 : sata_mv kernel: ata9: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb822000 irq 16 kernel: ata10: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb824000 irq 16 kernel: ata11: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb826000 irq 16 kernel: ata12: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb828000 irq 16 kernel: ata9: SATA link down (SStatus 0 SControl 300) kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) kernel: ata10.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 kernel: ata10.00: hard resetting link kernel: ata10.01: hard resetting link kernel: ata10.01: link resume succeeded after 1 retries kernel: ata10.02: hard resetting link kernel: ata10.02: link resume succeeded after 1 retries kernel: ata10.03: hard resetting link kernel: ata10.03: link resume succeeded after 1 retries kernel: ata10.04: hard resetting link kernel: ata10.05: hard resetting link kernel: ata10.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 kernel: ata10.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata10.00: configured for UDMA/133 kernel: ata10.01: qc timeout (cmd 0x27) kernel: ata10.01: failed to read native max address (err_mask=0x4) kernel: ata10.01: HPA support seems broken, skipping HPA handling kernel: ata10.15: hard resetting link kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) kernel: ------------[ cut here ]------------ kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() kernel: Hardware name: System Product Name kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore kernel: Pid: 1636, comm: scsi_eh_9 Not tainted 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 kernel: Call Trace: kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 kernel: [<c014b5bb>] ? up+0x2b/0x2f kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 kernel: [<c037213a>] sata_pmp_read+0x66/0x9d kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 kernel: [<c012750b>] ? complete+0x34/0x3e kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d kernel: [<c01476c0>] kthread+0x64/0x69 kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd kernel: ---[ end trace cdcd2b0b3f6829ed ]--- kernel: ata10.00: hard resetting link kernel: ata10.01: hard resetting link kernel: ata10.01: link resume succeeded after 1 retries kernel: ata10.02: hard resetting link kernel: ata10.02: link resume succeeded after 1 retries kernel: ata10.03: hard resetting link kernel: ata10.03: link resume succeeded after 1 retries kernel: ata10.04: hard resetting link kernel: ata10.04: link resume succeeded after 1 retries kernel: ata10.05: hard resetting link kernel: ata10.00: configured for UDMA/133 kernel: ata10.01: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 kernel: ata10.01: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata10.01: configured for UDMA/133 kernel: ata10.02: qc timeout (cmd 0x27) kernel: ata10.02: failed to read native max address (err_mask=0x4) kernel: ata10.02: HPA support seems broken, skipping HPA handling kernel: ata10.15: hard resetting link kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) kernel: ------------[ cut here ]------------ kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() kernel: Hardware name: System Product Name kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 kernel: Call Trace: kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 kernel: [<c014b5bb>] ? up+0x2b/0x2f kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 kernel: [<c037213a>] sata_pmp_read+0x66/0x9d kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 kernel: [<c012750b>] ? complete+0x34/0x3e kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d kernel: [<c01476c0>] kthread+0x64/0x69 kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd kernel: ---[ end trace cdcd2b0b3f6829ee ]--- kernel: ata10.00: hard resetting link kernel: ata10.01: hard resetting link kernel: ata10.01: link resume succeeded after 1 retries kernel: ata10.02: hard resetting link kernel: ata10.02: link resume succeeded after 1 retries kernel: ata10.03: hard resetting link kernel: ata10.03: link resume succeeded after 1 retries kernel: ata10.04: hard resetting link kernel: ata10.04: link resume succeeded after 1 retries kernel: ata10.05: hard resetting link kernel: ata10.00: configured for UDMA/133 kernel: ata10.01: configured for UDMA/133 kernel: ata10.02: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 kernel: ata10.02: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata10.02: configured for UDMA/133 kernel: ata10.03: qc timeout (cmd 0x27) kernel: ata10.03: failed to read native max address (err_mask=0x4) kernel: ata10.03: HPA support seems broken, skipping HPA handling kernel: ata10.15: hard resetting link kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) kernel: ------------[ cut here ]------------ kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() kernel: Hardware name: System Product Name kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 kernel: Call Trace: kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 kernel: [<c014b5bb>] ? up+0x2b/0x2f kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 kernel: [<c037213a>] sata_pmp_read+0x66/0x9d kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 kernel: [<c012750b>] ? complete+0x34/0x3e kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d kernel: [<c01476c0>] kthread+0x64/0x69 kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd kernel: ---[ end trace cdcd2b0b3f6829ef ]--- kernel: ata10.00: hard resetting link kernel: ata10.01: hard resetting link kernel: ata10.01: link resume succeeded after 1 retries kernel: ata10.02: hard resetting link kernel: ata10.02: link resume succeeded after 1 retries kernel: ata10.03: hard resetting link kernel: ata10.03: link resume succeeded after 1 retries kernel: ata10.04: hard resetting link kernel: ata10.04: link resume succeeded after 1 retries kernel: ata10.05: hard resetting link kernel: ata10.00: configured for UDMA/133 kernel: ata10.01: configured for UDMA/133 kernel: ata10.02: configured for UDMA/133 kernel: ata10.03: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 kernel: ata10.03: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata10.03: configured for UDMA/133 kernel: ata10.04: ATA-7: ST3750640AS, 3.AAK, max UDMA/133 kernel: ata10.04: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata10.04: configured for UDMA/133 kernel: ata10: EH complete kernel: scsi 9:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 kernel: sd 9:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB) kernel: sd 9:0:0:0: [sdc] Write Protect is off kernel: sd 9:0:0:0: [sdc] Mode Sense: 00 3a 00 00 kernel: sd 9:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: scsi 9:1:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 kernel: sd 9:1:0:0: [sdd] 976773168 512-byte logical blocks: (500 GB/465 GiB) kernel: sd 9:1:0:0: [sdd] Write Protect is off kernel: sd 9:1:0:0: [sdd] Mode Sense: 00 3a 00 00 kernel: sd 9:1:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: scsi 9:2:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 kernel: sd 9:2:0:0: [sde] 976773168 512-byte logical blocks: (500 GB/465 GiB) kernel: sd 9:2:0:0: [sde] Write Protect is off kernel: sd 9:2:0:0: [sde] Mode Sense: 00 3a 00 00 kernel: sd 9:2:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: scsi 9:3:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 kernel: sd 9:3:0:0: [sdf] 976773168 512-byte logical blocks: (500 GB/465 GiB) kernel: sd 9:3:0:0: [sdf] Write Protect is off kernel: sd 9:3:0:0: [sdf] Mode Sense: 00 3a 00 00 kernel: sd 9:3:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: scsi 9:4:0:0: Direct-Access ATA ST3750640AS 3.AA PQ: 0 ANSI: 5 kernel: sd 9:4:0:0: [sdg] 1465149168 512-byte logical blocks: (750 GB/698 GiB) kernel: sd 9:4:0:0: [sdg] Write Protect is off kernel: sd 9:4:0:0: [sdg] Mode Sense: 00 3a 00 00 kernel: sd 9:4:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: sdc: sdc1 kernel: sd 9:0:0:0: [sdc] Attached SCSI disk kernel: sdg: sdg1 sdg2 kernel: sd 9:4:0:0: [sdg] Attached SCSI disk kernel: sdd: sdd1 kernel: sd 9:1:0:0: [sdd] Attached SCSI disk kernel: sde: sde1 kernel: sdf: sdf1 kernel: sd 9:2:0:0: [sde] Attached SCSI disk kernel: sd 9:3:0:0: [sdf] Attached SCSI disk kernel: ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300) kernel: ata11.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 kernel: ata11.00: hard resetting link kernel: ata11.01: hard resetting link kernel: ata11.02: hard resetting link kernel: ata11.03: hard resetting link kernel: ata11.04: hard resetting link kernel: ata11.05: hard resetting link kernel: ata11.00: ATA-8: WDC WD20EADS-00W4B0, 01.00A01, max UDMA/133 kernel: ata11.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata11.00: configured for Uel kernel: ata11.02: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 kernel: ata11.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata11.02: configured for UDMA/133 kernel: ata11.03: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 kernel: ata11.03: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata11.03: configured for UDMA/133 kernel: ata11.04: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133 kernel: ata11.04: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) kernel: ata11.04: configured for UDMA/133 kernel: ata11: EH complete kernel: scsi 10:0:0:0: Direct-Access ATA WDC WD20EADS-00W 01.0 PQ: 0 ANSI: 5 kernel: sd 10:0:0:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) kernel: sd 10:0:0:0: [sdh] Write Protect is off kernel: sd 10:0:0:0: [sdh] Mode Sense: 00 3a 00 00 kernel: sd 10:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: scsi 10:1:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 kernel: sd 10:1:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) kernel: sd 10:1:0:0: [sdi] Write Protect is off kernel: sd 10:1:0:0: [sdi] Mode Sense: 00 3a 00 00 kernel: sd 10:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: scsi 10:2:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 kernel: sd 10:2:0:0: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) kernel: sd 10:2:0:0: [sdj] Write Protect is off kernel: sd 10:2:0:0: [sdj] Mode Sense: 00 3a 00 00 kernel: sd 10:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: scsi 10:3:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 kernel: sd 10:3:0:0: [sdk] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) kernel: sd 10:3:0:0: [sdk] Write Protect is off kernel: sd 10:3:0:0: [sdk] Mode Sense: 00 3a 00 00 kernel: sd 10:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: scsi 10:4:0:0: Direct-Access ATA WDC WD20EADS-00S 01.0 PQ: 0 ANSI: 5 kernel: sd 10:4:0:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) kernel: sd 10:4:0:0: [sdl] Write Protect is off kernel: sd 10:4:0:0: [sdl] Mode Sense: 00 3a 00 00 kernel: sd 10:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: sdi: sdi1 kernel: sd 10:1:0:0: [sdi] Attached SCSI disk kernel: sdk: sdk1 kernel: sd 10:3:0:0: [sdk] Attached SCSI disk kernel: sdl: sdl1 kernel: sd 10:4:0:0: [sdl] Attached SCSI disk kernel: sdj: sdj1 kernel: sd 10:2:0:0: [sdj] Attached SCSI disk kernel: ata12: SATA link down (SStatus 0 SControl 300) kernel: sdh: sdh1 kernel: sd 10:0:0:0: [sdh] Attached SCSI disk -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: sata_mv WARNING: at drivers/ata/libata-sff.c:1322 2011-06-29 15:07 ` sata_mv WARNING: at drivers/ata/libata-sff.c:1322 Marc MERLIN @ 2011-06-29 16:03 ` Mark Lord 2011-07-12 14:29 ` Tejun Heo 0 siblings, 1 reply; 23+ messages in thread From: Mark Lord @ 2011-06-29 16:03 UTC (permalink / raw) To: Marc MERLIN; +Cc: Tejun Heo, linux-ide, Larry Li, hbailey On 11-06-29 11:07 AM, Marc MERLIN wrote: > On Tue, Jun 28, 2011 at 10:03:41PM -0700, Marc MERLIN wrote: >> On Tue, Jun 28, 2011 at 11:53:37PM -0400, Mark Lord wrote: >>> On 11-06-28 11:41 PM, Marc MERLIN wrote: >>> .. >>>> So it seems it was a false alarm after all, I'll report back if I have >>>> problems again, but it looks like it's working solidly and for what it's >>>> worth with 5 drives and software raid 5, I can both read and write files >>>> at about 115MB/s, which isn't too shabby :) >>> >>> Mmm.. power everything OFF, wait a few seconds, >>> then power on and verify that it all still works. >> >> Yep, it does (even powered off the power supply to the MB that isn't truly >> off otherwise). > > Mmh, although the card works fine now, I did notice 3 libata-sff errors > in my boot log. > Once boot is finished, there are no more errors. > > The card is: > 02:00.0 SCSI storage controller: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II (rev 02) > >>From the errors, should I try swapping the card considering it otherwise > works fine after boot, or is the problem elsewhere? > Can the 3 warnings just be ignored, or are they important? > > So I suppose this is also why my kernel gets tainted? > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > > kernel: sata_mv 0000:02:00.0: version 1.28 > kernel: sata_mv 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx > kernel: sata_mv 0000:02:00.0: setting latency timer to 64 > kernel: scsi8 : sata_mv > kernel: scsi9 : sata_mv > kernel: scsi10 : sata_mv > kernel: scsi11 : sata_mv > kernel: ata9: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb822000 irq 16 > kernel: ata10: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb824000 irq 16 > kernel: ata11: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb826000 irq 16 > kernel: ata12: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb828000 irq 16 > kernel: ata9: SATA link down (SStatus 0 SControl 300) > kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > kernel: ata10.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 > kernel: ata10.00: hard resetting link > kernel: ata10.01: hard resetting link > kernel: ata10.01: link resume succeeded after 1 retries > kernel: ata10.02: hard resetting link > kernel: ata10.02: link resume succeeded after 1 retries > kernel: ata10.03: hard resetting link > kernel: ata10.03: link resume succeeded after 1 retries > kernel: ata10.04: hard resetting link > kernel: ata10.05: hard resetting link > kernel: ata10.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 > kernel: ata10.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata10.00: configured for UDMA/133 > kernel: ata10.01: qc timeout (cmd 0x27) > kernel: ata10.01: failed to read native max address (err_mask=0x4) > kernel: ata10.01: HPA support seems broken, skipping HPA handling > kernel: ata10.15: hard resetting link > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > kernel: ------------[ cut here ]------------ > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() > kernel: Hardware name: System Product Name > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore > kernel: Pid: 1636, comm: scsi_eh_9 Not tainted 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > kernel: Call Trace: > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 > kernel: [<c014b5bb>] ? up+0x2b/0x2f > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 > kernel: [<c012750b>] ? complete+0x34/0x3e > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > kernel: [<c01476c0>] kthread+0x64/0x69 > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd > kernel: ---[ end trace cdcd2b0b3f6829ed ]--- > kernel: ata10.00: hard resetting link > kernel: ata10.01: hard resetting link > kernel: ata10.01: link resume succeeded after 1 retries > kernel: ata10.02: hard resetting link > kernel: ata10.02: link resume succeeded after 1 retries > kernel: ata10.03: hard resetting link > kernel: ata10.03: link resume succeeded after 1 retries > kernel: ata10.04: hard resetting link > kernel: ata10.04: link resume succeeded after 1 retries > kernel: ata10.05: hard resetting link > kernel: ata10.00: configured for UDMA/133 > kernel: ata10.01: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 > kernel: ata10.01: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata10.01: configured for UDMA/133 > kernel: ata10.02: qc timeout (cmd 0x27) > kernel: ata10.02: failed to read native max address (err_mask=0x4) > kernel: ata10.02: HPA support seems broken, skipping HPA handling > kernel: ata10.15: hard resetting link > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > kernel: ------------[ cut here ]------------ > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() > kernel: Hardware name: System Product Name > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > kernel: Call Trace: > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 > kernel: [<c014b5bb>] ? up+0x2b/0x2f > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 > kernel: [<c012750b>] ? complete+0x34/0x3e > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > kernel: [<c01476c0>] kthread+0x64/0x69 > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd > kernel: ---[ end trace cdcd2b0b3f6829ee ]--- > kernel: ata10.00: hard resetting link > kernel: ata10.01: hard resetting link > kernel: ata10.01: link resume succeeded after 1 retries > kernel: ata10.02: hard resetting link > kernel: ata10.02: link resume succeeded after 1 retries > kernel: ata10.03: hard resetting link > kernel: ata10.03: link resume succeeded after 1 retries > kernel: ata10.04: hard resetting link > kernel: ata10.04: link resume succeeded after 1 retries > kernel: ata10.05: hard resetting link > kernel: ata10.00: configured for UDMA/133 > kernel: ata10.01: configured for UDMA/133 > kernel: ata10.02: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 > kernel: ata10.02: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata10.02: configured for UDMA/133 > kernel: ata10.03: qc timeout (cmd 0x27) > kernel: ata10.03: failed to read native max address (err_mask=0x4) > kernel: ata10.03: HPA support seems broken, skipping HPA handling > kernel: ata10.15: hard resetting link > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > kernel: ------------[ cut here ]------------ > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() > kernel: Hardware name: System Product Name > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > kernel: Call Trace: > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 > kernel: [<c014b5bb>] ? up+0x2b/0x2f > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 > kernel: [<c012750b>] ? complete+0x34/0x3e > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > kernel: [<c01476c0>] kthread+0x64/0x69 > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd > kernel: ---[ end trace cdcd2b0b3f6829ef ]--- > kernel: ata10.00: hard resetting link > kernel: ata10.01: hard resetting link > kernel: ata10.01: link resume succeeded after 1 retries > kernel: ata10.02: hard resetting link > kernel: ata10.02: link resume succeeded after 1 retries > kernel: ata10.03: hard resetting link > kernel: ata10.03: link resume succeeded after 1 retries > kernel: ata10.04: hard resetting link > kernel: ata10.04: link resume succeeded after 1 retries > kernel: ata10.05: hard resetting link > kernel: ata10.00: configured for UDMA/133 > kernel: ata10.01: configured for UDMA/133 > kernel: ata10.02: configured for UDMA/133 > kernel: ata10.03: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 > kernel: ata10.03: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata10.03: configured for UDMA/133 > kernel: ata10.04: ATA-7: ST3750640AS, 3.AAK, max UDMA/133 > kernel: ata10.04: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata10.04: configured for UDMA/133 > kernel: ata10: EH complete > kernel: scsi 9:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 > kernel: sd 9:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB) > kernel: sd 9:0:0:0: [sdc] Write Protect is off > kernel: sd 9:0:0:0: [sdc] Mode Sense: 00 3a 00 00 > kernel: sd 9:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: scsi 9:1:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 > kernel: sd 9:1:0:0: [sdd] 976773168 512-byte logical blocks: (500 GB/465 GiB) > kernel: sd 9:1:0:0: [sdd] Write Protect is off > kernel: sd 9:1:0:0: [sdd] Mode Sense: 00 3a 00 00 > kernel: sd 9:1:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: scsi 9:2:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 > kernel: sd 9:2:0:0: [sde] 976773168 512-byte logical blocks: (500 GB/465 GiB) > kernel: sd 9:2:0:0: [sde] Write Protect is off > kernel: sd 9:2:0:0: [sde] Mode Sense: 00 3a 00 00 > kernel: sd 9:2:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: scsi 9:3:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 > kernel: sd 9:3:0:0: [sdf] 976773168 512-byte logical blocks: (500 GB/465 GiB) > kernel: sd 9:3:0:0: [sdf] Write Protect is off > kernel: sd 9:3:0:0: [sdf] Mode Sense: 00 3a 00 00 > kernel: sd 9:3:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: scsi 9:4:0:0: Direct-Access ATA ST3750640AS 3.AA PQ: 0 ANSI: 5 > kernel: sd 9:4:0:0: [sdg] 1465149168 512-byte logical blocks: (750 GB/698 GiB) > kernel: sd 9:4:0:0: [sdg] Write Protect is off > kernel: sd 9:4:0:0: [sdg] Mode Sense: 00 3a 00 00 > kernel: sd 9:4:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: sdc: sdc1 > kernel: sd 9:0:0:0: [sdc] Attached SCSI disk > kernel: sdg: sdg1 sdg2 > kernel: sd 9:4:0:0: [sdg] Attached SCSI disk > kernel: sdd: sdd1 > kernel: sd 9:1:0:0: [sdd] Attached SCSI disk > kernel: sde: sde1 > kernel: sdf: sdf1 > kernel: sd 9:2:0:0: [sde] Attached SCSI disk > kernel: sd 9:3:0:0: [sdf] Attached SCSI disk > kernel: ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > kernel: ata11.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 > kernel: ata11.00: hard resetting link > kernel: ata11.01: hard resetting link > kernel: ata11.02: hard resetting link > kernel: ata11.03: hard resetting link > kernel: ata11.04: hard resetting link > kernel: ata11.05: hard resetting link > kernel: ata11.00: ATA-8: WDC WD20EADS-00W4B0, 01.00A01, max UDMA/133 > kernel: ata11.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata11.00: configured for Uel kernel: ata11.02: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 > kernel: ata11.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata11.02: configured for UDMA/133 > kernel: ata11.03: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 > kernel: ata11.03: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata11.03: configured for UDMA/133 > kernel: ata11.04: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133 > kernel: ata11.04: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) > kernel: ata11.04: configured for UDMA/133 > kernel: ata11: EH complete > kernel: scsi 10:0:0:0: Direct-Access ATA WDC WD20EADS-00W 01.0 PQ: 0 ANSI: 5 > kernel: sd 10:0:0:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > kernel: sd 10:0:0:0: [sdh] Write Protect is off > kernel: sd 10:0:0:0: [sdh] Mode Sense: 00 3a 00 00 > kernel: sd 10:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: scsi 10:1:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 > kernel: sd 10:1:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > kernel: sd 10:1:0:0: [sdi] Write Protect is off > kernel: sd 10:1:0:0: [sdi] Mode Sense: 00 3a 00 00 > kernel: sd 10:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: scsi 10:2:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 > kernel: sd 10:2:0:0: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > kernel: sd 10:2:0:0: [sdj] Write Protect is off > kernel: sd 10:2:0:0: [sdj] Mode Sense: 00 3a 00 00 > kernel: sd 10:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: scsi 10:3:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 > kernel: sd 10:3:0:0: [sdk] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > kernel: sd 10:3:0:0: [sdk] Write Protect is off > kernel: sd 10:3:0:0: [sdk] Mode Sense: 00 3a 00 00 > kernel: sd 10:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: scsi 10:4:0:0: Direct-Access ATA WDC WD20EADS-00S 01.0 PQ: 0 ANSI: 5 > kernel: sd 10:4:0:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > kernel: sd 10:4:0:0: [sdl] Write Protect is off > kernel: sd 10:4:0:0: [sdl] Mode Sense: 00 3a 00 00 > kernel: sd 10:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > kernel: sdi: sdi1 > kernel: sd 10:1:0:0: [sdi] Attached SCSI disk > kernel: sdk: sdk1 > kernel: sd 10:3:0:0: [sdk] Attached SCSI disk > kernel: sdl: sdl1 > kernel: sd 10:4:0:0: [sdl] Attached SCSI disk > kernel: sdj: sdj1 > kernel: sd 10:2:0:0: [sdj] Attached SCSI disk > kernel: ata12: SATA link down (SStatus 0 SControl 300) > kernel: sdh: sdh1 > kernel: sd 10:0:0:0: [sdh] Attached SCSI disk Those WARNINGS are probably harmless right now, so don't panic over them. Not hardware related; more just alerting Tejun to a possible libata bug. cheers -- Mark Lord Real-Time Remedies Inc. mlord@pobox.com ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: sata_mv WARNING: at drivers/ata/libata-sff.c:1322 2011-06-29 16:03 ` Mark Lord @ 2011-07-12 14:29 ` Tejun Heo 2011-07-13 20:54 ` Gwendal Grignou 0 siblings, 1 reply; 23+ messages in thread From: Tejun Heo @ 2011-07-12 14:29 UTC (permalink / raw) To: Mark Lord; +Cc: Gwendal Grignou, Marc MERLIN, linux-ide, Larry Li, hbailey Hello, (cc'ing Gwendal Grignou and quoting whole message for him.) That warning wasn't added by me. It's from ea3c64506ea79 "libata-sff: Reenable Port Multiplier after libata-sff remodeling." Hmmm... I never expected SFF to be used in combination with PMP. Anyways, Gwendal, any ideas? On Wed, Jun 29, 2011 at 12:03:19PM -0400, Mark Lord wrote: > On 11-06-29 11:07 AM, Marc MERLIN wrote: > > On Tue, Jun 28, 2011 at 10:03:41PM -0700, Marc MERLIN wrote: > >> On Tue, Jun 28, 2011 at 11:53:37PM -0400, Mark Lord wrote: > >>> On 11-06-28 11:41 PM, Marc MERLIN wrote: > >>> .. > >>>> So it seems it was a false alarm after all, I'll report back if I have > >>>> problems again, but it looks like it's working solidly and for what it's > >>>> worth with 5 drives and software raid 5, I can both read and write files > >>>> at about 115MB/s, which isn't too shabby :) > >>> > >>> Mmm.. power everything OFF, wait a few seconds, > >>> then power on and verify that it all still works. > >> > >> Yep, it does (even powered off the power supply to the MB that isn't truly > >> off otherwise). > > > > Mmh, although the card works fine now, I did notice 3 libata-sff errors > > in my boot log. > > Once boot is finished, there are no more errors. > > > > The card is: > > 02:00.0 SCSI storage controller: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II (rev 02) > > > >>From the errors, should I try swapping the card considering it otherwise > > works fine after boot, or is the problem elsewhere? > > Can the 3 warnings just be ignored, or are they important? > > > > So I suppose this is also why my kernel gets tainted? > > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > > > > kernel: sata_mv 0000:02:00.0: version 1.28 > > kernel: sata_mv 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > > kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx > > kernel: sata_mv 0000:02:00.0: setting latency timer to 64 > > kernel: scsi8 : sata_mv > > kernel: scsi9 : sata_mv > > kernel: scsi10 : sata_mv > > kernel: scsi11 : sata_mv > > kernel: ata9: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb822000 irq 16 > > kernel: ata10: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb824000 irq 16 > > kernel: ata11: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb826000 irq 16 > > kernel: ata12: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb828000 irq 16 > > kernel: ata9: SATA link down (SStatus 0 SControl 300) > > kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > kernel: ata10.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 > > kernel: ata10.00: hard resetting link > > kernel: ata10.01: hard resetting link > > kernel: ata10.01: link resume succeeded after 1 retries > > kernel: ata10.02: hard resetting link > > kernel: ata10.02: link resume succeeded after 1 retries > > kernel: ata10.03: hard resetting link > > kernel: ata10.03: link resume succeeded after 1 retries > > kernel: ata10.04: hard resetting link > > kernel: ata10.05: hard resetting link > > kernel: ata10.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 > > kernel: ata10.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata10.00: configured for UDMA/133 > > kernel: ata10.01: qc timeout (cmd 0x27) > > kernel: ata10.01: failed to read native max address (err_mask=0x4) > > kernel: ata10.01: HPA support seems broken, skipping HPA handling > > kernel: ata10.15: hard resetting link > > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > kernel: ------------[ cut here ]------------ > > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() > > kernel: Hardware name: System Product Name > > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore > > kernel: Pid: 1636, comm: scsi_eh_9 Not tainted 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > > kernel: Call Trace: > > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 > > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 > > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 > > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d > > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 > > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] > > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 > > kernel: [<c014b5bb>] ? up+0x2b/0x2f > > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 > > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 > > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde > > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 > > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 > > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d > > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 > > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 > > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 > > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a > > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] > > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] > > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa > > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e > > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] > > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 > > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd > > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f > > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 > > kernel: [<c012750b>] ? complete+0x34/0x3e > > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > > kernel: [<c01476c0>] kthread+0x64/0x69 > > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 > > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd > > kernel: ---[ end trace cdcd2b0b3f6829ed ]--- > > kernel: ata10.00: hard resetting link > > kernel: ata10.01: hard resetting link > > kernel: ata10.01: link resume succeeded after 1 retries > > kernel: ata10.02: hard resetting link > > kernel: ata10.02: link resume succeeded after 1 retries > > kernel: ata10.03: hard resetting link > > kernel: ata10.03: link resume succeeded after 1 retries > > kernel: ata10.04: hard resetting link > > kernel: ata10.04: link resume succeeded after 1 retries > > kernel: ata10.05: hard resetting link > > kernel: ata10.00: configured for UDMA/133 > > kernel: ata10.01: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 > > kernel: ata10.01: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata10.01: configured for UDMA/133 > > kernel: ata10.02: qc timeout (cmd 0x27) > > kernel: ata10.02: failed to read native max address (err_mask=0x4) > > kernel: ata10.02: HPA support seems broken, skipping HPA handling > > kernel: ata10.15: hard resetting link > > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > kernel: ------------[ cut here ]------------ > > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() > > kernel: Hardware name: System Product Name > > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore > > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > > kernel: Call Trace: > > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 > > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 > > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 > > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d > > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 > > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] > > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 > > kernel: [<c014b5bb>] ? up+0x2b/0x2f > > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 > > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 > > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde > > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 > > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 > > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d > > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 > > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 > > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 > > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a > > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] > > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] > > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa > > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e > > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] > > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 > > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd > > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f > > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 > > kernel: [<c012750b>] ? complete+0x34/0x3e > > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > > kernel: [<c01476c0>] kthread+0x64/0x69 > > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 > > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd > > kernel: ---[ end trace cdcd2b0b3f6829ee ]--- > > kernel: ata10.00: hard resetting link > > kernel: ata10.01: hard resetting link > > kernel: ata10.01: link resume succeeded after 1 retries > > kernel: ata10.02: hard resetting link > > kernel: ata10.02: link resume succeeded after 1 retries > > kernel: ata10.03: hard resetting link > > kernel: ata10.03: link resume succeeded after 1 retries > > kernel: ata10.04: hard resetting link > > kernel: ata10.04: link resume succeeded after 1 retries > > kernel: ata10.05: hard resetting link > > kernel: ata10.00: configured for UDMA/133 > > kernel: ata10.01: configured for UDMA/133 > > kernel: ata10.02: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 > > kernel: ata10.02: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata10.02: configured for UDMA/133 > > kernel: ata10.03: qc timeout (cmd 0x27) > > kernel: ata10.03: failed to read native max address (err_mask=0x4) > > kernel: ata10.03: HPA support seems broken, skipping HPA handling > > kernel: ata10.15: hard resetting link > > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > kernel: ------------[ cut here ]------------ > > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() > > kernel: Hardware name: System Product Name > > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore > > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 > > kernel: Call Trace: > > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 > > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 > > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 > > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d > > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 > > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] > > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 > > kernel: [<c014b5bb>] ? up+0x2b/0x2f > > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 > > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 > > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde > > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 > > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 > > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d > > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 > > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 > > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 > > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a > > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] > > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] > > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 > > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa > > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e > > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] > > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 > > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd > > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f > > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 > > kernel: [<c012750b>] ? complete+0x34/0x3e > > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d > > kernel: [<c01476c0>] kthread+0x64/0x69 > > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 > > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd > > kernel: ---[ end trace cdcd2b0b3f6829ef ]--- > > kernel: ata10.00: hard resetting link > > kernel: ata10.01: hard resetting link > > kernel: ata10.01: link resume succeeded after 1 retries > > kernel: ata10.02: hard resetting link > > kernel: ata10.02: link resume succeeded after 1 retries > > kernel: ata10.03: hard resetting link > > kernel: ata10.03: link resume succeeded after 1 retries > > kernel: ata10.04: hard resetting link > > kernel: ata10.04: link resume succeeded after 1 retries > > kernel: ata10.05: hard resetting link > > kernel: ata10.00: configured for UDMA/133 > > kernel: ata10.01: configured for UDMA/133 > > kernel: ata10.02: configured for UDMA/133 > > kernel: ata10.03: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 > > kernel: ata10.03: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata10.03: configured for UDMA/133 > > kernel: ata10.04: ATA-7: ST3750640AS, 3.AAK, max UDMA/133 > > kernel: ata10.04: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata10.04: configured for UDMA/133 > > kernel: ata10: EH complete > > kernel: scsi 9:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 > > kernel: sd 9:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB) > > kernel: sd 9:0:0:0: [sdc] Write Protect is off > > kernel: sd 9:0:0:0: [sdc] Mode Sense: 00 3a 00 00 > > kernel: sd 9:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: scsi 9:1:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 > > kernel: sd 9:1:0:0: [sdd] 976773168 512-byte logical blocks: (500 GB/465 GiB) > > kernel: sd 9:1:0:0: [sdd] Write Protect is off > > kernel: sd 9:1:0:0: [sdd] Mode Sense: 00 3a 00 00 > > kernel: sd 9:1:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: scsi 9:2:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 > > kernel: sd 9:2:0:0: [sde] 976773168 512-byte logical blocks: (500 GB/465 GiB) > > kernel: sd 9:2:0:0: [sde] Write Protect is off > > kernel: sd 9:2:0:0: [sde] Mode Sense: 00 3a 00 00 > > kernel: sd 9:2:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: scsi 9:3:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 > > kernel: sd 9:3:0:0: [sdf] 976773168 512-byte logical blocks: (500 GB/465 GiB) > > kernel: sd 9:3:0:0: [sdf] Write Protect is off > > kernel: sd 9:3:0:0: [sdf] Mode Sense: 00 3a 00 00 > > kernel: sd 9:3:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: scsi 9:4:0:0: Direct-Access ATA ST3750640AS 3.AA PQ: 0 ANSI: 5 > > kernel: sd 9:4:0:0: [sdg] 1465149168 512-byte logical blocks: (750 GB/698 GiB) > > kernel: sd 9:4:0:0: [sdg] Write Protect is off > > kernel: sd 9:4:0:0: [sdg] Mode Sense: 00 3a 00 00 > > kernel: sd 9:4:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: sdc: sdc1 > > kernel: sd 9:0:0:0: [sdc] Attached SCSI disk > > kernel: sdg: sdg1 sdg2 > > kernel: sd 9:4:0:0: [sdg] Attached SCSI disk > > kernel: sdd: sdd1 > > kernel: sd 9:1:0:0: [sdd] Attached SCSI disk > > kernel: sde: sde1 > > kernel: sdf: sdf1 > > kernel: sd 9:2:0:0: [sde] Attached SCSI disk > > kernel: sd 9:3:0:0: [sdf] Attached SCSI disk > > kernel: ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > kernel: ata11.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 > > kernel: ata11.00: hard resetting link > > kernel: ata11.01: hard resetting link > > kernel: ata11.02: hard resetting link > > kernel: ata11.03: hard resetting link > > kernel: ata11.04: hard resetting link > > kernel: ata11.05: hard resetting link > > kernel: ata11.00: ATA-8: WDC WD20EADS-00W4B0, 01.00A01, max UDMA/133 > > kernel: ata11.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata11.00: configured for Uel kernel: ata11.02: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 > > kernel: ata11.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata11.02: configured for UDMA/133 > > kernel: ata11.03: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 > > kernel: ata11.03: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata11.03: configured for UDMA/133 > > kernel: ata11.04: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133 > > kernel: ata11.04: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) > > kernel: ata11.04: configured for UDMA/133 > > kernel: ata11: EH complete > > kernel: scsi 10:0:0:0: Direct-Access ATA WDC WD20EADS-00W 01.0 PQ: 0 ANSI: 5 > > kernel: sd 10:0:0:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > > kernel: sd 10:0:0:0: [sdh] Write Protect is off > > kernel: sd 10:0:0:0: [sdh] Mode Sense: 00 3a 00 00 > > kernel: sd 10:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: scsi 10:1:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 > > kernel: sd 10:1:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > > kernel: sd 10:1:0:0: [sdi] Write Protect is off > > kernel: sd 10:1:0:0: [sdi] Mode Sense: 00 3a 00 00 > > kernel: sd 10:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: scsi 10:2:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 > > kernel: sd 10:2:0:0: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > > kernel: sd 10:2:0:0: [sdj] Write Protect is off > > kernel: sd 10:2:0:0: [sdj] Mode Sense: 00 3a 00 00 > > kernel: sd 10:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: scsi 10:3:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 > > kernel: sd 10:3:0:0: [sdk] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > > kernel: sd 10:3:0:0: [sdk] Write Protect is off > > kernel: sd 10:3:0:0: [sdk] Mode Sense: 00 3a 00 00 > > kernel: sd 10:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: scsi 10:4:0:0: Direct-Access ATA WDC WD20EADS-00S 01.0 PQ: 0 ANSI: 5 > > kernel: sd 10:4:0:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) > > kernel: sd 10:4:0:0: [sdl] Write Protect is off > > kernel: sd 10:4:0:0: [sdl] Mode Sense: 00 3a 00 00 > > kernel: sd 10:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > kernel: sdi: sdi1 > > kernel: sd 10:1:0:0: [sdi] Attached SCSI disk > > kernel: sdk: sdk1 > > kernel: sd 10:3:0:0: [sdk] Attached SCSI disk > > kernel: sdl: sdl1 > > kernel: sd 10:4:0:0: [sdl] Attached SCSI disk > > kernel: sdj: sdj1 > > kernel: sd 10:2:0:0: [sdj] Attached SCSI disk > > kernel: ata12: SATA link down (SStatus 0 SControl 300) > > kernel: sdh: sdh1 > > kernel: sd 10:0:0:0: [sdh] Attached SCSI disk > > > Those WARNINGS are probably harmless right now, so don't panic over them. > Not hardware related; more just alerting Tejun to a possible libata bug. > > cheers > -- > Mark Lord > Real-Time Remedies Inc. > mlord@pobox.com -- tejun ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: sata_mv WARNING: at drivers/ata/libata-sff.c:1322 2011-07-12 14:29 ` Tejun Heo @ 2011-07-13 20:54 ` Gwendal Grignou 2011-07-13 22:41 ` Mark Lord 0 siblings, 1 reply; 23+ messages in thread From: Gwendal Grignou @ 2011-07-13 20:54 UTC (permalink / raw) To: Tejun Heo; +Cc: Mark Lord, Marc MERLIN, linux-ide, Larry Li, hbailey I put the warning because a new pio task should not be queued while another one is pending. Therefore, either sff_pio_task_link is NULL [no task pending] or sff_pio_task_link is equal to the link of the task [assumed to be the task in progress]. I must have missed something and did not cleanup sff_pio_task_link properly in case of error... Gwendal. On Tue, Jul 12, 2011 at 7:29 AM, Tejun Heo <tj@kernel.org> wrote: > Hello, > > (cc'ing Gwendal Grignou and quoting whole message for him.) > > That warning wasn't added by me. It's from ea3c64506ea79 "libata-sff: > Reenable Port Multiplier after libata-sff remodeling." Hmmm... I > never expected SFF to be used in combination with PMP. Anyways, > Gwendal, any ideas? > > On Wed, Jun 29, 2011 at 12:03:19PM -0400, Mark Lord wrote: >> On 11-06-29 11:07 AM, Marc MERLIN wrote: >> > On Tue, Jun 28, 2011 at 10:03:41PM -0700, Marc MERLIN wrote: >> >> On Tue, Jun 28, 2011 at 11:53:37PM -0400, Mark Lord wrote: >> >>> On 11-06-28 11:41 PM, Marc MERLIN wrote: >> >>> .. >> >>>> So it seems it was a false alarm after all, I'll report back if I have >> >>>> problems again, but it looks like it's working solidly and for what it's >> >>>> worth with 5 drives and software raid 5, I can both read and write files >> >>>> at about 115MB/s, which isn't too shabby :) >> >>> >> >>> Mmm.. power everything OFF, wait a few seconds, >> >>> then power on and verify that it all still works. >> >> >> >> Yep, it does (even powered off the power supply to the MB that isn't truly >> >> off otherwise). >> > >> > Mmh, although the card works fine now, I did notice 3 libata-sff errors >> > in my boot log. >> > Once boot is finished, there are no more errors. >> > >> > The card is: >> > 02:00.0 SCSI storage controller: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II (rev 02) >> > >> >>From the errors, should I try swapping the card considering it otherwise >> > works fine after boot, or is the problem elsewhere? >> > Can the 3 warnings just be ignored, or are they important? >> > >> > So I suppose this is also why my kernel gets tainted? >> > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 >> > >> > kernel: sata_mv 0000:02:00.0: version 1.28 >> > kernel: sata_mv 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 >> > kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx >> > kernel: sata_mv 0000:02:00.0: setting latency timer to 64 >> > kernel: scsi8 : sata_mv >> > kernel: scsi9 : sata_mv >> > kernel: scsi10 : sata_mv >> > kernel: scsi11 : sata_mv >> > kernel: ata9: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb822000 irq 16 >> > kernel: ata10: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb824000 irq 16 >> > kernel: ata11: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb826000 irq 16 >> > kernel: ata12: SATA max UDMA/133 mmio m1048576@0xfb800000 port 0xfb828000 irq 16 >> > kernel: ata9: SATA link down (SStatus 0 SControl 300) >> > kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> > kernel: ata10.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 >> > kernel: ata10.00: hard resetting link >> > kernel: ata10.01: hard resetting link >> > kernel: ata10.01: link resume succeeded after 1 retries >> > kernel: ata10.02: hard resetting link >> > kernel: ata10.02: link resume succeeded after 1 retries >> > kernel: ata10.03: hard resetting link >> > kernel: ata10.03: link resume succeeded after 1 retries >> > kernel: ata10.04: hard resetting link >> > kernel: ata10.05: hard resetting link >> > kernel: ata10.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 >> > kernel: ata10.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata10.00: configured for UDMA/133 >> > kernel: ata10.01: qc timeout (cmd 0x27) >> > kernel: ata10.01: failed to read native max address (err_mask=0x4) >> > kernel: ata10.01: HPA support seems broken, skipping HPA handling >> > kernel: ata10.15: hard resetting link >> > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> > kernel: ------------[ cut here ]------------ >> > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() >> > kernel: Hardware name: System Product Name >> > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore >> > kernel: Pid: 1636, comm: scsi_eh_9 Not tainted 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 >> > kernel: Call Trace: >> > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 >> > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 >> > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 >> > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d >> > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 >> > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] >> > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 >> > kernel: [<c014b5bb>] ? up+0x2b/0x2f >> > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 >> > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 >> > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde >> > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 >> > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 >> > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d >> > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 >> > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 >> > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 >> > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 >> > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a >> > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] >> > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] >> > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 >> > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa >> > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e >> > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] >> > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 >> > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd >> > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f >> > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d >> > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 >> > kernel: [<c012750b>] ? complete+0x34/0x3e >> > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d >> > kernel: [<c01476c0>] kthread+0x64/0x69 >> > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 >> > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd >> > kernel: ---[ end trace cdcd2b0b3f6829ed ]--- >> > kernel: ata10.00: hard resetting link >> > kernel: ata10.01: hard resetting link >> > kernel: ata10.01: link resume succeeded after 1 retries >> > kernel: ata10.02: hard resetting link >> > kernel: ata10.02: link resume succeeded after 1 retries >> > kernel: ata10.03: hard resetting link >> > kernel: ata10.03: link resume succeeded after 1 retries >> > kernel: ata10.04: hard resetting link >> > kernel: ata10.04: link resume succeeded after 1 retries >> > kernel: ata10.05: hard resetting link >> > kernel: ata10.00: configured for UDMA/133 >> > kernel: ata10.01: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 >> > kernel: ata10.01: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata10.01: configured for UDMA/133 >> > kernel: ata10.02: qc timeout (cmd 0x27) >> > kernel: ata10.02: failed to read native max address (err_mask=0x4) >> > kernel: ata10.02: HPA support seems broken, skipping HPA handling >> > kernel: ata10.15: hard resetting link >> > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> > kernel: ------------[ cut here ]------------ >> > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() >> > kernel: Hardware name: System Product Name >> > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore >> > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 >> > kernel: Call Trace: >> > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 >> > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 >> > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 >> > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d >> > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 >> > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] >> > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 >> > kernel: [<c014b5bb>] ? up+0x2b/0x2f >> > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 >> > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 >> > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde >> > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 >> > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 >> > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d >> > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 >> > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 >> > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 >> > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 >> > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a >> > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] >> > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] >> > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 >> > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa >> > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e >> > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] >> > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 >> > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd >> > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f >> > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d >> > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 >> > kernel: [<c012750b>] ? complete+0x34/0x3e >> > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d >> > kernel: [<c01476c0>] kthread+0x64/0x69 >> > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 >> > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd >> > kernel: ---[ end trace cdcd2b0b3f6829ee ]--- >> > kernel: ata10.00: hard resetting link >> > kernel: ata10.01: hard resetting link >> > kernel: ata10.01: link resume succeeded after 1 retries >> > kernel: ata10.02: hard resetting link >> > kernel: ata10.02: link resume succeeded after 1 retries >> > kernel: ata10.03: hard resetting link >> > kernel: ata10.03: link resume succeeded after 1 retries >> > kernel: ata10.04: hard resetting link >> > kernel: ata10.04: link resume succeeded after 1 retries >> > kernel: ata10.05: hard resetting link >> > kernel: ata10.00: configured for UDMA/133 >> > kernel: ata10.01: configured for UDMA/133 >> > kernel: ata10.02: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 >> > kernel: ata10.02: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata10.02: configured for UDMA/133 >> > kernel: ata10.03: qc timeout (cmd 0x27) >> > kernel: ata10.03: failed to read native max address (err_mask=0x4) >> > kernel: ata10.03: HPA support seems broken, skipping HPA handling >> > kernel: ata10.15: hard resetting link >> > kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> > kernel: ------------[ cut here ]------------ >> > kernel: WARNING: at drivers/ata/libata-sff.c:1322 ata_sff_queue_pio_task+0x26/0x44() >> > kernel: Hardware name: System Product Name >> > kernel: Modules linked in: keyspan ati_remote visor pl2303 ftdi_sio pci_hotplug soundcore backlight option processor usb_wwan rtc_cmos thermal_sys rtc_core hwmon parport_pc button snd_page_alloc parport usbserial wmi i2c_i801 evdev rtc_lib sata_mv pcspkr intel_agp intel_gtt agpgart tpm_tis r8169 iTCO_wdt iTCO_vendor_support xhci_hcd ehci_hcd usbcore >> > kernel: Pid: 1636, comm: scsi_eh_9 Tainted: G W 2.6.39.1-core2-volpreempt-noide-hm64-20110620 #2 >> > kernel: Call Trace: >> > kernel: [<c0133599>] warn_slowpath_common+0x60/0x75 >> > kernel: [<c01335bd>] warn_slowpath_null+0xf/0x13 >> > kernel: [<c0370812>] ata_sff_queue_pio_task+0x26/0x44 >> > kernel: [<c0370946>] ata_sff_qc_issue+0x116/0x14d >> > kernel: [<c03709d6>] ata_bmdma_qc_issue+0x59/0x156 >> > kernel: [<f844650b>] mv_qc_issue+0x441/0x44d [sata_mv] >> > kernel: [<c028ea13>] ? vsnprintf+0x80/0x2d7 >> > kernel: [<c014b5bb>] ? up+0x2b/0x2f >> > kernel: [<c036309d>] ata_qc_issue+0x30b/0x329 >> > kernel: [<c03638c2>] ata_exec_internal_sg+0x27f/0x4a0 >> > kernel: [<c036f84b>] ? ata_sff_tf_read+0x53/0xde >> > kernel: [<c0363b41>] ata_exec_internal+0x5e/0x66 >> > kernel: [<c036a0a3>] ? ata_eh_done+0x12/0x18 >> > kernel: [<c037213a>] sata_pmp_read+0x66/0x9d >> > kernel: [<c0372197>] sata_pmp_read_gscr+0x26/0x65 >> > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 >> > kernel: [<c03727b8>] sata_pmp_error_handler+0x2ff/0xa42 >> > kernel: [<c01289e3>] ? dequeue_task_fair+0x1fc/0x204 >> > kernel: [<c03704f9>] ? ata_sff_drain_fifo+0x5a/0x5a >> > kernel: [<f8445f41>] ? mv_port_start+0x19f/0x19f [sata_mv] >> > kernel: [<f8445c50>] ? mv_pmp_hardreset+0x8c/0x8c [sata_mv] >> > kernel: [<c0371e77>] ? ata_sff_softreset+0x150/0x150 >> > kernel: [<c044194d>] ? __mutex_lock_slowpath+0x1f2/0x1fa >> > kernel: [<c013cadd>] ? lock_timer_base+0x1f/0x3e >> > kernel: [<f8445bbf>] mv_pmp_error_handler+0x60/0x65 [sata_mv] >> > kernel: [<c036e283>] ata_scsi_port_error_handler+0x206/0x522 >> > kernel: [<c01448f6>] ? cancel_delayed_work_sync+0xb/0xd >> > kernel: [<c036e60c>] ata_scsi_error+0x6d/0x8f >> > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d >> > kernel: [<c032ae1a>] scsi_error_handler+0x103/0x507 >> > kernel: [<c012750b>] ? complete+0x34/0x3e >> > kernel: [<c032ad17>] ? scsi_eh_get_sense+0x16d/0x16d >> > kernel: [<c01476c0>] kthread+0x64/0x69 >> > kernel: [<c014765c>] ? kthread_worker_fn+0x119/0x119 >> > kernel: [<c0443bbe>] kernel_thread_helper+0x6/0xd >> > kernel: ---[ end trace cdcd2b0b3f6829ef ]--- >> > kernel: ata10.00: hard resetting link >> > kernel: ata10.01: hard resetting link >> > kernel: ata10.01: link resume succeeded after 1 retries >> > kernel: ata10.02: hard resetting link >> > kernel: ata10.02: link resume succeeded after 1 retries >> > kernel: ata10.03: hard resetting link >> > kernel: ata10.03: link resume succeeded after 1 retries >> > kernel: ata10.04: hard resetting link >> > kernel: ata10.04: link resume succeeded after 1 retries >> > kernel: ata10.05: hard resetting link >> > kernel: ata10.00: configured for UDMA/133 >> > kernel: ata10.01: configured for UDMA/133 >> > kernel: ata10.02: configured for UDMA/133 >> > kernel: ata10.03: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 >> > kernel: ata10.03: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata10.03: configured for UDMA/133 >> > kernel: ata10.04: ATA-7: ST3750640AS, 3.AAK, max UDMA/133 >> > kernel: ata10.04: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata10.04: configured for UDMA/133 >> > kernel: ata10: EH complete >> > kernel: scsi 9:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 >> > kernel: sd 9:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB) >> > kernel: sd 9:0:0:0: [sdc] Write Protect is off >> > kernel: sd 9:0:0:0: [sdc] Mode Sense: 00 3a 00 00 >> > kernel: sd 9:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: scsi 9:1:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 >> > kernel: sd 9:1:0:0: [sdd] 976773168 512-byte logical blocks: (500 GB/465 GiB) >> > kernel: sd 9:1:0:0: [sdd] Write Protect is off >> > kernel: sd 9:1:0:0: [sdd] Mode Sense: 00 3a 00 00 >> > kernel: sd 9:1:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: scsi 9:2:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 >> > kernel: sd 9:2:0:0: [sde] 976773168 512-byte logical blocks: (500 GB/465 GiB) >> > kernel: sd 9:2:0:0: [sde] Write Protect is off >> > kernel: sd 9:2:0:0: [sde] Mode Sense: 00 3a 00 00 >> > kernel: sd 9:2:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: scsi 9:3:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 >> > kernel: sd 9:3:0:0: [sdf] 976773168 512-byte logical blocks: (500 GB/465 GiB) >> > kernel: sd 9:3:0:0: [sdf] Write Protect is off >> > kernel: sd 9:3:0:0: [sdf] Mode Sense: 00 3a 00 00 >> > kernel: sd 9:3:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: scsi 9:4:0:0: Direct-Access ATA ST3750640AS 3.AA PQ: 0 ANSI: 5 >> > kernel: sd 9:4:0:0: [sdg] 1465149168 512-byte logical blocks: (750 GB/698 GiB) >> > kernel: sd 9:4:0:0: [sdg] Write Protect is off >> > kernel: sd 9:4:0:0: [sdg] Mode Sense: 00 3a 00 00 >> > kernel: sd 9:4:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: sdc: sdc1 >> > kernel: sd 9:0:0:0: [sdc] Attached SCSI disk >> > kernel: sdg: sdg1 sdg2 >> > kernel: sd 9:4:0:0: [sdg] Attached SCSI disk >> > kernel: sdd: sdd1 >> > kernel: sd 9:1:0:0: [sdd] Attached SCSI disk >> > kernel: sde: sde1 >> > kernel: sdf: sdf1 >> > kernel: sd 9:2:0:0: [sde] Attached SCSI disk >> > kernel: sd 9:3:0:0: [sdf] Attached SCSI disk >> > kernel: ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> > kernel: ata11.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 >> > kernel: ata11.00: hard resetting link >> > kernel: ata11.01: hard resetting link >> > kernel: ata11.02: hard resetting link >> > kernel: ata11.03: hard resetting link >> > kernel: ata11.04: hard resetting link >> > kernel: ata11.05: hard resetting link >> > kernel: ata11.00: ATA-8: WDC WD20EADS-00W4B0, 01.00A01, max UDMA/133 >> > kernel: ata11.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata11.00: configured for Uel kernel: ata11.02: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 >> > kernel: ata11.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata11.02: configured for UDMA/133 >> > kernel: ata11.03: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 >> > kernel: ata11.03: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata11.03: configured for UDMA/133 >> > kernel: ata11.04: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133 >> > kernel: ata11.04: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) >> > kernel: ata11.04: configured for UDMA/133 >> > kernel: ata11: EH complete >> > kernel: scsi 10:0:0:0: Direct-Access ATA WDC WD20EADS-00W 01.0 PQ: 0 ANSI: 5 >> > kernel: sd 10:0:0:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) >> > kernel: sd 10:0:0:0: [sdh] Write Protect is off >> > kernel: sd 10:0:0:0: [sdh] Mode Sense: 00 3a 00 00 >> > kernel: sd 10:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: scsi 10:1:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 >> > kernel: sd 10:1:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) >> > kernel: sd 10:1:0:0: [sdi] Write Protect is off >> > kernel: sd 10:1:0:0: [sdi] Mode Sense: 00 3a 00 00 >> > kernel: sd 10:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: scsi 10:2:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 >> > kernel: sd 10:2:0:0: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) >> > kernel: sd 10:2:0:0: [sdj] Write Protect is off >> > kernel: sd 10:2:0:0: [sdj] Mode Sense: 00 3a 00 00 >> > kernel: sd 10:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: scsi 10:3:0:0: Direct-Access ATA WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 >> > kernel: sd 10:3:0:0: [sdk] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) >> > kernel: sd 10:3:0:0: [sdk] Write Protect is off >> > kernel: sd 10:3:0:0: [sdk] Mode Sense: 00 3a 00 00 >> > kernel: sd 10:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: scsi 10:4:0:0: Direct-Access ATA WDC WD20EADS-00S 01.0 PQ: 0 ANSI: 5 >> > kernel: sd 10:4:0:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) >> > kernel: sd 10:4:0:0: [sdl] Write Protect is off >> > kernel: sd 10:4:0:0: [sdl] Mode Sense: 00 3a 00 00 >> > kernel: sd 10:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >> > kernel: sdi: sdi1 >> > kernel: sd 10:1:0:0: [sdi] Attached SCSI disk >> > kernel: sdk: sdk1 >> > kernel: sd 10:3:0:0: [sdk] Attached SCSI disk >> > kernel: sdl: sdl1 >> > kernel: sd 10:4:0:0: [sdl] Attached SCSI disk >> > kernel: sdj: sdj1 >> > kernel: sd 10:2:0:0: [sdj] Attached SCSI disk >> > kernel: ata12: SATA link down (SStatus 0 SControl 300) >> > kernel: sdh: sdh1 >> > kernel: sd 10:0:0:0: [sdh] Attached SCSI disk >> >> >> Those WARNINGS are probably harmless right now, so don't panic over them. >> Not hardware related; more just alerting Tejun to a possible libata bug. >> >> cheers >> -- >> Mark Lord >> Real-Time Remedies Inc. >> mlord@pobox.com > > -- > tejun > ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: sata_mv WARNING: at drivers/ata/libata-sff.c:1322 2011-07-13 20:54 ` Gwendal Grignou @ 2011-07-13 22:41 ` Mark Lord 2011-07-14 7:19 ` Gwendal Grignou 0 siblings, 1 reply; 23+ messages in thread From: Mark Lord @ 2011-07-13 22:41 UTC (permalink / raw) To: Gwendal Grignou; +Cc: Tejun Heo, Marc MERLIN, linux-ide, Larry Li, hbailey On 11-07-13 04:54 PM, Gwendal Grignou wrote: > I put the warning because a new pio task should not be queued while > another one is pending. Therefore, either sff_pio_task_link is NULL > [no task pending] or sff_pio_task_link is equal to the link of the > task [assumed to be the task in progress]. > I must have missed something and did not cleanup sff_pio_task_link > properly in case of error... .. I wonder if any of those changes are what broke PMP support? I have a Marvell PMP here that used to work when I finished with sata_mv, but no longer works with it now. ?? -- Mark Lord Real-Time Remedies Inc. mlord@pobox.com ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: sata_mv WARNING: at drivers/ata/libata-sff.c:1322 2011-07-13 22:41 ` Mark Lord @ 2011-07-14 7:19 ` Gwendal Grignou 2011-07-14 12:03 ` Mark Lord 2011-07-15 15:55 ` Marc MERLIN 0 siblings, 2 replies; 23+ messages in thread From: Gwendal Grignou @ 2011-07-14 7:19 UTC (permalink / raw) To: Mark Lord; +Cc: Tejun Heo, Marc MERLIN, linux-ide, Larry Li, hbailey Mark, How PMP support with sata_mv broken for you? I am using marvell 7042 and sil3726 and it works fine, but I am still using 2.6.36. Tejun, Marc, I think what happen is if a command is canceled while waiting for sff_pio_task to fire up, the warning may happen. The following patch should fix it. Marc, can you reproduce the problem easily? Thanks, Gwendal. diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c index 996a7a5..c24127d 100644 --- a/drivers/ata/libata-sff.c +++ b/drivers/ata/libata-sff.c @@ -1333,6 +1333,7 @@ void ata_sff_flush_pio_task(struct ata_port *ap) cancel_delayed_work_sync(&ap->sff_pio_task); ap->hsm_task_state = HSM_ST_IDLE; + ap->sff_pio_task_link = NULL; if (ata_msg_ctl(ap)) ata_port_dbg(ap, "%s: EXIT\n", __func__); On Wed, Jul 13, 2011 at 3:41 PM, Mark Lord <mlord@pobox.com> wrote: > On 11-07-13 04:54 PM, Gwendal Grignou wrote: >> I put the warning because a new pio task should not be queued while >> another one is pending. Therefore, either sff_pio_task_link is NULL >> [no task pending] or sff_pio_task_link is equal to the link of the >> task [assumed to be the task in progress]. >> I must have missed something and did not cleanup sff_pio_task_link >> properly in case of error... > .. > > I wonder if any of those changes are what broke PMP support? > I have a Marvell PMP here that used to work when I finished with sata_mv, > but no longer works with it now. > > ?? > -- > Mark Lord > Real-Time Remedies Inc. > mlord@pobox.com > ^ permalink raw reply related [flat|nested] 23+ messages in thread
* Re: sata_mv WARNING: at drivers/ata/libata-sff.c:1322 2011-07-14 7:19 ` Gwendal Grignou @ 2011-07-14 12:03 ` Mark Lord 2011-07-15 15:55 ` Marc MERLIN 1 sibling, 0 replies; 23+ messages in thread From: Mark Lord @ 2011-07-14 12:03 UTC (permalink / raw) To: Gwendal Grignou; +Cc: Tejun Heo, Marc MERLIN, linux-ide, Larry Li, hbailey On 11-07-14 03:19 AM, Gwendal Grignou wrote: > Mark, > > How PMP support with sata_mv broken for you? I am using marvell 7042 > and sil3726 and it works fine, but I am still using 2.6.36. It's broken when used with a Marvell PMP. Still works with other brands. Strange, that. -- Mark Lord Real-Time Remedies Inc. mlord@pobox.com ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: sata_mv WARNING: at drivers/ata/libata-sff.c:1322 2011-07-14 7:19 ` Gwendal Grignou 2011-07-14 12:03 ` Mark Lord @ 2011-07-15 15:55 ` Marc MERLIN 2011-07-16 0:32 ` [PATCH] Prevent warning during PMP error recovery Gwendal Grignou 1 sibling, 1 reply; 23+ messages in thread From: Marc MERLIN @ 2011-07-15 15:55 UTC (permalink / raw) To: Gwendal Grignou; +Cc: Mark Lord, Tejun Heo, linux-ide, Larry Li, hbailey On Thu, Jul 14, 2011 at 12:19:16AM -0700, Gwendal Grignou wrote: > Mark, > > How PMP support with sata_mv broken for you? I am using marvell 7042 > and sil3726 and it works fine, but I am still using 2.6.36. > > Tejun, Marc, > > I think what happen is if a command is canceled while waiting for > sff_pio_task to fire up, the warning may happen. The following patch > should fix it. Marc, can you reproduce the problem easily? > > Thanks, > Gwendal. > > diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c > index 996a7a5..c24127d 100644 > --- a/drivers/ata/libata-sff.c > +++ b/drivers/ata/libata-sff.c > @@ -1333,6 +1333,7 @@ void ata_sff_flush_pio_task(struct ata_port *ap) > > cancel_delayed_work_sync(&ap->sff_pio_task); > ap->hsm_task_state = HSM_ST_IDLE; > + ap->sff_pio_task_link = NULL; > > if (ata_msg_ctl(ap)) > ata_port_dbg(ap, "%s: EXIT\n", __func__); I can confirm this makes the warnings go away, thanks Gwendal. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ ^ permalink raw reply [flat|nested] 23+ messages in thread
* [PATCH] Prevent warning during PMP error recovery 2011-07-15 15:55 ` Marc MERLIN @ 2011-07-16 0:32 ` Gwendal Grignou 2011-07-16 0:34 ` Gwendal Grignou 2011-07-21 7:24 ` Tejun Heo 0 siblings, 2 replies; 23+ messages in thread From: Gwendal Grignou @ 2011-07-16 0:32 UTC (permalink / raw) To: tj; +Cc: mlord, linux-ide, lil, hbailey, marc, Gwendal Grignou Cleanup sff_pio_task_link when a command is cancel while the pio_task thread has been scheduled. Change-Id: I4397bed3ee0878d92933d4897eed025ffaf3a9bd Signed-off-by: Gwendal Grignou <gwendal@google.com> --- drivers/ata/libata-sff.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c index 996a7a5..c24127d 100644 --- a/drivers/ata/libata-sff.c +++ b/drivers/ata/libata-sff.c @@ -1333,6 +1333,7 @@ void ata_sff_flush_pio_task(struct ata_port *ap) cancel_delayed_work_sync(&ap->sff_pio_task); ap->hsm_task_state = HSM_ST_IDLE; + ap->sff_pio_task_link = NULL; if (ata_msg_ctl(ap)) ata_port_dbg(ap, "%s: EXIT\n", __func__); -- 1.7.3.1 ^ permalink raw reply related [flat|nested] 23+ messages in thread
* [PATCH] Prevent warning during PMP error recovery 2011-07-16 0:32 ` [PATCH] Prevent warning during PMP error recovery Gwendal Grignou @ 2011-07-16 0:34 ` Gwendal Grignou 2011-07-21 7:24 ` Tejun Heo 1 sibling, 0 replies; 23+ messages in thread From: Gwendal Grignou @ 2011-07-16 0:34 UTC (permalink / raw) To: tj; +Cc: mlord, linux-ide, lil, hbailey, marc, Gwendal Grignou Cleanup sff_pio_task_link when a command is cancel while the pio_task thread has been scheduled. Signed-off-by: Gwendal Grignou <gwendal@google.com> --- drivers/ata/libata-sff.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c index 996a7a5..c24127d 100644 --- a/drivers/ata/libata-sff.c +++ b/drivers/ata/libata-sff.c @@ -1333,6 +1333,7 @@ void ata_sff_flush_pio_task(struct ata_port *ap) cancel_delayed_work_sync(&ap->sff_pio_task); ap->hsm_task_state = HSM_ST_IDLE; + ap->sff_pio_task_link = NULL; if (ata_msg_ctl(ap)) ata_port_dbg(ap, "%s: EXIT\n", __func__); -- 1.7.3.1 ^ permalink raw reply related [flat|nested] 23+ messages in thread
* Re: [PATCH] Prevent warning during PMP error recovery 2011-07-16 0:32 ` [PATCH] Prevent warning during PMP error recovery Gwendal Grignou 2011-07-16 0:34 ` Gwendal Grignou @ 2011-07-21 7:24 ` Tejun Heo 2011-07-21 7:25 ` Tejun Heo 1 sibling, 1 reply; 23+ messages in thread From: Tejun Heo @ 2011-07-21 7:24 UTC (permalink / raw) To: Gwendal Grignou; +Cc: mlord, linux-ide, lil, hbailey, marc On Fri, Jul 15, 2011 at 05:32:02PM -0700, Gwendal Grignou wrote: > Cleanup sff_pio_task_link when a command is cancel while the > pio_task thread has been scheduled. > > Change-Id: I4397bed3ee0878d92933d4897eed025ffaf3a9bd > > Signed-off-by: Gwendal Grignou <gwendal@google.com> Acked-by: Tejun Heo <tj@kernel.org> Thank you. -- tejun ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH] Prevent warning during PMP error recovery 2011-07-21 7:24 ` Tejun Heo @ 2011-07-21 7:25 ` Tejun Heo 2011-07-22 20:48 ` Gwendal Grignou 0 siblings, 1 reply; 23+ messages in thread From: Tejun Heo @ 2011-07-21 7:25 UTC (permalink / raw) To: Gwendal Grignou; +Cc: mlord, linux-ide, lil, hbailey, marc On Thu, Jul 21, 2011 at 09:24:20AM +0200, Tejun Heo wrote: > On Fri, Jul 15, 2011 at 05:32:02PM -0700, Gwendal Grignou wrote: > > Cleanup sff_pio_task_link when a command is cancel while the > > pio_task thread has been scheduled. > > > > Change-Id: I4397bed3ee0878d92933d4897eed025ffaf3a9bd > > > > Signed-off-by: Gwendal Grignou <gwendal@google.com> > > Acked-by: Tejun Heo <tj@kernel.org> Oooh, Jeff isn't cc'd. Please re-send to jgarzik with Acked-by added. Thank you. -- tejun ^ permalink raw reply [flat|nested] 23+ messages in thread
* [PATCH] Prevent warning during PMP error recovery 2011-07-21 7:25 ` Tejun Heo @ 2011-07-22 20:48 ` Gwendal Grignou 0 siblings, 0 replies; 23+ messages in thread From: Gwendal Grignou @ 2011-07-22 20:48 UTC (permalink / raw) To: jeff; +Cc: tj, mlord, linux-ide, lil, hbailey, marc, Gwendal Grignou Cleanup sff_pio_task_link when a command is cancel while the pio_task thread has been scheduled. Signed-off-by: Gwendal Grignou <gwendal@google.com> Acked-by: Tejun Heo <tj@kernel.org> --- drivers/ata/libata-sff.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c index 996a7a5..c24127d 100644 --- a/drivers/ata/libata-sff.c +++ b/drivers/ata/libata-sff.c @@ -1333,6 +1333,7 @@ void ata_sff_flush_pio_task(struct ata_port *ap) cancel_delayed_work_sync(&ap->sff_pio_task); ap->hsm_task_state = HSM_ST_IDLE; + ap->sff_pio_task_link = NULL; if (ata_msg_ctl(ap)) ata_port_dbg(ap, "%s: EXIT\n", __func__); -- 1.7.3.1 ^ permalink raw reply related [flat|nested] 23+ messages in thread
end of thread, other threads:[~2011-07-22 20:49 UTC | newest] Thread overview: 23+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-06-26 7:08 decoding PMP errors with Marvel SATA controller Marc MERLIN 2011-06-26 9:03 ` Tejun Heo 2011-06-26 17:38 ` Mark Lord 2011-06-27 0:06 ` Marc MERLIN 2011-06-27 1:29 ` Mark Lord 2011-06-27 1:58 ` Hubert Bailey 2011-07-06 20:55 ` Tim Small 2011-06-29 3:41 ` Marc MERLIN 2011-06-29 3:53 ` Mark Lord 2011-06-29 5:03 ` Marc MERLIN 2011-06-29 15:07 ` sata_mv WARNING: at drivers/ata/libata-sff.c:1322 Marc MERLIN 2011-06-29 16:03 ` Mark Lord 2011-07-12 14:29 ` Tejun Heo 2011-07-13 20:54 ` Gwendal Grignou 2011-07-13 22:41 ` Mark Lord 2011-07-14 7:19 ` Gwendal Grignou 2011-07-14 12:03 ` Mark Lord 2011-07-15 15:55 ` Marc MERLIN 2011-07-16 0:32 ` [PATCH] Prevent warning during PMP error recovery Gwendal Grignou 2011-07-16 0:34 ` Gwendal Grignou 2011-07-21 7:24 ` Tejun Heo 2011-07-21 7:25 ` Tejun Heo 2011-07-22 20:48 ` Gwendal Grignou
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).