From: Andrea Arcangeli <andrea@suse.de>
To: Teodor.Iacob@astral.kappa.ro
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.18 : lots of "state D" processes ....
Date: Sat, 2 Mar 2002 02:28:53 +0100 [thread overview]
Message-ID: <20020302022853.E4431@inspiron.random> (raw)
In-Reply-To: <20020228183120.C1705@inspiron.school.suse.de> <Pine.LNX.4.31.0203010002100.5620-100000@linux.kappa.ro>
In-Reply-To: <Pine.LNX.4.31.0203010002100.5620-100000@linux.kappa.ro>
On Fri, Mar 01, 2002 at 12:03:49AM +0200, Teodor Iacob wrote:
> Ok, I rushed to reply but it seems like I still get the perl process in a
> "D state", no matter if I compile USB as module or built-in, with rmap12g
> or with your patch. Anyway to track this?
SYSRQ+T run on top of 2.4.19pre1aa1 should allow to track down whatever
USB problem it is.
Andrea
next prev parent reply other threads:[~2002-03-02 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 23:07 Chris Rankin
2002-02-28 10:38 ` Teodor Iacob
2002-02-28 17:31 ` Andrea Arcangeli
2002-02-28 21:46 ` Teodor Iacob
2002-02-28 21:50 ` Linux-2.4.18 : lots of "state D" processes (more) Teodor Iacob
2002-02-28 22:03 ` Linux-2.4.18 : lots of "state D" processes Teodor Iacob
2002-03-02 1:28 ` Andrea Arcangeli [this message]
2002-03-02 1:35 ` Rik van Riel
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=20020302022853.E4431@inspiron.random \
--to=andrea@suse.de \
--cc=Teodor.Iacob@astral.kappa.ro \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®