Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Brian Murphy <brian@murphy.dk>
To: Linux-MIPS <linux-mips@linux-mips.org>
Cc: Matthew Dharm <mdharm@momenco.com>
Subject: Re: fs problem between 2.4.19-rc1 and tip?
Date: Wed, 18 Sep 2002 18:57:12 +0200	[thread overview]
Message-ID: <3D88B068.6080303@murphy.dk> (raw)
In-Reply-To: NEBBLJGMNKKEEMNLHGAIKEPOCIAA.mdharm@momenco.com

Matthew Dharm wrote:

>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.
>  
>
This sounds like a problem I had with cache flushing in pci.h which got 
triggered
by a change in the ide dma driver. Is it a pci driver? If so you could 
try the fix
I submitted a few days ago with ide-dma in the subject line.

/Brian

  parent reply	other threads:[~2002-09-18 16:57 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
2002-09-18 16:57 ` Brian Murphy [this message]
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=3D88B068.6080303@murphy.dk \
    --to=brian@murphy.dk \
    --cc=linux-mips@linux-mips.org \
    --cc=mdharm@momenco.com \
    /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