[Buildroot] buildroot file system: Kernel panic

[Buildroot] buildroot file system: Kernel panic

[Rohit Kumar]

Hello,

i used buildroot to make toolchain and file system.
i used toolchain to compile the kernel source given by processor
manufacturer.
kernel compiled successfully and boots fine but the file system generated
by buildroot doesnt work.

and gives following error:

VFS: Mounted root (nfs filesystem) on device 0:13.
devtmpfs: mounted
Freeing init memory: 480K
Kernel panic - not syncing: Attempted to kill init!
[<c0086408>] (unwind_backtrace+0x0/0xcc) from [<c034af6c>]
(panic+0x54/0x11c)
[<c034af6c>] (panic+0x54/0x11c) from [<c00b2458>] (do_exit+0x5c/0x684)
[<c00b2458>] (do_exit+0x5c/0x684) from [<c00b2d98>]
(do_group_exit+0xac/0xf0)
[<c00b2d98>] (do_group_exit+0xac/0xf0) from [<c00bc130>]
(get_signal_to_deliver+0x3b8/0x410)
[<c00bc130>] (get_signal_to_deliver+0x3b8/0x410) from [<c0083434>]
(do_signal+0x5c/0x5e0)
[<c0083434>] (do_signal+0x5c/0x5e0) from [<c0083e98>]
(do_notify_resume+0x18/0x48)
[<c0083e98>] (do_notify_resume+0x18/0x48) from [<c0080d8c>]
(work_pending+0x1c/0x20)

i dont how to solve it.
file system given by processor manufacturer works fine.

-- 

With Regards,

Rohit Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140416/e9630955/attachment.html>

[Buildroot] buildroot file system: Kernel panic

[Thomas Petazzoni]

Dear Rohit Kumar,

On Wed, 16 Apr 2014 11:21:25 +0900, Rohit Kumar wrote:

> i used buildroot to make toolchain and file system.
> i used toolchain to compile the kernel source given by processor
> manufacturer.
> kernel compiled successfully and boots fine but the file system generated
> by buildroot doesnt work.
> 
> and gives following error:
> 
> VFS: Mounted root (nfs filesystem) on device 0:13.
> devtmpfs: mounted
> Freeing init memory: 480K
> Kernel panic - not syncing: Attempted to kill init!

Can you give us:

 * The platform you're using, so that we can figure out which processor
   it is using.

 * The Buildroot .config file you're using, to check that the
   configuration you've made matches the processor of your platform.

Most of the time, those errors are due to inadequate architecture
variant / floating point configuration.

Also, how did you prepare your NFS filesystem? By just copying
output/target, or by following the instructions at
http://buildroot.org/downloads/manual/manual.html#_nfs_boot ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] buildroot file system: Kernel panic

[Rohit Kumar]

** The platform you're using, so that we can figure out which processor
 it is using.*

i am using an ARM11 processor form Nexell (NXP2120)
32bit Embedded CPU : 700/800Mhz ARM1176 with
16KByte I-Cache, 16Kbyte D-cache with VFP(vector floating-point processor)


* * The Buildroot .config file you're using, to check that the
 configuration you've made matches the processor of your platform.*

please see the attached configuration.



*Also, how did you prepare your NFS filesystem? By just copying
output/target, or by following the instructions at
http://buildroot.org/downloads/manual/manual.html#_nfs_boot
<http://buildroot.org/downloads/manual/manual.html#_nfs_boot> ?*

i am following as mentioned in above manual.




On Wed, Apr 16, 2014 at 4:16 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Rohit Kumar,
>
> On Wed, 16 Apr 2014 11:21:25 +0900, Rohit Kumar wrote:
>
> > i used buildroot to make toolchain and file system.
> > i used toolchain to compile the kernel source given by processor
> > manufacturer.
> > kernel compiled successfully and boots fine but the file system generated
> > by buildroot doesnt work.
> >
> > and gives following error:
> >
> > VFS: Mounted root (nfs filesystem) on device 0:13.
> > devtmpfs: mounted
> > Freeing init memory: 480K
> > Kernel panic - not syncing: Attempted to kill init!
>
> Can you give us:
>
>  * The platform you're using, so that we can figure out which processor
>    it is using.
>
>  * The Buildroot .config file you're using, to check that the
>    configuration you've made matches the processor of your platform.
>
> Most of the time, those errors are due to inadequate architecture
> variant / floating point configuration.
>
> Also, how did you prepare your NFS filesystem? By just copying
> output/target, or by following the instructions at
> http://buildroot.org/downloads/manual/manual.html#_nfs_boot ?
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>



