Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-13-2007, 07:55 AM
|
#1
|
Member
Registered: Oct 2007
Location: The States, Florida
Distribution: Lonely Werewolf
Posts: 251
Rep:
|
MP BIOS bug: 8254
Hey,
I just got an error that states "MP BIOS bug: 8254. Timer not connected to IO-APIC. I've researched this and it has to do with sending IRQ to multiple CPU's. Now I have an AMD 64 X2 4200, and Fedora 8 64-bit has been installed since Sunday. I only received this error when I installed a new PSU and video card last night at about 11:00EST. I've seen various fixes for this problem, but I have a question... will any of them make my processor lose functionality? I don't want to lose any performance if possible. Any help is appreciated.
Thanks,
Brandon
|
|
|
11-14-2007, 11:56 AM
|
#2
|
LQ 5k Club
Registered: May 2003
Location: London, UK
Distribution: Fedora40
Posts: 6,156
|
Quote:
I've seen various fixes for this problem, but I have a question... will any of them make my processor lose functionality? I don't want to lose any performance if possible. Any help is appreciated.
|
Well, you have not told us what these "fixes" are, so we cannot comment on what they might or might not do.
However, it's unlikely you'll loose any performance.
I suggest you benchmark your PC, apply one of the fixes, and re-test it. All OK = Good. Something not right = Undo the "fix" you tried an try a different "fix".
Have fun 
|
|
|
11-14-2007, 12:22 PM
|
#3
|
Member
Registered: Oct 2007
Location: The States, Florida
Distribution: Lonely Werewolf
Posts: 251
Original Poster
Rep:
|
Hey,
Sorry for being so vague. I posted this after I first woke up in the morning. NOt much of a morning person. The fixes I was referring to were posted in the Ubuntuforums.org: http://ubuntuforums.org/showthread.php?t=191355&page=1
The fixes consisted of passing 'noapic' to the kernel, or disabling it from the BIOS. I was thinking that if this was disabled, it would decrease performance. Can you suggest a decent benchmarking tool? I'm not familiar with any.
Thanks,
Brandon
|
|
|
11-14-2007, 12:53 PM
|
#4
|
LQ 5k Club
Registered: May 2003
Location: London, UK
Distribution: Fedora40
Posts: 6,156
|
Quote:
Can you suggest a decent benchmarking tool? I'm not familiar with any.
|
Sorry, no. If my PC is working, I'm happy.
But passing noapic to the kernel is not going to affect your performance, only the way interrupts are allocated and handled by the kernel (which is concerned with performance, and will do things the very best way it can). So just try it 
|
|
|
11-14-2007, 01:44 PM
|
#5
|
Member
Registered: Oct 2007
Location: The States, Florida
Distribution: Lonely Werewolf
Posts: 251
Original Poster
Rep:
|
Hey,
Thanks. T minus 3 hours and count before I go home and try it.
Regards,
Brandon
|
|
|
11-17-2007, 09:37 AM
|
#6
|
Member
Registered: Oct 2007
Location: The States, Florida
Distribution: Lonely Werewolf
Posts: 251
Original Poster
Rep:
|
Hey,
sorry it took me so long to get back. I've tried many switches from the grub menu and none of them work. The ones I've tried are: noapic--, nolapic, nolapic_timer. I've also tried looking in my BIOS to try and disable apic, but there is no such option. Anyone else have any ideas? It doesn't seem to be system critical, but it's kind of annoying seeing that pop up every time I boot.
Regards,
Brandon
|
|
|
11-17-2007, 10:44 AM
|
#7
|
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613
Rep:
|
APIC is your Advanced Programmable Interrupt Controller. You may want to hunt around your BIOS for IRQ options. The one time I had similar messages from some hardware there was indeed an APIC option in the BIOS, you may just have to look for different names.
-Chad
|
|
|
11-17-2007, 11:39 AM
|
#8
|
LQ 5k Club
Registered: May 2003
Location: London, UK
Distribution: Fedora40
Posts: 6,156
|
Kernel interrupt options I am aware of:
Code:
Interrupts are a complex aspect of kernel behavior. The boot time options deal
mostly with the interface between the kernel and the hardware that handles inter-
rupts, such as the Intel chip’s Advanced Programmable Interrupt Controller
(APIC).
apic Change the verbosity of the APIC subsystem when booting.
apic=[quiet|verbose|debug]
Control how much information the APIC subsystem generates
when booting the kernel. The default is quiet.
noapic Do not use any IOAPICs.
Prevent the kernel from using any of the IOAPICs that might be
present in the system.
lapic Enable the local APIC.
Cause the kernel to enable the local APIC even if the BIOS had
disabled it.
nolapic Do not use the local APIC.
Tell the kernel not to use the local APIC.
noirqbalance Disable kernel IRQ balancing.
Disable all of the built-in kernel IRQ balancing logic.
irqfixup Basic fix to interrupt problems.
When an interrupt is not handled, search all known interrupt
handlers for it. This is intended to get systems with badly broken
firmware running.
irqpoll Extended fix to interrupt problems.
When an interrupt is not handled, search all known interrupt
handlers for it and also check all handlers on each
timer-interrupt.
This is intended to get systems with badly broken firmware
running.
noirqdebug Disable unhandled interrupt detection.
By default, the kernel attempts to detect and disable unhandled
interrupt sources because they can cause problems with the respon-
siveness of the rest of the kernel if left unchecked. This option
disables this logic.
BIOS options differ, but if there is an option for "Enable PnP", disable it.
|
|
|
11-17-2007, 01:16 PM
|
#9
|
Member
Registered: Oct 2007
Location: The States, Florida
Distribution: Lonely Werewolf
Posts: 251
Original Poster
Rep:
|
Hey,
Thanks Tred. I'll try those when I get home. Chad... I looked everywhere in my BIOS. The only thing in there related to IRQ is for my parallel port and what IRQ number I'd like it to be or if I'd like to disable it. I've disabled it and it still comes up. there is NO other disable option for IRQ.
Regards,
Brandon
|
|
|
All times are GMT -5. The time now is 01:23 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|