From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: "Noah J. Misch" <noah-7GExONQZ6ZKVc3sceRu5cw@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [ACPI] Re: [BUG] test9 ACPI bad: scheduling while atomic!
Date: Mon, 27 Oct 2003 12:24:04 -0800 (PST) [thread overview]
Message-ID: <20031027122259.Y77994@root.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0310262327040.19469-8Uwgm7wxmYs@public.gmane.org>
On Mon, 27 Oct 2003, Noah J. Misch wrote:
> > are shown below. It looks like the AML associated with the AC event is
> > trying to do an AML_SLEEP_OP. Since this is called while in the
> > interrupt handler, and the eventual call to acpi_os_sleep() sets the
> > current state to interruptible... boom. One simple, but terribly ugly,
> > workaround is to make acpi_os_sleep() call acpi_os_stall() if
> > in_atomic() is true (patch below). Hopefully there's a better way to
> > fix this. Somehow the interpreter really needs to drop interrupt
> > context before it starts making calls like this. Thanks,
I thought a change was committed to address this, calling Stall for up to
255 us and Sleep for more than that.
-Nate
WARNING: multiple messages have this Message-ID (diff)
From: Nate Lawson <nate@root.org>
To: "Noah J. Misch" <noah@caltech.edu>
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: [BUG] test9 ACPI bad: scheduling while atomic!
Date: Mon, 27 Oct 2003 12:24:04 -0800 (PST) [thread overview]
Message-ID: <20031027122259.Y77994@root.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0310262327040.19469@clyde>
On Mon, 27 Oct 2003, Noah J. Misch wrote:
> > are shown below. It looks like the AML associated with the AC event is
> > trying to do an AML_SLEEP_OP. Since this is called while in the
> > interrupt handler, and the eventual call to acpi_os_sleep() sets the
> > current state to interruptible... boom. One simple, but terribly ugly,
> > workaround is to make acpi_os_sleep() call acpi_os_stall() if
> > in_atomic() is true (patch below). Hopefully there's a better way to
> > fix this. Somehow the interpreter really needs to drop interrupt
> > context before it starts making calls like this. Thanks,
I thought a change was committed to address this, calling Stall for up to
255 us and Sleep for more than that.
-Nate
next prev parent reply other threads:[~2003-10-27 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 8:22 [BUG] test9 ACPI bad: scheduling while atomic! Noah J. Misch
2003-10-27 8:22 ` Noah J. Misch
[not found] ` <Pine.GSO.4.58.0310262327040.19469-8Uwgm7wxmYs@public.gmane.org>
2003-10-27 16:47 ` Alex Williamson
2003-10-27 16:47 ` Alex Williamson
[not found] ` <1067273229.7497.30.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
2003-10-27 18:02 ` Noah J. Misch
2003-10-27 18:02 ` Noah J. Misch
2003-10-27 20:24 ` Nate Lawson [this message]
2003-10-27 20:24 ` [ACPI] " Nate Lawson
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=20031027122259.Y77994@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=noah-7GExONQZ6ZKVc3sceRu5cw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.