-- 

With Regards,

Rohit Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140416/8eefb781/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config
Type: application/octet-stream
Size: 39372 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140416/8eefb781/attachment-0001.obj>

[Buildroot] buildroot file system: Kernel panic

[Thomas Petazzoni]

Dear Rohit Kumar,

Would it be possible to avoid top posting, and instead use bottom
posting, as is the usage of most mailing lists? Thanks!

On Wed, 16 Apr 2014 16:31:13 +0900, Rohit Kumar wrote:
> ** The platform you're using, so that we can figure out which processor
>  it is using.*
> 
> i am using an ARM11 processor form Nexell (NXP2120)
> 32bit Embedded CPU : 700/800Mhz ARM1176 with
> 16KByte I-Cache, 16Kbyte D-cache with VFP(vector floating-point processor)

Ok.

> * * The Buildroot .config file you're using, to check that the
>  configuration you've made matches the processor of your platform.*
> 
> please see the attached configuration.

Your configuration indeed looks appropriate in terms of toolchain.

However, the kernel part of the configuration looks weird: it refers to
the kernel configuration file
board/atmel/at91sam9260ek/linux-3.9.config. Are you building a kernel
in Buildroot, but not using it for your platform?

Also, please enable CONFIG_DEBUG_USER=y in your kernel, and pass
user_debug=31 on your kernel command line. This should give more
details about the userspace crash.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] buildroot file system: Kernel panic

[Rohit Kumar]

On Wed, Apr 16, 2014 at 4:57 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Rohit Kumar,
>
> Would it be possible to avoid top posting, and instead use bottom
> posting, as is the usage of most mailing lists? Thanks!
>
> On Wed, 16 Apr 2014 16:31:13 +0900, Rohit Kumar wrote:
> > ** The platform you're using, so that we can figure out which processor
> >  it is using.*
> >
> > i am using an ARM11 processor form Nexell (NXP2120)
> > 32bit Embedded CPU : 700/800Mhz ARM1176 with
> > 16KByte I-Cache, 16Kbyte D-cache with VFP(vector floating-point
> processor)
>
> Ok.
>

 it is weird because when i use arm926t from the processor option, file
system works.
but as i shift to arm1176 it starts giving panic messages.

>
> > * * The Buildroot .config file you're using, to check that the
> >  configuration you've made matches the processor of your platform.*
> >
> > please see the attached configuration.
>
> Your configuration indeed looks appropriate in terms of toolchain.
>
> However, the kernel part of the configuration looks weird: it refers to
> the kernel configuration file
> board/atmel/at91sam9260ek/linux-3.9.config. Are you building a kernel
> in Buildroot, but not using it for your platform?
>

i am not using kernel from the buildroot rather compiling the source i have
with the toolchain generated.

>
> Also, please enable CONFIG_DEBUG_USER=y in your kernel, and pass
> user_debug=31 on your kernel command line. This should give more
> details about the userspace crash.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>



-- 

With Regards,

Rohit Kumar
Sr. Research Developer
Hitec Robotic systems Ltd.
+91 9891691967
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140416/1d35c93e/attachment.html>

[Buildroot] buildroot file system: Kernel panic

[Thomas Petazzoni]

Dear Rohit Kumar,

On Wed, 16 Apr 2014 17:12:01 +0900, Rohit Kumar wrote:

> > > i am using an ARM11 processor form Nexell (NXP2120)
> > > 32bit Embedded CPU : 700/800Mhz ARM1176 with
> > > 16KByte I-Cache, 16Kbyte D-cache with VFP(vector floating-point
> > processor)
> >
> > Ok.
> 
>  it is weird because when i use arm926t from the processor option, file
> system works.
> but as i shift to arm1176 it starts giving panic messages.

Ok, that is interesting. Did you compile your kernel with CONFIG_VFP=y ?

> > However, the kernel part of the configuration looks weird: it refers to
> > the kernel configuration file
> > board/atmel/at91sam9260ek/linux-3.9.config. Are you building a kernel
> > in Buildroot, but not using it for your platform?
> 
> i am not using kernel from the buildroot rather compiling the source i have
> with the toolchain generated.

