From: William Lee Irwin III <wli@holomorphy.com>
To: James W McMechan <mcmechanjw@juno.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with tmpfs on both 2.4.22 & 2.6.0-test11
Date: Sun, 30 Nov 2003 11:27:51 -0800 [thread overview]
Message-ID: <20031130192751.GM8039@holomorphy.com> (raw)
In-Reply-To: <20031130.085729.-1591395.1.mcmechanjw@juno.com>
On Sun, Nov 30, 2003 at 08:57:26AM -0800, James W McMechan wrote:
> I have a test program much shorter then the Oops
> If someone wants to work from a Oops I will send
> one, no maintainer was listed and the last Google
> reference is about 2 years back, and it does not
> seem to be about this issue.
> This Oops both 2.4.22 and 2.6.0-test11
> It results from a ARCH=um bugreport and
> I kept making the test program shorter
> This seems silly but one line to Oops?
Please post the oops (run through ksymoops as-needed).
-- wli
next prev parent reply other threads:[~2003-11-30 19:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 16:57 Oops with tmpfs on both 2.4.22 & 2.6.0-test11 James W McMechan
2003-11-30 19:27 ` William Lee Irwin III [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-30 17:34 James W McMechan
2003-11-30 20:06 ` William Lee Irwin III
2003-11-30 21:21 ` Oleg Drokin
2003-11-30 21:17 James W McMechan
2003-12-01 1:21 ` William Lee Irwin III
2003-12-01 7:58 ` Andries Brouwer
2003-12-01 8:00 ` William Lee Irwin III
2003-12-01 1:06 James W McMechan
2003-12-01 3:43 ` William Lee Irwin III
2003-12-01 2:06 James W McMechan
2003-12-01 4:51 ` William Lee Irwin III
2003-12-01 2:59 James W McMechan
2003-12-01 11:37 ` Maneesh Soni
2003-12-03 11:06 James W McMechan
2003-12-03 12:02 ` Maneesh Soni
2003-12-07 22:48 James McMechan
[not found] <20031207.140732.-1654081.3.mcmechanjw@juno.com>
2003-12-08 5:10 ` Maneesh Soni
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=20031130192751.GM8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcmechanjw@juno.com \
/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.