From: David Brownell <david-b@pacbell.net>
To: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@osdl.org>, "Brown, Len" <len.brown@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: ACPI breakage (Re: 2.6.19-rc6: known regressions (v2))
Date: Sat, 18 Nov 2006 20:33:56 -0800 [thread overview]
Message-ID: <200611182033.56332.david-b@pacbell.net> (raw)
In-Reply-To: <200611181105.15421.david-b@pacbell.net>
On Saturday 18 November 2006 11:05 am, David Brownell wrote:
>
> Running right now with a patch reverting the update which
> made trouble on Linus' machine, but without Alexey's two
> tweaks to the EC interrupt handler. So far so good, even
> after doing things which had previously caused AE_TIME
> errors pretty quickly. But then, the errors weren't what
> I'd call reproducible either.
Hmm, well after a reboot to sort out some other patches,
and at uptime of ~2 hours, I noticed confusion about
whether AC or battery power was active, then the old:
ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for [EmbeddedControl] [20060707]
ACPI Exception (dswexec-0458): AE_TIME, While resolving operands for [OpcodeName unavailable] [20060707]
ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.THRM._TMP] (Node ffff810002032d10), AE_TIME
So maybe that's not the entire story; sigh.
- Dave
next prev parent reply other threads:[~2006-11-19 4:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 16:23 ACPI breakage (Re: 2.6.19-rc6: known regressions (v2)) Starikovskiy, Alexey Y
2006-11-18 17:12 ` Linus Torvalds
2006-11-18 19:05 ` David Brownell
2006-11-18 22:09 ` Linus Torvalds
2006-11-18 22:16 ` Adrian Bunk
2006-11-19 4:33 ` David Brownell [this message]
2006-11-20 18:46 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2006-11-18 19:01 Starikovskiy, Alexey Y
2006-11-18 19:05 ` Linus Torvalds
[not found] ` <455FB44C.8050103@linux.intel.com>
[not found] ` <Pine.LNX.4.64.0611182048560.3692@woody.osdl.org>
[not found] ` <456043F7.1030105@linux.intel.com>
[not found] ` <Pine.LNX.4.64.0611201003540.3692@woody.osdl.org>
2006-11-20 18:27 ` Linus Torvalds
2006-11-20 19:31 ` Alexey Starikovskiy
2006-11-21 3:10 ` Sanjoy Mahajan
2006-11-20 22:13 ` Alexey Starikovskiy
2006-11-16 4:21 Linux 2.6.19-rc6 Linus Torvalds
2006-11-17 20:40 ` 2.6.19-rc6: known regressions (v2) Adrian Bunk
2006-11-17 23:58 ` ACPI breakage (Re: 2.6.19-rc6: known regressions (v2)) Linus Torvalds
2006-11-18 1:25 ` Linus Torvalds
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=200611182033.56332.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=alexey.y.starikovskiy@linux.intel.com \
--cc=bunk@stusta.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=torvalds@osdl.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.