public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Capello <luca@pca.it>
To: ML Linux-ACPI <linux-acpi@vger.kernel.org>
Subject: Re: Oops removing thinkpad_acpi and video on git:linux-acpi-2.6
Date: Fri, 19 Oct 2007 14:00:32 +0200	[thread overview]
Message-ID: <871wbr2u1r.fsf@gismo.pca.it> (raw)
In-Reply-To: 20071018230334.GD4483@khazad-dum.debian.net

Hi Henrique!

On Fri, 19 Oct 2007 01:03:34 +0200, Henrique de Moraes Holschuh wrote:
> On Thu, 18 Oct 2007, Luca Capello wrote:
>> Since I experienced the oops after having changed the LCD
>> brightness, I pressed several times the brightness up/down Fn keys,
>> then removed only the thinkpad_acpi module and voila, I got the
>> oops again.
[...]
>
> Hmm, I will see if I can reproduce it.

Thank you.

> Do you get that problem if you use 2.6.23 + thinkpad-acpi
> 0.18-20071013 available at:
> http://sourceforge.net/project/showfiles.php?group_id=117042 ?

I tested 2.6.23.1 + 0.18-20071013, oops still there.  Should I test it
with the latest linux-acpi-2.6 git tree, also?  I don't think it's
necessary, but I can do it in case (but please read below).

> There is also a git tree, if you prefer:
> http://repo.or.cz/w/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git for
> the gitweb interface, there is more data in that.  Look at the
> release/ branches.

Sorry, I'm quite lost with the git tree: in release/ there's nothing
about the latest linux-acpi-2.6 tree, what I can see is the different
linux releases with spare patches.  And if I correctly read the
README, I should check what's in for-upstream, which I don't really
know how to checkout with git (I performed a `git clone $TREE`).

>> Should I perform my tests again with the new BIOS?  Or is this bug
>> completely unrelated to the BIOS version?
>
> The bug might even be triggered by the BIOS, but it is a real bug in the
> driver.  But the new BIOS will probably behave much better re. brightness
> functions.

Is it OK to wait to upgrade the BIOS until the bug has been fixed?
Because if the bug won't be present anymore with the new BIOS, we
don't have a way to be sure it's fixed.

Thx, bye,
Gismo / Luca

  reply	other threads:[~2007-10-19 12:00 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
2007-10-18 19:13   ` Luca Capello
2007-10-18 23:03     ` Henrique de Moraes Holschuh
2007-10-19 12:00       ` Luca Capello [this message]
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=871wbr2u1r.fsf@gismo.pca.it \
    --to=luca@pca.it \
    --cc=linux-acpi@vger.kernel.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