Re: Machine Check Exception on dual core Xeon

On Fri, 20 Oct 2006 23:30:49 -0400 Dave Jones wrote:

>  > You missed the blatantly obvious error message:
>  > "This is not a software problem!"
>  > 
>  > Immediately followed by:
>  > "contact your hardware vendor"
>  > 
>  > Please follow that advice
> 
> Maybe someone needs to implement <blink> tags for printk ;-)

oops, I didn't do it for MCEs.. :)
and I used reverse video since I dislike blinking.

photo:  http://www.xenotime.net/linux/doc/kernel-msg-hilite.jpg

patch:  http://www.xenotime.net/linux/patches/kernel-hilite-msg.patch
(with caveats)

---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Machine Check Exception on dual core Xeon
    • From: Dave Jones <[email protected]>

• References:
  • Machine Check Exception on dual core Xeon
    • From: "Steven Truong" <[email protected]>
  • Re: Machine Check Exception on dual core Xeon
    • From: Kyle Moffett <[email protected]>
  • Re: Machine Check Exception on dual core Xeon
    • From: Dave Jones <[email protected]>

• Prev by Date: Re: [patch] drivers: wait for threaded probes between initcall levels
• Next by Date: Re: AMD X2 unsynced TSC fix?
• Previous by thread: Re: Machine Check Exception on dual core Xeon
• Next by thread: Re: Machine Check Exception on dual core Xeon
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]