From: Kevin Bowling <kevinb@analograils.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Shirley Ma <mashirle@us.ibm.com>,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: INFO: task journal:337 blocked for more than 120 seconds
Date: Sun, 04 Oct 2009 00:12:37 -0400 [thread overview]
Message-ID: <4AC820B5.2050504@analograils.com> (raw)
In-Reply-To: <4AC646D7.5030709@goop.org>
On 10/2/2009 2:30 PM, Jeremy Fitzhardinge wrote:
> On 09/30/09 14:11, Shirley Ma wrote:
>
>> Anybody found this problem before? I kept hitting this issue for 2.6.31
>> guest kernel even with a simple network test.
>>
>> INFO: task kjournal:337 blocked for more than 120 seconds.
>> "echo 0> /proc/sys/kernel/hung_task_timeout_sec" disables this message.
>>
>> kjournald D 00000041 0 337 2 0x00000000
>>
>> My test is totally being blocked.
>>
> I'm assuming from the lists you've posted to that this is under KVM?
> What disk drivers are you using (virtio or emulated)?
>
> Can you get a full stack backtrace of kjournald?
>
> Kevin Bowling submitted a RH bug against Xen with apparently the same
> symptoms (https://bugzilla.redhat.com/show_bug.cgi?id=526627). I'm
> wondering if there's a core kernel bug here, which is perhaps more
> easily triggered by the changed timing in a virtual machine.
>
> Thanks,
> J
>
I've had a stable system thus far by appending "clocksource=jiffies" to
the kernel boot line. The default clocksource is otherwise "xen".
The dmesg boot warnings in my bugzilla report still occur.
Regards,
Kevin Bowling
http://www.analograils.com/
next prev parent reply other threads:[~2009-10-04 4:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 21:11 INFO: task journal:337 blocked for more than 120 seconds Shirley Ma
2009-10-01 13:20 ` Marcelo Tosatti
2009-10-01 16:58 ` Shirley Ma
2009-10-01 21:00 ` INFO: task kjournal:337 " Shirley Ma
2009-10-01 21:00 ` Shirley Ma
2009-10-01 21:03 ` Javier Guerra
2009-10-01 21:03 ` Javier Guerra
2009-10-01 21:17 ` Shirley Ma
2009-10-01 21:17 ` Shirley Ma
2009-10-01 22:09 ` Shirley Ma
2009-10-01 22:09 ` Shirley Ma
2009-10-01 16:58 ` INFO: task journal:337 " Shirley Ma
2009-10-01 13:20 ` Marcelo Tosatti
2009-10-02 18:30 ` Jeremy Fitzhardinge
2009-10-02 18:30 ` Jeremy Fitzhardinge
2009-10-02 19:06 ` Shirley Ma
2009-10-02 19:13 ` Jeremy Fitzhardinge
2009-10-02 19:13 ` Jeremy Fitzhardinge
2009-10-02 19:06 ` Shirley Ma
2009-10-04 4:12 ` Kevin Bowling
2009-10-04 4:12 ` Kevin Bowling [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-30 21:11 Shirley Ma
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=4AC820B5.2050504@analograils.com \
--to=kevinb@analograils.com \
--cc=drjones@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=jeremy@goop.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mashirle@us.ibm.com \
--cc=virtualization@lists.linux-foundation.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.