Bug#639331: linux-image-2.6.36-rc6-686-bigmem: Closing laptop lid hangs the system on Dell studio 1555

[Jonathan Nieder <jrnieder@gmail.com>]

Hi Thibault,

Thibault Manlay wrote:

> I have a problem occurring for some time now, my system hangs each
> time I close the lid of my laptop
[...]
> This problem was not present in the 2.6.32 version and appeared in
> the 2.6.38 version. I had not much time to determine at which
> version this problem began to be present but now I have time I had a
> closer look.
>
> I installed some versions of 'old' Debian kernel packages I found on
> <http://snapshot.debian.org/> and I determined that the issue
> appeared between linux-image-2.6.35-trunk-686-bigmem
> (2.6.35-1~experimental.3) and linux-image-2.6.36-rc6-686-bigmem
> (2.6.36~rc6-1~experimental.1). Everything works fine in 2.6.35-trunk
> and issue in 2.6.36-rc6.

Thanks, that's very useful.

Does the latest -pae or -amd64 kernel from sid produce the same
symptoms?  Are you able to get logs from right before the hang (for
example with netconsole)?  If you have time to bisect to find the
exact change that introduced this, that would be best of all --- it
works like this:

1. Name an executable with the following content "as" and put it in
   your $PATH before /usr/bin, to work around Bug#620448.

	#!/bin/sh
	exec /usr/bin/as --size-check=warning "$@"

2.
	# apt-get install build-essential git-core
	$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
	$ git bisect start v2.6.36-rc6 v2.6.35
	$ make localmodconfig; # minimal configuration
	$ make deb-pkg
	# dpkg -i ../<name of package>
	# reboot
	... test test test ...

	$ cd ~/src/linux
	$ git bisect good; # if it works
	$ git bisect bad; # if the hang occurs
	$ git bisect skip; # if some other bug makes it hard to test

	# git checks out an appropriate next revision to test
	$ make silentoldconfig; # reuse configuration
	$ make deb-pkg
	# dpkg -i ../<name of package>
	# reboot
	... test test test ...

3. Continue until it says the "first bad commit", or until bored.  In
the latter case, run "git bisect log" to present the results.  If the
gitk package is installed, you can run "git bisect visualize" at any
time to watch the regression range narrowing.