All of lore.kernel.org
 help / color / mirror / Atom feed
From: David McCullough <david_mccullough@au.securecomputing.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Trevor Hamm <Trevor_Hamm@pmc-sierra.com>,
	'Atsushi Nemoto' <anemo@mba.ocn.ne.jp>,
	linux-mips@linux-mips.org
Subject: Re: Problems booting Linux 2.6.18.1 on MIPS34K core
Date: Thu, 23 Nov 2006 08:43:01 +1000	[thread overview]
Message-ID: <20061122224301.GA27309@au.securecomputing.com> (raw)
In-Reply-To: <20061122215803.GA8819@linux-mips.org>


Jivin Ralf Baechle lays it down ...
> On Wed, Nov 22, 2006 at 12:31:10PM -0800, Trevor Hamm wrote:
> 
> > The source of the problem seems to be with squashfs.  When I compare booting a kernel using squashfs to one using cramfs (which always seems to boot successfully on power-up), both are reading the troublesome page from /lib/ld-uClibc.so, and both are calling flush_dcache_page() on this page.  But in the case of cramfs, flush_dcache_page() causes an immediate cache flush of that page (mapping_mapped(mapping) in __flush_dcache_page() is returning non-zero), while squashfs just marks the page as dirty and defers the cache flush (mapping_mapped(mapping) is returning zero).  I have no idea what causes this difference in behaviour, but right now it appears to be a bug in squashfs rather than the linux-mips kernel.
> 
> There are a few other potencial and real bugs me and Atsushi have found
> in squashfs.  Guess there is a reason why it's not yet in the kernel ...
> I'm still waiting for feedback from the squashfs author.

Not sure if it helps much,  but we run squashfs (with 7zip patch) on
ARM9, ARM10, SuperH and x86 without problems.  I haven't had any issues
with it so far on the au1500 either,

Cheers,
Davidm

-- 
David McCullough,  david_mccullough@securecomputing.com,   Ph:+61 734352815
Secure Computing - SnapGear  http://www.uCdot.org http://www.cyberguard.com

  reply	other threads:[~2006-11-22 22:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 20:31 Problems booting Linux 2.6.18.1 on MIPS34K core Trevor Hamm
2006-11-22 21:58 ` Ralf Baechle
2006-11-22 22:43   ` David McCullough [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-15 23:09 Trevor Hamm
2006-11-15 19:23 Trevor Hamm
2006-11-17 10:13 ` Atsushi Nemoto
2006-11-14 21:47 Trevor Hamm
2006-11-15 14:06 ` Atsushi Nemoto
2006-11-09 17:20 Trevor Hamm
2006-11-10  3:16 ` Atsushi Nemoto
2006-11-08 19:51 Trevor Hamm
2006-11-08 19:09 Trevor Hamm
2006-11-08 19:24 ` Ralf Baechle
2006-11-09  1:57 ` Atsushi Nemoto
2006-11-01 20:06 Trevor Hamm
2006-11-02  2:19 ` Atsushi Nemoto

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=20061122224301.GA27309@au.securecomputing.com \
    --to=david_mccullough@au.securecomputing.com \
    --cc=Trevor_Hamm@pmc-sierra.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.