I've just built a new machine using a ASUS M2A-VM boardboard (ATI SB600 chipset), AMD X2 3800+ processor, and 2 Western Digital 2.5" 80Gb drives running in RAID-1 using MD. I've had these problems with both 2.6.22.1 and now 2.6.22.5 kernels. I'm getting the following errors on occasion: Aug 24 13:19:22 playpbx kernel: APIC error on CPU0: 00(40) Aug 24 13:19:33 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:20:01 playpbx last message repeated 5 times Aug 24 13:20:54 playpbx last message repeated 2 times Aug 24 13:21:40 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:23:23 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:24:35 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:25:51 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:26:37 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:29:11 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:30:01 playpbx last message repeated 4 times Aug 24 13:30:46 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:32:21 playpbx last message repeated 2 times Aug 24 13:33:33 playpbx last message repeated 2 times Aug 24 13:35:14 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:36:10 playpbx last message repeated 3 times Aug 24 13:37:04 playpbx last message repeated 2 times Aug 24 13:38:25 playpbx last message repeated 2 times Aug 24 13:38:43 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:40:08 playpbx last message repeated 3 times Aug 24 13:40:57 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:42:28 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:43:37 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:45:04 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:45:11 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:46:47 playpbx last message repeated 2 times Aug 24 13:47:33 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:48:15 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:49:56 playpbx kernel: APIC error on CPU0: 40(40) Aug 24 13:51:34 playpbx kernel: APIC error on CPU0: ...
On Fri, 24 Aug 2007 14:39:10 +0100 Probably not connected - your drive seems to be talking rubbish Neither are good, the latter is probably a drive firmware problem and the kernel will give up using NCQ with it if it keeps doing that, which should be just fine. -
FWIW, I've got the HDMI version of this board and I have exactly the same problem (even with the newest BIOS) if nmi_watchdog is not set to zero. Try booting with nmi_watchdog=0 (default on x86-64, I think) and see if these go away. I get the feeling this problem is independent of the APIC errors, and I don't see it here. I'm using Hitachi Deskstars on the on-board controller in AHCI mode, and everything works fine. As Alan said, it's very possibly just the drive not properly supporting NCQ. -- Cheers, Alistair. 137/1 Warrender Park Road, Edinburgh, UK. -
