From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Chris Stromsoe <cbs@cts.ucla.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
Date: Tue, 27 Dec 2005 22:10:47 -0200 [thread overview]
Message-ID: <20051228001047.GA3607@dmt.cnet> (raw)
In-Reply-To: <Pine.LNX.4.64.0512270844080.14284@potato.cts.ucla.edu>
Hi Chris,
On Tue, Dec 27, 2005 at 08:58:39AM -0800, Chris Stromsoe wrote:
> I have a machine that oopsed twice in the last 3 weeks. Immediately
> before each oops was a "filemap.c:2234: bad pmd" message. The first oops
> happened with 2.4.30, the second with 2.4.32. The oops from 2.4.30 is
> below. I don't have the oops from 2.4.32.
>
> The machine is a usenet feeder and does a constant ~110mbit/s traffic. I
> have the tg3 and bonding modules loaded. There are 2 Adaptec controllers,
> one onboard, one pci (aic7899 and 3960D). There are 5 disks off the first
> channel of aic7899 (comes up as scsi2), 4 of which are in a RAID5. The
> other 3 channels are unused. I have the .config for 2.4.30 available if
> needed.
>
> Pointers for where to look if/when it happens again would be appreciated.
>
> Thanks.
>
>
> -Chris
>
> filemap.c:2234: bad pmd 00c001e3.
> filemap.c:2234: bad pmd 010001e3.
This is usually due to memory corruption. Please verify it with
memtest86.
next prev parent reply other threads:[~2005-12-28 6:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 16:58 bad pmd filemap.c, oops; 2.4.30 and 2.4.32 Chris Stromsoe
2005-12-28 0:10 ` Marcelo Tosatti [this message]
2005-12-29 2:52 ` Chris Stromsoe
2005-12-29 5:12 ` Willy Tarreau
2005-12-29 9:33 ` Chris Stromsoe
2005-12-29 10:08 ` Willy Tarreau
2005-12-29 12:01 ` Chris Stromsoe
2005-12-31 0:12 ` Chris Stromsoe
2005-12-31 1:48 ` Chris Stromsoe
2005-12-31 4:00 ` Chris Stromsoe
2005-12-31 7:25 ` Willy Tarreau
2005-12-31 11:06 ` Chris Stromsoe
2005-12-31 7:12 ` Willy Tarreau
2005-12-31 10:39 ` Chris Stromsoe
2005-12-31 10:56 ` Willy Tarreau
2005-12-31 12:08 ` Alan Cox
2005-12-31 13:01 ` Willy Tarreau
2006-01-05 3:52 ` Chris Stromsoe
2006-01-05 5:43 ` Willy Tarreau
2006-01-06 21:54 ` Chris Stromsoe
2006-01-06 22:14 ` Chris Stromsoe
2006-01-06 22:16 ` Chris Stromsoe
2006-01-07 9:19 ` Roberto Nibali
2006-01-09 18:28 ` Chris Stromsoe
2006-01-09 20:16 ` Roberto Nibali
2006-01-09 20:22 ` Chris Stromsoe
2006-01-09 22:22 ` Roberto Nibali
2006-01-10 0:59 ` Chris Stromsoe
2006-01-15 11:29 ` Chris Stromsoe
2006-01-15 12:12 ` Willy Tarreau
2006-01-15 21:18 ` Chris Stromsoe
2006-01-15 22:38 ` Chris Stromsoe
2006-01-15 22:46 ` Willy TARREAU
2006-01-15 22:54 ` Chris Stromsoe
2006-01-16 20:52 ` Roberto Nibali
2006-01-16 21:32 ` Chris Stromsoe
2006-02-08 6:32 ` Chris Stromsoe
2006-02-08 6:37 ` Willy Tarreau
2006-01-08 9:45 ` Willy Tarreau
2006-01-09 18:33 ` Chris Stromsoe
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=20051228001047.GA3607@dmt.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=cbs@cts.ucla.edu \
--cc=linux-kernel@vger.kernel.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.