mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Chuck Ebbert" <cebbert@redhat.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.23] tasks stuck in running state?
Date: Sun, 21 Oct 2007 19:34:42 +0200	[thread overview]
Message-ID: <b647ffbd0710211034s664eec81hb3dac639f5575fac@mail.gmail.com> (raw)
In-Reply-To: <b647ffbd0710211025k1e5935a2ra6886724872437c8@mail.gmail.com>

On 21/10/2007, Dmitry Adamushko <dmitry.adamushko@gmail.com> wrote:
> On 20/10/2007, Jeff Garzik <jeff@garzik.org> wrote:
> > Chuck Ebbert wrote:
> > > On 10/19/2007 05:39 PM, Jeff Garzik wrote:
> > >> On my main devel box, vanilla 2.6.23 on x86-64/Fedora-7, I'm seeing a
> > >> certain behavior at least once a day.  I'll start a kernel build (make
> > >> -sj5 on this box), and it will "hang" in the following way:
> > >>
> > >
> > > Can you try to strace the hanging task?
> >
> > Well, to the system it's running, so that doesn't do much of anything...
> >
> > >
> > >  8482 pts/0    S+     0:00                          \_ /bin/sh /garz/repo/misc-2.6/scripts/hdrcheck.sh /garz/repo/misc-2.6/usr/include /garz/repo/misc-2.6/usr/include/linux/kernelcapi.h /garz/repo/misc-2.6/usr/include/linux/.check.kernelcapi.h
> > >  8484 pts/0    R+     3:10                              \_ grep ^[ \t]*#[ \t]*include[ \t]*< /garz/repo/misc-2.6/usr/include/linux/kernelcapi.h
> > >  8486 pts/0    S+     0:00                              \_ cut -f2 -d<
> > >  8487 pts/0    S+     0:00                              \_ cut -f1 -d>
> > >  8488 pts/0    S+     0:00                              \_ egrep ^linux|^asm
> > > [jgarzik@pretzel misc-2.6]$ strace -p8484
> > > Process 8484 attached - interrupt to quit
> > [sits there, chewing up CPU grepping a 47-line header file]
>
> I think, the following information would be helpful :
>
> (1)  # cat /proc/PID/stat ; sleep 5; cat /proc/PID/stat
>
> as we could know :
>
> - whether utime or/and stime keeps increasing ;
>
> - one of the fields is actually 'eip' ... so we could, hopefully, more
> or less precisely localize the area of the code where it's looping.

sure, this 'eip' will be useless in this case.

[ ... ]

-- 
Best regards,
Dmitry Adamushko

  reply	other threads:[~2007-10-21 17:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 21:39 Jeff Garzik
2007-10-19 21:53 ` Chuck Ebbert
2007-10-19 22:03   ` Jeff Garzik
2007-10-19 22:18     ` Chuck Ebbert
2007-10-20  0:01       ` David Miller
2007-10-21 15:59         ` Chuck Ebbert
2007-10-21 19:52           ` David Miller
2007-10-21 17:25     ` Dmitry Adamushko
2007-10-21 17:34       ` Dmitry Adamushko [this message]
2007-10-20  1:08 ` Ray Lee
2007-10-21 20:11   ` ext3 deadlock or " Guennadi Liakhovetski

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=b647ffbd0710211034s664eec81hb3dac639f5575fac@mail.gmail.com \
    --to=dmitry.adamushko@gmail.com \
    --cc=cebbert@redhat.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®