From: Andi Kleen <andi@firstfloor.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: 2.6.35-rc3 regression: IBM Maia system is unbootable [ACPI related?]
Date: Mon, 21 Jun 2010 18:18:17 +0200 [thread overview]
Message-ID: <87pqzkqrzq.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1277136189.10998.63.camel@mulgrave.site> (James Bottomley's message of "Mon, 21 Jun 2010 11:03:09 -0500")
James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> The system in question has a set of root bridges, with the CD rom (which
> is seen) being on bus 0 and the SCSI controller, which doesn't show up
> being on bus 1 (with several other things on busses > 1).
>
> The system uses ACPI to detect the multiple bridges, so it seems that
> this failure in 2.6.35-rc3:
>
> ACPI: Core revision 20100428
> ACPI Error: Hardware did not enter ACPI mode (20100428/evxfevnt-103)
> ACPI Warning: AcpiEnable failed (20100428/utxface-147)
> ACPI: Unable to enable ACPI
That probably causes all the other problems. Without ACPI enabled
modern systems generally do not work.
Just guessing, but maybe try to revert
b430acbd7c4b919886fa7fd92eeb7a695f1940d3
That was the last change in this area.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-06-21 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 16:03 2.6.35-rc3 regression: IBM Maia system is unbootable [ACPI related?] James Bottomley
2010-06-21 16:14 ` James Bottomley
2010-06-21 16:18 ` Andi Kleen [this message]
2010-06-21 16:33 ` James Bottomley
2010-06-21 16:54 ` James Bottomley
2010-06-21 17:26 ` James Bottomley
2010-06-29 3:49 ` Len Brown
2010-06-29 16:49 ` James Bottomley
2010-06-22 14:28 ` Maciej Rutecki
2010-06-28 21:59 ` Len Brown
2010-06-29 4:01 ` James Bottomley
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=87pqzkqrzq.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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