FS#33052 - [linux] 3.6.x ATA bus error frozen fatal

Attached to Project: Arch Linux
Opened by Sarah Knappisch (umcomue) - Tuesday, 11 December 2012, 20:47 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 January 2013, 16:08 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Arch Linux Live CD ends in errors.
Mounting '/dev/disk/by-label/ARCH_201212' to 'run/archiso/bootmnt/'
[ 34.439272] ata2.00:exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
[ 34.....] ata2: SError ( RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHyInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[ 34.....] ata2.00: failed command: IDENTIFY PACKET DEVICE
[ 34 ....] ata2..00 cmd a1/00:01:00:00:00/00:00:00:0000/00 tag 0 pio 512 in
[ 34.....] res 40/0002:00.................. Emask 0x56 (ATA bus error)
[ 34 ....] ata2.00 status {DRDY}



Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 23 January 2013, 16:08 GMT
Reason for closing:  Upstream
Comment by Greg (gm25flew) - Wednesday, 12 December 2012, 00:34 GMT
I've heard of this error with a few different things.
1. Bad SATA cable
2. PSU problems (not enough wattage)
3. Corrupted sector on disk
Comment by Demonseed (Demonseed) - Friday, 14 December 2012, 22:37 GMT
Had same error, and for multiple kernel versions through 3.4.X to 3.6.10.

Removed the PCI Bus Power management in BIOS and all works well now. (on a laptop T500 Lenovo).

Hope this helps for now.
Comment by Alexander F. Rødseth (xyproto) - Saturday, 15 December 2012, 16:35 GMT
djgera, hope it's ok that I assigned this one to you
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 15 December 2012, 20:09 GMT
Nothing to do here, hardware problem or upstream bug (Linux) or firmware config/bug issue.

Loading...