[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AC646D7.5030709@goop.org>
Date: Fri, 02 Oct 2009 11:30:47 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Shirley Ma <mashirle@...ibm.com>
CC: virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>,
Kevin Bowling <kevinb@...lograils.com>,
Andrew Jones <drjones@...hat.com>
Subject: Re: INFO: task journal:337 blocked for more than 120 seconds
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists