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: Sun, 15 Jun 2008 21:14:32 +0200 [thread overview]
Message-ID: <200806152114.33007.dex@dragonslave.de> (raw)
In-Reply-To: <86802c440806140126l7a949783of0fb08d11ae07bef@mail.gmail.com>
Hi all,
Yinghai Lu wrote:
> >> To clarify myself:
> >> 2.6.25.5: --> relatively fast no IOAPIC Errors in dmesg
> >> 2.6.26-rc5: --> relatively no IOAPIC Errors in dmesg
> >> 2.6.26-rc5 + git-acpi Patch: --> relatively no IOAPIC Errors in dmesg
> >> 2.6.26-rc5 + linux-next snapshot 20080604 --> even slower than before
> >> my ide Patch many "unable to locate IOAPIC" Errors
> >>
> >>
> >> So I think the problem lies not in the acpi tree but somewhre else.
> >>
> >> Is it possible to tell git to explicitly _exclude_ a specific tree while
> >> bisecting?
>
> can you check if the attached patch fix the problem?
> it will not check entries before MP_intsrc_info...
This fixed it, thanks :)
Also maschine feels not as fast as with 2.6.25.x but noticeable faster :)
I guss you no longer need the complete dmesg output?
Greetings
Daniel Exner
next prev parent reply other threads:[~2008-06-15 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 9:00 linux-next Regression: Unable to locate IOAPIC Daniel Exner
2008-06-06 10:17 ` 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 [this message]
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
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=200806152114.33007.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;
as well as URLs for NNTP newsgroup(s).