All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: caglar@pardus.org.tr
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, Gerd Hoffmann <kraxel@suse.de>,
	john stultz <johnstul@us.ibm.com>
Subject: Re: [Opps] Invalid opcode
Date: Sun, 12 Nov 2006 20:20:23 -0800	[thread overview]
Message-ID: <4557F287.7050807@vmware.com> (raw)
In-Reply-To: <200611120439.56199.caglar@pardus.org.tr>

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; I suspect, as does 
Andi, that it could just be dormant. You had problems still with 
2.6.18.latest, correct? If I can find the cause, I would like to get a 
fix into 2.6.18-stable if possible. I think you already sent me the 
reproducing kernel config, but I seem to have misplaced it. Could you 
resend? I should have some time to look at this early this week.

Thanks,

Zach

  parent reply	other threads:[~2006-11-13  4:20 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 [this message]
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=4557F287.7050807@vmware.com \
    --to=zach@vmware.com \
    --cc=ak@suse.de \
    --cc=caglar@pardus.org.tr \
    --cc=johnstul@us.ibm.com \
    --cc=kraxel@suse.de \
    --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.