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

2008-02-26 Thread Klaus S. Madsen
On Mon, Feb 25, 2008 at 11:46:11 -0800, Andrew Morton wrote: On Mon, 25 Feb 2008 21:19:24 +0200 Michael S. Tsirkin [EMAIL PROTECTED] wrote: On my T61p, 2.6.25-rc2 seems to get acpi events from keypresses such as Fn-F4 and lid open/close, prints them in /var/log/acpid and reacts

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

2008-02-25 Thread Alexey Starikovskiy
Michael S. Tsirkin wrote: On my T61p, 2.6.25-rc2 seems to get acpi events from keypresses such as Fn-F4 and lid open/close, prints them in /var/log/acpid and reacts accordingly (my acpi scripts suspend on lid close and Fn-F4). This no longer happens in 2.6.25-rc3: I see nothing in

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

2008-02-25 Thread Michael S. Tsirkin
On my T61p, 2.6.25-rc2 seems to get acpi events from keypresses such as Fn-F4 and lid open/close, prints them in /var/log/acpid and reacts accordingly (my acpi scripts suspend on lid close and Fn-F4). This no longer happens in 2.6.25-rc3: I see nothing in /var/log/acpid after power on: [Mon Feb

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

2008-02-25 Thread Andrew Morton
On Mon, 25 Feb 2008 21:19:24 +0200 Michael S. Tsirkin [EMAIL PROTECTED] wrote: On my T61p, 2.6.25-rc2 seems to get acpi events from keypresses such as Fn-F4 and lid open/close, prints them in /var/log/acpid and reacts accordingly (my acpi scripts suspend on lid close and Fn-F4). You mean

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

2008-02-25 Thread Michael S. Tsirkin
On Mon, Feb 25, 2008 at 9:42 PM, Alexey Starikovskiy [EMAIL PROTECTED] wrote: Michael S. Tsirkin wrote: On my T61p, 2.6.25-rc2 seems to get acpi events from keypresses such as Fn-F4 and lid open/close, prints them in /var/log/acpid and reacts accordingly (my acpi scripts suspend on lid

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

2008-02-25 Thread Michael S. Tsirkin
On Mon, Feb 25, 2008 at 9:46 PM, Andrew Morton [EMAIL PROTECTED] wrote: On Mon, 25 Feb 2008 21:19:24 +0200 Michael S. Tsirkin [EMAIL PROTECTED] wrote: On my T61p, 2.6.25-rc2 seems to get acpi events from keypresses such as Fn-F4 and lid open/close, prints them in /var/log/acpid and

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

2008-02-25 Thread Alexey Starikovskiy
Michael S. Tsirkin wrote: Did you guys stop accepting reports by mail? I hope not. It is easier to track bug information in bugzilla. If you for some reason do not wish to create a bug report, I can do it for you. You only need to provide acpidump. and attach acpidump? I'll see if I can

broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

2008-02-25 Thread Rafael J. Wysocki
On Monday, 25 of February 2008, Michael S. Tsirkin wrote: On Mon, Feb 25, 2008 at 9:46 PM, Andrew Morton [EMAIL PROTECTED] wrote: On Mon, 25 Feb 2008 21:19:24 +0200 Michael S. Tsirkin [EMAIL PROTECTED] wrote: On my T61p, 2.6.25-rc2 seems to get acpi events from keypresses such as

Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

2008-02-25 Thread Jeff Garzik
Pavel Machek wrote: commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2 Author: Pavel Machek [EMAIL PROTECTED] Date: Thu Feb 21 13:56:55 2008 +0100 power_state: get rid of write-only variable in SATA This is pretty unlikely to be it. Can you double check that this patch really breaks

Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

2008-02-25 Thread Pavel Machek
Hi! commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2 Author: Pavel Machek [EMAIL PROTECTED] Date: Thu Feb 21 13:56:55 2008 +0100 power_state: get rid of write-only variable in SATA This is pretty unlikely to be it. Can you double check that this patch really

Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

2008-02-25 Thread Michael S. Tsirkin
On Mon, Feb 25, 2008 at 11:50 PM, Pavel Machek [EMAIL PROTECTED] wrote: Hi! commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2 Author: Pavel Machek [EMAIL PROTECTED] Date: Thu Feb 21 13:56:55 2008 +0100 power_state: get rid of write-only variable in SATA

Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

2008-02-25 Thread Pavel Machek
Hi! commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2 Author: Pavel Machek [EMAIL PROTECTED] Date: Thu Feb 21 13:56:55 2008 +0100 power_state: get rid of write-only variable in SATA This is pretty unlikely to be it. Can you double check that this

Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

2008-02-25 Thread Michael S. Tsirkin
On Tue, Feb 26, 2008 at 12:20 AM, Pavel Machek [EMAIL PROTECTED] wrote: Hi! commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2 Author: Pavel Machek [EMAIL PROTECTED] Date: Thu Feb 21 13:56:55 2008 +0100 power_state: get rid of write-only variable

Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

2008-02-25 Thread Andrew Morton
On Tue, 26 Feb 2008 00:48:12 +0200 Michael S. Tsirkin [EMAIL PROTECTED] wrote: On Tue, Feb 26, 2008 at 12:39 AM, Andrew Morton [EMAIL PROTECTED] wrote: On Tue, 26 Feb 2008 00:36:54 +0200 Michael S. Tsirkin [EMAIL PROTECTED] wrote: Hmm, mystery partly solved... as you guessed it,

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

2008-02-25 Thread Michael S. Tsirkin
On Tue, Feb 26, 2008 at 12:33 AM, Alexey Starikovskiy [EMAIL PROTECTED] wrote: Attached is the acpidump output run under 2.6.23-rc3 + with reverted 37f9b4c7c612fcbeb8fb6faddaef4ccdb5350145 (IOW - this is a working configuration). Thanks, you've got round 10100 bug number. Please