From: davidw@dedasys.com (David N. Welton)
To: linuxppc-dev@lists.linuxppc.org
Subject: threaded core dump oops
Date: 23 Mar 2004 14:47:00 +0100 [thread overview]
Message-ID: <87zna7fzfv.fsf@dedasys.com> (raw)
[ Please CC replies to me - thanks! ]
Hi,
Looking around, after bumping into this bug myself I found this:
http://www.ussg.iu.edu/hypermail/linux/kernel/0402.3/0566.html
and was wondering if it will be going in anytime soon. If not, is
there anything I can do to help? I can reproduce the Oops reliably...
Thankyou,
--
David N. Welton
Consulting: http://www.dedasys.com/
Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
Apache Tcl: http://tcl.apache.org/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-03-23 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 13:47 David N. Welton [this message]
2004-03-23 21:24 ` threaded core dump oops Tom Rini
2004-03-24 12:25 ` David N. Welton
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=87zna7fzfv.fsf@dedasys.com \
--to=davidw@dedasys.com \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.