Re: [OMAP 1710] Mainline Broken

[Kevin Hilman <khilman@deeprootsystems.com>]

"DebBarma, Tarun Kanti" <tarun.kanti@ti.com> writes:

>> -----Original Message-----
>> From: Kevin Hilman [mailto:khilman@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.belisko@gmail.com> writes:
>> 
>> > Hi,
>> >
>> > On Thu, Dec 16, 2010 at 4:30 PM, DebBarma, Tarun Kanti
>> > <tarun.kanti@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 00000000.
> Code: e08f1001 e1a0c000 e3a0702d ef000000 (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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html