ata2 exception EMask delays/prevents booting 9.04 & 8.10

Bug #379831 reported by tokyoahead
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Arch Linux)
New
Undecided
Unassigned
linux (Fedora)
New
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Release: 9.04
Installed from the LiveCD, worked fine. When then booting from the HD w/o interaction, the PC freezes after the ubuntu progressbar is displayed with a black screen.

If I press CTRL-ALT-F1 as soon as the progress-bar screen appears I can see many error messages from ATA2 similar to:

[ 35.845586] ata2.00: exception Emask 0x2 SAct 0x6de SErr 0x3000400 action 0x6
[ 35.845636] ata2.00: irq_stat 0x45000008
[ 35.845678] ata2: SError: { Proto TrStaTrns UnrecFIS }
[ 35.845737] ata2.00: cmd 60/40:08:20:08:a0/00:00:01:00:00/40 tag 1 ncq 32768 in
[ 35.845739] res 50/00:07:ba:d6:42/00:00:25:00:00/40 Emask 0x2 (HSM violation)

along with a timeout message

after some time these meessages stop. I can then press ENTER and {initramfs} shows up. I enter EXIT and then some more progress messages come, then finally the system boots up.

Hardware (as reported by vista):

Acer Timeline 3810T
HD Hitachi HTS545032B9A300
Intel ICH9M-E/M SATA AHCI Controller

I also tried to install 8.10 and 9.04 with http://unetbootin.sourceforge.net/, but then I cannot even boot into the system anymore, the same error messages come up.

DMESG is attached.

switching the SATA mode frm AHCI to IDE prevents the issue overall. I consider this a workaround however and not a solution, since this disables any pre-installed Vista setup.

additionally, booting with "libata.noacpi=1" in the kernel line also resolves the issue

tokyoahead (tokyoahead)
description: updated
tags: added: acer ahci sata
tokyoahead (tokyoahead)
description: updated
tags: added: acpi
Revision history for this message
eventhorizon (eventhorizon42) wrote :

confirmed
Acer Timeline 3810T (Core 2 Solo)
BIOS: 1.04
Ubuntu 9.04 64

Revision history for this message
red-naxela (red-naxela) wrote :

I found out that it is also possible to use the libata option "force=noncq". It may be implemented under Debian (and Ubuntu perhaps too, I don't have it so please verify) by adding the line

libata force=noncq

to the file "/etc/initramfs-tools/modules" and then doing a "update-initramfs -u".
Further more I created a new file "options.conf" in the directory "/etc/modprobe.d" with the line

options libata force=noncq

in it and then rebooted. My linux then booted without the mysterious SATA errors in AHCI mode. I have a Hitachi Disk HTS545032B9A300 in my 3810T.

I don't know which option is better "libata noacpi=1" or "libata force=noncq". Found the clue for disabling NCQ on a website: http://lkml.indiana.edu/hypermail/linux/kernel/0706.1/0237.html .Probably not all hard disk drives support the NCQ (Native command queuing, see Wikipedia http://en.wikipedia.org/wiki/Native_command_queuing). If someone knows more, thanks for telling me.

Remark: For adding the kernel boot parameters it did not work for me to just add "libata.force=noncq" or "libata.noacpi=1" to the grub parameters. It did not recognize the option and ignored it. This is why I did the "more complicated" way described above, works also if you prefer using the noacpi=1 variant.

Revision history for this message
Klaus Wölfel (k-woelfel) wrote :

I can confirm that. Booting with "libata.force=noncq" in the grub parameters also works with my 3810t

Revision history for this message
eventhorizon (eventhorizon42) wrote :

Confirm "libata.force=noncq" works on my 3810T.

Revision history for this message
Klaus Wölfel (k-woelfel) wrote :

I'm not sure if libata.force=noncq was a good idea. After some day I had some strange "clacking" noises from time to time, also crashes with filesystem error . With the clacking noises came kernel messages with "ata.. something, but I don't rember what it was exactly sorry.

So now I went back to using libata.noacpi=1

Revision history for this message
Klaus Wölfel (k-woelfel) wrote :

please ignore my last comment. libata.force=noncq was not the reason for my drive going offline. The reason seemd to be that I was running the 3810t without the battery.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi All,

First I'm reassigning this to the "linux (Ubuntu)" kernel package. It's important to make sure you file your bugs against a specific package and not Ubuntu as a whole to make sure the appropriate teams and developers are notified. For more information take a look at https://wiki.ubuntu.com/Bugs/FindRightPackage .

Another workaround that may also work here is using the "all_generic_ide" boot parameter.

Most importantly, it would be great if anyone here could confirm this issue remains with both the actively developed kernel for Karmic as well as the latest Mainline kernel build. ISO CD images with the recent Karmic kernel are available for testing at http://cdimage.ubuntu.com/releases/ . If the issue remains, please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.:

apport-collect -p linux 379831

Also, if you could test the latest Mainline kernel build available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

Thanks in advance.

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-kernel-logs needs-upstream-testing
Revision history for this message
Ziggi (sihelset) wrote :

Maybe this is confusing, but:

Installed Dualboot vista/Ubuntu 9.04 amd64 on ACER Timeline 3810T (bios 1.08). Did not change anything in bios, i.e. still SATA AHCI mode. Worked fine (except wired network card, but thats another story).
Updated to latest kernel(i.e. from 2.6.28-11 ->13), tried to reboot. Failed due to / was still busy, not able to kill all remaining processes.
Did a hard reset and rebooted. Ok, succeeded.
-> seems ok with the harddisk

Revision history for this message
OliverWeiss (olivier-blanc-gmail) wrote :

Hi all,
I installed KK alpha 3 using UNetBootin yesterday evening, and it works well. Do you need any log data?

Revision history for this message
almozavr (almozavr) wrote :

No matter what kernel I used the only one issue worked for me.

From log file it's true to know that ncq hdd feature doesn't work in AHCI mode. So the solution is disable ncq.

Do it by adding to kernel string "libata.force=noncq" in /boot/grub/menu.lst.

Worked fine on Jaunty with kernels 2.6.28, 2.6.30 and 2.6.31 (Karmic Koala)! Good Luck ;)

