From: Neil Brown <neilb@cse.unsw.edu.au>
To: Albert Cahalan <albert@users.sourceforge.net>
Date: Tue, 25 Nov 2003 13:05:26 +1100
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16322.47334.29252.724441@notabene.cse.unsw.edu.au>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
       oliver@neukum.name, aliakc@web.de, lenehan@twibble.org,
       mingo@redhat.com
Subject: Re: kernel BUG at raid5.c:337!
In-Reply-To: message from Albert Cahalan on  November 24
References: <1069721971.723.408.camel@cube>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 952
Lines: 25

On  November 24, albert@users.sourceforge.net wrote:
> 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?  :-)
> 

Well, given that it could be any release, pre-release, vendor, or
local-patched kernel since 2.2.something, even if you found one with a
BUG at raid5.c:337 you couldn't be sure that you had found the right
one, the only suggestion that I would have, assuming the owner of the
machine wanted a suggestion, is "Upgrade to a current kernel".

NeilBrown

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