All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Zachary Amsden <zach@vmware.com>
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, Gerd Hoffmann <kraxel@suse.de>,
	Andrew Morton <akpm@osdl.org>, Daniel Hecht <dhecht@vmware.com>,
	Sahil Rihan <srihan@vmware.com>,
	Trampus Richmond <trampus@vmware.com>,
	betts@vmware.com
Subject: Re: Fix for OpenSUSE kernel bug (was Re: [Opps] Invalid opcode)
Date: Thu, 30 Nov 2006 16:21:43 +0200	[thread overview]
Message-ID: <200611301621.51240.caglar@pardus.org.tr> (raw)
In-Reply-To: <456E7DE2.5070808@vmware.com>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Hi;

30 Kas 2006 Per 08:44 tarihinde, Zachary Amsden şunları yazmıştı: 
> I'm proposing this as a fix for your bug. Having tasklets scheduled
> before softirqd gets to run might be somewhat backwards, but there is
> nothing I can find wrong about it from a correctness point of view.
> Better to boot the kernel even when compiled with bug checking on, I think.
>
> This bug started becoming apparent in 2.6.18 because of some rework with
> the CPU hotplug code, but in theory, it exists at least all the way back
> to 2.6.10, which is as far as I looked backwards in time.

I cannot reproduce that opps with 2.6.18.4 + your patch any longer, so at 
least works for me :), thanks

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 --]

  reply	other threads:[~2006-11-30 12:29 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 [this message]
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=200611301621.51240.caglar@pardus.org.tr \
    --to=caglar@pardus.org.tr \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=betts@vmware.com \
    --cc=dhecht@vmware.com \
    --cc=kraxel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srihan@vmware.com \
    --cc=trampus@vmware.com \
    --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.