Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel Panic with BB Black + buildroot-2016.11.1
Date: Wed, 04 Jan 2017 17:39:40 +0100	[thread overview]
Message-ID: <87bmvm2303.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1483536685380-153942.post@n4.nabble.com> (Ashish Kumar Mishra's message of "Wed, 4 Jan 2017 05:31:25 -0800 (PST)")

>>>>> "Ashish" == Ashish Kumar Mishra <dgashu55@gmail.com> writes:

 > Hi All , 
 > I updated my build root  setup from buildroot-2016.05 to buildroot-2016.11.1
 > . 
 > I was having an working build with buildroot-2016.05. 
 > Could team members provide some pointers as to how could i debug & figure
 > the cause of this panic. 
 > *The defconfig is :*-
 > ~/my_virtual_project/release_branch_v2 :: cat defconfig 
 > BR2_arm=y
 > BR2_cortex_a8=y
 > BR2_TOOLCHAIN_EXTERNAL=y
 > BR2_LINUX_KERNEL=y
 > BR2_LINUX_KERNEL_DEFCONFIG="omap2plus"
 > BR2_LINUX_KERNEL_DTS_SUPPORT=y
 > BR2_LINUX_KERNEL_INTREE_DTS_NAME="am335x-boneblack"
 > BR2_TARGET_UBOOT=y
 > BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 > BR2_TARGET_UBOOT_BOARD_DEFCONFIG="am335x_boneblack"
 > # BR2_TARGET_UBOOT_FORMAT_BIN is not set
 > BR2_TARGET_UBOOT_FORMAT_IMG=y
 > BR2_TARGET_UBOOT_SPL=y
 > BR2_TARGET_UBOOT_SPL_NAME="MLO"


So how do you create your rootfs and filesystem image?

Does it work if you instead build out beaglebone_defconfig? (E.G. make
clean; make beaglebone_defconfig; make)

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-01-04 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 13:31 [Buildroot] Kernel Panic with BB Black + buildroot-2016.11.1 Ashish_Kumar_Mishra
2017-01-04 16:39 ` Peter Korsgaard [this message]
2017-01-05  5:13   ` Ashish_Kumar_Mishra
2017-01-05  8:34     ` Ashish_Kumar_Mishra

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=87bmvm2303.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox