From: Andi Kleen <ak@muc.de>
To: "S.??a??lar Onur" <caglar@pardus.org.tr>
Cc: john stultz <johnstul@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [Ops] 2.6.18
Date: 4 Oct 2006 16:47:36 +0200
Date: Wed, 4 Oct 2006 16:47:36 +0200 [thread overview]
Message-ID: <20061004144736.GA67993@muc.de> (raw)
In-Reply-To: <200610041638.25955.caglar@pardus.org.tr>
On Wed, Oct 04, 2006 at 04:38:25PM +0300, S.??a??lar Onur wrote:
> 02 Eki 2006 Pts 20:36 tarihinde, john stultz ??unlar?? yazm????t??:
> > On Sun, 2006-10-01 at 03:32 +0300, S.??a??lar Onur wrote:
> > > Hi;
> > >
> > > Here [1] are the two different panics with 2.6.18 on vmware, its
> > > reproducable on every 4-5 reboot [same config/kernel in "2.6.18 Nasty
> > > Lockup" thread, so i CC'd to that thread's posters also]
> > >
> > > [1] http://cekirdek.pardus.org.tr/~caglar/2.6.18/
> >
> > Hmmm.. That first oops looks interesting to me.
> >
> > When you say they're reproducible every 4-5 reboots, which one do you
> > mean?
>
> For every 10 reboots first one occurs at least 6 times, 3 times second one
> occurs and for last it boots :)
I assume it must be something specific to your configuration
or setup.
If plain 2.6.18 was that unstable we would be flooded in reports.
But that's not the case. I also definitely don't see it on any of my systems
(except that if you use PIT time source on a multi core system
things break on i386)
Perhaps you list your setup and your configuration and a boot log
for the working case? I also I would really recommend to do the make
distclean ; recompile step I mentioned earlier.
-Andi
next prev parent reply other threads:[~2006-10-04 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 0:32 [Ops] 2.6.18 S.Çağlar Onur
2006-10-01 10:34 ` Andi Kleen
2006-10-01 16:11 ` S.Çağlar Onur
2006-10-02 17:36 ` john stultz
2006-10-04 13:38 ` S.Çağlar Onur
2006-10-04 14:47 ` Andi Kleen [this message]
2006-10-04 16:08 ` S.Çağlar Onur
2006-10-04 17:56 ` 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=20061004144736.GA67993@muc.de \
--to=ak@muc.de \
--cc=caglar@pardus.org.tr \
--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.