From: ChristopherHuhn <c.huhn@gsi.de>
To: linux-smp <linux-smp@vger.kernel.org>, linux-kernel@vger.kernel.org
Cc: Walter Schoen <w.schoen@GSI.de>, support-gsi@credativ.de
Subject: Re: Kernel Bug at spinlock.h ?!
Date: Tue, 04 Mar 2003 14:58:02 +0100 [thread overview]
Message-ID: <3E64B0EA.4080109@GSI.de> (raw)
In-Reply-To: <Pine.LNX.4.50.0303031248220.29455-100000@montezuma.mastecende.com>
Zwane Mwaikambo wrote:
>On Mon, 3 Mar 2003, ChristopherHuhn wrote:
>
>
>
>>Feb 27 20:51:37 lxb039 kernel: Unable to handle kernel NULL pointer
>>dereference at virtual address 00000000
>>Feb 27 20:51:37 lxb039 kernel: printing eip:
>>Feb 27 20:51:37 lxb039 kernel: 00000000
>>Feb 27 20:51:38 lxb039 kernel: Code: Bad EIP value.
>>
>>
>>Looks like a NFS problem, huh?
>>
>>
>
>Is that absolutely the first oops?
>
It's the only one in the log file of that machine. I think it didn't die
rigth after that.
>Looks valid, could you, if possible,
>try running a newer 2.4 and we can debug from there.
>
>Cheers,
> Zwane
>
>
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.
Have a nice day,
Christopher
next prev parent reply other threads:[~2003-03-04 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 8:11 Kernel Bug at spinlock.h ?! ChristopherHuhn
2003-03-03 8:51 ` Zwane Mwaikambo
2003-03-03 10:12 ` ChristopherHuhn
2003-03-03 15:13 ` ChristopherHuhn
2003-03-03 15:30 ` Tomas Szepe
2003-03-03 15:41 ` Richard B. Johnson
2003-03-03 16:03 ` ChristopherHuhn
2003-03-03 16:42 ` Richard B. Johnson
2003-03-03 17:49 ` Zwane Mwaikambo
2003-03-04 13:58 ` ChristopherHuhn [this message]
2003-03-05 5:49 ` Zwane Mwaikambo
2003-03-06 13:16 ` ChristopherHuhn
2003-03-07 15:47 ` Zwane Mwaikambo
2003-03-10 8:52 ` ChristopherHuhn
2003-03-03 16:39 ` Alan Cox
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=3E64B0EA.4080109@GSI.de \
--to=c.huhn@gsi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@vger.kernel.org \
--cc=support-gsi@credativ.de \
--cc=w.schoen@GSI.de \
/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