From: Shaya Potter <spotter@cs.columbia.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: hard lockup on 2.4.20 w/ nfs over frees/wan
Date: 19 Feb 2003 15:36:11 -0500 [thread overview]
Message-ID: <1045686971.8084.2.camel@zaphod> (raw)
In-Reply-To: <1045634189.4761.44.camel@zaphod>
didn't get any responses on this, but its crashes again a few times
again today, the status code it printed out was ffff.
On Wed, 2003-02-19 at 00:56, Shaya Potter wrote:
> I'm trying to use frees/wan 1.99 w/ NFSv3. I've been testing it w/
> large r and wsize's (32k each). When used w/o ipsec, it seems to work
> fine. When used w/ ipsec, make dep on a kernel source tree has
> consistently frozen up these IBM Netfinity boxes (2*933mhz P3s w/ smp
> kernel). One time the last thing the kernel printk'd was
>
> pcnet32.c: printk(KERN_ERR "%s: Bus master arbitration failure,
> status %4.4x.\n",
>
> but didn't record the status number (well it was eth0: Bus master....,
> and it's using a pcnet32 controller, so assume that's the line).
> Usually it's locked up w/o printk'ing anything, last things I see on
> console are the normal ipsec printk's
>
> Is it possible that the r/w size's are causing issues when used in
> conjuction w/ ipsec? Am I triggering some sort of race condition? The
> NFS client is running the exact same kernel on the same exact hardware
> and hasn't had an issue yet.
>
> any ideas on what I can do to debug it?
>
> thanks,
>
> shaya
>
> -
> 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/
next prev parent reply other threads:[~2003-02-19 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 5:56 hard lockup on 2.4.20 w/ nfs over frees/wan Shaya Potter
2003-02-19 20:36 ` Shaya Potter [this message]
2003-02-20 16:16 ` Shaya Potter
2003-02-20 16:44 ` Jeff Garzik
2003-02-21 9:05 ` Shaya Potter
2003-02-24 22:10 ` Shaya Potter
2003-02-24 22:51 ` Jeff Garzik
2003-02-21 15:17 ` Bill Davidsen
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=1045686971.8084.2.camel@zaphod \
--to=spotter@cs.columbia.edu \
--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