Thread (8 messages) 8 messages, 3 authors, 2012-06-26

geting weird semi-random panic on kmalloc

From: NorthPole <hidden>
Date: 2012-06-22 16:27:52

Hi...

The virtual machine is supposed to run on 128 mb ram and according to the
batman folks its more than enough

How can I force a backtrace?

(kfree is supposed to be called on the list after the desired number of
nodes is  allocated but it never gets there )

On Fri, Jun 22, 2012 at 7:18 PM, Mulyadi Santosa
[off-list ref]wrote:
Hi...

On Fri, Jun 22, 2012 at 7:50 AM, NorthPole [off-list ref] wrote:
quoted
when I run the kernel code on an open-wrt build for x86 which is run
virtualized under a standard qemu running on debian squeeze produces this
output
http://pastebin.com/tY3Vkzvw
(in short it prints everything as its supposed to do for a random number
of
quoted
iterations between 3 and 24 and the the kernel oops happens)
I have no idea on what kind of modification openwrt folks do on top of
Linux kernel, but there is a chance the kernel space smaller or change
the way slab/slub/slob allocator works. In essence, the crash might
happen due to memory shortage or something like that.

Can you force a backtrace?

PS: I see no kfree() on the pastebin, is that true?

--
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120622/34d7cf4e/attachment.html 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help