ata1.00: failed command: READ FPDMA QUEUED, on boot

Bug #981465 reported by PieroCampa
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Sometimes I get very long boots due to error on sda5 partition (see attached dmseg). E.g. :

    ...
    [ 29.284082] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
    ...
    [ 279.804433] ata1.00: failed command: READ FPDMA QUEUED
    [ 279.804438] ata1.00: cmd 60/00:e8:00:34:c6/04:00:10:00:00/40 tag 29 ncq 524288 in
    [ 279.804439] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 279.804445] ata1.00: status: { DRDY }
    [ 279.804448] ata1.00: failed command: READ FPDMA QUEUED
    [ 279.804453] ata1.00: cmd 60/00:f0:00:50:c6/04:00:10:00:00/40 tag 30 ncq 524288 in
    [ 279.804454] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 279.804460] ata1.00: status: { DRDY }
    [ 279.804465] ata1: hard resetting link
    [ 280.296180] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 280.301566] ata1.00: configured for UDMA/133
    [ 280.301573] ata1.00: device reported invalid CHS sector 0
    [ 280.301576] ata1.00: device reported invalid CHS sector 0
    [ 280.301580] ata1.00: device reported invalid CHS sector 0
    ...

Running W7 + Ubuntu Oneiric (LXDE) on Dell XPS Studio 1640 Laptop, with following HDD:

    ATA device, with non-removable media
    Model Number: WDC WD3200BJKT-75F4T0
    Serial Number: WD-WXM209AS1908
    Firmware Revision: 11.01A11
    Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5

When this READ error does not happen, the boot is still generally quite long (~1 min.), sda5 partition is always re-mounted two times during boot, e.g.

    ...
    [ 4.724127] EXT4-fs (sda5): INFO: recovery required on readonly filesystem
    [ 4.724134] EXT4-fs (sda5): write access will be enabled during recovery
    [ 29.260329] EXT4-fs (sda5): recovery complete
    [ 29.284082] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
    ...
    [ 352.896213] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
    ...
    [ 383.332436] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
    ...

Further info:

    > sudo fdisk -l
    Device Boot Start End Blocks Id System
    /dev/sda1 63 610469 305203+ de Dell Utility
    /dev/sda2 612352 32069631 15728640 7 HPFS/NTFS/exFAT
    /dev/sda3 * 32069632 238979788 103455078+ 7 HPFS/NTFS/exFAT
    /dev/sda4 238983166 625141759 193079297 5 Extended
    /dev/sda5 238983168 612630527 186823680 83 Linux
    /dev/sda6 612632576 625141759 6254592 82 Linux swap / Solaris

Thanks for all your work to help us.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-17-generic 3.0.0-17.30
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: piero 2363 F.... pulseaudio
 /dev/snd/controlC0: piero 2363 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc400000 irq 48'
   Mixer name : 'IDT 92HD73C1X5'
   Components : 'HDA:111d7675,10280272,00100103'
   Controls : 16
   Simple ctrls : 10
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfeec000 irq 49'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Sat Apr 14 11:07:46 2012
HibernationDevice: RESUME=UUID=7c9071cc-b77b-40da-9f80-6b8a9a220cb1
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Studio XPS 1640
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic root=UUID=b33be99b-5c9e-449e-ad48-be608aeff001 ro
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-17-generic N/A
 linux-backports-modules-3.0.0-17-generic N/A
 linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2012-01-14 (90 days ago)
WifiSyslog:

dmi.bios.date: 04/09/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0U785D
dmi.board.vendor: Dell Inc.
dmi.board.version: A15
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A15
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15:
dmi.product.name: Studio XPS 1640
dmi.product.version: A153
dmi.sys.vendor: Dell Inc.

Revision history for this message
PieroCampa (piero-campa) wrote :
description: updated
description: updated
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
PieroCampa (piero-campa) wrote :

Joseph,
so I downloaded

    linux-headers-3.4.0-030400rc3_3.4.0-030400rc3.201204152235_all.deb
    linux-headers-3.4.0-030400rc3-generic_3.4.0-030400rc3.201204152235_amd64.deb
    linux-image-3.4.0-030400rc3-generic_3.4.0-030400rc3.201204152235_amd64.deb

but the installation threw some windows regarding system problems, as well as problems with upgrade of virtualbox.
Take a look at the attached file.

May I try to boot that kernel anyway or will I encounter problems?
Thanks

Revision history for this message
PieroCampa (piero-campa) wrote :

So, I am booting with the linux-image-3. 3.4.0-030400rc kernel.
Attached you can find a dmesg sample.

Since the behaviour is not reproduciblle I will wait some days to see if some problem arises.

Revision history for this message
penalvch (penalvch) wrote :

PieroCampa, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-a15
Revision history for this message
PieroCampa (piero-campa) wrote :

A long time I don't observe this issue anymore.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise

$ uname --kernel-name --kernel-release
Linux 3.2.0-57-generic

Revision history for this message
penalvch (penalvch) wrote :

PieroCampa, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/981465/comments/6 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.