Re: [2.6.24-rc] pdflush stuck in D state

[Rafael J. Wysocki]

On Thursday, 22 of November 2007, tvrtko.ursulin@xxxxxxxxxx wrote:
> linux-kernel-owner@xxxxxxxxxxxxxxx wrote on 22/11/2007 16:28:22:
> 
> > linux-kernel-owner@xxxxxxxxxxxxxxx wrote on 22/11/2007 16:34:01:
> > 
> > > On Thursday, 22 of November 2007, Tvrtko A. Ursulin wrote:
> > > > 
> > > > Hi all,
> > > > 
> > > > So as the subject says - pdflush is stuck i D state which means 
> > > constant load 
> > > > average of at least one:
> > > > 
> > > > root       151  0.0  0.0      0     0 ?        D    Nov20   0:33 
> > [pdflush]
> > > 
> > > Hm, this is supposed to be fixed.  Please see:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=9323
> > 
> > Doesn't look like the same bug to me - I have only ever seen pdflush get 
> 
> > stuck in D, not random processes.
> > 
> > Also, I can confirm that -rc3 I am running contains the patch referenced 
> 
> > in your bugzilla link above.
> 
> Here is a trace for good and bad pdflush processes:
> 
> Nov 22 16:35:09 oxygene kernel:  =======================
> Nov 22 16:35:09 oxygene kernel: pdflush       S c014fe4e     0   150 2
> Nov 22 16:35:09 oxygene kernel:        00000000 00000046 00000000 c014fe4e 
> f7c30fa4 c014f9c6 f7ce8560 f7ce869c
> Nov 22 16:35:09 oxygene kernel:        c201e100 00000001 fffffffc 00000002 
> 00000000 00000000 00000000 00000000
> Nov 22 16:35:09 oxygene kernel:        00000021 f7c30fc8 c014fe4e 00000000 
> 00000000 c014ff09 00000202 f7ce8560
> Nov 22 16:35:09 oxygene kernel: Call Trace:
> Nov 22 16:35:09 oxygene kernel:  [pdflush+0/434] pdflush+0x0/0x1b2
> Nov 22 16:35:09 oxygene kernel:  [background_writeout+125/173] 
> background_writeout+0x7d/0xad
> Nov 22 16:35:09 oxygene kernel:  [pdflush+0/434] pdflush+0x0/0x1b2
> Nov 22 16:35:09 oxygene kernel:  [pdflush+187/434] pdflush+0xbb/0x1b2
> Nov 22 16:35:09 oxygene kernel:  [kthread+56/96] kthread+0x38/0x60
> Nov 22 16:35:09 oxygene kernel:  [kthread+0/96] kthread+0x0/0x60
> Nov 22 16:35:09 oxygene kernel:  [kernel_thread_helper+7/16] 
> kernel_thread_helper+0x7/0x10
> Nov 22 16:35:09 oxygene kernel:  =======================
> Nov 22 16:35:09 oxygene kernel: pdflush       D f7c3aef4     0   151 2
> Nov 22 16:35:09 oxygene kernel:        0b83b953 00000046 00000002 f7c3aef4 
> f7c3aeec 00000000 f7ce8ac0 f7ce8bfc
> Nov 22 16:35:09 oxygene kernel:        c201e100 00000001 f7c3af18 0b83b9cc 
> f7c3af18 00000003 00000000 00000001
> Nov 22 16:35:09 oxygene kernel:        00000000 f7c3af18 0b83b9cc f7c3af70 
> 00000000 c027ddb7 f781e000 c010490c
> Nov 22 16:35:09 oxygene kernel: Call Trace:
> Nov 22 16:35:09 oxygene kernel:  [schedule_timeout+112/141] 
> schedule_timeout+0x70/0x8d
> Nov 22 16:35:09 oxygene kernel:  [apic_timer_interrupt+40/48] 
> apic_timer_interrupt+0x28/0x30
> Nov 22 16:35:09 oxygene kernel:  [process_timeout+0/5] 
> process_timeout+0x0/0x5
> Nov 22 16:35:09 oxygene kernel:  [schedule_timeout+107/141] 
> schedule_timeout+0x6b/0x8d
> Nov 22 16:35:09 oxygene kernel:  [io_schedule_timeout+27/36] 
> io_schedule_timeout+0x1b/0x24
> Nov 22 16:35:09 oxygene kernel:  [congestion_wait+80/100] 
> congestion_wait+0x50/0x64
> Nov 22 16:35:09 oxygene kernel:  [autoremove_wake_function+0/53] 
> autoremove_wake_function+0x0/0x35
> Nov 22 16:35:09 oxygene kernel:  [pdflush+0/434] pdflush+0x0/0x1b2
> Nov 22 16:35:09 oxygene kernel:  [wb_kupdate+152/219] wb_kupdate+0x98/0xdb
> Nov 22 16:35:09 oxygene kernel:  [pdflush+282/434] pdflush+0x11a/0x1b2
> Nov 22 16:35:09 oxygene kernel:  [wb_kupdate+0/219] wb_kupdate+0x0/0xdb
> Nov 22 16:35:09 oxygene kernel:  [kthread+56/96] kthread+0x38/0x60
> Nov 22 16:35:09 oxygene kernel:  [kthread+0/96] kthread+0x0/0x60
> Nov 22 16:35:09 oxygene kernel:  [kernel_thread_helper+7/16] 
> kernel_thread_helper+0x7/0x10
> Nov 22 16:35:09 oxygene kernel:  =======================

Can you attach these traces to the Bugzilla entry at:
http://bugzilla.kernel.org/show_bug.cgi?id=9441 , please?

Thanks,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/