Date: Fri, 23 Sep 2005 12:16:16 +0930 From: "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au> To: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: Broken MP table detected ... Message-ID: <20050923024615.GT91606@squash.dsto.defence.gov.au> In-Reply-To: <200509211640.38493.jhb@FreeBSD.org> References: <20050920004358.GA76462@squash.dsto.defence.gov.au> <432F5E10.7080406@samsco.org> <200509211640.38493.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
0n Wed, Sep 21, 2005 at 04:40:36PM -0400, John Baldwin wrote:
>On Monday 19 September 2005 08:55 pm, Scott Long wrote:
>> Wilkinson, Alex wrote:
>> > Can anyone tell me what the following means, and how to fix it:
>> >
>> > APIC_IO: Testing 8254 interrupt delivery
>> > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0
>> > intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0
>> >
>> > - aW
>>
>> It means that you need to use 6.0 instead of 5.x =-) It represents the
>> old way that we connected the timecounters, which apparently isn't well
>> supported with newer amd64 boards. 6.0 solves this problem by using a
>> better supported mechanism.
>
>Actually, this is a 4.x method and it basically means that it has fallen back
>to mixed mode for IRQ0. 6.0 certainly does this better. 5.x just uses mixed
>mode by default.
John, what is mixed mode ?
- aW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050923024615.GT91606>