Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi Khem, On Aug 17, 2012, at 9:48 AM, Khem Raj wrote: On Tue, Aug 14, 2012 at 7:26 AM, Khem Raj raj.k...@gmail.com wrote: There are differences in eglibc.inc and initrd recipes. Try to see if they make difference Also the libgcc one after the above two Elvis Did you try the above ? I have pushed a patch into my contrib tree. http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/miscid=502a61792cdb219c1ee35bb9474b8f0c4b007385 can you try that out and see if it helps with gcc 4.7 I had to manually apply the patch to poky/master. The gcc-4.7 patch alone didn't fix the issue with not getting a bash prompt, which makes sense I guess, since the eglibc recipes also need to be modified to ensure that the soft-float libraries are also generated into the target root filesystem. I'll now, make the necessary changes to eglibc-2.13, in poky/master, with gcc-4.7, and see if it works. If it does, then I'll adapt the same solution for eglibc-2.15, eglibc-2.16, and gcc-4.6 recipes, and sent them across. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
hi Khem, On Aug 19, 2012, at 10:08 AM, Elvis Dowson wrote: I'll now, make the necessary changes to eglibc-2.13, in poky/master, with gcc-4.7, and see if it works. Sorry, I meant to say libgcc-4.7 diff --git a/tool/yocto/poky/meta/recipes-devtools/gcc/libgcc_4.6.bb b/tool/eldk/meta/recipes-devtools/gcc/libgcc_4.6.bb index 9a8b20d..f75ca34 100644 --- a/tool/yocto/poky/meta/recipes-devtools/gcc/libgcc_4.6.bb +++ b/tool/eldk/meta/recipes-devtools/gcc/libgcc_4.6.bb @@ -16,8 +16,10 @@ PACKAGES = \ FILES_${PN} = ${base_libdir}/libgcc*.so.* FILES_${PN}-dev = \ ${base_libdir}/libgcc*.so \ - ${libdir}/${TARGET_SYS}/${BINV}/*crt* \ - ${libdir}/${TARGET_SYS}/${BINV}/libgcc* + ${libdir}/${TARGET_SYS}/${BINV}/crt* \ + ${libdir}/${TARGET_SYS}/${BINV}/libgcc* \ + ${libdir}/${TARGET_SYS}/${BINV}/nof/crt* \ + ${libdir}/${TARGET_SYS}/${BINV}/nof/libgcc* FILES_libgcov${PKGSUFFIX}-dev = \ ${libdir}/${TARGET_SYS}/${BINV}/libgcov.a Best regards, Elvis Dowson___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Sat, Aug 18, 2012 at 11:36 PM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi Khem, What should I do to enable multilib in gcc-4.7? I think at the moment, in gcc-configure-common.inc, it is disabled. If I were to re-enable it as follows, based on what I've diff'd from the Denx ELDK repo, what how does the GCCMULTILIB variable evaluate? just for tests. append --enable-multilib to EXTRA_OECONF in gcc-cross_4.7.bb something like EXTRA_OECONF_append = xxx -GCCMULTILIB = --disable-multilib +GCCMULTILIB = '${@base_contains(MULTILIB_ARCH_LIST, ${TARGET_ARCH}, --enable-multilib, --disable-multilib,d)}' I think multilib has to be enabled, no? In file gcc/config/rs6000/t-ppcos.c # Multilibs for a powerpc hosted ELF target (linux, SVR4) MULTILIB_OPTIONS = msoft-float MULTILIB_DIRNAMES = nof MULTILIB_EXTRA_OPTS = fPIC mstrict-align MULTILIB_EXCEPTIONS = MULTILIB_MATCHES = ${MULTILIB_MATCHES_FLOAT} Here is the full patch, which I am assuming enables multilib, and get libgcc to generate the nof libraries to the target: diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc b/meta/recipes-devtools/gcc/gcc-configure-common.inc index 908ad3e..a3fa294 100644 --- a/meta/recipes-devtools/gcc/gcc-configure-common.inc +++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc @@ -25,7 +25,7 @@ EXTRA_OECONF_PATHS ?= EXTRA_OECONF_INITIAL ?= EXTRA_OECONF_INTERMEDIATE ?= -GCCMULTILIB = --disable-multilib +GCCMULTILIB = '${@base_contains(MULTILIB_ARCH_LIST, ${TARGET_ARCH}, --enable-multilib, --disable-multilib,d)}' EXTRA_OECONF = ${@['--enable-clocale=generic', ''][d.getVar('USE_NLS', True) != 'no']} \ --with-gnu-ld \ diff --git a/meta/recipes-devtools/gcc/libgcc_4.7.bb b/meta/recipes-devtools/gcc/libgcc_4.7.bb index c796253..aac81f6 100644 --- a/meta/recipes-devtools/gcc/libgcc_4.7.bb +++ b/meta/recipes-devtools/gcc/libgcc_4.7.bb @@ -18,7 +18,9 @@ FILES_${PN} = ${base_libdir}/libgcc*.so.* FILES_${PN}-dev = \ ${base_libdir}/libgcc*.so \ ${libdir}/${TARGET_SYS}/${BINV}/*crt* \ - ${libdir}/${TARGET_SYS}/${BINV}/libgcc* + ${libdir}/${TARGET_SYS}/${BINV}/libgcc* \ + ${libdir}/${TARGET_SYS}/${BINV}/nof/crt* \ + ${libdir}/${TARGET_SYS}/${BINV}/nof/libgcc* FILES_libgcov${PKGSUFFIX}-dev = \ ${libdir}/${TARGET_SYS}/${BINV}/libgcov.a \ Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi Khem, On Aug 17, 2012, at 9:48 AM, Khem Raj wrote: On Tue, Aug 14, 2012 at 7:26 AM, Khem Raj raj.k...@gmail.com wrote: There are differences in eglibc.inc and initrd recipes. Try to see if they make difference Also the libgcc one after the above two Did you try the above ? I took a slight detour, the past 2 days, trying to use icecc, to reduce my build time across two quad-core i7 Ubuntu machines, but that didn't work for some reason. No workloads got distributed across to the second machine. I'll get back to continuing these tests this weekend. I have pushed a patch into my contrib tree. http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/miscid=502a61792cdb219c1ee35bb9474b8f0c4b007385 can you try that out and see if it helps with gcc 4.7 Will do that for sure! :-) Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Tue, Aug 14, 2012 at 7:26 AM, Khem Raj raj.k...@gmail.com wrote: There are differences in eglibc.inc and initrd recipes. Try to see if they make difference Also the libgcc one after the above two Elvis Did you try the above ? I have pushed a patch into my contrib tree. http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/miscid=502a61792cdb219c1ee35bb9474b8f0c4b007385 can you try that out and see if it helps with gcc 4.7 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi Khem, I also just tried gcc-4.6.3 and eglibc-2.13, and I get a segmentation fault while running /bin/getty, and a kernel panic when running init=/bin/bash, building off poky/master branch recipes. zImage starting: loaded at 0x0080 (sp: 0x0185dfa0) Allocating 0x548f0c bytes for kernel ... gunzipping (0x - 0x0080f000:0x00a1563f)...done 0x42b5c0 bytes Attached initrd image at 0x00a16000-0x0185ce95 initrd head: 0x1f8b0808 Linux/PowerPC load: console=ttyS0,9600n8 ip=off root=/dev/ram rw rootwait init=/bin/sh Finalizing device tree... flat tree at 0x186a0e0 PM: Adding info for No Bus:ttyv9 [0.588026] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.593401] 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 20) is a 16550 [0.788848] console [ttyS0] enabled [0.834170] brd: module loaded [0.880867] loop: module loaded [0.918134] xsysace 8360.sysace: Xilinx SystemACE revision 1.0.12 [0.994836] xsysace 8360.sysace: No CF in slot [1.053840] Xilinx SystemACE device driver, major=254 [1.114793] xilinx_emaclite 8100.ethernet: Device Tree Probing [1.188315] xilinx_emaclite 8100.ethernet: error registering MDIO bus [1.269388] xilinx_emaclite 8100.ethernet: MAC address is now 00:0a:35:b7:78:00 [1.363146] xilinx_emaclite 8100.ethernet: Xilinx EmacLite at 0x8100 mapped to 0xD10A, irq=17 [1.477955] xilinx_ps2 8148.ps2: Device Tree Probing 'ps2' [1.547173] xilinx_ps2 8148.ps2: Xilinx PS2 at 0x8148 mapped to 0xd1036000, irq=22 [1.646551] xilinx_ps2 81481000.ps2: Device Tree Probing 'ps2' [1.716251] xilinx_ps2 81481000.ps2: Xilinx PS2 at 0x81481000 mapped to 0xd1038000, irq=23 [1.816836] mousedev: PS/2 mouse device common for all mice [1.884361] i2c /dev entries driver [1.925909] Device Tree Probing 'i2c' [1.970181] xilinx-iic #0 at 0x8160 mapped to 0xD10C, irq=18 [2.047926] TCP cubic registered [2.085783] NET: Registered protocol family 17 [2.882898] atkbd serio0: keyboard reset failed on xilinxps2/serio at 8148 [3.367192] RAMDISK: gzip image found at block 0 [3.891097] input: AT Raw Set 2 keyboard as /devices/plb.0/xps-ps2.1/81481000.ps2/serio1/input/input0 [6.271270] EXT2-fs (ram0): warning: mounting unchecked fs, running e2fsck is recommended [6.368556] VFS: Mounted root (ext2 filesystem) on device 1:0. [6.439318] Freeing unused kernel memory: 156k freed /bin/sh: can't access tty; job control turned off [6.583032] Kernel panic - not syncing: Attempted to kill init! [6.653114] Rebooting in 180 seconds.. So, in summary: The following combinations didn't work for the poky/master branch gcc-4.5.1, eglibc-2.15, binutils-2.22 gcc-4.5.1, eglibc-2.16, binutils-2.22 gcc-4.6.3, eglibc-2.13, binutils-2.22 gcc-4.7.2, eglibc-2.13, binutils-2.22 The combinations that worked are gcc-4.5.1, eglibc-2.13, binutils-2.22 (from poky/master) gcc-4.6.3, eglibc-2.13, binutils-2.22 (from the Denx ELDK 5.2.1 release, which corresponds to the denzil release) What would you like me to do next, to try and narrow down this issue? Some things that I can try are: a. build gcc-4.6.3, eglibc-2.13, binutils-2.22 (from poky/denzil branch, to establish a known good build data point) b. try and build gcc-4.8.0, with eglibc-2.13, binutils-2.22 (I prepare a gcc-4.8 recipe already, but need to try it out) c. try eglibc-2.13/2.15/2.16 combination with gcc-4.5.1 and binutils-2.22 on a different architecture (e.g. TI OMAP 3530 ARM Cortex A8 Gumstix Overo, TI OMAP 4430 PandaBoard, Xilinx Zynq-7020 Dual ARM Cortex A9) just to see if the problem manifests on different architectures as well Best regards, Elvis Dowson___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi Khem, I've made tangential progress!! I found out that Denx had a bunch of pre-built rootfilesystems, generated from yocto/denzil branch. I took the core-image-core-generic-powerpc-4xx-softfloat.tar.gz from the following location: ftp://ftp.denx.de/pub/eldk/5.2.1/targets/powerpc-4xx-softfloat I used the linux-xilinx-3.3.0 kernel that I built earlier (since the linux sources are independent) with gcc-4.5.1, and use the pre-build root filesystem, and guess what, I get the bash prompt!! zImage starting: loaded at 0x0080 (sp: 0x016defa0) Allocating 0x54cf4c bytes for kernel ... gunzipping (0x - 0x0080f000:0x00a1aedf)...done 0x42f600 bytes Attached initrd image at 0x00a1b000-0x016ddb0f initrd head: 0x1f8b0808 Linux/PowerPC load: console=ttyS0,9600n8 ip=off root=/dev/ram rw rootwait init=/bin/sh Finalizing device tree... flat tree at 0x16eb0e0 PM: Adding info for No Bus:ttyv9 [0.572492] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.577880] 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 20) is a 16550 [0.773419] console [ttyS0] enabled [0.818736] brd: module loaded [0.865394] loop: module loaded [0.902715] xsysace 8360.sysace: Xilinx SystemACE revision 1.0.12 [0.979410] xsysace 8360.sysace: No CF in slot [1.038416] Xilinx SystemACE device driver, major=254 [1.099449] xilinx_emaclite 8100.ethernet: Device Tree Probing [1.172953] xilinx_emaclite 8100.ethernet: error registering MDIO bus [1.254057] xilinx_emaclite 8100.ethernet: MAC address is now 00:0a:35:b7:78:00 [1.347806] xilinx_emaclite 8100.ethernet: Xilinx EmacLite at 0x8100 mapped to 0xD10A, irq=17 [1.462670] xilinx_ps2 8148.ps2: Device Tree Probing 'ps2' [1.531949] xilinx_ps2 8148.ps2: Xilinx PS2 at 0x8148 mapped to 0xd1036000, irq=22 [1.631395] xilinx_ps2 81481000.ps2: Device Tree Probing 'ps2' [1.701014] xilinx_ps2 81481000.ps2: Xilinx PS2 at 0x81481000 mapped to 0xd1038000, irq=23 [1.801542] mousedev: PS/2 mouse device common for all mice [1.869031] i2c /dev entries driver [1.910602] Device Tree Probing 'i2c' [1.954862] xilinx-iic #0 at 0x8160 mapped to 0xD10C, irq=18 [2.032541] TCP cubic registered [2.070347] NET: Registered protocol family 17 [2.867055] atkbd serio0: keyboard reset failed on xilinxps2/serio at 8148 [3.351351] RAMDISK: gzip image found at block 0 [3.875264] input: AT Raw Set 2 keyboard as /devices/plb.0/xps-ps2.1/81481000.ps2/serio1/input/input0 [6.223416] EXT2-fs (ram0): warning: mounting unchecked fs, running e2fsck is recommended [6.320721] VFS: Mounted root (ext2 filesystem) on device 1:0. [6.391510] Freeing unused kernel memory: 160k freed /bin/sh: can't access tty; job control turned off / # The following link gives
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi Khem, I just noticed that libquadmath was disabled in the gcc-4.7.inc recipe. EXTRA_OECONF_INITIAL = --disable-libmudflap \ --disable-libgomp \ --disable-libssp \ --disable-libquadmath \ --with-system-zlib \ --disable-lto \ --disable-plugin \ --enable-decimal-float=no Isn't that required for powerpc targets, since it ends up using quads for floats? Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Sat, Aug 11, 2012 at 10:23 AM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi Khem, I just noticed that libquadmath was disabled in the gcc-4.7.inc recipe. EXTRA_OECONF_INITIAL = --disable-libmudflap \ --disable-libgomp \ --disable-libssp \ --disable-libquadmath \ --with-system-zlib \ --disable-lto \ --disable-plugin \ --enable-decimal-float=no Isn't that required for powerpc targets, since it ends up using quads for floats? thats only for bootstrap stage 1. Its not final cross gcc. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi Khem, I added support for gcc-4.5.1 inside meta-openembedded/toolchain-layer, and got it building against the latest yocto/master branch. However, switching to gcc-4.5.1 did not fix the issue. Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Sat, Aug 11, 2012 at 8:34 PM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi Khem, I added support for gcc-4.5.1 inside meta-openembedded/toolchain-layer, and got it building against the latest yocto/master branch. However, switching to gcc-4.5.1 did not fix the issue. OK. You might want to downgrade the eglibc version to 2.15 and then to 2.13 if thats around. Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi, I switched to using gcc-4.6 from the meta-openembedded layer, and still get the same issue, i.e. no login or bash prompt with init=/bin/sh zImage starting: loaded at 0x0080 (sp: 0x016d2fa0) Allocating 0x546e0c bytes for kernel ... gunzipping (0x - 0x0080f000:0x00a14e83)...done 0x4295c0 bytes Attached initrd image at 0x00a15000-0x016d1e57 initrd head: 0x1f8b0808 Linux/PowerPC load: console=ttyS0,9600n8 ip=off root=/dev/ram rw rootwait init=/bin/sh Finalizing device tree... flat tree at 0x16df0e0 PM: Adding info for No Bus:ttyv9 [0.571186] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.576568] 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 20) is a 16550 [0.772047] console [ttyS0] enabled [0.836379] brd: module loaded [0.883293] loop: module loaded [0.920576] xsysace 8360.sysace: Xilinx SystemACE revision 1.0.12 [0.997321] xsysace 8360.sysace: No CF in slot [1.056390] Xilinx SystemACE device driver, major=254 [1.117274] xilinx_emaclite 8100.ethernet: Device Tree Probing [1.190788] xilinx_emaclite 8100.ethernet: error registering MDIO bus [1.271877] xilinx_emaclite 8100.ethernet: MAC address is now 00:0a:35:b7:78:00 [1.365554] xilinx_emaclite 8100.ethernet: Xilinx EmacLite at 0x8100 mapped to 0xD10A, irq=17 [1.480513] xilinx_ps2 8148.ps2: Device Tree Probing 'ps2' [1.549769] xilinx_ps2 8148.ps2: Xilinx PS2 at 0x8148 mapped to 0xd1036000, irq=22 [1.649154] xilinx_ps2 81481000.ps2: Device Tree Probing 'ps2' [1.718826] xilinx_ps2 81481000.ps2: Xilinx PS2 at 0x81481000 mapped to 0xd1038000, irq=23 [1.819612] mousedev: PS/2 mouse device common for all mice [1.887013] i2c /dev entries driver [1.928583] Device Tree Probing 'i2c' [1.972867] xilinx-iic #0 at 0x8160 mapped to 0xD10C, irq=18 [2.050528] TCP cubic registered [2.088448] NET: Registered protocol family 17 [2.882860] atkbd serio0: keyboard reset failed on xilinxps2/serio at 8148 [3.367142] RAMDISK: gzip image found at block 0 [3.895064] input: AT Raw Set 2 keyboard as /devices/plb.0/xps-ps2.1/81481000.ps2/serio1/input/input0 [6.255216] EXT2-fs (ram0): warning: mounting unchecked fs, running e2fsck is recommended [6.352491] VFS: Mounted root (ext2 filesystem) on device 1:0. [6.423252] Freeing unused kernel memory: 156k freed gdb, connected to the target board via JTAG to debug the kernel, also doesn't seem to complain: (gdb) syslog device: 'input0': device_add 7[3.890268] PM: Adding info for No Bus:input0 6[3.895007] input: AT Raw Set 2 keyboard as /devices/plb.0/xps-ps2.1/81481000.ps2/serio1/input/input0 7[4.110886] driver: 'serio1': driver_bound: bound to device 'atkbd' 7[4.110922] bus: 'serio': really_probe: bound device serio1 to driver atkbd 7[4.110956] bus: 'serio': driver_probe_device: matched device serio0 with driver psmouse 7[4.110975] bus: 'serio': really_probe: probing driver psmouse with device serio0 7[4.310941] psmouse: probe of serio0 rejects match -19 4[6.259162] EXT2-fs (ram0): warning: mounting unchecked fs, running e2fsck is recommended 6[6.356473] VFS: Mounted root (ext2 filesystem) on device 1:0. 6[6.427235] Freeing unused kernel memory: 156k freed So weird. Best regards, Elvis Dowson___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On 07/31/2012 01:27 PM, Elvis Dowson wrote: Is serial console login prompt broken on yocto for targets other than Intel? Does it work on ARM or PowerPC at the moment, with the latest yocto updates as of today? Hi Elvis, For my Freescale QorIQ e500v2 target, the use of getty inside init / inittab has been broken for awhile. I used to get the hangs you're reporting, but now I also see the following at the conclusion of init: serial8250: too much work for irq42 I'm glad you're working this issue, and I'll try to jump in this week. My workaround has been a hack to inittab to replace getty with /bin/sh - most of my work is done across the network via ssh to the target, so I didn't mind ignoring the problem. Bob ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Wed, Aug 8, 2012 at 8:44 AM, Bob Cochran yo...@mindchasers.com wrote: On 07/31/2012 01:27 PM, Elvis Dowson wrote: Is serial console login prompt broken on yocto for targets other than Intel? Does it work on ARM or PowerPC at the moment, with the latest yocto updates as of today? Hi Elvis, For my Freescale QorIQ e500v2 target, the use of getty inside init / inittab has been broken for awhile. I used to get the hangs you're reporting, but now I also see the following at the conclusion of init: serial8250: too much work for irq42 I'm glad you're working this issue, and I'll try to jump in this week. My workaround has been a hack to inittab to replace getty with /bin/sh - most of my work is done across the network via ssh to the target, so I didn't mind ignoring the problem. These seem like quite different issues, code generation vs. some inittab foo... are you seeing this issues with upstream? I've recently gotten some inittab cleanups into oe-core for master / denzil / my own edison branch + meta-fsl-ppc... -M Bob ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On 08/08/2012 03:05 PM, McClintock Matthew-B29882 wrote: These seem like quite different issues, code generation vs. some inittab foo... are you seeing this issues with upstream? I've recently gotten some inittab cleanups into oe-core for master / denzil / my own edison branch + meta-fsl-ppc... On 08/08/2012 03:05 PM, McClintock Matthew-B29882 wrote: These seem like quite different issues, code generation vs. some inittab foo... are you seeing this issues with upstream? I've recently gotten some inittab cleanups into oe-core for master / denzil / my own edison branch + meta-fsl-ppc... Thanks Matthew. I need to sort this out with some regression testing. The latest master branches of poky meta-fsl-ppc provides a kernel that oops while it's probing flash during boot. With the latest fsl-image-minimal rootfs and a mainline kernel, I get an init that hangs when it tries to exec getty. I see that the the serial8250: too much work for irq42 message comes from drivers/tty/serial/8250/8250.c and that there have been plenty of patches to this file this year. I'll chime in again later. Bob ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi, I decided to modify the bash and busybox recipes to build statically, and try to create a core-image-minimal root filesystem, so that I can get a sensible prompt with paths set, etc, to debug the dynamic linking issue. Just copying a static bash binary to the root of the ramdisk image and specifying init=/bash didn't work for a static bash+core-image-minimal root filesystem, it aborts with a panic. If I have only the bash executable in the ramdisk and nothing else, it displays the bash prompt. Now, I've noticed something weird during core-image-minimal image generation. When I build the static versions of bash, the size of the binary is 8MB, but when I explore the binary in the tar.gz image or extract it to my ramdisk, it shows as being only 1.6MB. How can there be a difference between the statically built bash file /tool/yocto/poky/build/tmp/work/ppc440-poky-linux/bash-4.2-r4/image/bin/bash (8MB) and in the file contained in the core-image-minimal-virtex-5.tar.gz /bin/bash (1.6MB) I'm seeing the same discrepancy for busybox /tool/yocto/poky/build/tmp/work/ppc440-poky-linux/busybox-1.19.4-r18/image/bin/busybox (8.2 MB) and in the generate rootfs image /bin/busybox (1.4MB) This shouldn't happen, right? Best regards, Elvis Dowson___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi, On Aug 8, 2012, at 0:30, Khem Raj raj.k...@gmail.com wrote: On Tue, Aug 7, 2012 at 1:24 PM, Elvis Dowson elvis.dow...@gmail.com wrote: Is there something that I can disable to get static bash to run to the prompt, with the core-image-minimal image? well compile bash or dash as static and copy it manually into the rootfile system nfs root works well for such experiments. Do you have that option ? I tired manually copying the static bash binary 8mb, over to the ramdisk root folder. The problem still manifests, if there is no other file other than the static bash file, it displays the prompt. If the core-minimal-console image exists, along with the static bash binary in the root location, it gives the kernel panic, as shown above. Best regards, Elvis ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi, I was just going through the recipes-devtools/gcc/gcc-common.inc file, and noticed the following snippet: def get_gcc_multiarch_setting(bb, d): target_arch = d.getVar('TRANSLATED_TARGET_ARCH', True) multiarch_options = { i586:--enable-targets=all, powerpc: --enable-targets=powerpc64, sparc: --enable-targets=all, } My target is a 32-bit ppc440 cpu. What is the impact of an incorrectly set multiarch_options for powerpc to powerpc64 on the final build? Elvis Dowson___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Tue, Aug 7, 2012 at 7:36 PM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi, I was just going through the recipes-devtools/gcc/gcc-common.inc file, and noticed the following snippet: def get_gcc_multiarch_setting(bb, d): target_arch = d.getVar('TRANSLATED_TARGET_ARCH', True) multiarch_options = { i586:--enable-targets=all, powerpc: --enable-targets=powerpc64, sparc: --enable-targets=all, } My target is a 32-bit ppc440 cpu. What is the impact of an incorrectly set multiarch_options for powerpc to powerpc64 on the final build? thats not a issue. Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Tue, Aug 7, 2012 at 1:33 PM, Elvis Dowson elvis.dow...@gmail.com wrote: I tired manually copying the static bash binary 8mb, over to the ramdisk root folder. The problem still manifests, if there is no other file other than the static bash file, it displays the prompt. If the core-minimal-console image exists, along with the static bash binary in the root location, it gives the kernel panic, as shown above. I dont understand why it would boot when the rfs is just static bash and not when you bundle it along with rest of file system and setting init=/bin/bash you should get same results imo unless there are some conflicts in the latter case where /bin/bash is not static OK, another approach I could suggest is to use chroot. So boot the system into a known root file system. Then untar the new root file system under /opt or somewhere then chroot into it and try to run any dynamically linked program and see if that works. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Sat, Aug 4, 2012 at 12:16 PM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi Khem, On Aug 4, 2012, at 9:12 PM, Khem Raj wrote: Try to see if /lib/ld.so.1 runs ok ? How can I run /lib/ld.so.1? /lib/ld.so.1 Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi, On Aug 4, 2012, at 1:30 AM, Elvis Dowson wrote: I'll try to switch back to a non-static bash, and try booting the core-image-minimal filesystem once again. Switching back to the core-image-default non-static bash version, didn't work. I get no bash prompt, even through I specified init=/bin/sh for the kernel bootargs zImage starting: loaded at 0x0080 (sp: 0x00dacfb0) Allocating 0x540e0c bytes for kernel ... gunzipping (0x - 0x0080f000:0x00a17ddd)...done 0x4235c0 bytes Attached initrd image at 0x00a18000-0x00dab775 initrd head: 0x1f8b0808 Linux/PowerPC load: console=ttyS0,9600n8 ip=off root=/dev/ram rw rootwait init=/bin/sh Finalizing device tree... flat tree at 0xdb90e0 PM: Adding info for No Bus:ttyv9 [0.478914] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.484189] 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 20) is a 16550 [0.679634] console [ttyS0] enabled [0.743646] brd: module loaded [0.790371] loop: module loaded [0.827695] xsysace 8360.sysace: Xilinx SystemACE revision 1.0.12 [0.904387] xsysace 8360.sysace: No CF in slot [0.963434] Xilinx SystemACE device driver, major=254 [1.024322] xilinx_emaclite 8100.ethernet: Device Tree Probing [1.097851] xilinx_emaclite 8100.ethernet: error registering MDIO bus [1.178937] xilinx_emaclite 8100.ethernet: MAC address is now 00:0a:35:b7:78:00 [1.272553] xilinx_emaclite 8100.ethernet: Xilinx EmacLite at 0x8100 mapped to 0xD10A, irq=17 [1.387465] xilinx_ps2 8148.ps2: Device Tree Probing 'ps2' [1.456732] xilinx_ps2 8148.ps2: Xilinx PS2 at 0x8148 mapped to 0xd1036000, irq=22 [1.556112] xilinx_ps2 81481000.ps2: Device Tree Probing 'ps2' [1.625786] xilinx_ps2 81481000.ps2: Xilinx PS2 at 0x81481000 mapped to 0xd1038000, irq=23 [1.726276] mousedev: PS/2 mouse device common for all mice [1.793618] i2c /dev entries driver [1.835429] Device Tree Probing 'i2c' [1.879626] xilinx-iic #0 at 0x8160 mapped to 0xD10C, irq=18 [1.957193] TCP cubic registered [1.995099] NET: Registered protocol family 17 [2.790435] atkbd serio0: keyboard reset failed on xilinxps2/serio at 8148 [3.274705] RAMDISK: gzip image found at block 0 [3.681850] atkbd serio1: Frame/parity error: 02 [3.858630] input: AT Raw Set 2 keyboard as /devices/plb.0/xps-ps2.1/81481000.ps2/serio1/input/input0 [4.242871] VFS: Mounted root (ext2 filesystem) on device 1:0. [4.313049] Freeing unused kernel memory: 152k freed What should I do now to debug this issue further? I have disabled image-prelink by not including it in my local.conf as follows: # Remove image-prelink for PowerPC 32-bit and 64-bit targets. USER_CLASSES ?= buildstats image-mklibs Any thoughts on what I can try to do next, to narrow down the issue, with bash working statically, but not when linked with shared libraries? Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On 08/03/2012 03:05 PM, Elvis Dowson wrote: Hi, On Aug 4, 2012, at 1:30 AM, Elvis Dowson wrote: I'll try to switch back to a non-static bash, and try booting the core-image-minimal filesystem once again. Switching back to the core-image-default non-static bash version, didn't work. I get no bash prompt, even through I specified init=/bin/sh for the kernel bootargs zImage starting: loaded at 0x0080 (sp: 0x00dacfb0) Allocating 0x540e0c bytes for kernel ... gunzipping (0x - 0x0080f000:0x00a17ddd)...done 0x4235c0 bytes Attached initrd image at 0x00a18000-0x00dab775 initrd head: 0x1f8b0808 Linux/PowerPC load: console=ttyS0,9600n8 ip=off root=/dev/ram rw rootwait init=/bin/sh Finalizing device tree... flat tree at 0xdb90e0 PM: Adding info for No Bus:ttyv9 [0.478914] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.484189] 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 20) is a 16550 [0.679634] console [ttyS0] enabled [0.743646] brd: module loaded [0.790371] loop: module loaded [0.827695] xsysace 8360.sysace: Xilinx SystemACE revision 1.0.12 [0.904387] xsysace 8360.sysace: No CF in slot [0.963434] Xilinx SystemACE device driver, major=254 [1.024322] xilinx_emaclite 8100.ethernet: Device Tree Probing [1.097851] xilinx_emaclite 8100.ethernet: error registering MDIO bus [1.178937] xilinx_emaclite 8100.ethernet: MAC address is now 00:0a:35:b7:78:00 [1.272553] xilinx_emaclite 8100.ethernet: Xilinx EmacLite at 0x8100 mapped to 0xD10A, irq=17 [1.387465] xilinx_ps2 8148.ps2: Device Tree Probing 'ps2' [1.456732] xilinx_ps2 8148.ps2: Xilinx PS2 at 0x8148 mapped to 0xd1036000, irq=22 [1.556112] xilinx_ps2 81481000.ps2: Device Tree Probing 'ps2' [1.625786] xilinx_ps2 81481000.ps2: Xilinx PS2 at 0x81481000 mapped to 0xd1038000, irq=23 [1.726276] mousedev: PS/2 mouse device common for all mice [1.793618] i2c /dev entries driver [1.835429] Device Tree Probing 'i2c' [1.879626] xilinx-iic #0 at 0x8160 mapped to 0xD10C, irq=18 [1.957193] TCP cubic registered [1.995099] NET: Registered protocol family 17 [2.790435] atkbd serio0: keyboard reset failed on xilinxps2/serio at 8148 [3.274705] RAMDISK: gzip image found at block 0 [3.681850] atkbd serio1: Frame/parity error: 02 [3.858630] input: AT Raw Set 2 keyboard as /devices/plb.0/xps-ps2.1/81481000.ps2/serio1/input/input0 [4.242871] VFS: Mounted root (ext2 filesystem) on device 1:0. [4.313049] Freeing unused kernel memory: 152k freed What should I do now to debug this issue further? I have disabled image-prelink by not including it in my local.conf as follows: # Remove image-prelink for PowerPC 32-bit and 64-bit targets. USER_CLASSES ?= buildstats image-mklibs Any thoughts on what I can try to do next, to narrow down the issue, with bash working statically, but not when linked with shared libraries? I haven't debugged a static vs. dynamic boot-time issue for some years, but here are a few ideas off the top of my head. First, use readelf or objdump to validate where the binary is expecting to load the dynamic linker from (that is, what directory path). Check that the linker and all libraries are in the proper places (in the paths as specified in the ELF headers for the program - bash in this case). Second, try instrumenting (ie adding printks to) the loader path, and see if the kernel knows what is failing. The way dynamic linking works is that the kernel loads the program image (ELF file), and treats the dynamic linker (ldlinux.so) as it's interpreter. If you're not seeing an attempt to load the interpreter, then something is going wrong. You could instrument the kernel open path to see all the files that are being opened during the boot. ldlinux.so should be one of them. The linker should then be trying to load the other libraries needed by the program. This should also result in open calls (or possibly mmap calls). Good luck. -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Aug 3, 2012, at 3:05 PM, Elvis Dowson elvis.dow...@gmail.com wrote: Hi, On Aug 4, 2012, at 1:30 AM, Elvis Dowson wrote: I'll try to switch back to a non-static bash, and try booting the core-image-minimal filesystem once again. Switching back to the core-image-default non-static bash version, didn't work. I get no bash prompt, even through I specified init=/bin/sh for the kernel bootargs zImage starting: loaded at 0x0080 (sp: 0x00dacfb0) Allocating 0x540e0c bytes for kernel ... gunzipping (0x - 0x0080f000:0x00a17ddd)...done 0x4235c0 bytes Attached initrd image at 0x00a18000-0x00dab775 initrd head: 0x1f8b0808 Linux/PowerPC load: console=ttyS0,9600n8 ip=off root=/dev/ram rw rootwait init=/bin/sh Finalizing device tree... flat tree at 0xdb90e0 PM: Adding info for No Bus:ttyv9 [0.478914] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.484189] 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 20) is a 16550 [0.679634] console [ttyS0] enabled [0.743646] brd: module loaded [0.790371] loop: module loaded [0.827695] xsysace 8360.sysace: Xilinx SystemACE revision 1.0.12 [0.904387] xsysace 8360.sysace: No CF in slot [0.963434] Xilinx SystemACE device driver, major=254 [1.024322] xilinx_emaclite 8100.ethernet: Device Tree Probing [1.097851] xilinx_emaclite 8100.ethernet: error registering MDIO bus [1.178937] xilinx_emaclite 8100.ethernet: MAC address is now 00:0a:35:b7:78:00 [1.272553] xilinx_emaclite 8100.ethernet: Xilinx EmacLite at 0x8100 mapped to 0xD10A, irq=17 [1.387465] xilinx_ps2 8148.ps2: Device Tree Probing 'ps2' [1.456732] xilinx_ps2 8148.ps2: Xilinx PS2 at 0x8148 mapped to 0xd1036000, irq=22 [1.556112] xilinx_ps2 81481000.ps2: Device Tree Probing 'ps2' [1.625786] xilinx_ps2 81481000.ps2: Xilinx PS2 at 0x81481000 mapped to 0xd1038000, irq=23 [1.726276] mousedev: PS/2 mouse device common for all mice [1.793618] i2c /dev entries driver [1.835429] Device Tree Probing 'i2c' [1.879626] xilinx-iic #0 at 0x8160 mapped to 0xD10C, irq=18 [1.957193] TCP cubic registered [1.995099] NET: Registered protocol family 17 [2.790435] atkbd serio0: keyboard reset failed on xilinxps2/serio at 8148 [3.274705] RAMDISK: gzip image found at block 0 [3.681850] atkbd serio1: Frame/parity error: 02 [3.858630] input: AT Raw Set 2 keyboard as /devices/plb.0/xps-ps2.1/81481000.ps2/serio1/input/input0 [4.242871] VFS: Mounted root (ext2 filesystem) on device 1:0. [4.313049] Freeing unused kernel memory: 152k freed What should I do now to debug this issue further? I have disabled image-prelink by not including it in my local.conf as follows: # Remove image-prelink for PowerPC 32-bit and 64-bit targets. USER_CLASSES ?= buildstats image-mklibs Any thoughts on what I can try to do next, to narrow down the issue, with bash working statically, but not when linked with shared libraries? OK couple of things. You could boot into static bash thats good, keep it that way and bundle some dynamically linked programs into the root file system may be just a hello world which is dynamically linked. I would also compile a static version of gdb and strace but that could be next steps. then boot into this static shell and try to run the dynamically linked hello world. Does that work ? if not we have a dynamic linking issue. Then you can go a step deeper and see whats going on. Many a times interpreter is specified wrongly in the elf file. and there could be dynamic linker issues too. But step at a time. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto