linux-kernel - Re: 2.6.32 seemed to have broken nVidia MCP7A sata controller

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-next>] [day] [month] [year] [list]

Message-ID: <4B2C80DD.9080005@garzik.org>
Date:	Sat, 19 Dec 2009 02:29:33 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Mike Cui <cuicui@...il.com>
CC:	linux-ide@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.32 seemed to have broken nVidia MCP7A sata controller

On 12/19/2009 01:13 AM, Mike Cui wrote:
> I have an nVidia MCP7A AHCI controller. I upgraded to 2.6.32.2 and my
> system deterministically freezes trying to mount file systems. Once in
> a while it will come back and finish booting after freezing for 1
> minute or 2. dmesg indicates that there were NCQ errors, but 2.6.31
> anb before has always worked flawlessly for me. What changed in
> 2.6.32? I will be more than happy to help track down this issue.

> ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
> ata1.00: cmd 61/08:00:4f:ad:03/00:00:00:00:00/40 tag 0 ncq 4096 out
>           res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1: hard resetting link
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: configured for UDMA/133
> ata1.00: device reported invalid CHS sector 0

Looks like things are timing out, and then go downhill from there.  This 
explanation of timeout gives some hints on possible causes: 
http://ata.wiki.kernel.org/index.php/Libata_error_messages#Error_classes

The ideal would be if you could bisect between 2.6.31 and 2.6.32, to see 
if it's a software change that is the cause.

Looking at drivers/ata/ahci.c history, the only thing that -might- cause 
problems is 388539f3ff0cf1de926b03f94e1eec112358f74d ('git show $commit' 
for full commit info and diff).

	Jeff


--
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/