From: Andi Kleen <ak@suse.de>
To: Zachary Amsden <zach@vmware.com>
Cc: caglar@pardus.org.tr, linux-kernel@vger.kernel.org,
Gerd Hoffmann <kraxel@suse.de>, john stultz <johnstul@us.ibm.com>
Subject: Re: [Opps] Invalid opcode
Date: Mon, 13 Nov 2006 06:31:45 +0100 [thread overview]
Message-ID: <200611130631.45682.ak@suse.de> (raw)
In-Reply-To: <4557F287.7050807@vmware.com>
On Monday 13 November 2006 05:20, Zachary Amsden wrote:
> S.Çağlar Onur wrote:
> > 05 Kas 2006 Paz 18:40 tarihinde, Andi Kleen şunları yazmıştı:
> >
> >> And does it still happen in 2.6.19-rc4?
> >>
> >
> > Sorry for delayed test result, i cannot reproduce this panic with 2.6.19-rc5
> >
>
> I would like to find the exact cause of the problem;
It's all related to i386's abuse of the cpu hotplug state machine.
Eventually that needs to be fixed properly like it was on x86-64
(I didn't dare touch i386 back then because this code is so fragile on old
hardware)
-Andi
next prev parent reply other threads:[~2006-11-13 5:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 13:07 [Opps] Invalid opcode S.Çağlar Onur
2006-11-05 16:40 ` Andi Kleen
2006-11-05 17:17 ` S.Çağlar Onur
2006-11-05 17:25 ` Jan Engelhardt
2006-11-05 17:38 ` S.Çağlar Onur
2006-11-05 18:57 ` Andi Kleen
2006-11-05 19:51 ` S.Çağlar Onur
2006-11-05 23:13 ` Zachary Amsden
2006-11-05 23:33 ` Andi Kleen
2006-11-30 6:44 ` Fix for OpenSUSE kernel bug (was Re: [Opps] Invalid opcode) Zachary Amsden
2006-11-30 14:21 ` S.Çağlar Onur
2006-11-12 2:39 ` [Opps] Invalid opcode S.Çağlar Onur
2006-11-12 3:32 ` Andi Kleen
2006-11-13 4:20 ` Zachary Amsden
2006-11-13 5:31 ` Andi Kleen [this message]
2006-11-15 16:08 ` S.Çağlar Onur
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=200611130631.45682.ak@suse.de \
--to=ak@suse.de \
--cc=caglar@pardus.org.tr \
--cc=johnstul@us.ibm.com \
--cc=kraxel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.com \
/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.