From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: geting weird semi-random panic on kmalloc
Date: Fri, 22 Jun 2012 23:18:05 +0700 [thread overview]
Message-ID: <CAGdaada+tBK9mH7L+vOxYmZvpsR+cvUL_pE7ZWgcjLxa66HEiA@mail.gmail.com> (raw)
In-Reply-To: <CA+wR77rXxHwJ7dH_MHVg-p+mZhG7vGAyZA8sdePstv4333d9Dg@mail.gmail.com>
Hi...
On Fri, Jun 22, 2012 at 7:50 AM, NorthPole <morfeas3000@gmail.com> wrote:
> 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
> 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 prev parent reply other threads:[~2012-06-22 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 0:50 geting weird semi-random panic on kmalloc NorthPole
2012-06-22 11:55 ` Jonathan Neuschäfer
2012-06-22 12:06 ` NorthPole
2012-06-22 16:18 ` Mulyadi Santosa [this message]
2012-06-22 16:27 ` NorthPole
2012-06-22 16:49 ` Mulyadi Santosa
2012-06-25 23:22 ` NorthPole
2012-06-26 4:31 ` Mulyadi Santosa
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=CAGdaada+tBK9mH7L+vOxYmZvpsR+cvUL_pE7ZWgcjLxa66HEiA@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).