aboutsummaryrefslogtreecommitdiffstats
path: root/arch/i386/kernel/traps.c
diff options
context:
space:
mode:
authorAndi Kleen <ak@suse.de>2006-12-06 20:14:03 -0500
committerAndi Kleen <andi@basil.nowhere.org>2006-12-06 20:14:03 -0500
commit9c5f8be4625e73f17e28fea89399ed871a30e064 (patch)
treeae203297cc2fa309ef5807349ee1303c2b20712f /arch/i386/kernel/traps.c
parent7cd8b6861eb586aabe4c725cc0c259ce2e653695 (diff)
[PATCH] x86: Mention PCI instead of RAM in NMI parity error message
On modern systems RAM errors don't cause NMIs, but it's usually caused by PCI SERR. Mention PCI instead of RAM in the printk. Reported by r_hayashi@ctc-g.co.jp (Ryutaro Hayashi) Cc: r_hayashi@ctc-g.co.jp Signed-off-by: Andi Kleen <ak@suse.de>
Diffstat (limited to 'arch/i386/kernel/traps.c')
-rw-r--r--arch/i386/kernel/traps.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/i386/kernel/traps.c b/arch/i386/kernel/traps.c
index 4a6fa2837df2..237f4884a1e1 100644
--- a/arch/i386/kernel/traps.c
+++ b/arch/i386/kernel/traps.c
@@ -708,8 +708,7 @@ mem_parity_error(unsigned char reason, struct pt_regs * regs)
708{ 708{
709 printk(KERN_EMERG "Uhhuh. NMI received for unknown reason %02x on " 709 printk(KERN_EMERG "Uhhuh. NMI received for unknown reason %02x on "
710 "CPU %d.\n", reason, smp_processor_id()); 710 "CPU %d.\n", reason, smp_processor_id());
711 printk(KERN_EMERG "You probably have a hardware problem with your RAM " 711 printk(KERN_EMERG "You have some hardware problem, likely on the PCI bus.\n");
712 "chips\n");
713 if (panic_on_unrecovered_nmi) 712 if (panic_on_unrecovered_nmi)
714 panic("NMI: Not continuing"); 713 panic("NMI: Not continuing");
715 714