All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Davidson <andy@ebuyer.com>
To: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: x86-64 bad pmds in 2.6.11.6
Date: Mon, 08 Aug 2005 17:55:44 +0100	[thread overview]
Message-ID: <42F78E90.7070001@ebuyer.com> (raw)

On Wed, 6 Apr, 2005 22:49:03 -0400, Dave Jones wrote:
> On Thu, Mar 31, 2005 at 12:41:17PM +0200, Andi Kleen wrote:
>  > On Wed, Mar 30, 2005 at 04:44:55PM -0500, Dave Jones wrote:
>  > >  I arrived at the office today to find my workstation had this spew
>  > >  in its dmesg buffer..
>  > Looks like random memory corruption to me.
>  > Can you enable slab debugging etc.?
>  > >  mm/memory.c:97: bad pmd ffff81004b017438(00000038a5500a88).
>  > >  mm/memory.c:97: bad pmd ffff81004b017440(0000000000000003).
>  > >  mm/memory.c:97: bad pmd ffff81004b017448(00007ffffffff73b).
>  > >  mm/memory.c:97: bad pmd ffff81004b017450(00007ffffffff73c).
> I realised today that this happens every time X starts up for
> the first time.   I did some experiments, and found that with 2.6.12rc1
> it's gone. Either it got fixed accidentally, or its hidden now
> by one of the many changes in 4-level patches.
> I'll try and narrow this down a little more tomorrow, to see if I
> can pinpoint the exact -bk snapshot (may be tricky given they were
> broken for a while), as it'd be good to get this fixed in 2.6.11.x
> if .12 isn't going to show up any time soon.

Hi, Dave, all --

Does anyone remember if they saw any system instability at the time of 
these messages ?

I'm running 2.6.11 on an SMP Opteron box, which is exhibiting these 
notices.  The box occasionally then behaves like it would during a 
serious memory leak - the load average shoots up, the box becomes 
unresponsive, stops accepting network connections, (but memory resources 
are not entirely starved, and nor does the kernel kill any processes off.)

Then - a few minutes later, the computer returns to normal.  This seems 
to happen maybe twice a week.  Thankfully, it's not ruined my weekend 
with a phone call from support yet, but it might. ;-)

If you do remember instability at this time, which was cured with an 
upgrade, then I will schedule some down time to try this out.


-- 

Regards, Andy Davidson                                andy@ebuyer.com
Systems Administrator,                                Ebuyer (UK) Ltd

             reply	other threads:[~2005-08-08 16:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 16:55 Andy Davidson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-20 17:12 x86-64 bad pmds in 2.6.11.6 Charles McCreary
2005-09-20 17:30 ` Linus Torvalds
2005-09-20 19:44   ` Chris Wedgwood
2005-09-20 23:23     ` Dave Jones
2005-04-08 16:33 Clem Taylor
2005-03-30 21:44 Dave Jones
2005-03-31 10:41 ` Andi Kleen
2005-03-31 21:52   ` Dave Jones
2005-04-01 11:52     ` Sergey S. Kostyliov
2005-04-07  2:49   ` Dave Jones
2005-04-07  6:29     ` Andi Kleen
2005-04-14 13:54       ` Hugh Dickins
2005-04-14 17:01         ` Andi Kleen
2005-04-14 17:34           ` Hugh Dickins
2005-04-14 18:10             ` Andi Kleen

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=42F78E90.7070001@ebuyer.com \
    --to=andy@ebuyer.com \
    --cc=davej@redhat.com \
    --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.