linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Angielski <jangiels@speakeasy.net>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux hanging on Xilinx SystemACE
Date: Wed, 16 Aug 2006 20:51:57 -0400	[thread overview]
Message-ID: <1155775917.10357.37.camel@sumo-jaa> (raw)
In-Reply-To: <528646bc0608161448y26e13398v3b818ed5f1124295@mail.gmail.com>

On Wed, 2006-08-16 at 15:48 -0600, Grant Likely wrote:
> On 8/16/06, Clint Thomas <cthomas@soneticom.com> wrote:
> >
> >
> > Hey,
> >
> > Using the powerpc development tree of Linux 2.4, I am trying to boot my
> > system from CompactFlash using Xilinx SystemACE. My compact flash card has
> > two partitions, a 16MB FAT16 that holds the combination FPGA image / Linux
> > Kernel ELF file, and an Ext2 partition that holds the root file system. The
> > system starts the boot process, uncompresses the Linux kernel and begins
> > loading drivers. Part way into this process, it conducts a partition check
> > of the drive being reported to it by SystemACE, however, it hangs at that
> > point. No kernel panic, no error message, it simply hangs. Here is the
> > output at that point...
> >
> > Partition check:
> >  xsysacea:
> >
> > what I am trying to find out is if this problem has been seen/fixed in the
> > past? or did I format the CF card incorrectly?

I forgot to mention that we used to see this problem when the identify
command that is sent during intialization fails.  The driver is written
in such a way that if any of this fails, the system hangs because it
sits in a polling loop waiting for the correct response.  There are no
timeout failures... :(  In our case we saw this error because we forgot
to put a CF into the system [usually during development with NFS
rootfs].

It is fairly easy to printk() the drivers init code to find out which
step is stuck in the polling loop.

> Checking partitions is a user-space activity (fsck).  Remove it from
> your init scripts.  Besides, unless your using a microdrive, your ext2
> rootfs should be mounted read-only which greatly reduces the need for
> fsck.  (because FLASH will wear out after too many writes)

The partition check he is referring to is part of a block device driver
initialization.  It is not fsck.  If he were only so luck to be that far
in the startup sequence... :)



Jeff Angielski
The PTR Group

  reply	other threads:[~2006-08-17  0:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 21:06 Linux hanging on Xilinx SystemACE Clint Thomas
2006-08-16 21:48 ` Grant Likely
2006-08-17  0:51   ` Jeff Angielski [this message]
2006-08-17  1:40     ` Grant Likely
2006-08-16 22:01 ` Keith J Outwater
2006-08-21 20:45   ` Clint Thomas
2006-08-21 21:16     ` Keith J Outwater
2006-08-16 22:07 ` Jeff Angielski
2006-08-16 23:28   ` Grant Likely

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=1155775917.10357.37.camel@sumo-jaa \
    --to=jangiels@speakeasy.net \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).