Rial Juan wrote:
> Have the same stuff with my BP6 board. I'm curious as to what it is though,
> all they could tell me is that an APIC error is something comparable to a
> lost interrupt...
>
> It happens more frequently when overclocking, and much less frequently when
> running at normal speeds.
>
> Does your board crash often? Mine does sometimes, and I'm still
> investigating if it has anything to do with these APIC errors.
>
>
>
> On 2001.05.04 04:17 Larry Sword wrote:
>
>> Help
>>
>> Unit: Abit Motherboard w/ 2x366 Celerons OC to 550MHz.
>> VGA: Maxtor 400 @ IRQ 18
>> SC: Soundblaster Live @ IRQ 17
>> Memory: 256Mb
>> OS: Linux-Mandrake 8.0 SMP Kernel
>>
>> 1. After loading Linux-Mandrake Version 8.0 I'm finding the following
>> message:
>>
>> May 2 18:15:09 sword kernel: Unknown bridge resource 0: assuming
>> transparent
>> May 2 18:25:23 sword kernel: APIC error on CPU0: 00(08)
>> May 2 18:25:23 sword kernel: APIC error on CPU1: 00(04)
>> May 2 18:33:06 sword kernel: APIC error on CPU0: 08(02)
>> May 2 22:27:21 sword kernel: APIC error on CPU0: 02(02)
>> May 3 08:57:16 sword kernel: Unknown bridge resource 0: assuming
>> transparent
>> May 3 18:39:57 sword kernel: APIC error on CPU0: 00(02)
>>
>> This is after opening xmms and playing a location radio station such as
>> Live365.
>> I've checked numerous time and the message occurs only after I use xmms
>> for any reason.
>>
>> 2. Things I've tried without success.
>>
>> Reduced the cpu speed to 366 (original speed of cpu)
>> Changed MPC to and from 1.1 to 1.4
>>
>> Any thought on what could be causing this and have any others
>> experienced this
>> type of behavior in L-M 8.0?
>
Yes, this came up on my machine as well when I switched to kernel > 2.4
Apparently it has something to do with the voltage regulator on the rev
1.0 BP6 board.
[quote from usenet]
> What's happening, if I understand it correctly, is the CPU is getting "hung
> up" momentarily. Eventually it works itself out, which is why it isn't really
> an issue. There's the argument that it hurts system performance, but I don't
> think it does so to a measurable degree.
[/quote]
Also, these errors were probably already there in kernel 2.2.x, but they
were not logged.
I used to get the same errors when I used the 2.4.0 kernel with mandrake
7.2, but they seem to be gone now in mandrake 8.
It doesn't seem to cause any serious problems though....I wouldn't worry
too much.
One option is to recompile the kernel with the apic stuff turned off, so
the errors are no longer logged.
It has also been suggested to switch the MPS specification in the bios
back to 1.1. Haven't tried that though
Leander
