Re: linux-next Regression: Unable to locate IOAPIC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Jun 15, 2008 at 12:14 PM, Daniel Exner <dex@xxxxxxxxxxxxxx> 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-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux