From: "Gregory K. Ruiz-Ade" <gregory@castandcrew.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 instability on bigmem systems?
Date: Sun, 16 Mar 2003 21:38:28 -0800 [thread overview]
Message-ID: <200303162138.28608.gregory@castandcrew.com> (raw)
In-Reply-To: <200303162059.48245.gregory@castandcrew.com>
On Sunday 16 March 2003 20:59, Gregory K. Ruiz-Ade wrote:
> Right now, I'm back to running 2.4.19 with the inode.c patch from one of
> the 2.4.19-preXX-aaY kernels (see
> http://castandcrew.com/~gregory/lkmlstuff/burpr/2.4.19/patches) as the
> most stable thing we've gotten so far.
Could you possibly take a look at the kernel BUG that I got Friday night on
the 2.4.19 kernel, to see if it (oh god please) hopefully points in a
useful direction?
http://castandcrew.com/~gregory/lkmlstuff/burpr/2.4.19
The files are:
burpr-kernel-bug.20030314.2100 (the raw bug)
burpr-kernel-bug.20030314.2100.ksymoops (processed through ksymoops)
FYI, the amaivschk program listed in the BUG is a shell script, and also at
that URL if you're curious as to what it does.
Thanks again...
--
Gregory K. Ruiz-Ade <gregory@castandcrew.com>
Sr. Systems Administrator
Cast & Crew Entertainment Services, Inc.
next prev parent reply other threads:[~2003-03-17 5:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 0:27 2.4.20 instability on bigmem systems? Gregory K. Ruiz-Ade
2003-03-14 0:42 ` William Lee Irwin III
2003-03-14 1:45 ` Gregory K. Ruiz-Ade
2003-03-14 1:53 ` William Lee Irwin III
2003-03-14 3:55 ` Gregory K. Ruiz-Ade
2003-03-14 4:13 ` William Lee Irwin III
2003-03-14 17:31 ` Gregory K. Ruiz-Ade
2003-03-14 20:08 ` William Lee Irwin III
2003-03-17 2:15 ` Gregory K. Ruiz-Ade
2003-03-17 2:26 ` William Lee Irwin III
2003-03-17 4:59 ` Gregory K. Ruiz-Ade
2003-03-17 5:38 ` Gregory K. Ruiz-Ade [this message]
2003-03-14 18:31 ` Martin J. Bligh
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=200303162138.28608.gregory@castandcrew.com \
--to=gregory@castandcrew.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox