From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: udev hangs on boot
Date: Fri, 20 Aug 2010 07:32:46 -0700 [thread overview]
Message-ID: <4C6E920E.4030806@balister.org> (raw)
In-Reply-To: <1282294508.6198.27.camel@dpdev>
On 08/20/2010 01:55 AM, Dimitris Papastamos wrote:
> Hello,
>
> I've built the standard console-image for the SMDK6410 platform using
> the configuration provided by oe. The problem is that when I boot the
> image over the network, and then mount the rootfs over nfs, the system
> hangs before even entering runlevel 5. If I chmod -x udev udev-cache in
> the init scripts then I can get a usable system which I can ssh into.
> I've also tried to use a snapshot from Linus's git however the same
> problem appeared.
Look in /etc/network/interfaces (I think, not at a desk where I can
check) and comment out the line auto eth0. I think the bootscripts take
the interface down and up and that is bad if you are using root over nfs.
Philip
>
> I am using the latest snapshot of oe as of now and bitbake 1.8.18. The
> version of udev appears to be 151. My target distro is angstrom-2008.1.
> I've also tried to build a base-image and a bootstrap-image and I had
> the same problem.
>
> I've attached my oe kernel configuration, my oe local.conf as well as
> the boot process log.
>
> Thanks,
> Dimitrios
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-08-20 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 8:55 udev hangs on boot Dimitris Papastamos
2010-08-20 14:32 ` Philip Balister [this message]
2010-08-20 15:47 ` Dimitris Papastamos
2010-08-25 10:45 ` Dimitris Papastamos
2010-08-25 13:12 ` Mark Brown
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=4C6E920E.4030806@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.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.