From: Andrew Morton <akpm@osdl.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.17-rc5-mm3 -- ACPI errors (are these ones that are significant?)
Date: Mon, 5 Jun 2006 01:59:22 -0700 [thread overview]
Message-ID: <20060605015922.0defacbc.akpm@osdl.org> (raw)
In-Reply-To: <a44ae5cd0606050124h4c82f45aq27f68f9d07956642@mail.gmail.com>
On Mon, 5 Jun 2006 01:24:27 -0700
"Miles Lane" <miles.lane@gmail.com> wrote:
> During boot:
>
> acpi_processor-0731 [00] processor_preregister_: Error while parsing
> _PSD domain information. Assuming no coordination
>
> During resume and after the "BUG: sleeping function called from
> invalid context at include/asm/semaphore.h:99 in_atomic():0,
> irqs_disabled():1" that I reported earlier:
>
> PM: Finishing wakeup.
> acpi: resuming
> ACPI: read EC, IB not empty
> ACPI: read EC, OB not full
> ACPI Exception (evregion-0412): AE_TIME, Returned by Handler for
> [EmbeddedControl] [20060310]
> ACPI Exception (dswexec-0459): AE_TIME, While resolving operands for
> [Store] [20060310]
> ACPI Error (psparse-0522): Method parse/execution failed
> [\_TZ_.THRM._TMP] (Node c189ec44), AE_TIME
> agpgart-intel 0000:00:00.0: resuming
Please copy linux-acpi on acpi-related problems.
next prev parent reply other threads:[~2006-06-05 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 8:24 2.6.17-rc5-mm3 -- ACPI errors (are these ones that are significant?) Miles Lane
2006-06-05 8:59 ` Andrew Morton [this message]
2006-06-25 6:46 ` 2.6.17-mm2 ACPI warnings: unexpected IRQ trap at vector 05 Fengguang Wu
2006-06-25 6:46 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 12:58 2.6.17-rc5-mm3 -- ACPI errors (are these ones that are significant?) Yu, Luming
2006-06-05 12:58 ` Yu, Luming
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=20060605015922.0defacbc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.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 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.