From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 0xffffe002 in ??
Date: Fri, 24 Jun 2005 20:37:23 -0600 [thread overview]
Message-ID: <42BCC363.4020605@shaw.ca> (raw)
In-Reply-To: <4ito6-TJ-7@gated-at.bofh.it>
KV Pavuram wrote:
> I think the threads are going into that strange
> address when they are waiting over an IPC object like
> semaphore or mutex. Atleast i saw a thread come out of
> that strange address immed. after another threads
> released a semaphore!!
>
> Thanks for the inputs.
We've seen that behavior on Red Hat 9 at work as well. However, when we
moved up to the Fedora Core 1 2.4.22 kernel (due to some apparent
futex/NPTL bugs in the RH9 kernel) we noticed that the correct pthread
call was listed in the stack trace.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-06-25 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4i8jP-156-9@gated-at.bofh.it>
[not found] ` <4ito6-TJ-7@gated-at.bofh.it>
2005-06-25 2:37 ` Robert Hancock [this message]
2005-06-21 15:21 0xffffe002 in ?? KV Pavuram
2005-06-21 15:38 ` Richard B. Johnson
2005-06-21 15:50 ` KV Pavuram
2005-06-22 5:54 ` Denis Vlasenko
2005-06-23 6:12 ` KV Pavuram
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=42BCC363.4020605@shaw.ca \
--to=hancockr@shaw.ca \
--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