From: Chuck Ebbert <cebbert@redhat.com>
To: Frantisek Rysanek <Frantisek.Rysanek@post.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [newbie:] Bonnie++2 hangs recent 2.6 kernels? Bash keeps looping in waitpid(), eating 100% CPU
Date: Wed, 19 Sep 2007 18:53:36 -0400 [thread overview]
Message-ID: <46F1A870.2020109@redhat.com> (raw)
In-Reply-To: <46EABE19.27660.2EE1940D@localhost>
On 09/14/2007 11:00 AM, Frantisek Rysanek wrote:
> Dear Mr. Piggin,
>
> thanks for your response in the first place :-)
>
> On 13 Sep 2007 at 2:30, Nick Piggin wrote:
>> Can you see if it is looping in userspace or kernel? Can you kill -9
>> the process?
>>
> I can't run any command. Any command hangs or coredumps.
>
>> Are you able to test with the latest 2.6.23-rc kernel? If not (or if it
>> still has the same problem), then can you get the output of sysrq+T
>> and three sysrq+P calls, please? (this might help work out where in
>> kernel it is spinning).
>>
> I've compiled 2.6.23-rc6, enabled serial console and captured
> the output of sysrq+P (on the affected virtual VGA console)
> and sysrq+T.
>
> http://www.fccps.cz/download/adv/frr/bonnie/2.6.23-rc6.txt
>
> The interesting bit of information, related to the erratic "bash"
> processes, is always a single line, such as:
>
> bash R running 0 2358 1
>
> I've also taken a photo of `top` running
> on another virtual console. I can't get any data out of the
> affected box, as I can't run any shell commands...
>
> http://www.fccps.cz/download/adv/frr/bonnie/top.jpg
>
Looks like process 2382 is stuck with the kernel trying to send
SIGBUS to that bash process, here:
int
force_sig_info(int sig, struct siginfo *info, struct task_struct *t)
{
unsigned long int flags;
int ret, blocked, ignored;
struct k_sigaction *action;
====> spin_lock_irqsave(&t->sighand->siglock, flags);
next prev parent reply other threads:[~2007-09-19 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 14:46 [newbie:] Bonnie++2 hangs recent 2.6 kernels? Bash keeps looping in waitpid(), eating 100% CPU Frantisek Rysanek
2007-09-13 0:30 ` Nick Piggin
2007-09-14 15:00 ` Frantisek Rysanek
2007-09-19 22:53 ` Chuck Ebbert [this message]
2007-09-20 7:30 ` Frantisek Rysanek
2007-09-19 8:50 ` Frantisek Rysanek
2007-09-19 15:34 ` Randy Dunlap
2007-09-19 16:08 ` Frantisek Rysanek
2008-03-06 20:46 ` Frantisek Rysanek
-- strict thread matches above, loose matches on Subject: below --
2007-09-19 14:58 Frantisek Rysanek
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=46F1A870.2020109@redhat.com \
--to=cebbert@redhat.com \
--cc=Frantisek.Rysanek@post.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.