All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: J?rgen Mell <j.mell@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PREEMPT causes corruption of application's FPU stack
Date: Sun, 18 May 2008 11:07:33 -0400	[thread overview]
Message-ID: <20080518150733.GC8100@goodmis.org> (raw)
In-Reply-To: <200805171831.08490.j.mell@t-online.de>

On Sat, May 17, 2008 at 06:31:08PM +0200, J?rgen Mell wrote:
> 
> I tracked this down to a single kernel configuration option. If 
> CONFIG_PREEMPT is set to 'y' the application will start crashing. If 
> CONFIG_PREEMPT is replaced by CONFIG_PREEMPT_VOLUNTARY, the application 
> will run without errors.
> 
> The problem is reproducible in so far as the error always occurs when 
> CONFIG_PREEMPT is set, but the time to the first occurrence varies greatly 
> from some minutes up to more than 10 CPU hours.
> 
> I found this error first on an openSUSE kernel 2.6.22.17-0.1-rt. I verified 
> the problem on the following kernel versions:
> 
> openSUSE 2.6.22.17-0.1-default
> openSUSE 2.6.23.17-ccj64-rt
> kernel.org 2.6.26-rc1
> kernel.org 2.6.26-rc2-git5

So you see this error in both the SuSE RT kernel, *and* mainline
kernel.org?

If you see it in the kernel.org kernel, can you please do a git-bisect
to see which commit caused the problem?

Thanks,

-- Steve

> 
> My CPU is an Intel Core2Duo 6420, running two of the Einstein applications 
> in 32-bit mode. From a discussion on the Einstein message boards I know 
> that other user of the application are also affected.
> 

  reply	other threads:[~2008-05-18 15:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-17 16:31 CONFIG_PREEMPT causes corruption of application's FPU stack Jürgen Mell
2008-05-18 15:07 ` Steven Rostedt [this message]
2008-05-18 15:57   ` Jürgen Mell
  -- strict thread matches above, loose matches on Subject: below --
2008-05-24 18:52 j.mell
2008-06-01  9:01 j.mell
2008-06-01 11:40 ` Andi Kleen
2008-06-01 16:47   ` Jürgen Mell
2008-06-02 21:37     ` Suresh Siddha
2008-06-02 22:57       ` Suresh Siddha
2008-06-03  6:02         ` Jürgen Mell
2008-06-04  7:44         ` Jürgen Mell
2008-06-04 10:53           ` Ingo Molnar
2008-06-04 12:55             ` Steven Rostedt
2008-06-04 13:02               ` Ingo Molnar
2008-06-01 12:12 ` Steven Rostedt
2008-06-01 17:11 ` Simon Holm Thøgersen
2008-06-02 21:31   ` Suresh Siddha
2008-06-03 13:23     ` Simon Holm Thøgersen
2008-06-03 19:43       ` Suresh Siddha
2008-06-03 21:08         ` Simon Holm Thøgersen

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=20080518150733.GC8100@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=j.mell@t-online.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.