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]

Message-ID: <dd18b0c30804021744m67fe4db4m8aed3897945baaa8@mail.gmail.com>
Date:	Thu, 3 Apr 2008 00:44:24 +0000
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"Tejun Heo" <htejun@...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; attached is kern.log as asked and lspci -nn.
I've noticed some avc's in there. makes me wonder if this is why
wpa_supplicant isnt working after a wakeup
regards;
                Justin P. Mattock

On Thu, Apr 3, 2008 at 12:18 AM, Tejun Heo <htejun@...il.com> wrote:
> 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
>



-- 
Justin P. Mattock

Download attachment "lspci" of type "application/octet-stream" (2374 bytes)