Sata exeption Emask failed command READ FPDMA QUEUED

Bug #588439 reported by James Thomas on 2010-06-01
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

I have been getting this error under high IO first with Lucid kernel 2.6.32-22-server. Everything was fine when the server was running karmic.

There are plenty of these errors during boot, but they only reappeared doing a RAID5 check. Also using iotop, the check isn't displayed as IO though cat /proc/mdstat shows the drives slowly checking.

Right now it seems to be performance related only, but that is yet to be seen.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-server 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-server x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Tue Jun 1 13:51:54 2010
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 002: ID 0665:5161 Cypress Semiconductor USB to Serial
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PciMultimedia:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-server root=UUID=e7ecb262-837d-49ef-b60e-c1663eb6e848 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux
dmi.bios.date: 04/24/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: K10N78M
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd04/24/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnK10N78M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

James Thomas (thomasjj) wrote :
Jeremy Foshee (jeremyfoshee) wrote :

Hi James,

If you could also please 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
James Thomas (thomasjj) wrote :

Unattended updates updated the kernel and now I cannot reproduce the bug. It is either gone or inconsistent now.

James Thomas (thomasjj) wrote :

However mdadm still doesn't show up in iotop where it used to under karmic

James,

I'm seeing similar symptoms under 2.6.32-22-server ; which kernel are you running now ?

my specs:

System:Supermicro X7SPA-HF, 1 x Atom D510 1.66GHz, 2GB / 2GB 667MHz DDR2
Disk: md0 (md): 8.0TB (0%) SW-RAID-5 == partitions: sdb, sdc, sdd, sde, sdf
Disk: sda (scsi0): 320GB (7%) JBOD == 1 x 320GB SATA 300MB/s WDC-WD3200BEVT-11ZCT0
Disk: sdb (scsi1): 2.0TB (0%) JBOD == 1 x 2TB SATA 300MB/s SAMSUNG-HD203WI
Disk: sdc (scsi2): 2.0TB (0%) JBOD == 1 x 2TB SATA 300MB/s SAMSUNG-HD203WI
Disk: sdd (scsi3): 2.0TB (0%) JBOD == 1 x 2TB SATA 300MB/s SAMSUNG-HD203WI
Disk: sde (scsi4): 2.0TB (0%) JBOD == 1 x 2TB SATA 300MB/s SAMSUNG-HD203WI
Disk: sdf (scsi5): 2.0TB (0%) JBOD == 1 x 2TB SATA 300MB/s SAMSUNG-HD203WI
Disk-Control: ahci0: Intel ICH9 82801I 6 Port SATA/300 AHCI
Chipset: Intel 82801IR A2 (ICH9R)

James Thomas (thomasjj) wrote :

Kernel: 2.6.32-22-server

I still haven't had a recurrence of this bug with this kernel and I've been pushing the system to try too.

@Peter: How did you output your specs like that? Everything I do is much more detailed and not as easy to read.

James Thomas (thomasjj) wrote :

The actual kernel package is 2.6.32-22.36 and I'm running the x86_64 version.

James,

The output is from a custom script i wrote that uses dmidecode and a bunch of other system tools.

Seems like my problem was due to a lack of power going to the box - I replaced my PSU with a more powerful one and the problem went away.

I hope that you've made some progress too.

Cheers

p

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 development release http://cdimage.ubuntu.com/daily-live/current/ . 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
Angel Guzman Maeso (shakaran) wrote :

I have this issue with Ubuntu 10.10 fully updated. I make a update to 11.04 development distribution and it don't solve the issue.

Then I fully reinstall my system except /home (I have two ext4 partitions / and /home). With

Linux steros 2.6.35-23-generic-pae #41-Ubuntu SMP Wed Nov 24 10:35:46 UTC 2010 i686 GNU/Linux

I dont have the issue anymore. I am updating now the packages for see when and the exact package produce the issue, but this is a huge regression, the system it is unusable for the timeouts (20-30 secondw each time).

PS: A note: When a bug is expired without find solution make a bad impression for the reporters that hopes find a response or fix.

Changed in linux (Ubuntu):
status: Expired → New
IKT (ikt) on 2011-04-04
Changed in linux (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Redsandro (redsandro) wrote :

This could be a duplicate of or related to bug #550559 .

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers