From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, Zachary Amsden <zach@vmware.com>,
Gerd Hoffmann <kraxel@suse.de>, john stultz <johnstul@us.ibm.com>
Subject: Re: [Opps] Invalid opcode
Date: Sun, 5 Nov 2006 19:17:53 +0200 [thread overview]
Message-ID: <200611051917.56971.caglar@pardus.org.tr> (raw)
In-Reply-To: <200611051740.47191.ak@suse.de>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
05 Kas 2006 Paz 18:40 tarihinde, Andi Kleen şunları yazmıştı:
> How do you know this?
Just guessing, if im not wrong panics occur after SMP alternative switching
code done its job.
> And does it still happen in 2.6.19-rc4?
Will try
> > in VmWare and Microsoft Virtual
> > PC and in order to confirm this bug is not our distro specific i
> > downloaded and tried latest OpenSuse also [1] and [2] are screens
> > captured by vmware but exact same panic occurs in Virtual PC as reported
> > to us in [3].
>
> Always the same BUG()?
Yes, same bug
> There is just some rolling Turkish text there.
Ah im sorry here is the correct links :(
[1] http://cekirdek.pardus.org.tr/~caglar/2.6.18/panic_on_opensuse.png
[2] http://cekirdek.pardus.org.tr/~caglar/2.6.18/panic_on_pardus.png
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-11-05 17:17 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 [this message]
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
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=200611051917.56971.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=ak@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox