[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: memory.c - bad pmd - x86_64



On Fri, Jun 03, 2005 at 11:36:06AM -0400, Dave Jones wrote:
 > On Fri, Jun 03, 2005 at 09:52:09AM +0200, Christoph Franke wrote:
 >  > Dave Jones - Thu, Jun 02 2005 15:01:20 -0400:
 >  > 
 >  > > On Thu, Jun 02, 2005 at 08:55:40PM +0200, Christoph Franke wrote:
 >  > >  > Dave Jones - Thu, Jun 02 2005 14:25:48 -0400:
 >  > >  > 
 >  > >  > > Is it repeatable ? Does it behave again if you boot with
 >  > >  > > exec-shield=0 ? or exec-shield-randomize=0 ?
 >  > >  > 
 >  > >  > Yes, it is repeatable, teamspeak segfaults on every start. Ntpd
 >  > >  > segfaults on both build -30 and -31 during boot, but can be restarted
 >  > >  > afterwards. Will try a boot with exec-shield=0 tomorrow morning and pass
 >  > >  > through the results.
 >  > > 
 >  > > Ok.
 >  > 
 >  > Oh, staring on teamspeak I didn't instantly see the old fellow came up
 >  > again with the -31 build (booted with "exec-shield=0").
 >  > 
 >  > This occures during compilation of programs as well as on a cronjob
 >  > renicing some processes and is always parallel to the memory.c log
 >  > entries. The older builds all showed up with this, -30 didn't but -31
 >  > does again.
 > 
 > I think that was just by chance than by design.
 > This has dragged on so long, and with no resolution in sight,
 > that I'm actually getting more and more tempted to backport the
 > current FC4 kernel (based on 2.6.12rc5) to FC3.
 > 
 >  ..
 > I'll think it over some more. The actual backporting of FC4
 > kernel to FC3 is probably just an afternoons work.

Ok, here's something for folks to chew on over the weekend
http://people.redhat.com/davej/kernels/test/  has a 2.6.12rc5 based
kernel for FC3.

I've not even had chance to test-boot this one yet, so
buyer-beware..  There's no guarantee I won't do another 2.6.11
update for FC3 before pushing this out as an update to updates-testing
(where it'll sit for a week or two). It all depends on how
this works out.

		Dave


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]