[lkml]   [2010]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Reiserfs deadlock in 2.6.36
On Fri, Nov 26, 2010 at 5:57 PM, Bastien ROUCARIES
<> wrote:
> Dear frederic,
>> Hi Bastien,
>> This really looks like a hung task detector report.
>> Several tasks are stuck in queue_log_writer(), waiting
>> to be woken up on the "journal->j_join_wait" event and
>> that never happens because the waker is also stuck.
>> The problem is your report doesn't show where the waker
>> is stuck, but the hung task detector reports it, it just
>> did before or after the chunk you've posted.
>> If you could provide me the entire report, I could fix this
>> easily.
> I have manged to reproduce it after six hour of stress. Unfornatly locked was
> disabled due to a known non bug, in the init sequence. I have used sysrq -t in
> order to get more information to you.

Without debugging enable lock up take about 30 minutes to occurs but
are really hard to reproduce with debugging on


> Do I need to try to reproduce it, with a newer kernel ? Or it is sufficient ?

 \ /
  Last update: 2010-11-26 18:29    [W:0.083 / U:0.036 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site