[Bug 285892] Re: ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen

tulskiy 285892 at bugs.launchpad.net
Thu Oct 21 03:09:20 UTC 2010


My hard drive's SMART check shows that there are about 2 million Command
Timeout's and high Seek Error rate. There are two wires connected to the
plate the hard drive is connected to that seem to be the power cables and
they are a bit loose. Check you power cables and SMART results.

2010/10/21 João Pinto <joao.pinto at getdeb.net>

> I am also experiencing this problem with Maverick.
>
> The disk is:
> Western Digital Caviar Black: WD1002FAEX-00Z3A0, 1 TB
>
> The error:
> [ 1870.860322] ata1: lost interrupt (Status 0x50)
> [ 1870.860343] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x5850002 action
> 0xe frozen
> [ 1870.860348] ata1.00: SError: { RecovComm PHYRdyChg CommWake LinkSeq
> TrStaTrns DevExch }
> [ 1870.860351] ata1.00: failed command: WRITE DMA EXT
> [ 1870.860357] ata1.00: cmd 35/00:30:f8:5f:f6/00:00:56:00:00/e0 tag 0 dma
> 24576 out
> [ 1870.860358]          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x14
> (ATA bus error)
> [ 1870.860361] ata1.00: status: { DRDY }
> [ 1870.860369] ata1.00: hard resetting link
> [ 1871.609326] ata1.01: hard resetting link
> [ 1872.118761] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 1872.118774] ata1.01: SATA link down (SStatus 0 SControl 300)
> [ 1872.178939] ata1.00: configured for UDMA/133
> [ 1872.178947] ata1.00: device reported invalid CHS sector 0
> [ 1872.178954] ata1: EH complete
>
> --
> ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
> https://bugs.launchpad.net/bugs/285892
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: Unknown
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: linux-headers-2.6.27-7-generic
>
> Since I'm running 8.10 alpha6 64-bit, I'm having now and then a frozen
> machine for 1 or more minutes.
> Although I can not pinpoint the reason, it seems to happen soon after
> booting and round the whole hour.
> I guess there is some process in the background responsible. So I include
> the entries of the system log  from the freezes at 12:00 and 14:00.
>
> I'm not sure if I file this issue under the right package. Sorry for that.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/linux/+bug/285892/+subscribe
>


-- 
--------------------------------
Best,
Denis Tulskiy

-- 
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.




More information about the kernel-bugs mailing list