From: Nix <nix@esperi.org.uk>
To: "Bram Matthys (Syzop)" <syzop@vulnscan.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] umls unresponsive & consuming 100% cpu time
Date: Wed, 07 May 2008 21:23:58 +0100 [thread overview]
Message-ID: <87hcd97ti9.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <4821B5FC.40307@vulnscan.org> (Bram Matthys's message of "Wed, 07 May 2008 16:00:28 +0200")
On 7 May 2008, Bram Matthys said:
> Or any help on how to get additional / useful info?
Set
CONFIG_DEBUG_INFO=y
CONFIG_FRAME_POINTER=y
in your kernel, and recompile. `bt' will then show heaps more info.
--
`If you are having a "ua luea luea le ua le" kind of day, I can only
assume that you are doing no work due [to] incapacitating nausea caused
by numerous lazy demons.' --- Frossie
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
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:[~2008-05-07 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 14:00 [uml-devel] umls unresponsive & consuming 100% cpu time Bram Matthys (Syzop)
2008-05-07 20:23 ` Nix [this message]
2008-05-08 10:02 ` [SPAM] " Bram Matthys (Syzop)
2008-05-09 15:45 ` Jeff Dike
2008-05-10 8:41 ` [SPAM] " Bram Matthys (Syzop)
2008-05-13 15:40 ` Jeff Dike
2008-05-14 8:41 ` Sakari Ailus
2008-05-19 16:16 ` Jeff Dike
2008-05-31 9:16 ` Bram Matthys (Syzop)
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=87hcd97ti9.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=syzop@vulnscan.org \
--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