From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot file system: Kernel panic
Date: Wed, 16 Apr 2014 10:39:24 +0200 [thread overview]
Message-ID: <20140416103924.64cdc49f@skate> (raw)
In-Reply-To: <CABzetm2VtaC-B4tv+2N9qpD-1anG7FkcgGnbV+fcimRCnCLzFQ@mail.gmail.com>
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
next prev parent reply other threads:[~2014-04-16 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 2:21 [Buildroot] buildroot file system: Kernel panic Rohit Kumar
2014-04-16 7:16 ` Thomas Petazzoni
2014-04-16 7:31 ` Rohit Kumar
2014-04-16 7:57 ` Thomas Petazzoni
2014-04-16 8:12 ` Rohit Kumar
2014-04-16 8:39 ` Thomas Petazzoni [this message]
2014-04-16 9:05 ` Rohit Kumar
2014-04-17 7:59 ` Rohit Kumar
2014-04-17 10:01 ` Thomas Petazzoni
2014-04-18 0:36 ` Rohit Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140416103924.64cdc49f@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.