lkml.org 
[lkml]   [2004]   [Jun]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: processes hung in D (raid5/dm/ext3)
    From
    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
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 14:03    [W:0.029 / U:91.872 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site