From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: Adrian Bunk <bunk@stusta.de>
Cc: len.brown@intel.com, linux-acpi@vger.kernel.org,
Jeff Garzik <jeff@garzik.org>,
linux-pm@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x60 backlight Re: [discuss] 2.6.19-rc1: known regressions (v2)
Date: Mon, 16 Oct 2006 21:39:25 +0200 [thread overview]
Message-ID: <20061016193925.GA20009@mellanox.co.il> (raw)
In-Reply-To: <20061008193005.GJ6755@stusta.de>
Quoting r. Adrian Bunk <bunk@stusta.de>:
> Subject: Re: x60 backlight Re: [discuss] 2.6.19-rc1: known regressions (v2)
>
> On Sun, Oct 08, 2006 at 07:59:58PM +0200, Michael S. Tsirkin wrote:
> > Quoting r. Adrian Bunk <bunk@stusta.de>:
> > > Subject: Re: x60 backlight Re: [discuss] 2.6.19-rc1: known regressions (v2)
> > >
> > > On Sun, Oct 08, 2006 at 07:12:54AM +0000, Pavel Machek wrote:
> > > >
> > > > On Sat 07-10-06 23:46:21, Adrian Bunk wrote:
> > > > > This email lists some known regressions in 2.6.19-rc1 compared to 2.6.18
> > > > > that are not yet fixed Linus' tree.
> > > > >
> > > > ...
> > > > > Subject : T60 stops triggering any ACPI events
> > > > > References : http://lkml.org/lkml/2006/10/4/425
> > > > > Submitter : "Michael S. Tsirkin" <mst@mellanox.co.il>
> > > > > Status : unknown
> >
> > This was on a pre -rc1 git tree.
> > I've been using -rc1 since it's out and does not happen to me anymore.
> > So we probably can write this off as a memory corruption
> > issue that got fixed in between.
>
> Thanks for the information, I've removed it from the list.
Unfortunately, this came back after using 2.6.19-rc1 for a couple of days
without reboot. And I just re-tested and was able to re-produce the problem on
2.6.19-rc2, as well. So the problem is still there, with the same symptoms:
after usig machine for a while, or under stress (e.g. if I do a full kernel
compile), I stop getting any ACPI events.
tail -f /var/log/acpid
does not show anything, even on Fn/F4 which is supposed ot be always enabled.
Restarting the acpid doesn't do anything either - ACPI starts working
again, for a while, only after reboot.
Worked fine under 2.6.18 (I was running vanilla + this patch
http://lkml.org/lkml/2006/7/20/56 which made it into upstream since then).
Any ideas? How to debug this?
--
MST
next prev parent reply other threads:[~2006-10-16 19:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0610042017340.3952@g5.osdl.org>
[not found] ` <871wpmoyjv.fsf@sycorax.lbl.gov>
2006-10-06 18:47 ` 2.6.19-rc1 regression: airo suspend fails Adrian Bunk
2006-10-07 3:54 ` Alex Romosan
2006-10-07 19:52 ` Dave Kleikamp
2006-10-07 20:17 ` Alex Romosan
2006-10-08 6:43 ` Pavel Machek
2006-10-07 21:46 ` 2.6.19-rc1: known regressions (v2) Adrian Bunk
2006-10-08 7:12 ` x60 backlight Re: [discuss] " Pavel Machek
2006-10-08 17:38 ` Adrian Bunk
2006-10-08 17:59 ` Michael S. Tsirkin
2006-10-08 19:30 ` Adrian Bunk
2006-10-16 19:39 ` Michael S. Tsirkin [this message]
2006-10-08 18:36 ` Pavel Machek
2006-10-08 19:29 ` Adrian Bunk
2006-10-08 23:44 ` Jeremy Fitzhardinge
2006-10-08 8:56 ` matthieu castet
2006-10-10 5:10 ` 2.6.19-rc1: known regressions (v3) Adrian Bunk
2006-10-10 22:58 ` Paul Mackerras
2006-10-11 3:08 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061016193925.GA20009@mellanox.co.il \
--to=mst@mellanox.co.il \
--cc=bunk@stusta.de \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox