RE: [OMAP 1710] Mainline Broken
-Original Message- From: Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: Thursday, December 16, 2010 10:39 PM To: Belisko Marek Cc: DebBarma, Tarun Kanti; linux-omap@vger.kernel.org Subject: Re: [OMAP 1710] Mainline Broken Belisko Marek marek.beli...@gmail.com writes: Hi, On Thu, Dec 16, 2010 at 4:30 PM, DebBarma, Tarun Kanti tarun.ka...@ti.com wrote: Did anyone observe this? I am using omap_generic_1710_defconfig [...] input: omap-keypad as /devices/platform/omap-keypad/input/input0 TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type eth0: link up IP-Config: Complete: device=eth0, addr=172.24.191.106, mask=255.255.252.0, gw=172.24.188.1, host=myomap, domain=, nis-domain=(none), bootserver=172.24.191.66, rootserver=172.24.191.66, rootpath= VFS: Mounted root (nfs filesystem) on device 0:10. Freeing init memory: 128K Kernel panic - not syncing: Attempted to kill init! Seems your userspace is broken. Try add user_debug=31 to command line to see what exactly happens. Looks like you're mounting an NFS rootfs. Was it compiled for armv5? My hunch would be you're trying to run an armv6/armv7 userspace on the 1710 which is armv5. To get more debugging, ensure these are enabled in your defconfig: CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_USER=y CONFIG_DEBUG_ERRORS=y and in addition to cmdline suggested by Marek, add user_debug=0xf This will give verbose output for userspace exceptions as well and possibly confirm my hunch. Kevin I checked .config and it shows: CONFIG_CPU_32v5=y With regard to additional log here they are!! [...] [1] init: obsolete system call . Code: e08f1001 e1a0c000 e3a0702d ef00 (e3700a01) Kernel panic - not syncing: Attempted to kill init! Backtrace: [...] -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [OMAP 1710] Mainline Broken
DebBarma, Tarun Kanti had written, on 12/17/2010 02:22 AM, the following: -Original Message- From: Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: Thursday, December 16, 2010 10:39 PM To: Belisko Marek Cc: DebBarma, Tarun Kanti; linux-omap@vger.kernel.org Subject: Re: [OMAP 1710] Mainline Broken Belisko Marek marek.beli...@gmail.com writes: Hi, On Thu, Dec 16, 2010 at 4:30 PM, DebBarma, Tarun Kanti tarun.ka...@ti.com wrote: Did anyone observe this? I am using omap_generic_1710_defconfig [...] input: omap-keypad as /devices/platform/omap-keypad/input/input0 TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type eth0: link up IP-Config: Complete: device=eth0, addr=172.24.191.106, mask=255.255.252.0, gw=172.24.188.1, host=myomap, domain=, nis-domain=(none), bootserver=172.24.191.66, rootserver=172.24.191.66, rootpath= VFS: Mounted root (nfs filesystem) on device 0:10. Freeing init memory: 128K Kernel panic - not syncing: Attempted to kill init! Seems your userspace is broken. Try add user_debug=31 to command line to see what exactly happens. Looks like you're mounting an NFS rootfs. Was it compiled for armv5? My hunch would be you're trying to run an armv6/armv7 userspace on the 1710 which is armv5. To get more debugging, ensure these are enabled in your defconfig: CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_USER=y CONFIG_DEBUG_ERRORS=y and in addition to cmdline suggested by Marek, add user_debug=0xf This will give verbose output for userspace exceptions as well and possibly confirm my hunch. Kevin I checked .config and it shows: CONFIG_CPU_32v5=y With regard to additional log here they are!! [...] [1] init: obsolete system call . Code: e08f1001 e1a0c000 e3a0702d ef00 (e3700a01) Kernel panic - not syncing: Attempted to kill init! Backtrace: [...] I wonder if the age old http://linux.omap.com/pub/documentation/Howto_build_Linux_on_H3.pdf and http://linux.omap.com/pub/filesystem/ might help? -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [OMAP 1710] Mainline Broken
DebBarma, Tarun Kanti tarun.ka...@ti.com writes: -Original Message- From: Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: Thursday, December 16, 2010 10:39 PM To: Belisko Marek Cc: DebBarma, Tarun Kanti; linux-omap@vger.kernel.org Subject: Re: [OMAP 1710] Mainline Broken Belisko Marek marek.beli...@gmail.com writes: Hi, On Thu, Dec 16, 2010 at 4:30 PM, DebBarma, Tarun Kanti tarun.ka...@ti.com wrote: Did anyone observe this? I am using omap_generic_1710_defconfig [...] input: omap-keypad as /devices/platform/omap-keypad/input/input0 TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type eth0: link up IP-Config: Complete: device=eth0, addr=172.24.191.106, mask=255.255.252.0, gw=172.24.188.1, host=myomap, domain=, nis-domain=(none), bootserver=172.24.191.66, rootserver=172.24.191.66, rootpath= VFS: Mounted root (nfs filesystem) on device 0:10. Freeing init memory: 128K Kernel panic - not syncing: Attempted to kill init! Seems your userspace is broken. Try add user_debug=31 to command line to see what exactly happens. Looks like you're mounting an NFS rootfs. Was it compiled for armv5? My hunch would be you're trying to run an armv6/armv7 userspace on the 1710 which is armv5. To get more debugging, ensure these are enabled in your defconfig: CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_USER=y CONFIG_DEBUG_ERRORS=y and in addition to cmdline suggested by Marek, add user_debug=0xf This will give verbose output for userspace exceptions as well and possibly confirm my hunch. Kevin I checked .config and it shows: CONFIG_CPU_32v5=y This is a kernel config option. I was asking about your userspace. Your kernel is obviously booting fine, but it crashes as soon as userspace starts. Is your *userspace* compiled for armv5? I'm guessing not. Kevin With regard to additional log here they are!! [...] [1] init: obsolete system call . Code: e08f1001 e1a0c000 e3a0702d ef00 (e3700a01) Kernel panic - not syncing: Attempted to kill init! Backtrace: [...] -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[OMAP 1710] Mainline Broken
Did anyone observe this? I am using omap_generic_1710_defconfig [...] input: omap-keypad as /devices/platform/omap-keypad/input/input0 TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type eth0: link up IP-Config: Complete: device=eth0, addr=172.24.191.106, mask=255.255.252.0, gw=172.24.188.1, host=myomap, domain=, nis-domain=(none), bootserver=172.24.191.66, rootserver=172.24.191.66, rootpath= VFS: Mounted root (nfs filesystem) on device 0:10. Freeing init memory: 128K Kernel panic - not syncing: Attempted to kill init! Backtrace: [c0032104] (dump_backtrace+0x0/0x114) from [c027ecd4] (dump_stack+0x18/0x1c) r7:c0826000 r6:c0826000 r5:c0304ce8 r4:c0320254 [c027ecbc] (dump_stack+0x0/0x1c) from [c027ed38] (panic+0x60/0x188) [c027ecd8] (panic+0x0/0x188) from [c0047414] (do_exit+0x74/0x600) r3:6013 r2:c0826000 r1:c08260f8 r0:c02d6cff [c00473a0] (do_exit+0x0/0x600) from [c0047a38] (do_group_exit+0x98/0xcc) [c00479a0] (do_group_exit+0x0/0xcc) from [c00535e4] (get_signal_to_deliver+0x304/0x33c) r7:c08ba484 r6:c0828000 r5:c0829ee4 r4:0004 [c00532e0] (get_signal_to_deliver+0x0/0x33c) from [c0030fb8] (do_notify_resume+0x7c/0x638) [c0030f3c] (do_notify_resume+0x0/0x638) from [c002eb14] (work_pending+0x24/0x28) -- Tarun -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [OMAP 1710] Mainline Broken
Hi, On Thu, Dec 16, 2010 at 4:30 PM, DebBarma, Tarun Kanti tarun.ka...@ti.com wrote: Did anyone observe this? I am using omap_generic_1710_defconfig [...] input: omap-keypad as /devices/platform/omap-keypad/input/input0 TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type eth0: link up IP-Config: Complete: device=eth0, addr=172.24.191.106, mask=255.255.252.0, gw=172.24.188.1, host=myomap, domain=, nis-domain=(none), bootserver=172.24.191.66, rootserver=172.24.191.66, rootpath= VFS: Mounted root (nfs filesystem) on device 0:10. Freeing init memory: 128K Kernel panic - not syncing: Attempted to kill init! Seems your userspace is broken. Try add user_debug=31 to command line to see what exactly happens. Backtrace: [c0032104] (dump_backtrace+0x0/0x114) from [c027ecd4] (dump_stack+0x18/0x1c) r7:c0826000 r6:c0826000 r5:c0304ce8 r4:c0320254 [c027ecbc] (dump_stack+0x0/0x1c) from [c027ed38] (panic+0x60/0x188) [c027ecd8] (panic+0x0/0x188) from [c0047414] (do_exit+0x74/0x600) r3:6013 r2:c0826000 r1:c08260f8 r0:c02d6cff [c00473a0] (do_exit+0x0/0x600) from [c0047a38] (do_group_exit+0x98/0xcc) [c00479a0] (do_group_exit+0x0/0xcc) from [c00535e4] (get_signal_to_deliver+0x304/0x33c) r7:c08ba484 r6:c0828000 r5:c0829ee4 r4:0004 [c00532e0] (get_signal_to_deliver+0x0/0x33c) from [c0030fb8] (do_notify_resume+0x7c/0x638) [c0030f3c] (do_notify_resume+0x0/0x638) from [c002eb14] (work_pending+0x24/0x28) -- Tarun -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html thanks, marek -- as simple and primitive as possible - Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite icq: 290551086 web: http://open-nandra.com -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [OMAP 1710] Mainline Broken
Belisko Marek marek.beli...@gmail.com writes: Hi, On Thu, Dec 16, 2010 at 4:30 PM, DebBarma, Tarun Kanti tarun.ka...@ti.com wrote: Did anyone observe this? I am using omap_generic_1710_defconfig [...] input: omap-keypad as /devices/platform/omap-keypad/input/input0 TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type eth0: link up IP-Config: Complete: device=eth0, addr=172.24.191.106, mask=255.255.252.0, gw=172.24.188.1, host=myomap, domain=, nis-domain=(none), bootserver=172.24.191.66, rootserver=172.24.191.66, rootpath= VFS: Mounted root (nfs filesystem) on device 0:10. Freeing init memory: 128K Kernel panic - not syncing: Attempted to kill init! Seems your userspace is broken. Try add user_debug=31 to command line to see what exactly happens. Looks like you're mounting an NFS rootfs. Was it compiled for armv5? My hunch would be you're trying to run an armv6/armv7 userspace on the 1710 which is armv5. To get more debugging, ensure these are enabled in your defconfig: CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_USER=y CONFIG_DEBUG_ERRORS=y and in addition to cmdline suggested by Marek, add user_debug=0xf This will give verbose output for userspace exceptions as well and possibly confirm my hunch. Kevin -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
