aboutsummaryrefslogtreecommitdiffstats
path: root/arch/x86_64/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/x86_64/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/x86_64/kernel/traps.c')
-rw-r--r--arch/x86_64/kernel/traps.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/x86_64/kernel/traps.c b/arch/x86_64/kernel/traps.c
index e37b4d77d5a8..70bfaab9822c 100644
--- a/arch/x86_64/kernel/traps.c
+++ b/arch/x86_64/kernel/traps.c
@@ -793,8 +793,7 @@ mem_parity_error(unsigned char reason, struct pt_regs * regs)
793{ 793{
794 printk(KERN_EMERG "Uhhuh. NMI received for unknown reason %02x.\n", 794 printk(KERN_EMERG "Uhhuh. NMI received for unknown reason %02x.\n",
795 reason); 795 reason);
796 printk(KERN_EMERG "You probably have a hardware problem with your " 796 printk(KERN_EMERG "You have some hardware problem, likely on the PCI bus.\n");
797 "RAM chips\n");
798 797
799 if (panic_on_unrecovered_nmi) 798 if (panic_on_unrecovered_nmi)
800 panic("NMI: Not continuing"); 799 panic("NMI: Not continuing");