linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Ristuccia <bristucc@sw.starentnetworks.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rmap15j: sometimes processes stuck in state D, WCHAN 'down'
Date: Thu, 10 Jul 2003 10:42:53 -0400	[thread overview]
Message-ID: <20030710144253.GJ24907@sw.starentnetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307032329190.8098-100000@chimarrao.boston.redhat.com>

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
bristucc@sw.starentnetworks.com

      reply	other threads:[~2003-07-10 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 12:48 2.4.21-rmap15j: sometimes processes stuck in state D, WCHAN 'down' Brian Ristuccia
2003-07-04  3:30 ` Rik van Riel
2003-07-10 14:42   ` Brian Ristuccia [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030710144253.GJ24907@sw.starentnetworks.com \
    --to=bristucc@sw.starentnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).