From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Nick Piggin <npiggin@suse.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Mike Travis <travis@sgi.com>, LKML <linux-kernel@vger.kernel.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: [BUG] kernel BUG at arch/x86/kernel/tlb_32.c:130!
Date: Wed, 21 Jan 2009 06:31:42 +0530 [thread overview]
Message-ID: <1232499702.3123.43.camel@localhost.localdomain> (raw)
In-Reply-To: <49766FF0.9040401@cn.fujitsu.com>
On Wed, 2009-01-21 at 08:44 +0800, Li Zefan wrote:
> >>> okay, a testsystem of mine just triggered this crash too.
> >>>
> >>> Li Zefan, Jaswinder, does the patch below fix it for you?
> >>>
> >> I'll test it, but I have to run for several hours to confirm it, since
> >> the bug is not easy to trigger. :)
> >
> > yes. It triggered on an old 32-bit dual-socket HyperThreading system for
> > me and that is because HyperThreading is very good at triggering narrow
> > SMP races. (which this one certainly is)
> >
> > (I'd expect Nehalem to trigger this TLB flushing race more easily too,
> > where HyperThreading made a comeback.)
> >
>
> Nothing bad happaned in the last 16+ hours. :)
>
> Tested-by: Li Zefan <lizf@cn.fujitsu.com>
>
And my HT machine is also happy with this patch :-)
--
JSR
next prev parent reply other threads:[~2009-01-21 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 6:29 Li Zefan
2009-01-20 7:54 ` Ingo Molnar
2009-01-20 8:17 ` Ingo Molnar
2009-01-20 8:20 ` Li Zefan
2009-01-20 8:29 ` Ingo Molnar
2009-01-20 13:44 ` Jaswinder Singh Rajput
2009-01-21 0:44 ` Li Zefan
2009-01-21 1:01 ` Jaswinder Singh Rajput [this message]
2009-01-20 18:17 ` Mike Travis
2009-01-20 7:56 ` Laurent Riffard
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=1232499702.3123.43.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=rusty@rustcorp.com.au \
--cc=suresh.b.siddha@intel.com \
--cc=travis@sgi.com \
--cc=venkatesh.pallipadi@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
Powered by JetHome