From: Stephen Hemminger <shemminger@osdl.org>
To: Jay Libove <libove@felines.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] recent crashes? Linux kernel 2.6.18-1.2239.fc5 (Linux Fedora Core 5)
Date: Wed, 29 Nov 2006 17:14:20 -0800 [thread overview]
Message-ID: <20061129171420.3d45ed78@freekitty> (raw)
In-Reply-To: <587BB495FD172F43931DE54C0AFD218616F9FF@reset6.ad2.felines.org>
On Wed, 29 Nov 2006 19:29:17 -0500
"Jay Libove" <libove@felines.org> wrote:
> Recently, possibly since the most recent one or two kernel upgrades in
> Linux Fedora Core 5, my system has been crashing with a kernel panic.
> The panic prevents anything useful from being written to any log files,
> but on the crash trace left on the screen each time I always see
> something which looks like it is in the bridge code.
>
If it is a server, please capture the console log during the panic output,
then developers can analyze it.
Ways of doing that are (in order of usefulness):
1. Serial console - most reliable
2. Camera picture with digital camera. Problem is screen resolution limits
the amount of info. Also not easy to get a good picture
3. Netconsole. Problem is that for networking bugs, the panic output
may never make it out.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-11-30 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 0:29 [Bridge] recent crashes? Linux kernel 2.6.18-1.2239.fc5 (Linux Fedora Core 5) Jay Libove
2006-11-30 1:14 ` Stephen Hemminger [this message]
2006-11-30 2:36 ` Stephen Hemminger
2006-11-30 2:43 ` Jay Libove
2006-11-30 13:55 ` Andy Gospodarek
[not found] <mailman.1.1164916801.6856.bridge@lists.osdl.org>
2006-12-01 22:10 ` Jay Libove
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=20061129171420.3d45ed78@freekitty \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=libove@felines.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