memory.c - bad pmd - x86_64

[Dave Jones]

On Thu, Jun 02, 2005 at 08:15:01PM +0200, Christoph Franke wrote:
 > Dave Jones - Thu, Jun 02 2005 13:21:20 -0400:
 > 
 > > On Thu, Jun 02, 2005 at 11:38:27AM -0400, Ivan Adzhubey wrote:
 > >  
 > >  > > I have been running 2.6.11-1.31_FC3smp for over a day and loading the
 > >  > > system in a manner that has caused the bad pmd problem in the past, but
 > >  > > haven't seen the problem :-))
 > >  > 
 > >  > I can confirm, 3 boxes here now running 48 hours under heavy to regular load, 
 > >  > no more pmd errors.
 > > 
 > > Two positive reports, and no negatives so far. It is starting to
 > > look good, but I'll give it a few more days before I pronounce
 > > this bug 'dead'.
 > 
 > Three, be to exact. :-)
 > 
 > > There were a number of x86-64 changes in 2.6.11.11. Looks like
 > > Andi picked the right bits to backport.
 > 
 > Seems to be. But the -31 build made some trouble. Not only didn't it
 > prevent ntpd from segfaulting (on boot, later on I can restart the
 > service), I had a few applications that didn't like the exec shield
 > patch, e.g. the teamspeak linux server, which segfaults when started
 > with this build. But as far as I know this could easily be a problem of
 > the application, which is nice to know but doesn't help really.

Is it repeatable ? Does it behave again if you boot with
exec-shield=0 ? or exec-shield-randomize=0 ?

		Dave