From: "Noah J. Misch" <noah@caltech.edu>
To: "Li, Shaohua" <shaohua.li@intel.com>
Cc: acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: RE: [BUG] test9 ACPI bad: scheduling while atomic!
Date: Tue, 28 Oct 2003 15:56:05 -0800 (PST) [thread overview]
Message-ID: <Pine.GSO.4.58.0310271858210.12662@blinky> (raw)
In-Reply-To: <571ACEFD467F7749BC50E0A98C17CDD8D5FDBB@pdsmsx403.ccr.corp.intel.com>
On Tue, 28 Oct 2003, Li, Shaohua wrote:
> The reason is just what you said. It's a race condition.
> In UP, the problem occurs also. But it can't cause anything, because spinlock
> does nothing in UP. In some machines which have the problem in UP, you will
> see some info like this:
> Hwregs-0760[35] hw_low_level_read: Unsupported address space:C8
It's clearly a spinlock that leads up to Alex's oops, but the T40 oops?
> > It seems rather theoretical, but perhaps we could fix it with a patch like
> > the following. I tested it for kicks and didn't hit any problems, but I'm
> > afraid it risks more problems than it solves. Thoughts?
>
> Did just discarding the events cause problem?
Hmmm. I don't imagine it would. Indeed, registering the address space handler
alone may be good enough for ECDT use. I'd favor that.
Regardless, we still have the Thinkpad T40 problem.
On Tue, 28 Oct 2003, Li, Shaohua wrote:
> one solution is using bh to handle such events before EC device added.
> After EC is loaded, we still use keventd to handle the events. Any idea?
Aren't BHs obsolete?
next parent reply other threads:[~2003-10-28 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <571ACEFD467F7749BC50E0A98C17CDD8D5FDBB@pdsmsx403.ccr.corp.intel.com>
2003-10-28 23:56 ` Noah J. Misch [this message]
2003-10-27 8:22 [BUG] test9 ACPI bad: scheduling while atomic! Noah J. Misch
2003-10-27 16:47 ` Alex Williamson
2003-10-27 18:02 ` Noah J. Misch
-- strict thread matches above, loose matches on Subject: below --
2003-10-27 2:23 Alex Williamson
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=Pine.GSO.4.58.0310271858210.12662@blinky \
--to=noah@caltech.edu \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
/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).