Revision history for this message
Tom Pringle (thomas-b-pringle) wrote : apport-collect data

Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a102,00100101'
   Controls : 37
   Simple ctrls : 20
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=2d473b4b-a6ed-4a25-972f-c25e36d4472c
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-UD4P
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-6-generic root=UUID=3678fa80-4a1e-47cb-bf3a-a4a6042c3955 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
RelatedPackageVersions: linux-firmware 1.16
RfKill:

Uname: Linux 2.6.31-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WifiSyslog:

dmi.bios.date: 03/02/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-MA790X-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/02/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790X-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790X-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA790X-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :
Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :

As you can see from the spew above I can see this bug on the very latest karmic kernel

Linux doggie 2.6.31-6-generic #25-Ubuntu SMP Fri Aug 14 16:25:04 UTC 2009 i686 GNU/Linux

and I ran:

apport-collect -p linux 379831

Hope this helps resolve the problem. Please let me know if there are debug experiments I can perform.

Thanks,
Tom

Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :

Is this the right place to file this problem?

Extracting part of the dmesg log file... You can see that the ATA logic appears to report lost interrupts during DMA operation which causes it to sequentially try slower DMA modes until it finally arrives at a PIO mode that works. This process appears to take approximately 40 seconds (boot time feels much longer).

After looking at this further, it is not clear to me that this is the same cause as the one which created this bug but merely the similar log dump text (exception Emask) and certainly the same symptom (delayed booting)

Perhaps forcing the device connected to ata7 to PIO from the start would work around this problem? Perhaps this can be configured in the bios. I will experiment this weekend.

