Re: 2.4.21-rmap15j: sometimes processes stuck in state D, WCHAN 'down'

[Brian Ristuccia]

On Thu, Jul 03, 2003 at 11:30:09PM -0400, Rik van Riel wrote:
> On Thu, 3 Jul 2003, Brian Ristuccia wrote:
> 
> > Is anyone else seeing this problem with stock 2.4.21 or 2.4.21-rmap15j?
> 
> I haven't heard of anything like this.  Could you please get
> a backtrace of all the stuck processes with alt+sysrq+t and
> decode the backtraces with ksymoops ?
> 

This is actually the backtrace from ctrl-scrollock or whatever - the
machine where it happened didn't have magic sysrq. If the difference is
important, I can put a magic sysrq kernel everywhere and try to reproduce it
again. 

Jul 10 10:18:19 grunt1 kernel: ld            D D6E5C848     0 25131      1
25142 25147 (NOTLB)
Jul 10 10:18:19 grunt1 kernel: Call Trace:    [dput+25/340] [__down+108/200]
[__down_failed+8/12] [.text.lock.namei+53/1246] [link_path_walk+1786/2460]
Jul 10 10:18:19 grunt1 kernel: ld            D D6E5C848     0 25142      1
25131 (NOTLB)
Jul 10 10:18:19 grunt1 kernel: Call Trace:    [dput+25/340] [__down+108/200]
[__down_failed+8/12] [.text.lock.namei+53/1246] [link_path_walk+1786/2460]
Jul 10 10:18:19 grunt1 kernel: ld            D D6E5C848     0 25143      1
25144  7575 (NOTLB)
Jul 10 10:18:19 grunt1 kernel: Call Trace:    [dput+25/340] [__down+108/200]
[__down_failed+8/12] [.text.lock.namei+53/1246] [link_path_walk+1786/2460]
Jul 10 10:18:19 grunt1 kernel: ld            D D6E5C848     0 25144      1
25147 25143 (NOTLB)
Jul 10 10:18:19 grunt1 kernel: Call Trace:    [dput+25/340] [__down+108/200]
[__down_failed+8/12] [.text.lock.namei+53/1246] [link_path_walk+1786/2460]
Jul 10 10:18:19 grunt1 kernel: ld            D D7A6A000   408 25147      1
25131 25144 (NOTLB)

-- 
Brian Ristuccia
[e-mail]