ata1: exception Emask 0x10 SAct 0x0 SErr 0x1990000 action 0xe frozen

Bug #1002256 reported by knapx
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux Mint
New
Undecided
Unassigned

Bug Description

problem found
With MCP7A Controller Nvidia chipset (ATOM / ION Platform), mini-ITX
AMI BIOS -> N1012WZT.rom - release12 October 2009

Creates many problems connecting hard disk SSD OCZ Agility 3
Consequent block of the entire operating system and reboot and errors created the filesystem (ext3-ext4).

Total instability detected using the motherboard:
Zotac IONITX FE - (MCP7A Controller Nvidia chipset)
SSD 60GB OCZ Agility 3 - (Sata Cable Short - Bios Settings AHCI)

Using Hard Disk to Another Motherboard:
ASUS P5E - (Controller Intel ICH9 Chipset)
ASROCK PV530 - (Chipset - VIA VX900)
I have not found any error in communication and / or instability of the operating system.

Can I assume that it is a form of Kernel Bugs, which manages the Controller MCP7A Nvidia chipset.

Please you to make changes readily resolutive this drawback ...

Best Regards

Complete Log ==>> http://pastebin.com/YGD3wCmm

[ 326.023319] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1990000 action 0xe frozen
[ 326.023329] ata1: irq_stat 0x00400000, PHY RDY changed
[ 326.023338] ata1: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns }
[ 326.023350] ata1: hard resetting link
[ 326.744046] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 326.765644] ata1.00: configured for UDMA/100
[ 326.766071] ata1: EH complete
[ 334.383910] ata1.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x1990000 action 0xe frozen
[ 334.383925] ata1.00: irq_stat 0x08400000, interface fatal error, PHY RDY changed
[ 334.383939] ata1: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns }
[ 334.383952] ata1.00: failed command: WRITE FPDMA QUEUED
[ 334.383975] ata1.00: cmd 61/c0:00:20:4c:56/01:00:03:00:00/40 tag 0 ncq 229376 out
[ 334.383979] res 40/00:b8:00:7d:56/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
[ 334.383991] ata1.00: status: { DRDY }
[ 334.384001] ata1.00: failed command: WRITE FPDMA QUEUED
[ 334.384052] ata1.00: cmd 61/08:08:f0:4d:56/00:00:03:00:00/40 tag 1 ncq 4096 out
[ 334.384057] res 40/00:b8:00:7d:56/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
[ 334.384068] ata1.00: status: { DRDY }
[ 334.384077] ata1.00: failed command: WRITE FPDMA QUEUED
[ 334.384096] ata1.00: cmd 61/00:10:00:4e:56/04:00:03:00:00/40 tag 2 ncq 524288 out
[ 334.384100] res 40/00:b8:00:7d:56/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: knap 1716 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfab78000 irq 23'
   Mixer name : 'Nvidia MCP79/7A HDMI'
   Components : 'HDA:10ec0662,19daa108,00100101 HDA:10de0007,10de0101,00100100'
   Controls : 42
   Simple ctrls : 21
DistroRelease: LinuxMint 13
HibernationDevice: RESUME=UUID=ab3786a8-24af-4eb8-bc41-761f035267e2
InstallationMedia: Linux Mint 13 "Maya" - Release i386 (20120520)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 002: ID 045e:00f9 Microsoft Corp. Wireless Desktop Receiver 3.1
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: tbs6981fe
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=533b4514-fa82-4470-bbcf-6f2b7e58f2da ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: maya
Uname: Linux 3.2.0-24-generic i686
UnreportableReason: Questo non è un pacchetto ufficiale di LinuxMint. Rimuovere tutti i pacchetti di terze parti, quindi riprovare.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/12/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
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.:bvr080015:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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.

knapx (knapx)
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1002256

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
knapx (knapx)
Changed in linux (Ubuntu):
status: Incomplete → New
status: New → Confirmed
Revision history for this message
knapx (knapx) wrote : AcpiTables.txt

apport information

tags: added: apport-collected maya
description: updated
Revision history for this message
knapx (knapx) wrote : AlsaDevices.txt

apport information

Revision history for this message
knapx (knapx) wrote : AplayDevices.txt

apport information

Revision history for this message
knapx (knapx) wrote : ArecordDevices.txt

apport information

Revision history for this message
knapx (knapx) wrote : BootDmesg.txt

apport information

Revision history for this message
knapx (knapx) wrote : CRDA.txt

apport information

Revision history for this message
knapx (knapx) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
knapx (knapx) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
knapx (knapx) wrote : Card0.Codecs.codec.3.txt

apport information

Revision history for this message
knapx (knapx) wrote : CurrentDmesg.txt

apport information

Revision history for this message
knapx (knapx) wrote : IwConfig.txt

apport information

Revision history for this message
knapx (knapx) wrote : Lspci.txt

apport information

Revision history for this message
knapx (knapx) wrote : PciMultimedia.txt

apport information

Revision history for this message
knapx (knapx) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
knapx (knapx) wrote : ProcInterrupts.txt

apport information

Revision history for this message
knapx (knapx) wrote : ProcModules.txt

apport information

Revision history for this message
knapx (knapx) wrote : PulseList.txt

apport information

Revision history for this message
knapx (knapx) wrote : UdevDb.txt

apport information

Revision history for this message
knapx (knapx) wrote : UdevLog.txt

apport information

Revision history for this message
knapx (knapx) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you know if this issue happened in a previous version of Ubuntu, or is this a new issue?

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-precise/

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

I Downloaded and installed the kernel you suggested:

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

I slightly improved the situation of instability of the system ...

But there are still de crash related to the same communication problem.

Prior to these crashes with kernel 3.2 occurred after 10 ~ 20 minutes from boot OS ... Now these crashes occur with kernel 3.4 after 60 ~ 90 minutes from boot OS.

Current Dmesg Log -->> http://pastebin.com/QJtFGCPm

Best Regards

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Logan Rosen (logan)
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Expired → Confirmed
penalvch (penalvch)
affects: linux (Ubuntu) → linuxmint
Changed in linuxmint:
importance: Medium → Undecided
status: Confirmed → New
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.