[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[microblaze-uclinux] Re: BUG: scheduling while atomic
- To: microblaze-uclinux@xxxxxxxxxxxxxx
- Subject: [microblaze-uclinux] Re: BUG: scheduling while atomic
- From: "Victor G." <vga9@xxxxxx>
- Date: Sun, 2 Aug 2009 01:40:43 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=/I7F+7b16/BlRXiBPgCep7bPUGdMvcgyfy13QuvUaXg=; b=ZLfnl3llavwJv9qgqcqndXjOTMtgsRC+z6WvtemHMOZJ8ib4Ftycx8E2Ketf5NCsMB 3eU+byARVwShOqNumqzkueBdxdgcTZ0twF0Qb8ejXyBQwpcQt5AnPC7jIfdbfu59Zcee KYTYTKVhnszcXG8KHtntS4YpAyoeHC+xl0Y9o=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=slDwjGFkaZRHEAa8cFptHcznaxmjc5JjsT5ACZzAGtjLzjxQeBL2cJsgPEcVyd53n7 /BBfM4KFv7KV5HFbfBwynR3ke7VRc4jjjEaPTeuVn2kPTSUXjZQblObD2pyi56w1j0Hu WoRosV6vScn3eU8/2sxYN2ewE05Nb4OaDDPww=
- In-reply-to: <7b24affd0908010155y9a6a90ep30b79b4ef2c40dc7@xxxxxxxxxxxxxx>
- References: <7b24affd0908010155y9a6a90ep30b79b4ef2c40dc7@xxxxxxxxxxxxxx>
- Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
- Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxxxxxxxx
On Sat, Aug 1, 2009 at 1:55 AM, Victor G.<vga9@xxxxxx> wrote:
> Hi,
>
> My boot procedure is stuck before mounting partitions and displays the
> error found at the end of the following kernel's printing to uart. The
> system is ML505, build from scratch in 11.1, is similar to the
> provided non-MMU example in 10.1 but does not have additional
> peripherals like Ethernet controller. Both caches are enabled. Could
> these be some stack size issues?
>
> ...
> uartlite.0: ttyUL0 at MMIO 0x84020000 (irq = 2) is a uartlite
> uartlite.1: ttyUL1 at MMIO 0x84000000 (irq = 0) is a uartlite
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> uclinux[mtd]: RAM probe address=0x501c885c size=0xef000
> Creating 1 MTD partitions on "RAM":
> 0x00000000-0x000ef000 : "ROMfs"
> uclinux[mtd]: set ROMfs to be root filesystem index=0
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> VFS: Mounted root (cramfs filesystem) readonly.
> Freeing unused kernel memory: 84k freed
> BUG: scheduling while atomic: /0xb8083fb0/3261
>
> Stack:
> 00001f10 00000001 00000000 00000000 00000000 500040e4 50170f94 5ffe8da0
> b8083fb0 00000cbd 885bb200 00001e78 b0005008 00000013 00000010 5fe9ff21
> 00000001 00000000 00000000 00000000 00000000 00000000 00000000 5fe9fe74
> Call Trace: [<500040e4>]
>
>
> Here is the petalinux-send-config otuput.
> ----
> #SYSTEM CONFIGS
> CONFIG_DEFAULTS_XILINX=y
> CONFIG_DEFAULTS_XILINX_XILINX_ML505_TEST_11_1=y
> CONFIG_DEFAULTS_KERNEL_2_6=y
> CONFIG_DEFAULTS_LIBC_NONE=y
> CONFIG_VENDOR=Xilinx
> CONFIG_PRODUCT=Xilinx-ML505-test_11.1
> CONFIG_LINUXDIR=linux-2.6.x
> CONFIG_LIBCDIR=
>
> ... etc
Looking at http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2007/07/msg00043.html,
I have tried enabling kernel preemption, but still see the "BUG:
scheduling while atomic" error. I am using nonMMU kernel.
The config file now has the following line:
CONFIG_PREEMPT=y
Following the thread further I found that two other patches helped
solving the problem. That was July 2007.
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2007/07/msg00137.html
Have these patches being applied in the latest petalinux-v0.40-rc4 release?
I will have to read about git to understand its history syntax and
usage. For now it looks like the current files in my kernel directory
are different from what the patch is suggesting.
Thanks,
Victor
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/