Re: [2.6.24-rc6] pdflush still stuck in D state regression
On Saturday, 22 of December 2007, Tvrtko A. Ursulin wrote: > > Hi, Hi, > As it was in this bug report: http://bugzilla.kernel.org/show_bug.cgi?id=9441 I have reopened http://bugzilla.kernel.org/show_bug.cgi?id=9291 . Please update add the new information in there. > I am still not sure it is a duplicate because it has nothing to do with > reiserfs on > my systems. Here is the latest trace: > > pdflush S 0 139 2 > 0046 eba01fc4 b0155a80 b0155b2c > eb82 >eaab6fc0 b02aa388 b034d9b0 b034d9b0 fffb6e4a fffc > b012f0d2 >b012f090 b0104b6f eb817f44 > > Call Trace: > [] pdflush+0x0/0x210 > [] pdflush+0xac/0x210 > [] schedule+0x168/0x2e0 > [] kthread+0x42/0x70 > [] kthread+0x0/0x70 > [] kernel_thread_helper+0x7/0x18 > === > pdflush D 00140f4c 0 140 2 >b02af660 0046 eba03f10 00140f4c 444d 000f22fd b02aa9a9 > eb5e092c >eba03f74 b03cbfe8 b03cbfe8 00140f4c b0124700 eaab7500 b03cbd80 > b02aa9a4 >6c666470 00687375 008c 0064 b034da20 > b02aa20b > Call Trace: > [] schedule_timeout+0x49/0xc0 > [] process_timeout+0x0/0x10 > [] schedule_timeout+0x44/0xc0 > [] __sched_text_start+0xb/0x20 > [] congestion_wait+0x73/0x90 > [] autoremove_wake_function+0x0/0x50 > [] wb_kupdate+0x95/0xe0 > [] pdflush+0x0/0x210 > [] pdflush+0x10a/0x210 > [] wb_kupdate+0x0/0xe0 > [] kthread+0x42/0x70 > [] kthread+0x0/0x70 > [] kernel_thread_helper+0x7/0x18 > === Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6.24-rc6] pdflush still stuck in D state regression
On Saturday, 22 of December 2007, Tvrtko A. Ursulin wrote: Hi, Hi, As it was in this bug report: http://bugzilla.kernel.org/show_bug.cgi?id=9441 I have reopened http://bugzilla.kernel.org/show_bug.cgi?id=9291 . Please update add the new information in there. I am still not sure it is a duplicate because it has nothing to do with reiserfs on my systems. Here is the latest trace: pdflush S 0 139 2 0046 eba01fc4 b0155a80 b0155b2c eb82 eaab6fc0 b02aa388 b034d9b0 b034d9b0 fffb6e4a fffc b012f0d2 b012f090 b0104b6f eb817f44 Call Trace: [b0155a80] pdflush+0x0/0x210 [b0155b2c] pdflush+0xac/0x210 [b02aa388] schedule+0x168/0x2e0 [b012f0d2] kthread+0x42/0x70 [b012f090] kthread+0x0/0x70 [b0104b6f] kernel_thread_helper+0x7/0x18 === pdflush D 00140f4c 0 140 2 b02af660 0046 eba03f10 00140f4c 444d 000f22fd b02aa9a9 eb5e092c eba03f74 b03cbfe8 b03cbfe8 00140f4c b0124700 eaab7500 b03cbd80 b02aa9a4 6c666470 00687375 008c 0064 b034da20 b02aa20b Call Trace: [b02aa9a9] schedule_timeout+0x49/0xc0 [b0124700] process_timeout+0x0/0x10 [b02aa9a4] schedule_timeout+0x44/0xc0 [b02aa20b] __sched_text_start+0xb/0x20 [b015a273] congestion_wait+0x73/0x90 [b012f3f0] autoremove_wake_function+0x0/0x50 [b0155625] wb_kupdate+0x95/0xe0 [b0155a80] pdflush+0x0/0x210 [b0155b8a] pdflush+0x10a/0x210 [b0155590] wb_kupdate+0x0/0xe0 [b012f0d2] kthread+0x42/0x70 [b012f090] kthread+0x0/0x70 [b0104b6f] kernel_thread_helper+0x7/0x18 === Thanks, Rafael -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
