From: Daniel Exner <dex@dragonslave.de>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next Regression: Unable to locate IOAPIC
Date: Wed, 18 Jun 2008 23:14:02 +0200 [thread overview]
Message-ID: <200806182314.03577.dex@dragonslave.de> (raw)
In-Reply-To: <86802c440806181341w7c2ac2det817548c68d00040c@mail.gmail.com>
Yinghai Lu wrote:
> On Wed, Jun 18, 2008 at 12:57 PM, Daniel Exner <dex@dragonslave.de> wrote:
> > Yinghai Lu wrote:
> >> On Sun, Jun 15, 2008 at 12:14 PM, Daniel Exner <dex@dragonslave.de>
> >> > I guss you no longer need the complete dmesg output?
> >>
> >> still need that... wonder why your irq routing have same entris from
> >> your BIOS/ACPI?
> >
> > Again, sorry for the delay. I raised the Kernel buffer and added an
> > output, done using rc6.
> > Local APIC disabled by BIOS -- you can enable it with "lapic"
>
> sound interesting...
Tried that numerous times before. This gives me:
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
mapped APIC to ffffb000 (fee00000)
But nothing else happens. I guess the chipset doesnt support IOAPIC so a local
APIC doesnt give any benefit. (And thats the deeper cause of the regression I
originaly reported)
--
Greetings
Daniel Exner
prev parent reply other threads:[~2008-06-18 21:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806051100.12885.dex@dragonslave.de>
2008-06-06 10:17 ` linux-next Regression: Unable to locate IOAPIC Andrew Morton
2008-06-06 17:30 ` Daniel Exner
2008-06-06 18:50 ` Andrew Morton
2008-06-10 20:29 ` Daniel Exner
2008-06-11 5:47 ` Andrew Morton
2008-06-12 22:16 ` Yinghai Lu
2008-06-12 22:58 ` Alexey Starikovskiy
2008-06-13 11:07 ` Daniel Exner
2008-06-13 15:42 ` Maciej W. Rozycki
2008-06-14 7:07 ` Alexey Starikovskiy
2008-06-14 8:26 ` Yinghai Lu
2008-06-14 8:31 ` Ingo Molnar
2008-06-15 19:14 ` Daniel Exner
2008-06-15 19:20 ` Yinghai Lu
2008-06-18 19:57 ` Daniel Exner
2008-06-18 20:41 ` Yinghai Lu
2008-06-18 21:14 ` Daniel Exner [this message]
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=200806182314.03577.dex@dragonslave.de \
--to=dex@dragonslave.de \
--cc=akpm@linux-foundation.org \
--cc=aystarik@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=webmaster@dragonslave.de \
--cc=yhlu.kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox