From: Andreas Mohr <andi@lisas.de>
To: Andreas Mohr <andi@lisas.de>
Cc: Robert Hancock <hancockr@shaw.ca>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-ide@vger.kernel.org, Tejun Heo <htejun@gmail.com>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: 2.6.24-rc4-git5: Reported regressions from 2.6.23
Date: Mon, 10 Dec 2007 01:04:31 +0100 [thread overview]
Message-ID: <20071210000429.GA3916@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <20071209213642.GA27096@rhlx01.hs-esslingen.de>
Hi,
On Sun, Dec 09, 2007 at 10:36:42PM +0100, Andreas Mohr wrote:
> And the second, possibly much more lucrative, question would be
> whether we're actually doing something wrong with our ACPI _GTM execution
> which triggers the AE_AML_PACKAGE_LIMIT problem.
>
> This might help here, perhaps (relevant snippets of AML dump):
Indeed, after looking over this horrid ASL stuff for ages I'm now starting
to believe that our IDE controller state is wrong,
since the Match()ing etc. in this particular _GTM implementation
is heavily dependant on actual PCI values
(it references some PCI_Config OperationRegion:s),
and some indexing seems to go wrong due to this.
IOW, it seems very likely that _GTM on these BIOSes (VIA chipsets) isn't
actually wrongly implemented but simply expects IDE controller values
to have been set up ""differently"".
Or... one could possibly even infer from this that - maybe -
the _GTM invocation spot is wrong, it should be done somewhere
different during bootup. Or whatever.
This seems to tell me again that we're often quick to blacklist
or whitelist things left and right when instead fundamental problems
are hidden somewhere.
Still investigating,
Andreas Mohr
next prev parent reply other threads:[~2007-12-10 0:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.qQhD8aJpiTOFaZqjRYwoaG7YT1c@ifi.uio.no>
[not found] ` <fa.yaP86AixGhz5Q7eXSu04pIQp6ho@ifi.uio.no>
[not found] ` <fa.c3k8VKWAx4HIo9zXWbL5Ek0oSBw@ifi.uio.no>
[not found] ` <fa.C8ACnOhs8bXB++vmugf5F34JcJg@ifi.uio.no>
[not found] ` <fa.5o6E6S0UWnARbQPxLe30TvLQIiY@ifi.uio.no>
2007-12-08 18:24 ` 2.6.24-rc4-git5: Reported regressions from 2.6.23 Robert Hancock
2007-12-09 5:59 ` Tejun Heo
2007-12-09 21:36 ` Andreas Mohr
2007-12-10 0:04 ` Andreas Mohr [this message]
2007-12-10 0:49 ` Andreas Mohr
2007-12-10 1:28 ` Robert Hancock
2007-12-10 2:25 ` Tejun Heo
2007-12-10 3:20 ` Robert Hancock
2007-12-10 2:20 ` Tejun Heo
[not found] <200712080340.49546.rjw@sisk.pl>
[not found] ` <20071208013631.3147986a.akpm@linux-foundation.org>
[not found] ` <20071208101256.GA25807@rhlx01.hs-esslingen.de>
2007-12-08 10:20 ` Andrew Morton
2007-12-08 10:28 ` Matthew Garrett
2007-12-08 10:55 ` Andreas Mohr
2007-12-09 15:46 ` Tejun Heo
2007-12-09 19:59 ` Andreas Mohr
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=20071210000429.GA3916@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=akpm@linux-foundation.org \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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