Messages in this thread | | | Date | Wed, 5 Mar 2003 00:49:55 -0500 (EST) | From | Zwane Mwaikambo <> | Subject | Re: Kernel Bug at spinlock.h ?! |
| |
On Tue, 4 Mar 2003, ChristopherHuhn wrote:
> Newer means 2.4.21pre, since we are running 2.4.20? > I assume that we will not upgrade the kernel before a new stable > release, since it is - should be - a production environment. > > We have some indications, that our whole problem might be related to > kernel NFS and mixing between 2.2.21 and 2.4.20 in both directions. > > I'll compile some more oopses and give you a report tomorrow.
Ok don't worry about upgrading kernels for now, (Disclaimer: I'm no NFS expert). it looks like there might have been a race here.
Code: Bad EIP value [rpc_call_sync+121/164] [rpc_run_timer+0/240]
It looks like a possible race with rpc_execute and possibly the timer, although i can't be certain where the other cpus are. Do the other oopses look somewhat similar? Could you supply them?
Zwane -- function.linuxpower.ca - 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/
| |