From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.23] tasks stuck in running state?
Date: Fri, 19 Oct 2007 18:08:20 -0700 [thread overview]
Message-ID: <2c0942db0710191808u7e417ac7ra93583fd15ffab36@mail.gmail.com> (raw)
In-Reply-To: <47192425.6020507@garzik.org>
On 10/19/07, Jeff Garzik <jeff@garzik.org> 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:
>
> > 31003 ? S 0:04 sshd: jgarzik@pts/0
> > 31004 pts/0 Ss 0:02 \_ -bash
> > 8280 pts/0 S+ 0:00 \_ make ARCH=i386 -sj4
> > 8690 pts/0 Z+ 0:00 \_ [rm] <defunct>
> > 8691 pts/0 S+ 0:00 \_ /bin/sh -c cat include/config/kernel.release 2> /dev/null
> > 8692 pts/0 R+ 6:12 \_ cat include/config/kernel.release
>
> Specifically, the symptom is a process, often a simple one like cat(1)
> or rm(1) or somewhere in check-headers, will stay in the running state,
> accumulating CPU time.
>
> If I Ctrl-C the build, and start over, the build will normally -not- get
> stuck at the same point, but proceed to chew through one of a bazillion
> allmodconfig builds.
I *think* I'm seeing this with firefox under 2.6.23-rc6. I tried a
`killall -SIGSTOP firefox; killall -SIGCONT firefox` and when I looked
back it was back to life again, but that may have been a fluke.
Regardless, try that the next time it happens?
Ray
next prev parent reply other threads:[~2007-10-20 1:08 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
2007-10-20 1:08 ` Ray Lee [this message]
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=2c0942db0710191808u7e417ac7ra93583fd15ffab36@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=jeff@garzik.org \
--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
all inboxes | Powered by JetHome®