[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440806151220l358ca541s9d87fe2acc360e8@mail.gmail.com>
Date: Sun, 15 Jun 2008 12:20:27 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: webmaster@...gonslave.de
Cc: "Alexey Starikovskiy" <aystarik@...il.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
linux-acpi@...r.kernel.org, "Ingo Molnar" <mingo@...e.hu>
Subject: Re: linux-next Regression: Unable to locate IOAPIC
On Sun, Jun 15, 2008 at 12:14 PM, Daniel Exner <dex@...gonslave.de> wrote:
> 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?
still need that... wonder why your irq routing have same entris from
your BIOS/ACPI?
YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists