From: Dave Jones <davej@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Kyle Moffett <mrmacman_g4@mac.com>,
Steven Truong <midair77@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Machine Check Exception on dual core Xeon
Date: Sat, 28 Oct 2006 02:29:21 -0400 [thread overview]
Message-ID: <20061028062921.GA27101@redhat.com> (raw)
In-Reply-To: <20061027222752.5560ad81.rdunlap@xenotime.net>
On Fri, Oct 27, 2006 at 10:27:52PM -0700, Randy Dunlap wrote:
> 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
Oh my. People take me seriously far too often :-)
Could be handy for some frequently ignored bits of text
(like that mce msg), but if this gets overused it just looks
like a horrible mess imo.
Now I'm just waiting for someone to go one step further
and make openbsd style 'white on blue' kernel text ;)
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-10-28 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 23:34 Machine Check Exception on dual core Xeon Steven Truong
2006-10-17 23:54 ` Steven Truong
2006-10-18 1:43 ` Kyle Moffett
2006-10-21 3:30 ` Dave Jones
2006-10-28 5:27 ` Randy Dunlap
2006-10-28 6:29 ` Dave Jones [this message]
2006-10-28 15:51 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061028062921.GA27101@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=midair77@gmail.com \
--cc=mrmacman_g4@mac.com \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.