public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <mike@compulab.co.il>
To: Graeme Russ <graeme.russ@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Request For Help - Embedded x86, Kernel 2.6.33 boots, Mounts JFFS2 rootfs, Stops at init
Date: Wed, 28 Apr 2010 18:32:00 +0300	[thread overview]
Message-ID: <4BD854F0.9040107@compulab.co.il> (raw)
In-Reply-To: <4BD8415C.9060409@gmail.com>

Graeme Russ wrote:
> Hi All,
> 
> I've been working for a while now getting the x86 U-Boot port up to speed
> to boot a linux kernel
> 
> I now have a root fs (build from Linux-From-Scratch and trimmed to <15M
> using qemu) but all attempts to get any serial console output past
> launching of init have failed.
> 
> I have taken the root fs which successfully boots using qemu and created a
> jffs2 image and flashed it onto one of the on-board flash chips. U-Boot can
> successfully 'ls' the root fs
> 
> My bootags are:
> 
>   root=/dev/mtdblock1 rw rootfstype=jffs2 console=ttyS0,115200
> 
> as Linux can mount the root partition:
> [    1.447819] Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled

[ snip ]

> [    1.911896] Write protecting the kernel read-only data: 596k
> [    1.915842] kernel_execve(/sbin/init)
> 
> (I've added a printk in kernel_execve() which gives me the last line)
> 
> I  initially had hot-plug support compiled into the kernel and was getting
> a lot of kernel_execve(/sbin/hotplug) messages as well (plus a udev:
> starting version 151 message which appear 100+ seconds and the above
> messages), but I have since removed that and used mknod to create
> /dev/ttyS0 directly
> 
> I have also tried the following test script:
> 
> #!/bin/bash
> stty -F /dev/ttyS0 115200
> cat hello > /dev/ttyS0
> 
> but still no luck
> 
> Does anyone have any advise on how I can debug this problem?

Have you tried with init=/bin/sh?
Also, make sure you have /dev/null and /dev/console nodes.

> 
> Regards,
> 
> Graeme
> --
> 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/


-- 
Sincerely yours,
Mike.

  reply	other threads:[~2010-04-28 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 14:08 Request For Help - Embedded x86, Kernel 2.6.33 boots, Mounts JFFS2 rootfs, Stops at init Graeme Russ
2010-04-28 15:32 ` Mike Rapoport [this message]
2010-04-28 15:37 ` Alexander Clouter
2010-04-28 23:14   ` Graeme Russ
2010-04-29  8:01     ` Request For Help - Embedded x86, Kernel 2.6.33 boots, Mounts ?JFFS2 " Alexander Clouter
2010-04-29 13:15     ` Request For Help - Embedded x86, Kernel 2.6.33 boots, Mounts JFFS2 " Graeme Russ

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=4BD854F0.9040107@compulab.co.il \
    --to=mike@compulab.co.il \
    --cc=graeme.russ@gmail.com \
    --cc=linux-kernel@vger.kernel.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