From: Jeff Dike <jdike@addtoit.com>
To: Anthony Brock <Anthony_Brock@ous.edu>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Recent patches of note
Date: Mon, 20 Jun 2005 10:47:47 -0400 [thread overview]
Message-ID: <20050620144747.GA5530@ccure.user-mode-linux.org> (raw)
In-Reply-To: <s2b1a1ed.010@ORANGE.OUS.EDU>
On Thu, Jun 16, 2005 at 03:59:24PM -0700, Anthony Brock wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x080b86d0 in __vmalloc_area (area=0xbd15be0, gfp_mask=210, prot={pgprot = 0}) at string.h:363
Segfaults in vmalloc are completely normal. They are just page faults.
> BUG: soft lockup detected on CPU#0!
The soft lockups should be fixed by the sched-starve patch. This one is
likely caused by you sitting in the debugger.
If you do see any that don't involve gdb, and you have sched-starve applied,
let me know.
Jeff
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next parent reply other threads:[~2005-06-20 14:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s2b1a1ed.010@ORANGE.OUS.EDU>
2005-06-20 14:47 ` Jeff Dike [this message]
[not found] <s2b6982e.048@ORANGE.OUS.EDU>
2005-06-20 20:11 ` [uml-devel] Recent patches of note Jeff Dike
[not found] <s2b19c99.097@ORANGE.OUS.EDU>
2005-06-20 14:53 ` Jeff Dike
2005-06-20 17:59 ` William Stearns
2005-06-20 21:31 ` Blaisorblade
2005-06-16 22:59 Anthony Brock
[not found] <s2b18c1b.063@ORANGE.OUS.EDU>
2005-06-16 22:13 ` Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2005-06-16 16:07 Jeff Dike
2005-06-16 17:36 ` Bodo Stroesser
2005-06-16 17:47 ` Jeff Dike
2005-06-16 17:55 ` Bodo Stroesser
2005-06-16 18:02 ` Bodo Stroesser
2005-06-16 18:09 ` Blaisorblade
2005-06-16 18:31 ` Bodo Stroesser
2005-06-16 18:41 ` Blaisorblade
2005-06-16 18:40 ` Bodo Stroesser
2005-06-16 18:51 ` Blaisorblade
2005-06-16 22:23 ` Jeff Dike
2005-06-17 9:09 ` Bodo Stroesser
2005-06-17 18:36 ` Blaisorblade
2005-06-17 0:35 ` Jeff Dike
2005-06-17 18:40 ` Blaisorblade
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=20050620144747.GA5530@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=Anthony_Brock@ous.edu \
--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;
as well as URLs for NNTP newsgroup(s).