linux-kernel - Re: ata link not reset properly

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]

Message-ID: <4C257CEE.2070309@gmail.com>
Date:	Fri, 25 Jun 2010 22:07:10 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Ortwin Glück <odi@....ch>
CC:	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: ata link not reset properly

On 06/25/2010 12:00 PM, Ortwin Glück wrote:
>
>
> On 25.06.2010 17:19, Tejun Heo wrote:
>> Patch attached, but please see below.
>
> Cheers, I will give it a try and provide feedback if "it" happens again.
>
>> Is it PATA?
>
> Yes. This chipset doesn't have SATA, only PATA.

Ahh, ok, it's not sata_nv at all then, it's pata_amd. On the same chip, 
totally different controller though.

PATA doesn't normally use hard-resets as a means of error recovery - 
that would mean hitting the RESET line, which I don't think most 
controllers can do on software command (it usually only gets asserted on 
power up or hitting the reset button), unlike on SATA where there's a 
defined way to trigger a COMRESET which is mostly equivalent. Also, that 
resets both devices on the channel, unlike soft reset which is specific 
to one device.

>
> CONFIG_ATA=y
> CONFIG_ATA_SFF=y
> CONFIG_SATA_NV=y
> CONFIG_PATA_AMD=y
>
>> Why do you have 2.01?
>
> for the DVD drive?
>
>> Can you please attach full boot
>> log?
>
> attached.
>
> Thanks.
>   Ortwin

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