Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Matthew Dharm" <mdharm@momenco.com>
To: "Linux-MIPS" <linux-mips@linux-mips.org>
Subject: RE: fs problem between 2.4.19-rc1 and tip?
Date: Wed, 18 Sep 2002 09:30:33 -0700	[thread overview]
Message-ID: <NEBBLJGMNKKEEMNLHGAIEEAPCJAA.mdharm@momenco.com> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAIKEPOCIAA.mdharm@momenco.com>

Okay... if nobody is going to report seeing a problem like this, can
someone confirm that using the CVS tip their SCSI disk works?

Matt

--
Matthew D. Dharm                            Senior Software Designer
Momentum Computer Inc.                      1815 Aston Ave.  Suite 107
(760) 431-8663 X-115                        Carlsbad, CA 92008-7310
Momentum Works For You                      www.momenco.com

> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org]On Behalf Of Matthew Dharm
> Sent: Monday, September 16, 2002 2:15 PM
> To: Linux-MIPS
> Subject: fs problem between 2.4.19-rc1 and tip?
>
>
> Is anyone else seeing a problem using SCSI disks (ext2 format) that
> was introduced between 2.4.19-rc1 and the tip revision?
>
> Upon booting the 2.4.20-pre6 (tip of CVS), the root
> filesystem throws
> an error about an "unaligned directory entry" and then cannot find
> init.
>
> 2.4.19-rc1 with the _same_ hardware configuration works just fine.
>
> Is it just me, or this this something general?
>
> Matt
>
> --
> Matthew D. Dharm                            Senior Software Designer
> Momentum Computer Inc.                      1815 Aston Ave.
>  Suite 107
> (760) 431-8663 X-115                        Carlsbad, CA 92008-7310
> Momentum Works For You                      www.momenco.com
>
>

  reply	other threads:[~2002-09-18 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 21:15 fs problem between 2.4.19-rc1 and tip? Matthew Dharm
2002-09-18 16:30 ` Matthew Dharm [this message]
2002-09-18 16:57 ` Brian Murphy
2002-09-18 20:52   ` Matthew Dharm

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=NEBBLJGMNKKEEMNLHGAIEEAPCJAA.mdharm@momenco.com \
    --to=mdharm@momenco.com \
    --cc=linux-mips@linux-mips.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