linux-kernel - Re: Unknown SATA PIIX PCI device ID 0x29b6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 07 Mar 2008 13:51:50 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	Jeff Garzik <jeff@...zik.org>, linux-ide@...r.kernel.org
Subject: Re: Unknown SATA PIIX PCI device ID 0x29b6

Guennadi Liakhovetski wrote:
> Mar  4 15:04:28 6a kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xa frozen
> Mar  4 15:04:28 6a kernel: ata4: irq_stat 0x00000040, connection status changed
> Mar  4 15:04:28 6a kernel: ata4: SError: { PHYRdyChg CommWake DevExch }Mar  4 15:04:28 6a kernel: ata4: hard resetting link
> Mar  4 15:04:38 6a kernel: ata4: softreset failed (device not ready)
> Mar  4 15:04:38 6a kernel: ata4: hard resetting link
> Mar  4 15:04:48 6a kernel: ata4: softreset failed (device not ready)
> Mar  4 15:04:48 6a kernel: ata4: hard resetting link
> Mar  4 15:04:55 6a kernel: ata4: port is slow to respond, please be patient (Status 0x80)
> Mar  4 15:05:20 6a kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

That's unusually long but if you look at the last reset try.  It began
at @48 and the device comes up after 32secs without the driver taking
further action, which might indicate that the device actually took that
long.  Hmmm.. maybe it's having problem establishing link at 3Gbps.

> Looks like almost a minute to me? On another occurence I see about 1.5 
> minutes, then "port is slow to respond, please be patient (Status 0x80)" 
> has been repeated 3 times. On cold-plug also 3 times, I think, about the 
> same time then (time is not updated in the log).

I see.  Does the attached patch make any difference?

>> And is it always like that?
> 
> So far - yes.
> 
>>> One more question, what do UDMA numbers mean in SATA context? The internal 
>>> SATA disk is "ata1.00: configured for UDMA/133", but should be SATA-2.
>> 1.00 is port 1 device 00 and UDMA numbers don't mean much to SATA devices.
> 
> Sorry, I actually meant to ask what "UDMA/133" means for a SATA link?

That doesn't really mean much to native SATA devices.  That's just
something we're carrying over from PATA days.

Thanks.

-- 
tejun

View attachment "force-1.5.patch" of type "text/x-patch" (382 bytes)