Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9c5f8be4 authored Dec 07, 2006 by Andi Kleen Committed by Andi Kleen Dec 07, 2006

[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>

parent 7cd8b686

arch/i386/kernel/traps.c

+1 −2

Original line number	Diff line number	Diff line
		@@ -708,8 +708,7 @@ mem_parity_error(unsigned char reason, struct pt_regs * regs)
		{
		printk(KERN_EMERG "Uhhuh. NMI received for unknown reason %02x on "
		"CPU %d.\n", reason, smp_processor_id());
		printk(KERN_EMERG "You probably have a hardware problem with your RAM "
		"chips\n");
		printk(KERN_EMERG "You have some hardware problem, likely on the PCI bus.\n");
		if (panic_on_unrecovered_nmi)
		panic("NMI: Not continuing");

arch/x86_64/kernel/traps.c

+1 −2

Original line number	Diff line number	Diff line
		@@ -793,8 +793,7 @@ mem_parity_error(unsigned char reason, struct pt_regs * regs)
		{
		printk(KERN_EMERG "Uhhuh. NMI received for unknown reason %02x.\n",
		reason);
		printk(KERN_EMERG "You probably have a hardware problem with your "
		"RAM chips\n");
		printk(KERN_EMERG "You have some hardware problem, likely on the PCI bus.\n");

		if (panic_on_unrecovered_nmi)
		panic("NMI: Not continuing");