From: Peter Zijlstra <peterz@infradead.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Andrew Athan <linux_kernel_aathan@memeplex.com>,
linux-kernel@vger.kernel.org, Darren Hart <dvhltc@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Futex hang/lockup problem in 2.6.30+ on AMD64
Date: Tue, 12 Jan 2010 15:55:27 +0100 [thread overview]
Message-ID: <1263308127.4244.142.camel@laptop> (raw)
In-Reply-To: <20100112145213.GB3925@hack>
On Tue, 2010-01-12 at 22:52 +0800, Américo Wang wrote:
> > $ uname -a
> > Linux UK22 2.6.30-2-amd64 #1 SMP Fri Sep 25 22:16:56 UTC 2009 x86_64
> > GNU/Linux
Does a recent kernel work?
next prev parent reply other threads:[~2010-01-12 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 9:18 Futex hang/lockup problem in 2.6.30+ on AMD64 Andrew Athan
2010-01-12 14:52 ` Américo Wang
2010-01-12 14:55 ` Peter Zijlstra [this message]
2010-01-12 15:00 ` Américo Wang
2010-01-12 16:25 ` Andrew Athan
2010-01-20 4:53 ` Andrew Athan
2010-01-20 17:54 ` Darren Hart
2010-01-28 17:46 ` Andrew Athan
2010-01-12 17:53 ` Gong Cheng
2010-01-13 16:03 ` Américo Wang
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=1263308127.4244.142.camel@laptop \
--to=peterz@infradead.org \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_kernel_aathan@memeplex.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=xiyou.wangcong@gmail.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