On Wed, 28 Feb 2007 07:40:23 -0500 (EST)
Gerhard Mack <[EMAIL PROTECTED]> wrote:
> hello,
>
> Can someone tell me what this means?
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x2 frozen
> ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288
> out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: port failed to respond (30 secs, Status 0xd0)
> ata1: soft resetting port
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: configured for UDMA/100
I am fairly certain this is a bug in the 2.6.20 kernel.
I never see it in 2.6.19*, just 2.6.20.
It is some kind of but in the SATA code paths, or at least that's all it
appears to affect on my system.
What chipset do you have?
I have an nforce4 chipset.
In another thread, I think they were saying it was either a SATA chipset
driver bug, or a problem in libata core.
--
shannon | governorrhea:
| a contagious disease that spreads from
| the governor of a state downward through other
| offices and his corporate sponsors
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
