From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>
Cc: James Bottomley <James.Bottomley@suse.de>, linux-scsi@vger.kernel.org
Subject: Re: Crash in 2.6.37
Date: Mon, 24 Jan 2011 15:00:31 +0100 [thread overview]
Message-ID: <20110124150031.0a30e263@stein> (raw)
In-Reply-To: <4D3D2054.1060905@grumpydevil.homelinux.org>
On Jan 24 Rudy Zijlstra wrote:
> On 01/24/2011 01:21 AM, James Bottomley wrote:
> > On Sun, 2011-01-23 at 11:41 +0100, Rudy Zijlstra wrote:
> >
> >> Dears,
> >>
> >> I got the following crash by:
> >> - cp several G onto a raid 5 on a Marvell 88SE6480//// based controller
> >> while also doing
> >> - cp * ../test/ on the same raid.
> >>
> >> I strongly suspect mvsas to be the cause
> >>
> > I've got to ask why?
> >
> cause the 88SE6480 has been giving grief for a long time, and i was
> loading that one specifically.
> you may well be right (i do not read crash info i fear), but a bit
> strange to have NFS crash when nfs was not much used at that moment
>
[...]
> >> [ 2821.393697] Pid: 1105, comm: rpc.mountd Not tainted 2.6.37 #1
> >> X7SB4/E/X7SB4/E
> >> [ 2821.393697] RIP: 0010:[<ffffffff815a1b5c>] [<ffffffff815a1b5c>]
> >> cache_revisit_request+0xab/0x105
> >>
> > This says the bad deref occurred in the sunrpc authentication cache.
> > Nothing at all in the trace implicates mvsas ... in fact nothing even
> > remotely relates to it at all. It really looks like an NFS problem.
Perhaps a silent memory corruption, with an innocent bystander becoming a
victim?
Rudy, if possible repeat the test with NFS completely shut down and
disabled.
--
Stefan Richter
-=====-==-== ---= ==---
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-01-24 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 10:41 Crash in 2.6.37 Rudy Zijlstra
2011-01-24 0:21 ` James Bottomley
2011-01-24 6:46 ` Rudy Zijlstra
2011-01-24 14:00 ` Stefan Richter [this message]
2011-01-24 18:14 ` Rudy Zijlstra
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=20110124150031.0a30e263@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=rudy@grumpydevil.homelinux.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