[yocto] beagleboard not booting yacto1.2.1

Tue Jul 24 02:59:39 PDT 2012

Hi,

For 1.2.1 and 1.3 M2, we only tested on beagleboard C4 since our xM 
didn't arrive at that time. The test results are good and no such errors 
on C4. Our beagleboard xM (revision C1) had arrived a few days ago, so I 
tested it today with 1.3 M2 RC1 (git info: 
eb0cb7e8234f5d2e5623406e9660be91cf52f65e) and also found the similar issues.

My u-boot commands (These commands work good on C4):
# setenv bootcmd 'mmc rescan 0; fatload mmc 0:1 0x80300000 uImage; bootm 
0x80300000'
# setenv bootargs 'console=tty0 console=ttyO2,115200n8 
root=/dev/mmcblk0p2 rootwait rootfstype=ext3 ro'
# boot

The system can bootup and login. But the rootfs was mounted as a 
read-only file system. Therefore many services can not startup include X.
###########
root at beagleboard:~# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 
(ro,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)
devtmpfs on /dev type devtmpfs 
(rw,relatime,size=248232k,nr_inodes=62058,mode=755)
proc on /proc type proc (rw,relatime)
tmpfs on /mnt/.psplash type tmpfs (rw,relatime,size=40k)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /var/volatile type tmpfs (rw,relatime)
tmpfs on /media/ram type tmpfs (rw,relatime)
root at beagleboard:~#
root at beagleboard:~# touch a
touch: cannot touch `a': Read-only file system
root at beagleboard:~#
root at beagleboard:~# uname -a
Linux beagleboard 3.0.32-yocto-standard #1 Wed Jul 11 14:11:07 PDT 2012 
armv7l GNU/Linux
###########

When I modified the u-boot command line: "setenv bootargs 'console=tty0 
console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait rootfstype=ext3 ro'" 
to "setenv bootargs 'console=tty0 console=ttyO2,115200n8 
root=/dev/mmcblk0p2 rootwait rootfstype=ext3 rw'" and booted again, then 
the kernel crashed:
##########
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
Please append a correct "root=" boot option; here are the available 
partitions:
b300 3813376 mmcblk0 driver: mmcblk
b301 72261 mmcblk0p1 00000000-0000-0000-0000-000000000000
b302 3735112 mmcblk0p2 00000000-0000-0000-0000-000000000000
VFS: Unable to mount root fs on unknown-block(179,2)
User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents 
continuing
[<c0063d00>] (unwind_backtrace+0x0/0xec) from [<c044baa0>] 
(dump_stack+0x20/0x24)
[<c044baa0>] (dump_stack+0x20/0x24) from [<c044bcb0>] (panic+0x64/0x184)
[<c044bcb0>] (panic+0x64/0x184) from [<c0008eb4>] 
(mount_block_root+0x1e4/0x230)
[<c0008eb4>] (mount_block_root+0x1e4/0x230) from [<c00090e0>] 
(mount_root+0xf8/0x11c)
##########

I attached the 2 detail boot logs.

On 2012年07月22日 11:46, Bruce Ashfield wrote:
> On Sat, Jul 21, 2012 at 11:32 PM, Saul Wold <saul.wold at intel.com> wrote:
>> On 07/21/2012 07:40 PM, Bruce Ashfield wrote:
>>> On 12-07-21 11:58 AM, Edward Vidal wrote:
>>>> hello,
>>>>
>>>> verifing that this is ver poky-1.2.1
>>>> The post by Elizabeth Flanagan Wed Jul 18 14:20:41 PDT 2012
>>>> Yocto 1.2.1 Released
>>>> Flanagan, Elizabeth elizabeth.flanagan at intel.com <http://intel.com>
>>>> Commit Information:
>>>> Tree/Branch: denzil
>>>> Commit id: 73cdebf60df225ee10f2eb215935be3b61e1b831
>>>> git clone -b denzil git://git.yoctoproject.org/poky.git
>>>> <http://git.yoctoproject.org/poky.git>
>>>> cd poky
>>>> git log
>>>> commit 73cdebf60df225ee10f2eb215935be3b61e1b831
>>>> I tried the default kernel 3.0 this would get a kernel panic could not
>>>> mount the mmc
>>>>
>>>> Modified the file meta-yocto/conf/machine/beagleboard.conf
>>>>
>>>> PREFERRED_VERSION_linux-yocto ?= "3.0%" -->
>>>> PREFERRED_VERSION_linux-yocto ?= "3.4%"
>>>> In this version there is no
>>>> /home/vidal/poky/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend
>>>> as
>>>> in version poky-1.2.0
>>>> so the kernel was Image Name: Linux-3.2.9-yocto-standard
>>>> git status
>>>> # On branch denzil
>>>> # Changes not staged for commit:
>>>> # (use "git add <file>..." to update what will be committed)
>>>> # (use "git checkout -- <file>..." to discard changes in working
>>>> directory)
>>>> #
>>>> # modified: meta-yocto/conf/machine/beagleboard.conf
>>>> #
>>>> # Untracked files:
>>>> # (use "git add <file>..." to include in what will be committed)
>>>> #
>>>> # build/
>>>> no changes added to commit (use "git add" and/or "git commit -a")
>>>>
>>>> -rw-r--r--. 1 vidal users 57409536 Jul 20 16:29
>>>> core-image-sato-beagleboard-20120720200156.rootfs.jffs2
>>>> -rw-r--r--. 1 vidal users 42607308 Jul 20 16:28
>>>> core-image-sato-beagleboard-20120720200156.rootfs.tar.bz2
>>>> -rw-r--r--. 1 vidal users 57409536 Jul 21 08:06
>>>> core-image-sato-beagleboard-20120721135125.rootfs.jffs2
>>>> -rw-r--r--. 1 vidal users 42612264 Jul 21 08:05
>>>> core-image-sato-beagleboard-20120721135125.rootfs.tar.bz2
>>>> lrwxrwxrwx. 1 vidal users 55 Jul 21 08:06
>>>> core-image-sato-beagleboard.jffs2 ->
>>>> core-image-sato-beagleboard-20120721135125.rootfs.jffs2
>>>> lrwxrwxrwx. 1 vidal users 57 Jul 21 08:05
>>>> core-image-sato-beagleboard.tar.bz2 ->
>>>> core-image-sato-beagleboard-20120721135125.rootfs.tar.bz2
>>>> -rw-r--r--. 1 vidal users 205521920 Jul 20 18:50
>>>> core-image-sato-qemuarm-20120720223121.rootfs.ext3
>>>> -rw-r--r--. 1 vidal users 37671422 Jul 20 18:50
>>>> core-image-sato-qemuarm-20120720223121.rootfs.tar.bz2
>>>> lrwxrwxrwx. 1 vidal users 50 Jul 20 18:50 core-image-sato-qemuarm.ext3
>>>> -> core-image-sato-qemuarm-20120720223121.rootfs.ext3
>>>> lrwxrwxrwx. 1 vidal users 53 Jul 20 18:50
>>>> core-image-sato-qemuarm.tar.bz2 ->
>>>> core-image-sato-qemuarm-20120720223121.rootfs.tar.bz2
>>>> lrwxrwxrwx. 1 vidal users 70 Jul 20 16:04 MLO-beagleboard ->
>>>> MLO-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0
>>>> -rwxr-xr-x. 1 vidal users 22388 Jul 20 16:04
>>>> MLO-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0
>>>> -rw-r--r--. 1 vidal users 33114370 Jul 20 18:26
>>>> modules-3.2.18-yocto-standard-r1-qemuarm.tgz
>>>> -rw-r--r--. 1 vidal users 35180410 Jul 20 16:04
>>>> modules-3.2.9-yocto-standard-r1-beagleboard.tgz
>>>> -rw-r--r--. 1 vidal users 294 Jul 21 07:54
>>>> README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
>>>> lrwxrwxrwx. 1 vidal users 81 Jul 21 07:54 u-boot-beagleboard.bin ->
>>>>
>>>> u-boot-beagleboard-v2011.06+git12+b1af6f532e0d348b153d5c148369229d24af361a-r1.bin
>>>>
>>>> -rwxr-xr-x. 1 vidal users 316348 Jul 21 07:54
>>>>
>>>> u-boot-beagleboard-v2011.06+git12+b1af6f532e0d348b153d5c148369229d24af361a-r1.bin
>>>>
>>>> -rw-r--r--. 1 vidal users 3375864 Jul 20 16:04
>>>>
>>>> uImage-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+90e3138c5a2a390dd6ddf2ed84fe5a9756d43397-r1-beagleboard-20120720200156.bin
>>>>
>>>> lrwxrwxrwx. 1 vidal users 136 Jul 20 16:04 uImage-beagleboard.bin ->
>>>>
>>>> uImage-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+90e3138c5a2a390dd6ddf2ed84fe5a9756d43397-r1-beagleboard-20120720200156.bin
>>>>
>>>> -rwxr-xr-x. 1 vidal users 22388 Jul 20 16:04
>>>>
>>>> x-load-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0.bin.ift
>>>>
>>>> lrwxrwxrwx. 1 vidal users 81 Jul 20 16:04 x-load-beagleboard.bin.ift ->
>>>>
>>>> x-load-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0.bin.ift
>>>>
>>>> -rw-r--r--. 1 vidal users 3034248 Jul 20 18:26
>>>>
>>>> zImage-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+259cff0813417d16baaaaf44b00a9f75103ebfcb-r1-qemuarm-20120720223121.bin
>>>>
>>>> lrwxrwxrwx. 1 vidal users 132 Jul 20 18:26 zImage-qemuarm.bin ->
>>>>
>>>> zImage-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+259cff0813417d16baaaaf44b00a9f75103ebfcb-r1-qemuarm-20120720223121.bin
>>>>
>>>> cp
>>>> MLO-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0
>>>> /run/media/vidal/boot/MLO
>>>> cp
>>>>
>>>> u-boot-beagleboard-v2011.06+git12+b1af6f532e0d348b153d5c148369229d24af361a-r1.bin
>>>>
>>>> /run/media/vidal/boot/u-boot.bin
>>>> cp
>>>>
>>>> uImage-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+90e3138c5a2a390dd6ddf2ed84fe5a9756d43397-r1-beagleboard-20120720200156.bin
>>>>
>>>> /run/media/vidal/boot/uImage
>>>> cp /home/vidal/uEnv.txt /run/media/vidal/boot/
>>>> ls /run/media/vidal/boot/
>>>> MLO u-boot.bin uEnv.txt uImage
>>>>
>>>> cd /run/media/vidal/rootfs/
>>>> tar jxf
>>>>
>>>> /home/vidal/poky/build/tmp/deploy/images/core-image-sato-beagleboard-20120721135125.rootfs.tar.bz2
>>>>
>>>>
>>>> cd ~/
>>>> umount /run/media/vidal/boot
>>>> umount /run/media/vidal/rootfs
>>>> sync
>>>>
>>>> Texas Instruments X-Loader 1.5.0 (Jul 19 2012 - 17:05:29)
>>>> Beagle xM
>>>> Reading boot sector
>>>> Loading u-boot.bin from mmc
>>>>
>>>>
>>>> U-Boot 2011.06 (Jul 19 2012 - 21:25:33)
>>>>
>>>> OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
>>>> OMAP3 Beagle board + LPDDR/NAND
>>>> I2C: ready
>>>> DRAM: 512 MiB
>>>> NAND: 0 MiB
>>>> MMC: OMAP SD/MMC: 0
>>>> *** Warning - readenv() failed, using default environment
>>>>
>>>> In: serial
>>>> Out: serial
>>>> Err: serial
>>>> Beagle unknown 0x02
>>>> No EEPROM on expansion board
>>>> Die ID #158000029ff800000160a7450b02602d
>>>> Hit any key to stop autoboot: 10 9 8 7 6 5 4 3 2 1 0
>>>> SD/MMC found on device 0
>>>> reading uEnv.txt
>>>>
>>>> 130 bytes read
>>>> Importing environment from mmc ...
>>>> reading uImage
>>>>
>>>> 3375856 bytes read
>>>> Booting from mmc ...
>>>> ## Booting kernel from Legacy Image at 82000000 ...
>>>> Image Name: Linux-3.2.9-yocto-standard
>>>> Image Type: ARM Linux Kernel Image (uncompressed)
>>>> Data Size: 3375792 Bytes = 3.2 MiB
>>>> Load Address: 80008000
>>>> Entry Point: 80008000
>>>> Verifying Checksum ... OK
>>>> Loading Kernel Image ... OK
>>>> OK
>>>>
>>>> Starting kernel ...
>>>>
>>>> Uncompressing Linux... done, booting the kernel.
>>>> This ver finds the mmc but does not
>>>> get to login screen on serial port or display
>>>> nothing displayed on beagleboard monitor expection sato display.
>>>> smsc95xx 1-2.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 but
>>>> no IP assigned.
>>>>
>>>> The lines below just keep repeating.
>>>>
>>>> Mouse] on usb-ehci-omap.0-2.5/input0
>>>> usb 1-2.5: USB disconnect, device number 65
>>>> usb 1-2.5: new low-speed USB device number 66 using ehci-omap
>>>> input: PixArt USB Optical Mouse as
>>>> /devices/platform/usbhs-omap.0/ehci-omap.0/us
>>>> b1/1-2/1-2.5/1-2.5:1.0/input/input63
>>>> generic-usb 0003:093A:2510.0040: input: USB HID v1.11 Mouse [PixArt USB
>>>> Optical
>>>> Mouse] on usb-ehci-omap.0-2.5/input0
>>>> usb 1-2.5: USB disconnect, device number 66
>>>> usb 1-2.5: new low-speed USB device number 67 using ehci-omap
>>>> input: PixArt USB Optical Mouse as
>>>> /devices/platform/usbhs-omap.0/ehci-omap.0/us
>>>> b1/1-2/1-2.5/1-2.5:1.0/input/input64
>>>> generic-usb 0003:093A:2510.0041: input: USB HID v1.11 Mouse [PixArt USB
>>>> Optical
>>>> Mouse] on usb-ehci-omap.0-2.5/input0
>>>> usb 1-2.5: USB disconnect, device number 67
>>>> usb 1-2.5: new low-speed USB device number 68 using ehci-omap
>>>> input: PixArt USB Optical Mouse as
>>>> /devices/platform/usbhs-omap.0/ehci-omap.0/us
>>>> b1/1-2/1-2.5/1-2.5:1.0/input/input65
>>>> generic-usb 0003:093A:2510.0042: input: USB HID v1.11 Mouse [PixArt USB
>>>> Optical
>>>> Mouse] on usb-ehci-omap.0-2.5/input0
>>>>
>>>> Is there any other information that I can provide?
>>>
>>> This should be enough .. What we still need is a comment from the QA
>>> folks that are reporting green builds and boots for the beagleboard.
>>>
>> Bruce, I am not sure that the beagle board has officially be updated in
>> meta-yocto, meaning we have not tested this configuration yet.
> Right, I'm bumping it to 3.4 at the moment, but Edward also reported
> the 3.0 kernel
> as not working on his board, on our release branches. So I'm looking to confirm
> that first.
>
>>
>>> Saul: Do you know who the contact for that is ? I've lost track of who
>>> it should be ..
>>>
>> This would most likely be Yi Zhao (yi.zhao at windriver.com)
> Thanks!
>
> Bruce
>
>> Sau!
>>
>>
>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>
>>>> Any help will be appreciated
>>>> Regards
>>>>
>>>>
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto at yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: beagleboardxm-boot-ro.log
Type: text/x-log
Size: 242994 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120724/63c933f7/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: beagleboardxm-boot-rw.log
Type: text/x-log
Size: 11380 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120724/63c933f7/attachment-0001.bin>