xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: manish jaggi <manishjaggi.oss@gmail.com>
To: stefano.stabellini@citrix.com, xen-devel@lists.xenproject.org,
	Vijay Kilari <vijay.kilari@gmail.com>,
	manish.jaggi@caviumnetworks.com
Subject: How to display dom0 kernel printk on hvc0
Date: Thu, 7 Aug 2014 13:53:37 +0530	[thread overview]
Message-ID: <CAAiw7Jng4EpmUaJrSu1Go8ffEnkAUU6Mqk63rQFENTwuPEryGw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 470 bytes --]

Hi Stefano,

I am debugging a kernel crash when I start xencommons. If I add prints in
kernel the prints are only visible in dmesg and not on dom0 console. This
makes it difficult to view kernel printks at the time of crash.

I tried xen_raw_printks but the print only comes when you press a key, so
while a crash is happening you cannot press a key.

Is there a way to enable printks on hvc0
OR
is there a way to dump __logbuf of linux from xen shell.

-Regards
Manish

[-- Attachment #1.2: Type: text/html, Size: 639 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2014-08-07  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07  8:23 manish jaggi [this message]
2014-08-07 12:44 ` How to display dom0 kernel printk on hvc0 Stefano Stabellini
2014-08-07 13:01   ` manish jaggi
2014-08-07 14:36     ` Stefano Stabellini
2014-08-07 14:52       ` Julien Grall
2014-08-07 15:01       ` David Vrabel
2014-08-07 15:43         ` manish jaggi
2014-08-07 14:05 ` Julien Grall

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=CAAiw7Jng4EpmUaJrSu1Go8ffEnkAUU6Mqk63rQFENTwuPEryGw@mail.gmail.com \
    --to=manishjaggi.oss@gmail.com \
    --cc=manish.jaggi@caviumnetworks.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=vijay.kilari@gmail.com \
    --cc=xen-devel@lists.xenproject.org \
    /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).