Re: INFO: task journal:337 blocked for more than 120 seconds

[Kevin Bowling <kevinb@analograils.com>]

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/