public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Wang, Baojun" <wangbj@lzu.edu.cn>
To: Mike Galbraith <efault@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.23 CFS problem?
Date: Fri, 26 Oct 2007 18:04:26 +0800	[thread overview]
Message-ID: <393455391.26095@eyou.net> (raw)
Message-ID: <200710261804.29136.wangbj@lzu.edu.cn> (raw)
In-Reply-To: <393390073.22773@lzu.edu.cn>

[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]

On Friday 26 October 2007 17:05:42, you wrote:
> On Fri, 2007-10-26 at 15:32 +0800, Wang, Baojun wrote:
> > > Perhaps he has any tasks stuck in 'D' state?  If so, SysRq-t output for
> > > these would be a good thing to collect.  What leads him to suspect the
> > > process scheduler, etc.  More details are needed.
> >
> > The task is S+ state, please see in the attachment tarball, SysRq-t
> > output has also been attached, I wish it would help. I doubt it's the CFS
> > problem because it's first introduced into the 2.6.23 kernel.
>
> (yeah, but there were a truckload of other changes as well)
>
> Looking at your data, _my_ first suspect would be the 2.6.22->2.6.23
> futex changes.  I'd revert all of the changes to kernel/futex.c and
> kernel/futex_compat.c, and see if the problem went away.  If it didn't,
> I'd then do a full git bisect to nail it down.
>
> 	-Mike

Thanks very much, also my glibc (2.6.1) is built under 2.6.23 (but not 
linux-headers, which is 2.6.22). but I've tried right now (install ELDK4.1) 
on another x86_64 machine, without any problem (x86_64, Core2Duo E6600, 4G 
RAM)

Wang
-- 
Wang, Baojun                                        Lanzhou University
Distributed & Embedded System Lab              http://dslab.lzu.edu.cn
School of Information Science and Engeneering        wangbj@lzu.edu.cn
Tianshui South Road 222. Lanzhou 730000                     .P.R.China
Tel:+86-931-8912025                                Fax:+86-931-8912022

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2007-10-26 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200710261057.48179.wangbj@lzu.edu.cn>
2007-10-26  2:57 ` kernel 2.6.23 CFS problem? Wang, Baojun
2007-10-26  4:45 ` WANG Cong
2007-10-26  6:47   ` Mike Galbraith
     [not found]   ` <393381760.18886@lzu.edu.cn>
     [not found]     ` <200710261532.22265.wangbj@lzu.edu.cn>
2007-10-26  7:32       ` Wang, Baojun
2007-10-26  9:05       ` Mike Galbraith
     [not found]       ` <393390073.22773@lzu.edu.cn>
     [not found]         ` <200710261804.29136.wangbj@lzu.edu.cn>
2007-10-26 10:04           ` Wang, Baojun [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=393455391.26095@eyou.net \
    --to=wangbj@lzu.edu.cn \
    --cc=efault@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox