From: "Stian Skjelstad" <stian@nixia.no>
To: Richard Weinberger <richard@nod.at>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] UML: Please help with __module_text_address crashing
Date: Wed, 14 Mar 2012 08:28:59 +0100 [thread overview]
Message-ID: <3c4d14d64492ddd8be406d4a15f1ee63.squirrel@nlc.no> (raw)
In-Reply-To: <4F5FDF42.90004@nod.at>
> Am 13.03.2012 23:38, schrieb Boaz Harrosh:
>> Since a while now my UMLs are constantly crashing in
>> __module_text_address
>>
>> which makes no sense because if I do gdb> list
>> *(__module_text_address+0xd)
>> I get:t
>>
>> 0x6005614e is in __module_text_address
>> (/media/usr0/export/dev/bharrosh/git/pub/linux-open-osd/kernel/module.c:3469).
>> 3464 * module doesn't get freed during this.
>> 3465 */
>> 3466 struct module *__module_text_address(unsigned long addr)
>> 3467 {
>> 3468 struct module *mod = __module_address(addr);
>> 3469 if (mod) {
>> 3470 /* Make sure it's within the text section. */
>> 3471 if (!within(addr, mod->module_init,
>> mod->init_text_size)
>> 3472&& !within(addr, mod->module_core, mod->core_text_size))
>> 3473 mod = NULL;
source listing vs where it crashes can be off aslong as you use CFLAGS
with -On where n is greater than 0. So the first thing you can test is to
compile UML with CFLAGS="-g -O0". It might be that it doesn't crash
anymore then, if so, you can try to play with different gcc optimization
flags in order to find out what triggers it.
Other sources of the crash can be gcc bugs, or some special CPU
optimization BUG (either in gcc or the UML source).
Your backtrace also included spin-lock right before the panic, which could
be the source of the issue. If I remember right, the kernel has some debug
options that can be enabled for spin-locks.
Stian Skjelstad
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2012-03-14 7:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 22:38 [uml-devel] UML: Please help with __module_text_address crashing Boaz Harrosh
2012-03-13 23:58 ` Richard Weinberger
2012-03-14 0:15 ` Boaz Harrosh
2012-03-14 0:22 ` Richard Weinberger
2012-03-14 0:51 ` Boaz Harrosh
2012-03-14 8:23 ` Richard Weinberger
2012-03-14 22:28 ` Boaz Harrosh
2012-03-14 22:40 ` Richard Weinberger
2012-05-25 7:35 ` Boaz Harrosh
2012-05-25 7:40 ` Richard RW. Weinberger
2012-05-25 9:19 ` Boaz Harrosh
2012-05-25 9:26 ` Richard Weinberger
2012-03-14 7:28 ` Stian Skjelstad [this message]
2012-03-14 8:44 ` Richard Weinberger
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=3c4d14d64492ddd8be406d4a15f1ee63.squirrel@nlc.no \
--to=stian@nixia.no \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.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