public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gabriel A. Devenyi" <ace@staticwave.ca>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] nfsv4 in linux 2.6.13 (-ck7)
Date: Wed, 12 Oct 2005 19:27:22 -0400	[thread overview]
Message-ID: <200510121927.22296.ace@staticwave.ca> (raw)
In-Reply-To: <20051012232418.GQ7991@shell0.pdx.osdl.net>

On October 12, 2005 19:24, Chris Wright wrote:
> * Gabriel A. Devenyi (ace@staticwave.ca) wrote:
> > This oops seems to occur during heavy i/o load over nfsv4.
> > 
> >  [kernel] Unable to handle kernel paging request at 0000000000100108 RIP:
> >  [kernel] <ffffffff80185e98>{generic_drop_inode+56}
> 
> There have been a couple recent reports of this, and a fix is in the works.
> 
> See the recent thread here:
> 
> http://lkml.org/lkml/2005/9/25/44
> 
> >  [kernel] Modules linked in: nvidia
>                                ^^^^^^
> >  [kernel] Pid: 179, comm: kswapd0 Tainted: P      2.6.13-ck7
> 
> Tainted kernel, when sending bug reports please be sure bug happens
> w/out tainted kernel.

Of course, my apologies, however, this is a fs error, is it even conceivable that something such as the nvidia kernel driver could affect this?


> thanks,
> -chris
> 
> 

-- 
Gabriel A. Devenyi
ace@staticwave.ca

  reply	other threads:[~2005-10-12 23:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12 23:03 [OOPS] nfsv4 in linux 2.6.13 (-ck7) Gabriel A. Devenyi
2005-10-12 23:24 ` Chris Wright
2005-10-12 23:27   ` Gabriel A. Devenyi [this message]
2005-10-12 23:31     ` Chris Wright
2005-10-12 23:37       ` Gabriel A. Devenyi
2005-10-12 23:56         ` Chris Wright
2005-10-14 14:05           ` Gabriel A. Devenyi
2005-10-14 18:13             ` Chris Wright
2005-10-14 15:49 ` Trond Myklebust
2005-10-15 17:23   ` Gabriel A. Devenyi

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=200510121927.22296.ace@staticwave.ca \
    --to=ace@staticwave.ca \
    --cc=chrisw@osdl.org \
    --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