[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1160592235.5973.5.camel@localhost.localdomain>
Date: Wed, 11 Oct 2006 11:43:55 -0700
From: john stultz <johnstul@...ibm.com>
To: caglar@...dus.org.tr, kraxel@...e.de
Cc: Andi Kleen <ak@...e.de>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] Avoid PIT SMP lockups
On Wed, 2006-10-11 at 21:37 +0300, S.Çağlar Onur wrote:
> 11 Eki 2006 Çar 20:59 tarihinde, john stultz şunları yazmıştı:
> > > Yep, [1] here is whole screen and used config, and as andi suggested i
> > > recompiled this kernel [pure vanilla 2.6.18] from scratch.
> > >
> > > [1] http://cekirdek.pardus.org.tr/~caglar/2.6.18/
> >
> > Huh.. that's an odd trace. Looks like the alternative code is involved.
> >
> > Mind booting w/ "noreplacement" to see if that avoids it?
>
> Booting with "noreplacement" solved panics (i tried booting 10 times with both
> kernel) for both vanilla one and yours patch included one.
Hey Gerd,
Looks like the smp replacements code in 2.6.18 is breaking with vmware.
I'm guessing we're taking an interrupt while apply_replacements is
running. Any ideas?
> By the way i just realize, panic occurs between
>
> Checking if this processor honours the WP bit even in supervisor mode... Ok.
>
> and
>
> Calibrating delay using timer specific routine.. xxxxx BogoMIPS (lpj=xxxxx)
>
> lines, and system waits there about 5 sec. maybe more (no matter if it panics
> or continues to boot somehow)
S.Çağlar: Didn't follow this bit at all. Could you explain a bit more?
thanks
-john
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists