linux-kernel - Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080226213200.GL17932@hjernemadsen.org>
Date:	Tue, 26 Feb 2008 22:32:00 +0100
From:	"Klaus S. Madsen" <ksm@...rnemadsen.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"Michael S. Tsirkin" <m.s.tsirkin@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Alexey Starikovskiy <astarikovskiy@...e.de>,
	Len Brown <len.brown@...el.com>, linux-acpi@...r.kernel.org
Subject: Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p

> I also have a T61p, on which STR works. I haven't tried 2.6.25, but it
> works with 2.6.24. Both using the suspend scripts included in Ubuntu
> 7.10, and with s2ram 0.8 (although I need to use --acpi_sleep 2
> (s3_mode) as an option, instead of 1 (s3_bios), which is used by default
> on my model).
> 
> But I'm using the NVidia module, so that most likely changes a lot of
> things.  I'll see if I can find time tonight to test 2.6.25-rc3 + nv,
> and report back.
Ok. I've spent some time testing this. The good news is that with the nv
driver, s2ram as available from suspend.sf.net works, when run without
parameters on a 32-bit 2.6.24.3.

The bad news, however, is that it segfaults reliably after "Calling
get_mode" when I run it on 2.6.25-rc3. GDB shows that the segmentation
fault happens in the libx86 library, but as the version I use doesn't
have debug symbols, I don't have a complete backtrace. I'll try to
compile a version of libx86 tomorrow evening with debug symbols, and
return with a proper backtrace.

I have also tried to bisect the problem (its somewhere between 2.6.24
and 2.6.25rc1, quite a large span). However reverting the resulting
commit didn't solve the problem, I suspect I took a wrong turn
somewhere. I'll try to redo the bisection also tomorrow evening.

So I'll return with a proper bug report tomorrow (in its own thread). I
just wanted to give a heads up, if the above makes sense to anyone ;-)

--
Kind regards
 	Klaus S. Madsen

--
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/