From: foo@porto.bmb.uga.edu
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: processes hung in D (raid5/dm/ext3)
Date: Tue, 15 Jun 2004 23:55:20 -0400 [thread overview]
Message-ID: <20040616035520.GA13868@porto.bmb.uga.edu> (raw)
In-Reply-To: <20040615195822.7e7151aa.akpm@osdl.org>
On Tue, Jun 15, 2004 at 07:58:22PM -0700, Andrew Morton wrote:
> 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.
command line is auto BOOT_IMAGE=Linux ro root=851 console=ttyS0,19200n8
This is the same as for the mainline kernels I've been using.
-ryan
next prev parent reply other threads:[~2004-06-16 3:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 6:22 foo
2004-06-15 10:09 ` Andrew Morton
2004-06-15 15:00 ` foo
2004-06-15 23:26 ` Andrew Morton
2004-06-15 23:44 ` Evaldo Gardenali
2004-06-16 2:03 ` foo
2004-06-16 2:16 ` foo
2004-06-16 12:57 ` Alasdair G Kergon
2004-06-16 19:00 ` foo
2004-06-16 19:15 ` Alasdair G Kergon
2004-06-17 2:28 ` foo
2004-06-16 2:48 ` foo
2004-06-16 2:58 ` Andrew Morton
2004-06-16 3:55 ` foo [this message]
2004-06-16 4:13 ` foo
2004-06-16 4:25 ` Andrew Morton
2004-06-16 4:41 ` foo
2004-06-16 4:53 ` linux-kernel-owner
2004-06-16 7:22 ` tg3 wrong speed foo
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=20040616035520.GA13868@porto.bmb.uga.edu \
--to=foo@porto.bmb.uga.edu \
--cc=akpm@osdl.org \
--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®