[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201205061344.25275.bugs@humanleg.org.uk>
Date: Sun, 6 May 2012 13:44:17 +0100
From: Robert Scott <bugs@...anleg.org.uk>
To: Jonathan Nieder <jrnieder@...il.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
Kevin Tian <kevin.tian@...el.com>,
Fengzhe Zhang <fengzhe.zhang@...el.com>, mingo@...hat.com,
hpa@...or.com, Ian Campbell <Ian.Campbell@...citrix.com>,
JBeulich@...ell.com, xen-devel@...ts.xensource.com,
Lars Boegild Thomsen <lth@....dk>,
e568b31a443d@...2cce7af2d.anonbox.net,
"Liu, Chuansheng" <chuansheng.liu@...el.com>
Subject: Re: [regression] Ideapad S10-3 does not wake up from suspend
On Tuesday 17 April 2012, Jonathan Nieder wrote:
> Robert Scott wrote:
> > On Sunday 15 April 2012, Jonathan Nieder wrote:
>
> >> Lars, Robert, anon: can you try 3.4-rc2 or newer and let us know how
> >> it goes? I suspect v3.4-rc2~24^2~4 ("x86: Preserve lazy irq disable
> >> semantics in fixup_irqs()") will fix this.
> >
> > Hmm, no, 3.4-rc2 seems to produce the same results I'm afraid.
>
> Alas. Does suspend-to-disk ("echo disk >/sys/power/state") have the
> same problem? Can you get a log of the failure with
> "no_console_suspend" appended to the kernel command line, for example
> with a serial console or netconsole?
Well, for what it's worth, using a USB serial console to capture output, all you get is:
[ 814.016541] PM: Syncing filesystems ... done.
[ 814.018516] PM: Preparing system for mem sleep
[ 814.100393] Freezing user space processes ... (elapsed 0.01 se
before it goes to sleep, and it doesn't output anything on (attempted) wakeup. Though I don't know if this is due to USB being woken up quite late or something.
robert.
--
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/
Powered by blists - more mailing lists