* Re: bug report [not found] ` <48DA7F1E.5030508@saturnosoft.biz> @ 2008-09-24 18:25 ` Simon Holm Thøgersen 2008-09-29 1:36 ` Tejun Heo 0 siblings, 1 reply; 7+ messages in thread From: Simon Holm Thøgersen @ 2008-09-24 18:25 UTC (permalink / raw) To: Todor Gyumyushev Cc: Tejun Heo, Jens Axboe, Albert Lee, linux-kernel, linux-ide [ CC'ing linux-ide mailing list and the people involved in commit 56c819df (libata: update ATAPI overflow draining) that introduced the WARN_ON. ] ons, 24 09 2008 kl. 20:55 +0300, skrev Todor Gyumyushev: > Simon Holm Thøgersen wrote: > > ons, 24 09 2008 kl. 12:41 +0300, skrev Todor Gyumyushev: > > > >> ------------[ cut here ]------------ > >> WARNING: at drivers/ata/libata-sff.c:944 ata_sff_hsm_move+0x4a9/0x6a0() > >> Modules linked in: cdc_acm eth1394 vboxdrv isofs zlib_inflate ath5k > >> aes_generic nls_utf8 nls_cp437 vfat fat nls_base i915 drm kvm > >> acpi_cpufreq hci_usb rfcomm l2cap pktcdvd nfsd lockd nfs_acl auth_rpcgss > >> sunrpc exportfs fan ac battery microcode firmware_class loop usb_storage > >> usbhid snd_hda_intel arc4 snd_pcm_oss sg ecb crypto_blkcipher > >> snd_mixer_oss cryptomgr snd_pcm snd_timer tpm_infineon sr_mod usblp snd > >> rng_core cdrom ehci_hcd mac80211 thermal ohci1394 ieee1394 processor > >> evdev thermal_sys tpm uhci_hcd iTCO_wdt iTCO_vendor_support soundcore > >> cfg80211 tpm_bios sky2 hwmon snd_page_alloc intel_agp button [last > >> unloaded: ath5k] > >> Pid: 0, comm: swapper Tainted: G W 2.6.26.5 #6 > >> > > > > This warning is not the first produced by your system, see the W flag in > > the line above. Can you find an earlier warning in your dmesg/log? Or is > > it similar to this one? > > > > > >> Call Trace: > >> <IRQ> [<ffffffff80236214>] warn_on_slowpath+0x64/0xc0 > >> [<ffffffff803c9ec8>] ata_sff_data_xfer+0x98/0xc0 > >> [<ffffffff803c96c9>] ata_sff_hsm_move+0x4a9/0x6a0 > >> [<ffffffff803c9c13>] ata_sff_interrupt+0x1a3/0x2c0 > >> [<ffffffff802748e4>] handle_IRQ_event+0x34/0x70 > >> [<ffffffff80275e60>] handle_edge_irq+0xc0/0x160 > >> [<ffffffff8020ebac>] do_IRQ+0x7c/0x100 > >> [<ffffffff8020bc51>] ret_from_intr+0x0/0xa > >> <EOI> [<ffffffff8021c800>] lapic_next_event+0x0/0x10 > >> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 > >> [<ffffffffa00564bc>] :processor:acpi_idle_enter_simple+0x1c5/0x235 > >> [<ffffffffa00564b2>] :processor:acpi_idle_enter_simple+0x1bb/0x235 > >> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 > >> [<ffffffff803fbce7>] cpuidle_idle_call+0xd7/0x120 > >> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 > >> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 > >> [<ffffffff80209410>] default_idle+0x0/0x50 > >> [<ffffffff8020a720>] cpu_idle+0x60/0xd0 > >> > >> ---[ end trace 05ba06d61030bbb9 ]--- > >> > >> > > > > > > Simon Holm Thøgersen > > > > > > > Hi there, > > yes you are correct, I found another one earlier, initially I thought is > the same but it is not. > > Regards, > Todor > > > ------------[ cut here ]------------ > WARNING: at drivers/ata/libata-sff.c:944 ata_sff_hsm_move+0x4a9/0x6a0() > Modules linked in: eth1394 vboxdrv isofs zlib_inflate ath5k aes_generic > nls_utf8 nls_cp437 vfat fat nls_base i915 drm kvm acpi_cpufreq hci_usb > rfcomm l2cap pktcdvd nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs fan > ac battery microcode firmware_class loop usb_storage usbhid > snd_hda_intel arc4 snd_pcm_oss sg ecb crypto_blkcipher snd_mixer_oss > cryptomgr snd_pcm snd_timer tpm_infineon sr_mod usblp snd rng_core cdrom > ehci_hcd mac80211 thermal ohci1394 ieee1394 processor evdev thermal_sys > tpm uhci_hcd iTCO_wdt iTCO_vendor_support soundcore cfg80211 tpm_bios > sky2 hwmon snd_page_alloc intel_agp button [last unloaded: ath5k] > Pid: 13270, comm: npviewer.bin Not tainted 2.6.26.5 #6 > > Call Trace: > <IRQ> [<ffffffff80236214>] warn_on_slowpath+0x64/0xc0 > [<ffffffff8032cf0b>] elv_next_request+0x12b/0x1f0 > [<ffffffff80252678>] getnstimeofday+0x48/0xc0 > [<ffffffff8024fe70>] ktime_get_ts+0x30/0x60 > [<ffffffff8024feac>] ktime_get+0xc/0x50 > [<ffffffff8022e58a>] hrtick_start_fair+0x12a/0x190 > [<ffffffff803c9ec8>] ata_sff_data_xfer+0x98/0xc0 > [<ffffffff803c96c9>] ata_sff_hsm_move+0x4a9/0x6a0 > [<ffffffff803c9c13>] ata_sff_interrupt+0x1a3/0x2c0 > [<ffffffff802748e4>] handle_IRQ_event+0x34/0x70 > [<ffffffff8023c44a>] __do_softirq+0x7a/0xf0 > [<ffffffff80275e60>] handle_edge_irq+0xc0/0x160 > [<ffffffff8020c8cc>] call_softirq+0x1c/0x30 > [<ffffffff8020ebac>] do_IRQ+0x7c/0x100 > [<ffffffff8020bc51>] ret_from_intr+0x0/0xa > <EOI> > ---[ end trace 05ba06d61030bbb9 ]--- > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: bug report 2008-09-24 18:25 ` bug report Simon Holm Thøgersen @ 2008-09-29 1:36 ` Tejun Heo 2008-09-29 8:30 ` Todor Gyumyushev 0 siblings, 1 reply; 7+ messages in thread From: Tejun Heo @ 2008-09-29 1:36 UTC (permalink / raw) To: Simon Holm Thøgersen Cc: Todor Gyumyushev, Jens Axboe, Albert Lee, linux-kernel, linux-ide Simon Holm Thøgersen wrote: > [ CC'ing linux-ide mailing list and the people involved in commit > 56c819df (libata: update ATAPI overflow draining) that introduced the > WARN_ON. ] > > ons, 24 09 2008 kl. 20:55 +0300, skrev Todor Gyumyushev: >> Simon Holm Thøgersen wrote: >>> ons, 24 09 2008 kl. 12:41 +0300, skrev Todor Gyumyushev: >>> >>>> ------------[ cut here ]------------ >>>> WARNING: at drivers/ata/libata-sff.c:944 ata_sff_hsm_move+0x4a9/0x6a0() >>>> Modules linked in: cdc_acm eth1394 vboxdrv isofs zlib_inflate ath5k >>>> aes_generic nls_utf8 nls_cp437 vfat fat nls_base i915 drm kvm >>>> acpi_cpufreq hci_usb rfcomm l2cap pktcdvd nfsd lockd nfs_acl auth_rpcgss >>>> sunrpc exportfs fan ac battery microcode firmware_class loop usb_storage >>>> usbhid snd_hda_intel arc4 snd_pcm_oss sg ecb crypto_blkcipher >>>> snd_mixer_oss cryptomgr snd_pcm snd_timer tpm_infineon sr_mod usblp snd >>>> rng_core cdrom ehci_hcd mac80211 thermal ohci1394 ieee1394 processor >>>> evdev thermal_sys tpm uhci_hcd iTCO_wdt iTCO_vendor_support soundcore >>>> cfg80211 tpm_bios sky2 hwmon snd_page_alloc intel_agp button [last >>>> unloaded: ath5k] >>>> Pid: 0, comm: swapper Tainted: G W 2.6.26.5 #6 >>>> >>> This warning is not the first produced by your system, see the W flag in >>> the line above. Can you find an earlier warning in your dmesg/log? Or is >>> it similar to this one? >>> >>> >>>> Call Trace: >>>> <IRQ> [<ffffffff80236214>] warn_on_slowpath+0x64/0xc0 >>>> [<ffffffff803c9ec8>] ata_sff_data_xfer+0x98/0xc0 >>>> [<ffffffff803c96c9>] ata_sff_hsm_move+0x4a9/0x6a0 >>>> [<ffffffff803c9c13>] ata_sff_interrupt+0x1a3/0x2c0 >>>> [<ffffffff802748e4>] handle_IRQ_event+0x34/0x70 >>>> [<ffffffff80275e60>] handle_edge_irq+0xc0/0x160 >>>> [<ffffffff8020ebac>] do_IRQ+0x7c/0x100 >>>> [<ffffffff8020bc51>] ret_from_intr+0x0/0xa >>>> <EOI> [<ffffffff8021c800>] lapic_next_event+0x0/0x10 >>>> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 >>>> [<ffffffffa00564bc>] :processor:acpi_idle_enter_simple+0x1c5/0x235 >>>> [<ffffffffa00564b2>] :processor:acpi_idle_enter_simple+0x1bb/0x235 >>>> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 >>>> [<ffffffff803fbce7>] cpuidle_idle_call+0xd7/0x120 >>>> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 >>>> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 >>>> [<ffffffff80209410>] default_idle+0x0/0x50 >>>> [<ffffffff8020a720>] cpu_idle+0x60/0xd0 Hmm... This shouldn't happen. Can you please attach full kernel log including the boot messages? Thanks. -- tejun ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: bug report 2008-09-29 1:36 ` Tejun Heo @ 2008-09-29 8:30 ` Todor Gyumyushev 2008-09-30 11:47 ` Tejun Heo 0 siblings, 1 reply; 7+ messages in thread From: Todor Gyumyushev @ 2008-09-29 8:30 UTC (permalink / raw) To: Tejun Heo Cc: Simon Holm Thøgersen, Jens Axboe, Albert Lee, linux-kernel, linux-ide [-- Attachment #1: Type: text/plain, Size: 2830 bytes --] Tejun Heo wrote: > Simon Holm Thøgersen wrote: > >> [ CC'ing linux-ide mailing list and the people involved in commit >> 56c819df (libata: update ATAPI overflow draining) that introduced the >> WARN_ON. ] >> >> ons, 24 09 2008 kl. 20:55 +0300, skrev Todor Gyumyushev: >> >>> Simon Holm Thøgersen wrote: >>> >>>> ons, 24 09 2008 kl. 12:41 +0300, skrev Todor Gyumyushev: >>>> >>>> >>>>> ------------[ cut here ]------------ >>>>> WARNING: at drivers/ata/libata-sff.c:944 ata_sff_hsm_move+0x4a9/0x6a0() >>>>> Modules linked in: cdc_acm eth1394 vboxdrv isofs zlib_inflate ath5k >>>>> aes_generic nls_utf8 nls_cp437 vfat fat nls_base i915 drm kvm >>>>> acpi_cpufreq hci_usb rfcomm l2cap pktcdvd nfsd lockd nfs_acl auth_rpcgss >>>>> sunrpc exportfs fan ac battery microcode firmware_class loop usb_storage >>>>> usbhid snd_hda_intel arc4 snd_pcm_oss sg ecb crypto_blkcipher >>>>> snd_mixer_oss cryptomgr snd_pcm snd_timer tpm_infineon sr_mod usblp snd >>>>> rng_core cdrom ehci_hcd mac80211 thermal ohci1394 ieee1394 processor >>>>> evdev thermal_sys tpm uhci_hcd iTCO_wdt iTCO_vendor_support soundcore >>>>> cfg80211 tpm_bios sky2 hwmon snd_page_alloc intel_agp button [last >>>>> unloaded: ath5k] >>>>> Pid: 0, comm: swapper Tainted: G W 2.6.26.5 #6 >>>>> >>>>> >>>> This warning is not the first produced by your system, see the W flag in >>>> the line above. Can you find an earlier warning in your dmesg/log? Or is >>>> it similar to this one? >>>> >>>> >>>> >>>>> Call Trace: >>>>> <IRQ> [<ffffffff80236214>] warn_on_slowpath+0x64/0xc0 >>>>> [<ffffffff803c9ec8>] ata_sff_data_xfer+0x98/0xc0 >>>>> [<ffffffff803c96c9>] ata_sff_hsm_move+0x4a9/0x6a0 >>>>> [<ffffffff803c9c13>] ata_sff_interrupt+0x1a3/0x2c0 >>>>> [<ffffffff802748e4>] handle_IRQ_event+0x34/0x70 >>>>> [<ffffffff80275e60>] handle_edge_irq+0xc0/0x160 >>>>> [<ffffffff8020ebac>] do_IRQ+0x7c/0x100 >>>>> [<ffffffff8020bc51>] ret_from_intr+0x0/0xa >>>>> <EOI> [<ffffffff8021c800>] lapic_next_event+0x0/0x10 >>>>> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 >>>>> [<ffffffffa00564bc>] :processor:acpi_idle_enter_simple+0x1c5/0x235 >>>>> [<ffffffffa00564b2>] :processor:acpi_idle_enter_simple+0x1bb/0x235 >>>>> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 >>>>> [<ffffffff803fbce7>] cpuidle_idle_call+0xd7/0x120 >>>>> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 >>>>> [<ffffffff803fbc10>] cpuidle_idle_call+0x0/0x120 >>>>> [<ffffffff80209410>] default_idle+0x0/0x50 >>>>> [<ffffffff8020a720>] cpu_idle+0x60/0xd0 >>>>> > > Hmm... This shouldn't happen. Can you please attach full kernel log > including the boot messages? > > Thanks. > > Hi, here is attached the full kernel log. It seems something is happening with ath5k module ? Regards, Todor [-- Attachment #2: kernel.log.gz --] [-- Type: application/gzip, Size: 33804 bytes --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: bug report 2008-09-29 8:30 ` Todor Gyumyushev @ 2008-09-30 11:47 ` Tejun Heo 0 siblings, 0 replies; 7+ messages in thread From: Tejun Heo @ 2008-09-30 11:47 UTC (permalink / raw) To: Todor Gyumyushev Cc: Simon Holm Thøgersen, Jens Axboe, Albert Lee, linux-kernel, linux-ide Todor Gyumyushev wrote: >> Hmm... This shouldn't happen. Can you please attach full kernel log >> including the boot messages? >> >> Thanks. >> >> > Hi, here is attached the full kernel log. > It seems something is happening with ath5k module ? Does the problem occur w/o ath5k? I don't really see how ata_piix can trigger the WARN_ON(). Thanks. -- tejun ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <CAL=PgHMH=5A5rLaO=RvYYA8MmcKEt1zay7f2=SS83RYayVVh+w@mail.gmail.com>]
* Re: Bug report [not found] <CAL=PgHMH=5A5rLaO=RvYYA8MmcKEt1zay7f2=SS83RYayVVh+w@mail.gmail.com> @ 2012-08-20 22:43 ` Randy Dunlap 2012-08-20 23:16 ` Alan Cox 2012-08-21 9:37 ` Borislav Petkov 1 sibling, 1 reply; 7+ messages in thread From: Randy Dunlap @ 2012-08-20 22:43 UTC (permalink / raw) To: mr.shroom; +Cc: linux-kernel, linux-ide (cc-ing linux-ide mailing list) On 08/20/2012 03:31 PM, mr.shroom wrote: > SATA for kernel(s) 3.5+ has an issue with IRQ Balancing on AMD SB710 > with motherboard ASRock m3a770d3. > > The problem started while using Arch linux, after going back to Debian > it persisted. I had tried to find problems with the bug but couldn't > find any direct help online. I had a break when finding similar bugs > on other sites stating that IRQ Balancing might be the fault. So I > tried ACPI_IRQ_NOBALANCE in the kernel boot parameters and so far the > issue has stopped. > > Linux version 3.6.0-rc2 (mboy@debian) (gcc version 4.7.1 (Debian > 4.7.1-6) ) #1 SMP Sat Aug 18 00:46:06 CDT 2012 > > Aug 20 12:32:08 debian kernel: [42238.075368] ata4.00: exception Emask > 0x0 SAct 0x7f SErr 0x0 action 0x6 frozen > Aug 20 12:32:08 debian kernel: [42238.075373] ata4.00: failed command: > WRITE FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075377] ata4.00: cmd > 61/08:00:c8:0a:89/00:00:01:00:00/40 tag 0 ncq 4096 out > Aug 20 12:32:08 debian kernel: [42238.075377] res > 40/00:00:00:4f:c2/00:00:00:4f:c2/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075379] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075381] ata4.00: failed command: > WRITE FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075384] ata4.00: cmd > 61/08:08:f8:cb:8a/00:00:03:00:00/40 tag 1 ncq 4096 out > Aug 20 12:32:08 debian kernel: [42238.075384] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075386] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075388] ata4.00: failed command: > WRITE FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075391] ata4.00: cmd > 61/10:10:80:95:86/00:00:08:00:00/40 tag 2 ncq 8192 out > Aug 20 12:32:08 debian kernel: [42238.075391] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075393] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075394] ata4.00: failed command: > READ FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075397] ata4.00: cmd > 60/60:18:60:71:62/00:00:00:00:00/40 tag 3 ncq 49152 in > Aug 20 12:32:08 debian kernel: [42238.075397] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075399] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075401] ata4.00: failed command: > READ FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075404] ata4.00: cmd > 60/08:20:c8:71:62/00:00:00:00:00/40 tag 4 ncq 4096 in > Aug 20 12:32:08 debian kernel: [42238.075404] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075406] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075407] ata4.00: failed command: > READ FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075410] ata4.00: cmd > 60/18:28:d8:71:62/00:00:00:00:00/40 tag 5 ncq 12288 in > Aug 20 12:32:08 debian kernel: [42238.075410] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075412] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075413] ata4.00: failed command: > READ FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075417] ata4.00: cmd > 60/08:30:f8:71:62/00:00:00:00:00/40 tag 6 ncq 4096 in > Aug 20 12:32:08 debian kernel: [42238.075417] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075418] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075422] ata4: hard resetting link > > After it would reset, it would try SATA I, fail, then mount the drive > as RO. I'm running a Phenom II on Debian Wheezy with a bit of Sid, > don't have the time at the moment to get a better grasp on what you > need for a proper bug report but I hope this helps. > -- -- ~Randy ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Bug report 2012-08-20 22:43 ` Bug report Randy Dunlap @ 2012-08-20 23:16 ` Alan Cox 0 siblings, 0 replies; 7+ messages in thread From: Alan Cox @ 2012-08-20 23:16 UTC (permalink / raw) To: Randy Dunlap; +Cc: mr.shroom, linux-kernel, linux-ide On Mon, 20 Aug 2012 15:43:35 -0700 Randy Dunlap <rdunlap@xenotime.net> wrote: > (cc-ing linux-ide mailing list) Classic "no IRQ being delivered" - looks like a platform IRQ routing problem ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Bug report [not found] <CAL=PgHMH=5A5rLaO=RvYYA8MmcKEt1zay7f2=SS83RYayVVh+w@mail.gmail.com> 2012-08-20 22:43 ` Bug report Randy Dunlap @ 2012-08-21 9:37 ` Borislav Petkov 1 sibling, 0 replies; 7+ messages in thread From: Borislav Petkov @ 2012-08-21 9:37 UTC (permalink / raw) To: mr.shroom; +Cc: linux-kernel, linux-ide Adding linux-ide. Please send also full dmesg of the box. Thanks. On Mon, Aug 20, 2012 at 05:31:44PM -0500, mr.shroom wrote: > SATA for kernel(s) 3.5+ has an issue with IRQ Balancing on AMD SB710 > with motherboard ASRock m3a770d3. > > The problem started while using Arch linux, after going back to Debian > it persisted. I had tried to find problems with the bug but couldn't > find any direct help online. I had a break when finding similar bugs > on other sites stating that IRQ Balancing might be the fault. So I > tried ACPI_IRQ_NOBALANCE in the kernel boot parameters and so far the > issue has stopped. > > Linux version 3.6.0-rc2 (mboy@debian) (gcc version 4.7.1 (Debian > 4.7.1-6) ) #1 SMP Sat Aug 18 00:46:06 CDT 2012 > > Aug 20 12:32:08 debian kernel: [42238.075368] ata4.00: exception Emask > 0x0 SAct 0x7f SErr 0x0 action 0x6 frozen > Aug 20 12:32:08 debian kernel: [42238.075373] ata4.00: failed command: > WRITE FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075377] ata4.00: cmd > 61/08:00:c8:0a:89/00:00:01:00:00/40 tag 0 ncq 4096 out > Aug 20 12:32:08 debian kernel: [42238.075377] res > 40/00:00:00:4f:c2/00:00:00:4f:c2/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075379] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075381] ata4.00: failed command: > WRITE FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075384] ata4.00: cmd > 61/08:08:f8:cb:8a/00:00:03:00:00/40 tag 1 ncq 4096 out > Aug 20 12:32:08 debian kernel: [42238.075384] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075386] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075388] ata4.00: failed command: > WRITE FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075391] ata4.00: cmd > 61/10:10:80:95:86/00:00:08:00:00/40 tag 2 ncq 8192 out > Aug 20 12:32:08 debian kernel: [42238.075391] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075393] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075394] ata4.00: failed command: > READ FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075397] ata4.00: cmd > 60/60:18:60:71:62/00:00:00:00:00/40 tag 3 ncq 49152 in > Aug 20 12:32:08 debian kernel: [42238.075397] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075399] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075401] ata4.00: failed command: > READ FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075404] ata4.00: cmd > 60/08:20:c8:71:62/00:00:00:00:00/40 tag 4 ncq 4096 in > Aug 20 12:32:08 debian kernel: [42238.075404] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075406] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075407] ata4.00: failed command: > READ FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075410] ata4.00: cmd > 60/18:28:d8:71:62/00:00:00:00:00/40 tag 5 ncq 12288 in > Aug 20 12:32:08 debian kernel: [42238.075410] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075412] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075413] ata4.00: failed command: > READ FPDMA QUEUED > Aug 20 12:32:08 debian kernel: [42238.075417] ata4.00: cmd > 60/08:30:f8:71:62/00:00:00:00:00/40 tag 6 ncq 4096 in > Aug 20 12:32:08 debian kernel: [42238.075417] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Aug 20 12:32:08 debian kernel: [42238.075418] ata4.00: status: { DRDY } > Aug 20 12:32:08 debian kernel: [42238.075422] ata4: hard resetting link > > After it would reset, it would try SATA I, fail, then mount the drive > as RO. I'm running a Phenom II on Debian Wheezy with a bit of Sid, > don't have the time at the moment to get a better grasp on what you > need for a proper bug report but I hope this helps. > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Regards/Gruss, Boris. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-08-21 9:37 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <48DA0B39.5050401@saturnosoft.biz>
[not found] ` <1222274317.14959.4.camel@odie.local>
[not found] ` <48DA7F1E.5030508@saturnosoft.biz>
2008-09-24 18:25 ` bug report Simon Holm Thøgersen
2008-09-29 1:36 ` Tejun Heo
2008-09-29 8:30 ` Todor Gyumyushev
2008-09-30 11:47 ` Tejun Heo
[not found] <CAL=PgHMH=5A5rLaO=RvYYA8MmcKEt1zay7f2=SS83RYayVVh+w@mail.gmail.com>
2012-08-20 22:43 ` Bug report Randy Dunlap
2012-08-20 23:16 ` Alan Cox
2012-08-21 9:37 ` Borislav Petkov
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).