Message-ID: <421B14A8.3000501@nodivisions.com>
Date: Tue, 22 Feb 2005 06:16:56 -0500
From: Anthony DiSante <theant@nodivisions.com>
User-Agent: Mozilla Thunderbird 0.9 (X11/20041103)
MIME-Version: 1.0
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: uninterruptible sleep lockups
References: <421A3414.2020508@nodivisions.com> <200502211945.j1LJjgbZ029643@turing-police.cc.vt.edu> <421A4375.9040108@nodivisions.com> <421B12DB.70603@aitel.hist.no>
In-Reply-To: <421B12DB.70603@aitel.hist.no>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1096
Lines: 22

Helge Hafting wrote:
> The infrastructure for that does not exist, so instead, the "killed" 
> process remains. Not all of it, but at least the memory pinned down by 
> the io request.  This overhead is typically small, and the overehad of 
> adding forced io abort to every driver might
> be larger than a handful of stuck processes.  It looks ugly, but perhaps 
> a ps flag that hides the ugly processes is enough.

I don't care about any overhead associated with stuck processes, nor do I 
care that they look ugly in the ps output.  What I care about is the fact 
that at least once a week on multiple systems with different hardware, some 
HW-related driver/process gets stuck, then immediately cascades its 
stuckness up to udevd or hald, and then I can't use any of my hardware 
anymore until I reboot.

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