[ 22.780016] ata7: lost interrupt (Status 0x7f)
[ 22.784002] ata7: drained 32768 bytes to clear DRQ.
[ 22.862739] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 22.862786] ata7.00: cmd a0/01:00:00:60:00/00:00:00:00:00/a0 tag 0 dma 96 in
[ 22.862787] cdb 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
[ 22.862788] res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 22.862900] ata7.00: status: { DRDY }
[ 22.862956] ata7: soft resetting link
[ 23.096414] ata7.00: configured for UDMA/33
[ 23.096941] ata7: EH complete
[ 43.780021] ata7: lost interrupt (Status 0x7f)
[ 43.784002] ata7: drained 32768 bytes to clear DRQ.
[ 43.862744] ata7.00: limiting speed to UDMA/25:PIO4
[ 43.862746] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 43.862791] ata7.00: cmd a0/01:00:00:60:00/00:00:00:00:00/a0 tag 0 dma 96 in
[ 43.862792] cdb 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
[ 43.862793] res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 43.862905] ata7.00: status: { DRDY }
[ 43.862961] ata7: soft resetting link
[ 44.096414] ata7.00: configured for UDMA/25
[ 44.096940] ata7: EH complete
[ 64.780019] ata7: lost interrupt (Status 0x7f)
[ 64.784002] ata7: drained 32768 bytes to clear DRQ.
[ 64.862741] ata7.00: limiting speed to PIO4
[ 64.862743] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 64.862788] ata7.00: cmd a0/01:00:00:60:00/00:00:00:00:00/a0 tag 0 dma 96 in
[ 64.862789] cdb 12 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
[ 64.862790] res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 64.862902] ata7.00: status: { DRDY }
[ 64.862957] ata7: soft resetting link
[ 65.096414] ata7.00: configured for PIO4
[ 65.096942] ata7: EH complete

Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :

I replaced the old CDROM drive I had been using with a new driver and this problem was resolved.

Revision history for this message
Tom Pringle (thomas-b-pringle) wrote :

Clarify previous comment: This problem was resolved by replacing the old CDROM drive with a new one.

Revision history for this message
lal68 (silvamethod) wrote :

Architecture: i386
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
Package: linux (not installed)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
Uname: Linux 2.6.31-14-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1648): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1648): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1767): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1756): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

Revision history for this message
almozavr (almozavr) wrote :

FINALLY!

There is no need to add libata.force=noncq to kernel command line for normal booting with AHCI mode!

It seems to be the latest linux 2.6.32-rc6 kernel supports NCQ mode for Acer 3810T (it's all about Hitachi HDD)! Also my booting speed is 32 second now after 40 seconds on 2.6.31 kernel.

I also hope that enabling NCQ feature now will increase battery life on 3810T (now it's only 4,5 hours for me versus 7(!) on Windows 7)

Good luck ;)

Revision history for this message
Floris (fdirkzwager) wrote :

Almozavr. I have the same issue but running 2.6.16 kernel. I am a bit at loss how to update the kernel to 2.6.32-rc6. I can not find it when I run apt-cache search linux-image only 2.6.16 kernel gets listed. Can you help how to install? Sorry for the noob question.

Revision history for this message
almozavr (almozavr) wrote :

Ok, it's really easy ;)

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32-rc6/ has deb packages of fresh kernel snapshots.
All you need is downloading and installing headers and image files:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32-rc6/linux-image-2.6.32-020632rc6-generic_2.6.32-020632rc6_i386.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32-rc6/linux-headers-2.6.32-020632rc6-generic_2.6.32-020632rc6_i386.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32-rc6/linux-headers-2.6.32-020632rc6_2.6.32-020632rc6_all.deb

Then you should update your grub:

sudo update-grub

Reboot ;)

* Certainly you can compile it from sources but this way is the most simple :)

Revision history for this message
cmello (cmello) wrote :

Hi,

I own an Acer Aspire Timeline 1810TZ and had the same problem. The 2.6.32rc6 kernel didn't solve the problem for me, but I just had to change the hard-coded model 3810T to 1810TZ in the file drivers/ata/ahci.c like this:

static void ahci_gtf_filter_workaround(struct ata_host *host)
{
 static const struct dmi_system_id sysids[] = {
  /*
   * Aspire 3810T issues a bunch of SATA enable commands
   * via _GTF including an invalid one and one which is
   * rejected by the device. Among the successful ones
   * is FPDMA non-zero offset enable which when enabled
   * only on the drive side leads to NCQ command
   * failures. Filter it out.
   */
  {
   .ident = "Aspire 1810TZ",
   .matches = {
    DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
    DMI_MATCH(DMI_PRODUCT_NAME, "Aspire 1810TZ"),
   },
   .driver_data = (void *)ATA_ACPI_FILTER_FPDMA_OFFSET,
  },
  { }
 };

Then it worked great! There is a sensible performance improvement in the boot time!

Thank you very much, I hope the kernel guys figure out a more generic way to fix this.

Best regards
Mello

Revision history for this message
cmello (cmello) wrote :

PS: * The performance improvement in the boot time when using AHCI compared to IDE mode, which can be set in the BIOS setup as a workaround too.

Revision history for this message
cmello (cmello) wrote :

Upgraded the BIOS to the latest version available in the Acer web site (for Aspire 1810TZ the version is 1.3303). After upgrading the problem was gone!

Nice that Acer fixed the problem in their BIOS. But unfortunately I lost a lot of time with this, and got no help from the "community".

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi tokyoahead,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 379831

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
suzker (szhiliang) wrote :

I got the same problem on my laptop:

HP CQ35-111tx
HD Hitatchi HTS545050B9A300 (500gb version instead of 320gb version reported by tokyohead)
Intel ICH9M-E/M SATA AHCI Controller

There is no problem with the original FUJITSU MHZ2320BH G2 hard-drive.

I've tested both Ubuntu 10.04, Ubuntu 10.04.x, Ubuntu 10.10, Fedora 13/14, Arch, and same problem occurred.

adding a kernel option of libata.force=noncq before booting in to linux is a work around, but both the battery and hard-drive's performances will be poor.

Changed in linux (Ubuntu):
status: Expired → New
Revision history for this message
suzker (szhiliang) wrote :

Current kernel: Linux 2.6.45-27-generic
part of the dmesg:

[ 8.079203] sd 0:0:0:0: [sdb] Attached SCSI removable disk
[ 37.804126] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[ 37.804132] ata1.00: failed command: READ FPDMA QUEUED
[ 37.804140] ata1.00: cmd 60/80:00:b3:fe:51/00:00:26:00:00/40 tag 0 ncq 65536 in
[ 37.804141] res 40/00:02:cd:2f:03/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 37.804145] ata1.00: status: { DRDY }
[ 37.804151] ata1: hard resetting link
[ 38.288144] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 38.289535] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 38.289735] ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) succeeded
[ 38.289960] ata1.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) succeeded
[ 38.289963] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 38.290216] ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) succeeded
[ 38.290507] ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
[ 38.293245] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 38.293250] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 38.293509] ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
[ 38.293963] ata1.00: configured for UDMA/133
[ 38.293979] ata1: EH complete
[ 45.652899] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 45.696090] ISO 9660 Extensions: RRIP_1991A
[ 45.973136] aufs 2-standalone.tree-20091207
[ 46.183031] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 114.804168] ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
[ 114.804174] ata1.00: failed command: READ FPDMA QUEUED
[ 114.804181] ata1.00: cmd 60/01:00:fb:bf:4f/00:00:35:00:00/40 tag 0 ncq 512 in
[ 114.804183] res 40/00:20:89:f9:8f/00:00:2c:00:00/40 Emask 0x4 (timeout)
[ 114.804186] ata1.00: status: { DRDY }
[ 114.804190] ata1.00: failed command: READ FPDMA QUEUED
[ 114.804196] ata1.00: cmd 60/01:08:fc:bf:4f/00:00:35:00:00/40 tag 1 ncq 512 in
[ 114.804198] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 114.804201] ata1.00: status: { DRDY }
[ 114.804204] ata1.00: failed command: READ FPDMA QUEUED
[ 114.804210] ata1.00: cmd 60/01:10:fd:bf:4f/00:00:35:00:00/40 tag 2 ncq 512 in
[ 114.804212] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 114.804215] ata1.00: status: { DRDY }
[ 114.804218] ata1.00: failed command: READ FPDMA QUEUED
[ 114.804225] ata1.00: cmd 60/01:18:fe:bf:4f/00:00:35:00:00/40 tag 3 ncq 512 in
[ 114.804226] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 114.804229] ata1.00: status: { DRDY }
[ 114.804235] ata1: hard resetting link

Brad Figg (brad-figg)
tags: added: b73a1py79
Revision history for this message
Brad Figg (brad-figg) wrote :

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in supported series, please file a new bug.

Changed in linux (Ubuntu):
status: New → Won't Fix
tags: removed: b73a1py79
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.