From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Gong Cheng <chengg11@yahoo.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"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: Thu, 14 Jan 2010 00:03:41 +0800 [thread overview]
Message-ID: <20100113160341.GB2902@hack> (raw)
In-Reply-To: <556048.68282.qm@web82105.mail.mud.yahoo.com>
On Tue, Jan 12, 2010 at 09:53:01AM -0800, Gong Cheng wrote:
>Hi guys,
> It has been a little while when we were hit by the problem, and from then I didn't touch that area, so forgive me if I can not answer all your questions.
> Basically after switching from 2.6.31.1 and 2.6.31.4, the problem seems to have gone away.
> It was very reproducible for us in 2.6.31.1 (if coupled with glibc 2.5.34.1 or any version around. I believe as long as it was after the private futex work in glibc).
>After the switch, we might have had another similar occurrence but it was not clear if was the same problem. Since it didn't occur again, we let it go.
> now we are in 2.6.32.1, and it is still running fine. So the problem is either completely gone with the newer kernels. Or it is just much less likely to happen.
>That is pretty much all I can provide, and hope it helps.
>
Ok, thanks for your confirm.
--
Live like a child, think like the god.
prev parent reply other threads:[~2010-01-13 16:01 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
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 [this message]
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=20100113160341.GB2902@hack \
--to=xiyou.wangcong@gmail.com \
--cc=chengg11@yahoo.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_kernel_aathan@memeplex.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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