From: Mulyadi Santosa <a_mulyadi@telkom.net>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>, Sonny Rao <sonny@burdell.org>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [patch] Re: [uml-devel] Kallsyms on UML
Date: Mon, 26 Jul 2004 21:40:50 +0700 [thread overview]
Message-ID: <200407262140.50298.a_mulyadi@telkom.net> (raw)
In-Reply-To: <200407261618.33778.blaisorblade_spam@yahoo.it>
hello
> Yes, exactly. (It is not matter of EXPORT_SYMBOL, you're right).
Thanks for correcting me :-)
BTW, why vmlinux might miss the stack trace? is it just because it missed
kallsysms?
> However, on any 2.6 UML, run cat /dev/kmem (which will panic, the fix is
> known but yet to submit) and say if you can get the stacktrace. For some
> reason, I cannot (even if dump_stack() is invoked); nothing is printed.
> Seems like the printk() are lost (maybe some tricks with bust_spinlock()
> are needed).
BTW, interesting to read tricks to beat lost printk, Paolo....can you share
your trick to defeat it? Just using bust_spinlock? or....just crazy
idea...force console/tty flush?
regards
Mulyadi
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&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 prev parent reply other threads:[~2004-07-26 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 0:27 [uml-devel] Kallsyms on UML Sonny Rao
2004-07-26 3:57 ` Mulyadi-Santosa
2004-07-26 6:01 ` Sonny Rao
2004-07-26 13:45 ` Mulyadi Santosa
2004-07-26 14:18 ` [patch] " BlaisorBlade
2004-07-26 14:40 ` Mulyadi Santosa [this message]
2004-07-26 14:54 ` 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=200407262140.50298.a_mulyadi@telkom.net \
--to=a_mulyadi@telkom.net \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=sonny@burdell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.