[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110902030140.GA31569@hallyn.com>
Date: Fri, 2 Sep 2011 03:01:40 +0000
From: "Serge E. Hallyn" <serge@...lyn.com>
To: Jonathan Nieder <jrnieder@...il.com>
Cc: Dave Hansen <dave@...ux.vnet.ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, Kevin Tian <kevin.tian@...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>,
Len Brown <len.brown@...el.com>
Subject: Re: [regression] Ideapad S10-3 does not wake up from suspend (Re:
[PATCH v2 2/2] x86: don't unmask disabled irqs when migrating them)
Quoting Jonathan Nieder (jrnieder@...il.com):
> Hi Dave,
>
> Dave Hansen wrote:
>
> > I'm seeing the exact same symptoms on my S10-3, fwiw. They definitely
> > don't happen when intel_idle is compiled out or when
> > intel_idle.max_cstate=0 is specified on the kernel command-line.
>
> Lars reminds me[1] that the kernel he was testing already had the
> intel_idle driver compiled out, so you're probably seeing a different
> (possibly related) bug. (By the way, Lars, it is fine to communicate
> with lkml directly. :) The people there don't bite.)
Right, over the past year or so this has been hit or miss. Sometimes
intel_idle.max_cstate=0 would fix it. Sometimes (like today) not. Ever
since the problems have started, using intel_idle has not worked once,
but disabling it is not 100% reliable. And when it doesn't work, it
doesn't work at all until I get a new kernel.
Sorry, not very helpful.
-serge
--
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