From: Heinz Diehl <htd@fancy-poultry.org>
To: Len Brown <lenb@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger-kernel.org, linux-acpi@vger.kernel.org
Subject: Re: ACPI exception with 2.6.29-rc6
Date: Tue, 24 Feb 2009 16:01:52 +0100 [thread overview]
Message-ID: <20090224150152.GA4885@fancy-poultry.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0902232128340.16923@localhost.localdomain>
On 24.02.2009, Len Brown wrote:
> Please attach the output of acpidump here:
> http://bugzilla.kernel.org/show_bug.cgi?id=12758
Did just upload the attachment.
> Also, if this system has both pic and IOAPIC mode,
> it would be interesting to try booting it in both,
> eg with "noapic".
Booting with the "noapic" option, the logfile shows:
[....]
<7>bus: 00 index 3 mmio: [d0000000, efffffff]
<7>bus: 00 index 4 mmio: [230000000, fcffffffff]
<6>ACPI: bus type pci registered
<5>PCI: MCFG configuration 0: base f0000000 segment 0 buses 0 - 127
<5>PCI: MCFG area at f0000000 reserved in E820
<6>PCI: Using MMCONFIG at f0000000 - f7ffffff
<6>PCI: Using configuration type 1 for base access
<4>bio: create slab <bio-0> at 0
<7>ACPI: EC: Look up EC in DSDT
<3>ACPI: Denied BIOS AML access to invalid port 0x4d0+0x2 (ELCR)
<4>ACPI Exception (dsopcode-0419): AE_AML_ILLEGAL_ADDRESS, During address validation of OpRegion [ELCR] [20081204]
<6>ACPI: Interpreter enabled
<6>ACPI: (supports S0 S1 S5)
<6>ACPI: Using PIC for interrupt routing
<6>ACPI: No dock devices found.
<6>ACPI: PCI Root Bridge [PCI0] (0000:00)
<7>pci 0000:00:01.1: reg 10 io port: [0xe800-0xe83f]
[....]
Greetings,
Heinz.
next prev parent reply other threads:[~2009-02-24 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871vtpqex0.wl%htd@fancy-poultry.org>
2009-02-23 21:25 ` ACPI exception with 2.6.29-rc6 Rafael J. Wysocki
2009-02-23 23:07 ` Andrew Morton
2009-02-24 2:30 ` Len Brown
2009-02-24 15:01 ` Heinz Diehl [this message]
2009-02-24 15:03 ` Heinz Diehl
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=20090224150152.GA4885@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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