From: Christoph Rohland <cr@sap.com>
To: buhr@stat.wisc.edu (Kevin Buhr)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test5 bug: invalid "shmid_kernel" passed to "shm_nopage_core"
Date: 26 Nov 2000 11:41:21 +0100 [thread overview]
Message-ID: <m37l5rggmm.fsf@linux.local> (raw)
In-Reply-To: <vbaaeapf4ti.fsf@mozart.stat.wisc.edu> <m3g0kggydi.fsf@linux.local> <vbay9y7dxgr.fsf@mozart.stat.wisc.edu>
In-Reply-To: buhr@stat.wisc.edu's message of "26 Nov 2000 01:05:56 -0600"
Hi Kevin,
buhr@stat.wisc.edu (Kevin Buhr) writes:
> I know no way to reproduce it. I've been using "test5" reliably since
> just after its release, and I've triggered this bug only the one time.
That's what I feared :-(
> I use a SysReq patch to do an oops-style dump instead of the usual
> "showPc" function, so I was able to copy a stack dump down.
Could you send me the patch? Does it do the dump on all cpus?
> I'll fiddle around a bit more and see if I can find a way to reproduce
> it reliably.
I would be happy to help debug the shm code if you find a way to
reproduce it.
Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-26 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 21:17 2.4.0-test5 bug: invalid "shmid_kernel" passed to "shm_nopage_core" Kevin Buhr
2000-11-25 10:05 ` Christoph Rohland
2000-11-26 7:05 ` Kevin Buhr
2000-11-26 10:41 ` Christoph Rohland [this message]
2000-11-26 20:35 ` Kevin Buhr
2000-12-19 8:58 ` Christoph Rohland
2000-12-19 18:11 ` Kevin Buhr
2000-12-20 7:30 ` Christoph Rohland
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=m37l5rggmm.fsf@linux.local \
--to=cr@sap.com \
--cc=buhr@stat.wisc.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