Re: hard lockup on 2.4.20 w/ nfs over frees/wan

From: Shaya Potter (spotter@cs.columbia.edu)
Date: Wed Feb 19 2003 - 15:36:11 EST


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/

-
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/



This archive was generated by hypermail 2b29 : Sun Feb 23 2003 - 22:00:26 EST