From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: john stultz <johnstul@us.ibm.com>
Cc: Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Avoid PIT SMP lockups
Date: Wed, 11 Oct 2006 21:37:01 +0300 [thread overview]
Message-ID: <200610112137.01160.caglar@pardus.org.tr> (raw)
In-Reply-To: <1160589556.5973.1.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
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.
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)
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-11 18:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 21:38 [RFC] Avoid PIT SMP lockups john stultz
2006-10-07 15:50 ` S.Çağlar Onur
2006-10-10 9:11 ` S.Çağlar Onur
2006-10-10 18:27 ` john stultz
2006-10-11 10:49 ` S.Çağlar Onur
2006-10-11 17:59 ` john stultz
2006-10-11 18:37 ` S.Çağlar Onur [this message]
2006-10-11 18:43 ` john stultz
2006-10-11 19:09 ` S.Çağlar Onur
2006-10-11 19:26 ` john stultz
2006-10-11 19:31 ` S.Çağlar Onur
2006-10-12 7:28 ` Gerd Hoffmann
2006-10-12 7:45 ` S.Çağlar Onur
2006-10-16 22:17 ` Zachary Amsden
2006-10-16 22:21 ` S.Çağlar Onur
2006-10-17 12:05 ` S.Çağlar Onur
2006-10-17 12:16 ` Andi Kleen
2006-10-19 8:00 ` [PATCH] Fix potential interrupts during alternative patching [was Re: [RFC] Avoid PIT SMP lockups] Zachary Amsden
2006-10-19 8:49 ` Jeremy Fitzhardinge
2006-10-19 9:00 ` Zachary Amsden
2006-10-20 10:36 ` S.Çağlar Onur
2006-10-20 5:25 ` Greg KH
2006-10-16 22:40 ` [RFC] Avoid PIT SMP lockups Andi Kleen
2006-10-16 23:25 ` Zachary Amsden
2006-10-16 16:08 ` Gerd Hoffmann
2006-10-16 16:22 ` Vmware problems was " Andi Kleen
2006-10-16 22:16 ` Petr Vandrovec
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=200610112137.01160.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=ak@suse.de \
--cc=johnstul@us.ibm.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.