Multiple ATA Exception Emask, NCQ disabled etc during boot

Bug #353812 reported by Markus Kilås
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

During boot I get several error messages like this below on my new laptop:

ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
ata1.00: cmd 60/08:00:0f:0a:74/00:00:02:00:00/40 tag 0 ncq 4096 in
  res 50/00:b8:df:08:0d/00:00:00:00:00/40 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY }

Sometimes there is just a few and after some time the boot continues and I can use the laptop but more often the messages repeats and the boot finally ends with the root partition mounted as read-only.

With dmesg I can also see that I got:
ata1.00: NCQ disabled due to excessive errors
ata1: hard resetting link

And a lot of this (but this might be an other issue):
ACPI: Transitioning device [FAN] to D3
ACPI: Unable to turn cooling device [ffff88013fa3aec0] 'off'

System:
Ubuntu 8.10
Linux markuz 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux
Laptop: Zepto Nox A15
Harddrive: Hitachi HTS72322

Revision history for this message
Markus Kilås (markuskilas) wrote :
Revision history for this message
Markus Kilås (markuskilas) wrote :
Revision history for this message
Markus Kilås (markuskilas) wrote :
Revision history for this message
Markus Kilås (markuskilas) wrote :
Revision history for this message
Markus Kilås (markuskilas) wrote :

I changed the BIOS setting from AHCI to ATA and now I can boot Ubuntu and there is no Emask exceptions in the syslog. This works for me right now but shouldn't AHCI work?

Revision history for this message
prerik (pererik-eriksson) wrote :

I have had the same problem with my Nox A15. I described the problem to Zepto chat support and I got the advice to change BIOS setting to IDE. That seems to have solved my problem.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Markus,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you 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 353812

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: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Donn Morrison (donn-morrison) wrote :

Hi, I am having this issue on an Acer Aspire 1810TZ with a fresh 10.04 install (kernel version 2.6.32-19-generic #28-Ubuntu). Boot is very slow and dmesg shows it is stuck after mounting the root partition with messages as described in the original report.

...
[ 1.452734] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.452925] sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
[ 1.516595] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.554650] usb 6-2: configuration #1 chosen from 1 choice
[ 1.772114] ata2: SATA link down (SStatus 0 SControl 300)
[ 2.108112] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.444135] ata6: SATA link down (SStatus 0 SControl 300)
[ 3.272334] EXT4-fs (sda6): mounted filesystem with ordered data mode
[ 33.804129] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[ 33.804136] ata1.00: failed command: READ FPDMA QUEUED
[ 33.804146] ata1.00: cmd 60/20:00:3e:7c:96/00:00:06:00:00/40 tag 0 ncq 16384 in
[ 33.804154] res 40/00:08:38:88:17/00:00:24:00:00/40 Emask 0x4 (timeout)
[ 33.804159] ata1.00: status: { DRDY }
[ 33.804166] ata1: hard resetting link
[ 34.288113] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 34.289656] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 34.289919] ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) succeeded
[ 34.290167] ata1.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) succeeded
[ 34.290173] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 34.290434] ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) succeeded
[ 34.290689] ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
...

I resolved the problem by changing from AHCI to IDE in the laptop's BIOS.

Revision history for this message
Anton Zayats (anton-zayats) wrote :

Copied from #539467 bug.
I have the same problem:
Multiple ata1.00 errors even when pc is idle on Gigabyte GA-E7AUM-DS2H motherboard.
One disk already is dead (Seagate) - it was on Jaunty.
The next was going down (WD) on 10.04 fresh minimal install with nvidia proprietary drivers.
Switching off AHCI from bios worked for me as well.
More reports about this issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/217920
http://www.nvnews.net/vbulletin/showthread.php?t=126152

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
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.