lkml.org 
[lkml]   [2010]   [Oct]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
On Sun, Sep 26, 2010 at 10:04:13PM +0200, Rafael J. Wysocki wrote:
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17361
> Subject : Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
> Submitter : Christian Casteyde <casteyde.christian@free.fr>
> Date : 2010-08-29 19:59 (29 days old)

See my latest comment here:

https://bugzilla.kernel.org/show_bug.cgi?id=17361#c14

This subject line is highly misleading, since after -rc4, the stack
traces are in places all over the kernel, in other places other than
ext4/jbd2. So I fear no one is looking at this bug report given the
highly misleading subject line.

It looks like you have spinlock debugging, and yet there wan't any
spinlocks listed on the initial ext4 might_sleep() warning. So
something looks highly confused.

The fact that you closed other bugs as duplicates of this one that
relate to kmemcheck makes me wonder if this is really a kmemcheck bug.
(If so, the subject line here is doubly, doubly misleading.)

Do you see any symptoms if you turn off kmemcheck? Are you sure this
isn't just only a kmemcheck bug?

- Ted


\
 
 \ /
  Last update: 2010-10-03 23:51    [W:0.148 / U:15.020 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site