From: Tom Rini <trini@kernel.crashing.org>
To: "David N. Welton" <davidw@dedasys.com>
Cc: linuxppc-dev@lists.linuxppc.org, Greg Weeks <greg.weeks@timesys.com>
Subject: Re: threaded core dump oops
Date: Tue, 23 Mar 2004 14:24:48 -0700 [thread overview]
Message-ID: <20040323212448.GD2330@smtp.west.cox.net> (raw)
In-Reply-To: <87zna7fzfv.fsf@dedasys.com>
On Tue, Mar 23, 2004 at 02:47:00PM +0100, David N. Welton wrote:
>
> [ 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...
Probably in time for 2.6.6-rc1 (I'm trying to take the term "release
candidate" seriously, at least for what I'm passing along). A simple
program which causes the oops would be quite helpful, too.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-23 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 13:47 threaded core dump oops David N. Welton
2004-03-23 21:24 ` Tom Rini [this message]
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=20040323212448.GD2330@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=davidw@dedasys.com \
--cc=greg.weeks@timesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).