Bug#428028: linux-image-2.6.18-4-686-bigmem: possible mutex deadlock; multiple pids stuck in D state near __mutex_lock_slowpath+0x4a/0x79

[Moritz Muehlenhoff <jmm@inutil.org>]

On Fri, Jun 08, 2007 at 01:30:32AM -0600, supaplex wrote:
> Package: linux-image-2.6.18-4-686-bigmem
> Version: 2.6.18.dfsg.1-12etch2
> Severity: normal
> 
> I've seen some issues like this in the past, were processes will start
> collecting in the D state (waiting on disk or i/o etc).  I almost caught
> a crashdump (not sure how usefull that would have been).  Fortunate for
> us however, my sysrq-trigger for showTasks worked.  I'm only pasting a
> few pids here.

[..]
 
> If you need something else, reply at will (to bts, I almost never check
> this inbox.)

Does this error still occur with more recent kernel versions?

If you're running Etch, could you try to reproduce this bug
with the 2.6.24 based kernel added in 4.0r4?
http://packages.qa.debian.org/l/linux-2.6.24.html

Cheers,
        Moritz