LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 07-29-2004, 02:04 PM   #1
robberttheman
LQ Newbie
 
Registered: Jul 2004
Posts: 15

Rep: Reputation: 0
Kernel: APIC error on CPU - What to do?


Hi there, i am kind of a newby and i have a clean install running of fedora core2. After that i have installed several programs, among that for example, Apache, mysql, php, samba and some other things.

Everything works fine, but sometimes i get segmentation faults. First i doubted my memory, but since i found where the syslog is, i found the following message:

irq 10: nobody cared! (screaming interrupt?)
and kernel: APIC error on CPU0: 40(40)

Well i don't know what these messages mean, but what i do know is that it crashes my system. After a reboot it works fine for a while. Because i would like to solve this "problem" I would like to ask wether someone has encountered this before and knows a solution for me?

My system has 1 Gb of memory, dual 800 P3 and plenty of hard drives in it :-)

Who could help my out please? A snippet of the code i pasted here: (sorry for the big thread, i didn't see an option to attach anything)

Jul 28 21:11:02 server2004 nmbd[1670]: *****
Jul 28 21:34:50 server2004 kernel: APIC error on CPU0: 00(40)
Jul 28 22:18:02 server2004 kernel: irq 10: nobody cared! (screaming interrupt?)
Jul 28 22:18:02 server2004 kernel: [<0210857a>] __report_bad_irq+0x2b/0x67
Jul 28 22:18:02 server2004 kernel: [<02108612>] note_interrupt+0x43/0x66
Jul 28 22:18:02 server2004 kernel: [<02108864>] do_IRQ+0x134/0x19a
Jul 28 22:18:02 server2004 kernel: [<02105018>] default_idle+0x0/0x2c
Jul 28 22:18:02 server2004 kernel: [<02105041>] default_idle+0x29/0x2c
Jul 28 22:18:02 server2004 kernel: [<0210509d>] cpu_idle+0x26/0x3b
Jul 28 22:18:02 server2004 kernel: [<0235d779>] start_kernel+0x197/0x199
Jul 28 22:18:02 server2004 kernel:
Jul 28 22:18:02 server2004 kernel: handlers:
Jul 28 22:18:02 server2004 kernel: [<02231ff1>] (usb_hcd_irq+0x0/0x4b)
Jul 28 22:18:02 server2004 kernel: [<02231ff1>] (usb_hcd_irq+0x0/0x4b)
Jul 28 22:18:02 server2004 kernel: Disabling IRQ #10
Jul 28 22:18:11 server2004 kernel: APIC error on CPU0: 40(40)
Jul 28 22:18:44 server2004 last message repeated 17 times
Jul 28 22:19:52 server2004 last message repeated 28 times
Jul 28 22:20:53 server2004 last message repeated 20 times
Jul 28 22:21:55 server2004 last message repeated 18 times
Jul 28 22:22:56 server2004 last message repeated 21 times
Jul 28 22:24:13 server2004 last message repeated 21 times
Jul 28 22:25:16 server2004 last message repeated 23 times
Jul 28 22:26:29 server2004 last message repeated 17 times
Jul 28 22:27:38 server2004 last message repeated 9 times
Jul 28 22:28:40 server2004 last message repeated 24 times
Jul 28 22:29:52 server2004 last message repeated 24 times
Jul 28 22:30:56 server2004 last message repeated 15 times
Jul 28 22:31:57 server2004 last message repeated 28 times
Jul 28 22:32:58 server2004 last message repeated 30 times
Jul 28 22:33:59 server2004 last message repeated 23 times
Jul 28 22:35:12 server2004 last message repeated 26 times
Jul 28 22:48:37 server2004 last message repeated 31 times
Jul 28 22:49:40 server2004 kernel: APIC error on CPU0: 40(40)
Jul 28 22:50:54 server2004 last message repeated 23 times
Jul 28 22:51:55 server2004 last message repeated 22 times
Jul 28 22:52:56 server2004 last message repeated 22 times
Jul 28 22:53:57 server2004 last message repeated 27 times
Jul 28 22:54:58 server2004 last message repeated 21 times
Jul 28 22:56:06 server2004 last message repeated 27 times
Jul 28 22:57:13 server2004 last message repeated 24 times
Jul 28 22:58:14 server2004 last message repeated 29 times
Jul 28 22:59:18 server2004 last message repeated 23 times
Jul 28 23:00:19 server2004 last message repeated 22 times
Jul 28 23:01:33 server2004 last message repeated 14 times
Jul 28 23:02:36 server2004 last message repeated 20 times
Jul 28 23:03:37 server2004 last message repeated 24 times
Jul 28 23:05:54 server2004 last message repeated 19 times
Jul 28 23:06:55 server2004 last message repeated 20 times
Jul 28 23:07:57 server2004 last message repeated 20 times
Jul 28 23:08:58 server2004 last message repeated 24 times
Jul 28 23:10:00 server2004 last message repeated 24 times
Jul 28 23:11:01 server2004 last message repeated 18 times
Jul 28 23:12:02 server2004 last message repeated 15 times
Jul 28 23:12:59 server2004 last message repeated 20 times
Jul 29 04:02:02 server2004 logrotate: ALERT exited abnormally with [1]
Jul 29 11:49:08 server2004 kernel: APIC error on CPU0: 40(40)
Jul 29 16:41:43 server2004 kernel: APIC error on CPU0: 40(40)
Jul 29 16:42:45 server2004 last message repeated 16 times
Jul 29 16:43:46 server2004 last message repeated 30 times
Jul 29 16:44:47 server2004 last message repeated 26 times
Jul 29 16:45:49 server2004 last message repeated 24 times
Jul 29 16:46:51 server2004 last message repeated 18 times
Jul 29 16:47:59 server2004 last message repeated 22 times
Jul 29 16:49:03 server2004 last message repeated 18 times
Jul 29 16:50:04 server2004 last message repeated 29 times
Jul 29 16:51:09 server2004 last message repeated 18 times
Jul 29 16:52:10 server2004 last message repeated 18 times
Jul 29 16:53:21 server2004 last message repeated 23 times
Jul 29 16:54:11 server2004 last message repeated 12 times
Jul 29 16:54:11 server2004 kernel: APIC error on CPU1: 00(40)
Jul 29 16:54:22 server2004 kernel: APIC error on CPU0: 40(40)
Jul 29 16:55:02 server2004 last message repeated 24 times
Jul 29 16:56:03 server2004 last message repeated 17 times
Jul 29 16:57:05 server2004 last message repeated 17 times
Jul 29 16:58:08 server2004 last message repeated 19 times
Jul 29 16:59:09 server2004 last message repeated 21 times
Jul 29 17:00:15 server2004 last message repeated 31 times
Jul 29 17:01:25 server2004 last message repeated 16 times
Jul 29 17:00:15 server2004 last message repeated 31 times
Jul 29 17:01:25 server2004 last message repeated 16 times
Jul 29 17:02:26 server2004 last message repeated 31 times
Jul 29 17:03:29 server2004 last message repeated 20 times
Jul 29 17:04:31 server2004 last message repeated 18 times
Jul 29 17:05:38 server2004 last message repeated 19 times
Jul 29 17:06:43 server2004 last message repeated 15 times
Jul 29 17:07:45 server2004 last message repeated 17 times
Jul 29 17:08:47 server2004 last message repeated 20 times
Jul 29 17:09:48 server2004 last message repeated 26 times
Jul 29 17:10:49 server2004 last message repeated 14 times
Jul 29 17:12:10 server2004 last message repeated 6 times
Jul 29 17:13:13 server2004 last message repeated 21 times
Jul 29 17:14:21 server2004 last message repeated 17 times
Jul 29 17:15:27 server2004 last message repeated 23 times
Jul 29 17:16:45 server2004 last message repeated 24 times
Jul 29 17:17:56 server2004 last message repeated 21 times
Jul 29 17:19:03 server2004 last message repeated 16 times
Jul 29 17:20:07 server2004 last message repeated 20 times
Jul 29 17:21:12 server2004 last message repeated 17 times
Jul 29 17:22:13 server2004 last message repeated 27 times
Jul 29 17:23:22 server2004 last message repeated 20 times
Jul 29 18:20:54 server2004 syslogd 1.4.1: restart.
Jul 29 18:20:55 server2004 syslog: syslogd startup succeeded
 
Old 07-29-2004, 04:08 PM   #2
slacky
Member
 
Registered: Feb 2004
Location: USA
Distribution: Debian
Posts: 174

Rep: Reputation: 16
You could try passing "noapic" as a kernel boot argument and see what happens:
http://www.ibiblio.org/mdw/HOWTO/BootPrompt-HOWTO.html
 
Old 07-30-2004, 12:00 AM   #3
robberttheman
LQ Newbie
 
Registered: Jul 2004
Posts: 15

Original Poster
Rep: Reputation: 0
Could you perhaps tell me how to use this? I am usning a 2.6.6 kernel, could you perhaps explain where i can alter this? I kind of a newby

Thx in advance,

Robbert
 
Old 07-30-2004, 07:55 AM   #4
slacky
Member
 
Registered: Feb 2004
Location: USA
Distribution: Debian
Posts: 174

Rep: Reputation: 16
Quote:
Originally posted by robberttheman
Could you perhaps tell me how to use this? I am usning a 2.6.6 kernel, could you perhaps explain where i can alter this? I kind of a newby
The simplest way to test this is to pass to "noapic" to the kernel at boot time - you can test it without making permanent changes at the boot loader when your system starts up. Fedora uses the GRUB boot loader by default (you could have possibly picked LILO at install time) - its the screen where you pick the kernel version to run right after the BIOS screens. I'm not too familiar with GRUB (I usually use LILO), but it should tell you a key to press to edit the kernel boot parameters before it times out - might even be 'e', iirc. You probably just add in "noapic" to the end of the line if GRUB works like LILO. Then if it works you can make the change permanent by editing the grub config file (/boot/grub/grub.conf?).
 
Old 07-30-2004, 07:57 AM   #5
robberttheman
LQ Newbie
 
Registered: Jul 2004
Posts: 15

Original Poster
Rep: Reputation: 0
Great i will try, thx 4 your help!
 
Old 01-26-2005, 02:01 PM   #6
whysyn
Member
 
Registered: Jun 2003
Location: Cleveburg, OH
Distribution: mostly Fedora
Posts: 154

Rep: Reputation: 30
I see this question asked all the time, and a very common answer seems to be "disable APIC"

What is APIC, and what are the effects of turning it off? If it isn't necessary, why is it on in the first place? I'm running a system that has been stable for over two years (in fact no even rebooted in over a year) that all of a sudden started logging these errors. I'm worried and would like to fix it, but I want to understand the effects of what I'm doing.

2.4.18-smp
up 386 days, 5:04

Dual AthlonMP 2000+
2 GB ECC RAM
4 x 76 GB SCSI on Adaptec RAID (raid 5, external enclosure with dedicated power)
Pioneer DVD-RW
 
Old 01-26-2005, 02:03 PM   #7
whysyn
Member
 
Registered: Jun 2003
Location: Cleveburg, OH
Distribution: mostly Fedora
Posts: 154

Rep: Reputation: 30
Sadly, the server crashed this afternoon. It didn't even make it to 386 days 6:00...

Any assistance on this error would be greatly appreciated, why it comes, what it means, how to troubleshoot it (without just passing noapic to the kernel). I want to fix it, not just do a workaround.

Thank you very much!

EDIT:
By the way, ALL of the errors I get are either
host.name kernel: APIC error on CPU0: 02(02)
or
host.name kernel: APIC error on CPU1: 02(02)

I assume the 02(02) code should be telling me something... don't know what. Also, the occur evenly on CPU0 and CPU1.


Last edited by whysyn; 01-26-2005 at 05:39 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
kernel: APIC error on CPU1: 02(02) Cronjob Linux - Hardware 1 03-22-2005 09:24 PM
APIC error on CPU0: 00(02) on a dual athlon running SMP kernel asalford Linux - Hardware 0 08-30-2004 11:23 PM
XT-PIC vs. IO-APIC-edge vs. IO-APIC-level pebraun Linux - Newbie 0 04-19-2004 04:10 PM
APIC error on CPU 0 upon install fedeloco Linux - Hardware 0 02-12-2004 11:30 AM
Kernel compile error/system hangs, APIC/ACPI taids Linux - Hardware 14 08-23-2003 06:11 AM


All times are GMT -5. The time now is 04:49 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration