From: Chuck Ebbert <76306.1226@compuserve.com>
To: Hawk Xu <hxunix@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Aiee, killing interrupt handler!
Date: Thu, 21 Dec 2006 03:05:24 -0500 [thread overview]
Message-ID: <200612210308_MC3-1-D5D4-3329@compuserve.com> (raw)
In-Reply-To: <4587B2C5.9000703@gmail.com>
On Tue, 19 Dec 2006 17:37:09 +0800, Hawk Xu wrote:
> > You need to post the entire oops message, not just the last part. It should
> > start with "BUG". And using a more recent kernel would be a good idea.
> >
>
> I'm sorry, but that's all we have now. Our customer just sent us a
> photo of the kernel panic screen.
They need to boot in 50-line vga mode then, so more can be seen.
> Our client also sent the /var/log/kernel file to us. According to the
> log file, everytime before kernel panic, there are some error messages.
> The server encountered kernel panic three times, below are the error
> messages before each time:
Those are normal when running buggy usermode code, but they should
never be able to affect the kernel.
--
MBTI: IXTP
next reply other threads:[~2006-12-21 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 8:05 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-19 7:02 Chuck Ebbert
2006-12-19 9:37 ` Hawk Xu
2006-12-19 4:06 Hawk Xu
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=200612210308_MC3-1-D5D4-3329@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=hxunix@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®