Comment 31 for bug 116734

Revision history for this message
Fabián Rodríguez (magicfab) wrote : Re: PCI: BIOS BUG #81[49435000] found - [HP pavilion dv2000]

If anyone commenting this bug would at least care to read my previous comment or just read this[1], it would save all subscribers to this bug some time when going through comments that don't contribute to actually solving this bug.

Sorry to be so blunt, let's focus on the issue here.

[1] http://www.fedoraforum.org/forum/showpost.php?p=901026&postcount=39

Citing:

"On the whole bug #81 can be ignored as it has no material affect on a running system. The way to fix this is to either hassle your manufacturer to fix it or delve into the bios code. As I said the linux kernel is trying to setup hardware one way but the bios is saying no, go away. When the processors are setup as x86_64 they function differently to when they are setup for 32bit so this may not be an issue under 64 bit linux's.

pepe123: you don't see the message when using those parameters because linux just accepts the hardware config as presented by the bios. No code is run to rearrange the hardware in a more functional way by the kernel (bad bios code will run as bad bios code, if it is really bad then at the very least stuff won't work at the wort you will get crashes.).

noapic disables the the kernel APIC Code (Advanced Programmable Interrupt Controller). Switch this off and you don't have programmable Interrupts and other stuff.

nolapic disables the kernel local apic code. The local apic resides on the CPU and mediates access to the processor. It is not required on single processor systems but is required on dual processor ystems including dual core processors.

Routing interrupts inefficiently can decrease the systems performance somewhat and also throw up other isssues.

In some senses it is bad to use these parameters because you lose performance and possibly some functionality (for example the bios configures some hardware to share interrupts with some other hardware. Linux has a problem with this but it knows how to set things up correctly. noapic disables linux' ability to resolve the problem.)

Sometimes you need to disable apic code to run linux but if you don't then don't.

For example installing fedora 8 on my laptop works if I disable apic but it will also work if I add the vga=0x0317. So I choose the second option. If you have a problem machine then use the least intrusive solution. For these cases Google is your friend. Just remember no problem is ever a new problem

The Acpi site is an interesting read but of no practical use to the average joe. To use that info you need to be able to rewrite your bios code and does not deal directly with apic issues anyway (APIC and ACPI are different although related beasties)"