[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46C42CAF.4040709@gmail.com>
Date: Thu, 16 Aug 2007 19:53:35 +0900
From: Tejun Heo <htejun@...il.com>
To: Andreas Radke <a.radke@...or.de>
CC: linux-kernel@...r.kernel.org,
Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
Jeff Garzik <jgarzik@...ox.com>,
IDE/ATA development list <linux-ide@...r.kernel.org>
Subject: Re: sata drive loosing connection/resetting port
Andreas Radke wrote:
[on ahci]
> Aug 13 18:00:33 workstation64 ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400101 action 0x2 frozen
> Aug 13 18:00:33 workstation64 ata1.00: (irq_stat 0x08000000, interface fatal error)
> Aug 13 18:00:33 workstation64 ata1.00: cmd ca/00:08:a0:cb:07/00:00:00:00:00/e8 tag 0 cdb 0x0 data 4096 out
> Aug 13 18:00:33 workstation64 res 50/00:00:bf:32:07/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
Errors are very consistent. Data transfer from the host to the drive
fails and SError indicates Handshake Error, Non-recovered transient data
integrity error and often Recovered Data integrity error. For some
reason, your drive doesn't like what it's hearing from the controller
and replies with R_ERR.
[on ata_piix]
> Aug 14 23:06:01 workstation64 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> Aug 14 23:06:01 workstation64 ata1.00: (BMDMA stat 0x26)
> Aug 14 23:06:01 workstation64 ata1.00: cmd ca/00:08:91:0d:45/00:00:00:00:00/e4 tag 0 cdb 0x0 data 4096 out
> Aug 14 23:06:01 workstation64 res 51/84:08:91:0d:45/00:00:00:00:00/e4 Emask 0x30 (host bus error)
As error reporting when using ata_piix is very limited. It gets
reported as host bus error but I think it's basically the same problem.
I don't think this is driver issue. I have the same controller and I've
never seen similar thing happening and I have plenty of drives and test
them often. Error reports also point to transmission problems. Your
drive just doesn't like what it's hearing. Does 'smartctl -a /dev/sda'
tell anything special?
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists