From: Warren Turkal <wturkal@cbu.edu>
To: "Grover, Andrew" <andrew.grover@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] laptop keyboard, tracked to ACPI
Date: Wed, 2 Apr 2003 03:35:02 -0600 [thread overview]
Message-ID: <200304020335.03120.wturkal@cbu.edu> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A847E96D93@orsmsx401.jf.intel.com>
On Monday 31 March 2003 12:09 pm, Grover, Andrew wrote:
> > From: Warren Turkal [mailto:wturkal@cbu.edu]
> > Andy Grover, ACPI Maintainer, I am CCing you directly as I
> > think this is your
> > bug at this point. When I compile a kernel without ACPI, the
> > bug does not
> > show its face. When I compile with ACPI in modules and load
> > none of the
> > modules, the bug still happens. I think that the bug exists
> > in the base ACPI
> > support code as a result. The bug is described below. I have
> > not tried the
> > latest linus bk patches. This current round of tests was
> > performed on 2.5.66.
> > 2.5.63 is the last version of the kernel that does not have this bug.
>
> Please try the ACPI patch from http://sf.net/projects/acpi and let me
> know if it doesn't fix things.
>
> Thanks -- Regards -- Andy
This does fix it. Thanks so much! :-D Now I just wonder if that OOPS on
shutdown is fixed yet.
Warren
--
Treasurer, GOLUM, Inc.
http://www.golum.org
next prev parent reply other threads:[~2003-04-02 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 18:09 Grover, Andrew
2003-04-02 9:35 ` Warren Turkal [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-22 12:05 [BUG] laptop keyboard Warren Turkal
2003-03-24 2:56 ` [BUG] laptop keyboard, more info Warren Turkal
[not found] ` <200303280828.20070.felix.seeger@gmx.de>
2003-03-29 7:42 ` [BUG] laptop keyboard, tracked to ACPI 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=200304020335.03120.wturkal@cbu.edu \
--to=wturkal@cbu.edu \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®