Ok, but Buildroot is still building a kernel for you, so you're
spending time for nothing :)

> > Also, please enable CONFIG_DEBUG_USER=y in your kernel, and pass
> > user_debug=31 on your kernel command line. This should give more
> > details about the userspace crash.

Did you try this?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] buildroot file system: Kernel panic

[Rohit Kumar]

On Wed, Apr 16, 2014 at 5:39 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Rohit Kumar,
>
> On Wed, 16 Apr 2014 17:12:01 +0900, Rohit Kumar wrote:
>
> > > > i am using an ARM11 processor form Nexell (NXP2120)
> > > > 32bit Embedded CPU : 700/800Mhz ARM1176 with
> > > > 16KByte I-Cache, 16Kbyte D-cache with VFP(vector floating-point
> > > processor)
> > >
> > > Ok.
> >
> >  it is weird because when i use arm926t from the processor option, file
> > system works.
> > but as i shift to arm1176 it starts giving panic messages.
>
> Ok, that is interesting. Did you compile your kernel with CONFIG_VFP=y ?
>

Kernel has already CONFIG_VFP=y

>
> > > However, the kernel part of the configuration looks weird: it refers to
> > > the kernel configuration file
> > > board/atmel/at91sam9260ek/linux-3.9.config. Are you building a kernel
> > > in Buildroot, but not using it for your platform?
> >
> > i am not using kernel from the buildroot rather compiling the source i
> have
> > with the toolchain generated.
>
> Ok, but Buildroot is still building a kernel for you, so you're
> spending time for nothing :)
>
> you are right..disabled it :)


> > > Also, please enable CONFIG_DEBUG_USER=y in your kernel, and pass
> > > user_debug=31 on your kernel command line. This should give more
> > > details about the userspace crash.
>
> Did you try this?
>

tried as above:
Looking up port of RPC 100003/2 on 192.168.1.35
Looking up port of RPC 100005/1 on 192.168.1.35
VFS: Mounted root (nfs filesystem) on device 0:13.
devtmpfs: mounted
Freeing init memory: 480K
Kernel panic - not syncing: Attempted to kill init!
[<c00865bc>] (unwind_backtrace+0x0/0xcc) from [<c034b18c>]
(panic+0x54/0x11c)
[<c034b18c>] (panic+0x54/0x11c) from [<c00b2678>] (do_exit+0x5c/0x684)
[<c00b2678>] (do_exit+0x5c/0x684) from [<c00b2fb8>]
(do_group_exit+0xac/0xf0)
[<c00b2fb8>] (do_group_exit+0xac/0xf0) from [<c00bc350>]
(get_signal_to_deliver+0x3b8/0x410)
[<c00bc350>] (get_signal_to_deliver+0x3b8/0x410) from [<c0083494>]
(do_signal+0x5c/0x5e0)
[<c0083494>] (do_signal+0x5c/0x5e0) from [<c0083ef8>]
(do_notify_resume+0x18/0x48)
[<c0083ef8>] (do_notify_resume+0x18/0x48) from [<c0080dec>]
(work_pending+0x1c/0x20)

user
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>



-- 

With Regards,

Rohit Kumar
Sr. Research Developer
Hitec Robotic systems Ltd.
+91 9891691967
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140416/ffb886e8/attachment.html>

[Buildroot] buildroot file system: Kernel panic

[Rohit Kumar]

Hello Thomas,

out of all this i figured out that file system works with cpu
subarchitecture of "armv6j" and not "armv6zk" which is ARM1176jzf-s
so how to get file system working with armv6zk?
am i missing some configuration in buildroot so when i use the generated
toolchain to compile the kernel, it is creating problem by not accessing
file system properly?


On Wed, Apr 16, 2014 at 6:05 PM, Rohit Kumar <
rohit.kumar@hitechroboticsystemz.com> wrote:

>
>
>
> On Wed, Apr 16, 2014 at 5:39 PM, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
>
>> Dear Rohit Kumar,
>>
>> On Wed, 16 Apr 2014 17:12:01 +0900, Rohit Kumar wrote:
>>
>> > > > i am using an ARM11 processor form Nexell (NXP2120)
>> > > > 32bit Embedded CPU : 700/800Mhz ARM1176 with
>> > > > 16KByte I-Cache, 16Kbyte D-cache with VFP(vector floating-point
>> > > processor)
>> > >
>> > > Ok.
>> >
>> >  it is weird because when i use arm926t from the processor option, file
>> > system works.
>> > but as i shift to arm1176 it starts giving panic messages.
>>
>> Ok, that is interesting. Did you compile your kernel with CONFIG_VFP=y ?
>>
>
> Kernel has already CONFIG_VFP=y
>
>>
>> > > However, the kernel part of the configuration looks weird: it refers
>> to
>> > > the kernel configuration file
>> > > board/atmel/at91sam9260ek/linux-3.9.config. Are you building a kernel
>> > > in Buildroot, but not using it for your platform?
>> >
>> > i am not using kernel from the buildroot rather compiling the source i
>> have
>> > with the toolchain generated.
>>
>> Ok, but Buildroot is still building a kernel for you, so you're
>> spending time for nothing :)
>>
>> you are right..disabled it :)
>
>
>> > > Also, please enable CONFIG_DEBUG_USER=y in your kernel, and pass
>> > > user_debug=31 on your kernel command line. This should give more
>> > > details about the userspace crash.
>>
>> Did you try this?
>>
>
> tried as above:
> Looking up port of RPC 100003/2 on 192.168.1.35
> Looking up port of RPC 100005/1 on 192.168.1.35
>
> VFS: Mounted root (nfs filesystem) on device 0:13.
> devtmpfs: mounted
> Freeing init memory: 480K
> Kernel panic - not syncing: Attempted to kill init!
> [<c00865bc>] (unwind_backtrace+0x0/0xcc) from [<c034b18c>]
> (panic+0x54/0x11c)
> [<c034b18c>] (panic+0x54/0x11c) from [<c00b2678>] (do_exit+0x5c/0x684)
> [<c00b2678>] (do_exit+0x5c/0x684) from [<c00b2fb8>]
> (do_group_exit+0xac/0xf0)
> [<c00b2fb8>] (do_group_exit+0xac/0xf0) from [<c00bc350>]
> (get_signal_to_deliver+0x3b8/0x410)
> [<c00bc350>] (get_signal_to_deliver+0x3b8/0x410) from [<c0083494>]
> (do_signal+0x5c/0x5e0)
> [<c0083494>] (do_signal+0x5c/0x5e0) from [<c0083ef8>]
> (do_notify_resume+0x18/0x48)
> [<c0083ef8>] (do_notify_resume+0x18/0x48) from [<c0080dec>]
> (work_pending+0x1c/0x20)
>
> user
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Free Electrons
>> Embedded Linux, Kernel and Android engineering
>> http://free-electrons.com
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>
>
>
> --
>
> With Regards,
>
> Rohit Kumar
> Sr. Research Developer
> Hitec Robotic systems Ltd.
> +91 9891691967
>



-- 

With Regards,

Rohit Kumar
Sr. Research Developer
Hitec Robotic systems Ltd.
+91 9891691967
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140417/d14f6900/attachment.html>

[Buildroot] buildroot file system: Kernel panic

[Thomas Petazzoni]

Dear Rohit Kumar,

On Thu, 17 Apr 2014 16:59:03 +0900, Rohit Kumar wrote:

> out of all this i figured out that file system works with cpu
> subarchitecture of "armv6j" and not "armv6zk" which is ARM1176jzf-s

Now that you have a booting system, can you show the output of
"cat /proc/cpuinfo" ? It will help understand exactly which variant of
ARM core your processor is using.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] buildroot file system: Kernel panic

[Rohit Kumar]

Hello Thomas,


On Thu, Apr 17, 2014 at 7:01 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Rohit Kumar,
>
> On Thu, 17 Apr 2014 16:59:03 +0900, Rohit Kumar wrote:
>
> > out of all this i figured out that file system works with cpu
> > subarchitecture of "armv6j" and not "armv6zk" which is ARM1176jzf-s
>
> Now that you have a booting system, can you show the output of
> "cat /proc/cpuinfo" ? It will help understand exactly which variant of
> ARM core your processor is using.
>

output of /proc/cpuinfo:
# cat /proc/cpuinfo
Processor       : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS        : 699.59
Features        : swp half thumb fastmult vfp edsp java
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb76
CPU revision    : 7

Hardware        : nxp2120
Revision        : 0000
Serial          : 0000000000000000



>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>



-- 

With Regards,

Rohit Kumar
Sr. Research Developer
Hitec Robotic systems Ltd.
+91 9891691967
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140418/2687965a/attachment.html>