Date: Tue, 15 Jun 2004 19:58:22 -0700
From: Andrew Morton <akpm@osdl.org>
To: foo@porto.bmb.uga.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: processes hung in D (raid5/dm/ext3)
Message-Id: <20040615195822.7e7151aa.akpm@osdl.org>
In-Reply-To: <20040616024842.GC13672@porto.bmb.uga.edu>
References: <20040615062236.GA12818@porto.bmb.uga.edu>
	<20040615030932.3ff1be80.akpm@osdl.org>
	<20040615150036.GB12818@porto.bmb.uga.edu>
	<20040615162607.5805a97e.akpm@osdl.org>
	<20040616024842.GC13672@porto.bmb.uga.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1130
Lines: 30

foo@porto.bmb.uga.edu wrote:
>
> On Tue, Jun 15, 2004 at 04:26:07PM -0700, Andrew Morton wrote:
> > OK, well I'd be suspecting that either devicemapper or raid5 lost an I/O
> > completion, causing that page to never be unlocked.
> > 
> > Please try the latest -mm kernel, which has a few devicemapper changes,
> > although they are unlikely to fix this.
> 
> OK, this was fun...
> 
> LILO 22.2 boot: linux-mm
> Loading Linux-mm.................................
> 
> This is all I see on the serial console.  The machine did boot, though;
> a few minutes later I see this (and only this) from my syslog server:
> 
> xarello kernel: bonding: bond0: link status definitely up for interface
> eth1.
> 
> Getty didn't come up on the serial console, and it's refusing ssh
> requests, although it seems to be dropping lots of packets.

Lovely.  Please send over the kernel boot command line.

-
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/