linux-kernel - Re: suspend

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:	Thu, 03 Apr 2008 09:18:33 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Justin Mattock <justinmattock@...il.com>
CC:	"Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org,
	Alan <alan@...rguk.ukuu.org.uk>, Jeff Garzik <jeff@...zik.org>,
	Pavel Machek <pavel@....cz>
Subject: Re: suspend

Hello,

Justin Mattock wrote:
>>  > [ 1233.811794] sd 2:0:1:0: [sda] Starting disk
>>  > [ 1234.013599] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
>>  > [ 1234.013601] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 filtered out
>>  > [ 1234.180232] ata1.00: configured for UDMA/66
>>  > [ 1222.732011] ata3.01: NODEV after polling detection
>>  > [ 1222.732016] ata3.01: revalidation failed (errno=-2)

I presume this is ata_piix, right?  What's hanging off of ata3.01?  An 
optical drive?

What happened is that, after resuming, libata reseted the channel and 
issued IDENTIFY[_PACKET] to make sure the device was still there.  The 
device violated the state machine transition in the same way as when 
there's no device attached.  libata paused for a while and retries and 
the device responded correctly at the retry.  Things like this can 
happen.  The problem is that libata resume is currently synchronous and 
retries like this hold the machine back from reaching operational status 
even when there's no reason for resume retrial on optical drive to delay 
the rest of resume process.

Can you please post full kernel log and the result of 'lspci -nn'?

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