forwarded 653398 http://thread.gmane.org/gmane.linux.kernel/1233033 # another report: http://thread.gmane.org/gmane.linux.kernel/1233389 # another report: http://thread.gmane.org/gmane.linux.kernel/1233159 # another report: http://thread.gmane.org/gmane.linux.kernel/1227868/focus=1230877 quit
Hi Phil, Phil Miller wrote: >> 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 <t...@linutronix.de> >> Date: Fri Dec 2 16:02:45 2011 +0100 >> >> clockevents: Set noop handler in clockevents_exchange_device() >> >> commit de28f25e8244c7353abed8de0c7792f5f883588c upstream. [...] >> I've tested that reverting this commit also restores my ability to >> resume from suspend on 3.2-rc6. > > I just went digging through the history, and it looks like the commit > I found to be problematic partially reverts > 7c1e76897492d92b6a1c2d6892494d39ded9680c, from 2008. Yeah, that commit looks completely broken. I've sent a note to Greg asking him to revert it. I fear that this will affect 2.6.32-40 from stable-proposed-updates, too. :/ If you have time to try it, that would be helpful. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111229121352.GG29150@elie.Belkin