Messages in this thread | | | Subject | Odd problem with dual processor AMD system | From | Alan <> | Date | Mon, 14 Feb 2005 01:19:34 -0800 |
| |
I have a dual processor AMD machine.
It give apic errors after running for a while. (Usually after heavy disk i/o.)
APIC error on CPU0: 02(02) APIC error on CPU1: 02(02)
After this occurs, read/writes to/from the drive slow down substantially.
Unless...
If I set the scheduler to deadline (elevator=deadline on the kernel load line), the APIC errors remain, but the disk slowdown goes away.
My initial thought is that something in the standard scheduler is getting corrupted, but not when the deadline scheduler is used.
Is there a way to prove this?
This occurs on every 2.6.x kernel I have used.
On a similar, but different vein, if I use the "elevator=deadline" on the dual processor AMD64 machine running Fedora Core 2 (64bit version), the kernel blows up real good early enough to not leave a message in the logs. (The machine is a couple of hundred miles from me, so I am not certain what the error message on the screen is on time of detonation.)
Ideas on how to log something that early in the boot process without being in front of the machine?
-- Jag vill inte köpa den här lutefisk , den er skrapet.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |