linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Grover, Andrew" <andrew.grover@intel.com>
To: "Warren Turkal" <wturkal@cbu.edu>, <linux-kernel@vger.kernel.org>,
	<acpi-devel@lists.sourceforge.net>
Subject: RE: [BUG] linux laptop keyboard problem since 2.5.74
Date: Fri, 25 Jul 2003 13:33:37 -0700	[thread overview]
Message-ID: <F760B14C9561B941B89469F59BA3A8470255EEA8@orsmsx401.jf.intel.com> (raw)

> From: Warren Turkal [mailto:wturkal@cbu.edu] 
> Something got merged between 2.5.73 and 74 that has messed 
> with my system ever 
> since. Some of the keys that are activated with Fn 
> combinations are messed up.
> 
> Some of these combinations involve turning on external 
> monitor output and 
> showing battery status.
> 
> I suspect ACPI as that was the culprit last time when I could 
> not use the Fn 
> combinations at all. I compiled my kernel with acpi as 
> modules and the 
> problems happens even when not loading the modules for acpi. 
> I also tried 
> booting with acpi=off and that did not seem to change anything.
> 
> Like I said, 2.5.73 was fine and didn't lock like 2.5.74 to 
> 2.6.0-test1 do. So 
> the bug was somewhere in that revision.
> 
> I have a Gateway 600 series laptop with 256mb ram and 1.9Ghz 
> P4. Does anyone 
> know where I should start investigating for more info.

I don't think it's ACPI to blame. The ACPI-related changesets applied
between 2.5.73 and 2.5.74 don't look like the culprit. Also, since it
continues to happen when acpi=off that also points away from ACPI.

I have other reports of things breaking in the same timeframe so I think
it's fair to say that something has regressed...somewhere.

Regards -- Andy

             reply	other threads:[~2003-07-25 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 20:33 Grover, Andrew [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-19  6:22 [BUG] linux laptop keyboard problem since 2.5.74 Warren Turkal

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=F760B14C9561B941B89469F59BA3A8470255EEA8@orsmsx401.jf.intel.com \
    --to=andrew.grover@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wturkal@cbu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).