From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Luca Capello <luca@pca.it>
Cc: ML Linux-ACPI <linux-acpi@vger.kernel.org>
Subject: Re: Oops removing thinkpad_acpi and video on git:linux-acpi-2.6
Date: Wed, 17 Oct 2007 23:21:06 -0200 [thread overview]
Message-ID: <20071018012106.GA24821@khazad-dum.debian.net> (raw)
In-Reply-To: <87lka1ffwc.fsf@gismo.pca.it>
On Thu, 18 Oct 2007, Luca Capello wrote:
> I just got the following oops when removing thinkpad_acpi and then
> video. Kernel is the linux-acpi-2.6 git branch up to
If you never load thinkpad_acpi in the first place, just video, and then
remove video, does the oops happen? I can't help much with video, but
thinkpad-acpi is my responsability.
> Just before the oops, dmesg shows the following, with the first being
> the event generated by brightness up/down with Fn keys and the second
> the ThinkFinger [1] device:
> =====
> thinkpad_acpi: unknown LID-related HKEY event: 0x5010
> input: Virtual ThinkFinger Keyboard as /class/input/input99
> =====
Yeah, that 5010 event seems to mean "something in NVRAM changed".
thinkpad-acpi just punts it to userspace. That event is gone in later BIOS
revisions, I think.
> This is on a Lenovo ThinkPad X60 [2], ThinkPad BIOS 7BETD0WW (2.11)
> [3] and EC 7BHT40WW-1.13, kernel compiled using the Debian
> kernel-package.
You have a BIOS with bugs. Please consider updating.
> [3] I'm aware there's a new version, but I'm waiting to understand if
> I can upgrade it using Free Software only (i.e. without the Lenovo
> bootable CD)
No. You should use the CD if you can. Otherwise, you are risking your
warranty, which is a very dumb thing to do.
Anyway, refer to http://thinkwiki.org/wiki/BIOS_Upgrade for upgrade
experiences on the X60 using various methods.
> [<ffffffff80325172>] acpi_os_execute_notify+0x0/0x2c
> [<ffffffff8032aae5>] acpi_ev_notify_dispatch+0x57/0x60
> [<ffffffff80325195>] acpi_os_execute_notify+0x23/0x2c
Looks like either thinkpad-acpi or video forgot to remove a notify handler
before unloading. Or maybe it is a race.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-10-18 1:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 0:03 Oops removing thinkpad_acpi and video on git:linux-acpi-2.6 Luca Capello
2007-10-18 1:21 ` Henrique de Moraes Holschuh [this message]
2007-10-18 19:13 ` Luca Capello
2007-10-18 23:03 ` Henrique de Moraes Holschuh
2007-10-19 12:00 ` Luca Capello
2007-10-19 13:02 ` Henrique de Moraes Holschuh
2007-10-20 0:27 ` Henrique de Moraes Holschuh
2007-10-21 17:45 ` Luca Capello
2007-10-22 1:32 ` Henrique de Moraes Holschuh
2007-10-22 6:48 ` Luca Capello
2007-10-22 17:00 ` Henrique de Moraes Holschuh
2007-11-02 14:16 ` Luca Capello
2007-11-02 19:42 ` Henrique de Moraes Holschuh
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=20071018012106.GA24821@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=luca@pca.it \
/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