On Tue, Oct 5, 2010 at 6:55 PM, Tejun Heo <tj@xxxxxxxxxx> wrote:
> On 10/05/2010 06:51 PM, Tejun Heo wrote:
>> On 10/05/2010 12:09 PM, Torsten Kaiser wrote:
>>> 2) the hang with 2.6.35-rc5 I have seen twice (triggered probably by
>>> high load while building KOffice on an tmpfs)
>>
>> The trace doesn't seem to firmly point at xfs locking up. There are
>> md and dm crypt involved. Are you sure this is locking up inside xfs?
>> Also, can you please enable frame pointers so that we can get more
>> reliable backtrace?
>>
>>> 3) the lockdep issue that started this thread and that I am seeing in
>>> mainline 2.6.36-rc5 and -rc6 and that seems to be rather easy to
>>> trigger for me.
>>>
>>> Because 3) is regarded as a false positive, it should not be the cause
>>> of 2)
>>
>> For now, let's not draw any conclusion or mix the issues. I'll look
>> up the original thread and look into what the lockdep warning means.
>
> Ah, okay, David already looked into it and concluded it to be a
> spurious one. Can you please attach full kernel message of the
> lockup?
Here is the complete log from bootup until the hang happened the second time.
I just logged into KDE and then started the upgrade of KOffice, which
meant that the package manager started to compile 4 programs each with
-j5. After a few minutes the load got to ~18 and probably at the point
where filecache and GCCs filled up my 4GB RAM the system got stuck.
The mouse so longer moved and SysRq+S did not work. The log was
captured via serial console on a second system.
I will try tomorrow with frame pointers enabled...
Torsten
xfs-lockup.txt
Description: Text document
|