From: Thomas Gleixner <tglx@linutronix.de>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>, Frederik Deweerdt <deweerdt@free.fr>,
linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Oops with strace_test
Date: Wed, 7 May 2008 15:36:12 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0805071534580.3318@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080507103615.GC2340@alice>
On Wed, 7 May 2008, Eric Sesterhenn wrote:
> * Ingo Molnar (mingo@elte.hu) wrote:
> >
> > * Frederik Deweerdt <deweerdt@free.fr> wrote:
> >
> > > Hi Eric,
> > >
> > > This appears to be caused by init_fpu() missing from the
> > > restore_sigcontext->restore_i387->restore_fpu_checking code path.
> > >
> > > I believe that moving the init_fpu() call from math_state_restore to
> > > restore_fpu_checking should fix the problem?
>
> sadly the patch does not work for me :( I still get the oopses. I am
> running this on a 32 Bit CPU, so arch/x86/kernel/traps_64.c doesnt get
> compiled. I tried removing the same part from traps_32.c but then
> the kernel oopses before netconsole is active.
I run that &$#@! intuitive test for an hour know with no effect. Can
you please provide your .config file ?
Thanks,
tglx
next prev parent reply other threads:[~2008-05-07 13:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 12:12 Eric Sesterhenn
2008-04-30 16:19 ` Andi Kleen
2008-05-05 10:00 ` Eric Sesterhenn
2008-05-05 18:00 ` Frederik Deweerdt
2008-05-06 12:10 ` Ingo Molnar
2008-05-06 15:07 ` Eric Sesterhenn
2008-05-07 10:36 ` Eric Sesterhenn
2008-05-07 13:36 ` Thomas Gleixner [this message]
2008-05-07 17:20 ` Eric Sesterhenn
2008-05-07 17:26 ` Thomas Gleixner
2008-05-07 19:09 ` Suresh Siddha
2008-05-07 21:46 ` Eric Sesterhenn
2008-05-08 15:02 ` Thomas Gleixner
2008-05-08 18:29 ` Eric Sesterhenn
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=alpine.LFD.1.10.0805071534580.3318@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=deweerdt@free.fr \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=snakebyte@gmx.de \
--cc=suresh.b.siddha@intel.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
all inboxes | Powered by JetHome®