From: Scott Wood <scottwood@freescale.com>
To: <smitha.vanga@wipro.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Kernel boot up
Date: Thu, 25 Aug 2011 14:31:27 -0500 [thread overview]
Message-ID: <4E56A30F.4010509@freescale.com> (raw)
In-Reply-To: <07ACDFB8ECA8EF47863A613BC01BBB22035E3A70@HYD-MKD-MBX02.wipro.com>
On 08/25/2011 02:57 AM, smitha.vanga@wipro.com wrote:
> Hi Scott,
>
> I am currently trying to bring up 2.6.39 kernel on a target based on MPC8247
> Processor, using the attched .dts file . I get the below logs while the
> kernel is booting.
> I see that the unflattening of the device tree and the initial loading
> of the kernel and ramdisk file system is happening correctly. Can you
> point me where exactly I can look for this issue. I am attaching the
> .config and .dts file I am using.
Which error are you referring to?
> of-flash ff800000.flash: do_map_probe() failed
What kind of flash chip do you have? Does the node in the device tree
accurately describe it (four interleaved 8-bit chips that only do JEDEC
and not CFI)?
> PPP generic driver version 2.4.2
> PPP Deflate Compression module registered
> tun: Universal TUN/TAP device driver, 1.6
> tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
> eth0: fs_enet: 00:00:00:00:00:00
> eth1: fs_enet: 00:00:00:00:00:00
These MAC addresses should have been set in the device tree. If you're
using U-Boot, it should be doing the fixup.
> Populating /dev using udev: /sbin/udevd: '/lib/libc.so.6' library
> contains unsup
> ported TLS
> /sbin/udevd: '/lib/libc.so.6' library contains unsupported TLS
> /sbin/udevd: can't load library 'libc.so.6'
> FAIL
> /sbin/udevstart: '/lib/libc.so.6' library contains unsupported TLS
> /sbin/udevstart: '/lib/libc.so.6' library contains unsupported TLS
> /sbin/udevstart: can't load library 'libc.so.6'
> FAIL
This is a problem with the root filesystem, not the kernel.
-Scott
next prev parent reply other threads:[~2011-08-25 19:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 5:31 FW: Ethernet driver WR linux smitha.vanga
2011-08-05 18:12 ` Scott Wood
2011-08-08 5:53 ` smitha.vanga
2011-08-08 20:54 ` Scott Wood
2011-08-09 5:46 ` smitha.vanga
2011-08-09 17:56 ` Scott Wood
2011-08-25 7:57 ` Kernel boot up smitha.vanga
2011-08-25 11:11 ` Gary Thomas
2011-08-25 19:31 ` Scott Wood [this message]
2011-08-26 6:00 ` smitha.vanga
2011-08-26 20:08 ` Scott Wood
2011-09-22 15:25 ` I2c driver crash smitha.vanga
2011-09-23 1:28 ` Benjamin Herrenschmidt
2011-09-23 6:05 ` MohanReddy koppula
2011-10-03 12:31 ` Request_irq fails for IRQ2 smitha.vanga
2011-12-30 12:51 ` Mac address in the DTS file smitha.vanga
2011-12-30 14:00 ` Lorenz Kolb
2011-12-30 18:28 ` Wolfgang Denk
2012-01-09 13:54 ` Mac address in the DT smitha.vanga
2012-01-09 14:20 ` Joakim Tjernlund
2012-01-09 14:28 ` smitha.vanga
2012-01-09 14:59 ` Joakim Tjernlund
2012-01-09 22:40 ` Wolfgang Denk
2012-01-10 9:37 ` smitha.vanga
2012-01-10 9:47 ` Joakim Tjernlund
2012-01-10 21:55 ` Wolfgang Denk
2012-01-11 6:03 ` smitha.vanga
2012-02-06 14:25 ` Erase flash boot from default env smitha.vanga
2012-01-02 17:53 ` Mac address in the DTS file Scott Wood
2012-01-24 7:35 ` NTP server sync issue smitha.vanga
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=4E56A30F.4010509@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=smitha.vanga@wipro.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;
as well as URLs for NNTP newsgroup(s).