From: David Luyer <david@luyer.net>
To: Rik van Riel <riel@redhat.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: Linux 2.4.25-rc1
Date: Tue, 2 Mar 2004 10:38:04 +1100 [thread overview]
Message-ID: <20040301233804.GC5447@pacific.net.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0403011020190.21897-100000@chimarrao.boston.redhat.com>
On Mon, Mar 01, 2004 at 10:20:46AM -0500, Rik van Riel wrote:
> On Mon, 1 Mar 2004, Marcelo Tosatti wrote:
> > > INIT: Sending processes the TERM signal
> > > memory.c:100: bad pmd 000001e3.
> > > memory.c
> >
> > This looks like hardware fault to me or a (maybe, not sure) badly
> > behaving driver. The inode-highmem modifications can't cause such
> > breakage, as far as I can see.
>
> Agreed, this looks like a hardware fault.
I swapped CPU, memory and kernel all at once which resolved the
fault, as I had a second failure after this and I had to resolve
the fault ASAP so I couldn't trouble-shoot changing things one by one.
I'll re-upgrade to 2.4.25 after the system has been stable for around
a week; the original CPU and memory have been placed in a test box and
have shown no faults running a memory tester for 24 hours but perhaps
it was just a seating issue on a component; I'll report back if there
are any problems after re-upgrading.
David.
prev parent reply other threads:[~2004-03-01 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 12:44 Marcelo Tosatti
2004-02-06 18:01 ` [patch] 2.4.25-rc1: amd7930_fn doesn't compile Adrian Bunk
2004-02-29 4:44 ` Linux 2.4.25-rc1 David Luyer
2004-03-01 15:16 ` Marcelo Tosatti
2004-03-01 15:20 ` Rik van Riel
2004-03-01 23:38 ` David Luyer [this message]
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=20040301233804.GC5447@pacific.net.au \
--to=david@luyer.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=riel@redhat.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
all inboxes | Powered by JetHome®