From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: oliver@neukum.name, aliakc@web.de, lenehan@twibble.org,
mingo@redhat.com, neilb@cse.unsw.edu.au
Subject: kernel BUG at raid5.c:337!
Date: 24 Nov 2003 19:59:32 -0500 [thread overview]
Message-ID: <1069721971.723.408.camel@cube> (raw)
Got a picture of a crash on a kiosk or something, as
a Linux example in Slashdot's public BSOD sightings...
http://w3.physics.uiuc.edu/~menscher/tekram1.jpg
So... unknown kernel version, but there's a
line number that ought to narrow things down.
Can anybody help this guy? :-)
next reply other threads:[~2003-11-25 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 0:59 Albert Cahalan [this message]
2003-11-25 2:05 ` kernel BUG at raid5.c:337! Neil Brown
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=1069721971.723.408.camel@cube \
--to=albert@users.sf.net \
--cc=aliakc@web.de \
--cc=lenehan@twibble.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
--cc=oliver@neukum.name \
/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.