netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <cel@citi.umich.edu>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11 oops in skb_drop_fraglist
Date: Mon, 21 Mar 2005 21:40:57 -0500	[thread overview]
Message-ID: <423F85B9.3020406@citi.umich.edu> (raw)
In-Reply-To: <20050321162444.31c6c68d.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

Andrew Morton wrote:
> Chuck Lever <cel@citi.umich.edu> wrote:
> 
>>testing NFS client workloads on a dual Pentium-III system running 2.6.11 
>>with some NFS patches.  i hit this oops while doing simple-minded ftps 
>>and tars.
>>
>>the system locks up once or twice a day under this workload.  this is 
>>the first time i had the console and captured the oops output.
>>
> 
> 
> Chuck, I didn't see any followup to this.  Is it still happening in current
> kernels?

i have not been able to reproduce it with the aforementioned NFS patches 
removed.  i'm now convinced it was a bug in one of the NFS patches i had 
applied, even though none of them come near the fraglist stuff, but i 
haven't had a chance to nail it down.

i had implemented a patch to cause the RPC client to reuse the port 
number when reconnecting to the server after the server drops the 
connection... this is a standard practice for other RPC implementations. 
  i suspect it was that patch that was causing the trouble.

thanks for the follow-up!

[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 439 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Charles
org:Network Appliance, Incorporated;Linux NFS Client Development
adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA
email;internet:cel@citi.umich.edu
title:Member of Technical Staff
tel;work:+1 734 763-4415
tel;fax:+1 734 763 4434
tel;home:+1 734 668-1089
x-mozilla-html:FALSE
url:http://www.monkey.org/~cel/
version:2.1
end:vcard


      parent reply	other threads:[~2005-03-22  2:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 18:54 2.6.11 oops in skb_drop_fraglist Chuck Lever
2005-03-22  0:24 ` Andrew Morton
2005-03-22  1:19   ` Herbert Xu
2005-03-22  2:40   ` Chuck Lever [this message]

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=423F85B9.3020406@citi.umich.edu \
    --to=cel@citi.umich.edu \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).