linux-um archives
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
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: Tue, 13 Mar 2012 17:51:44 -0700	[thread overview]
Message-ID: <4F5FEBA0.5010905@panasas.com> (raw)
In-Reply-To: <4F5FE4B8.4020006@nod.at>

On 03/13/2012 05:22 PM, Richard Weinberger wrote:
> Am 14.03.2012 01:15, schrieb Boaz Harrosh:
>> I guess if you don't have it then you don't. The most reliable way for me to get
>> it is a simple "halt". I'm not able to ever shut down properly it reliably crashes
>> like:
>>
>> Kernel panic - not syncing: Kernel mode fault at addr 0x54, ip 0x6015c233
> 
> What is at addr 0x6015c233?
> "addr2line -e vmlinux 0x6015c233" shows it.
> 

linux-open-osd/arch/um/drivers/line.c:46


> Does it also happen with a vanilla kernel?
> 

Yes, you mean git checkout v3.2 Yes it's the same all the way back to 2.6.39 or so

I just did that I get the same as above: addr2line -e .build_um/vmlinux 0x600179b8
linux-open-osd/arch/um/drivers/line.c:46

>>
>> OK then I have a problem because I get the "access not permitted" on attaching to any of these
>> forks but the top most parent. (as sudo)
> 
> You cannot attach to them because they are already being ptrace()'ed by 
> the UML main thread.

right that what I thought.
so if I make a break point that happened in another fork will it trigger still? I guess
yes. But if anything goes wrong in any of the other forks, is there a way for me to break
that fork into the debugger and see what happened like a bt? 

My current theory is that Fedora became UML unfriendly is there some random-exec-mem thingy
I need to turn off?

> 
> Thanks,
> //richard

Thanks richard for your help
Boaz

------------------------------------------------------------------------------
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


  reply	other threads:[~2012-03-14  0:51 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 [this message]
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
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=4F5FEBA0.5010905@panasas.com \
    --to=bharrosh@panasas.com \
    --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