Re: [REGRESSION,STABLE,BISECTED] Hang on resume from standby in3.1.[56], 3.2-rc*

From: Phil Miller
Date: Sat Dec 24 2011 - 11:51:45 EST

On Sat, Dec 24, 2011 at 03:09, Michael Tokarev <mjt@xxxxxxxxxx> wrote:
> On 24.12.2011 10:40, Phil Miller wrote:
>> On Fri, Dec 23, 2011 at 11:31, Phil Miller <mille121@xxxxxxxxxxxx> wrote:
>>> I've got a Dell Precision T1500 (lspci, dmidecode, and dmesg output at
>>> ) that I generally
>>> suspend when I'm out of the house or asleep, and wake up when I want
>>> to use it. Sadly, a recent change to the kernel has disrupted that
>>> happy state of affairs. When I run the most recent stable or
>>> pre-release versions, the kernel hangs on resume. I can still switch
>>> virtual consoles, and get keyboard output echoed to the screen, but no
>>> userspace code seems to be running (e.g. login doesn't give me a
>>> password prompt after entering a username), nor does the system
>>> respond to ping or SSH connections.
>>> Bisection between v3.1 and v3.1.6 points to the following commit as the culprit:
>>> =====
>>> commit aeed6baa702a285cf03b7dc4182ffc1a7f4e4ed6
>>> Author: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
>>> Date: Fri Dec 2 16:02:45 2011 +0100
>>> clockevents: Set noop handler in clockevents_exchange_device()
>> I just went digging through the history, and it looks like the commit
>> I found to be problematic partially reverts
>> 7c1e76897492d92b6a1c2d6892494d39ded9680c, from 2008.
> I Ânoticed that my host also stopped resuming with 3.1, and noted that
> with 3.1.3 it works ok. ÂI'm now trying to revert this commit too, to
> see if that's the problem.

I first noticed this using Debian unstable's packaged kernels, which
call themselves 3.x.0, but actually get revved through the stable
versions 3.x.y (I'll probably complain about that misnaming to them).
The upgrade from 3.1.4 to 3.1.5 is where it broke, matching the
bisection's results.

Thanks for the confirmation.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at