From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
manish jaggi <manishjaggi.oss@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Vijay Kilari <vijay.kilari@gmail.com>,
manish.jaggi@caviumnetworks.com,
Julien Grall <julien.grall@citrix.com>,
stefano.stabellini@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: How to display dom0 kernel printk on hvc0
Date: Thu, 7 Aug 2014 16:01:16 +0100 [thread overview]
Message-ID: <53E394BC.5000506@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1408071535580.2293@kaball.uk.xensource.com>
On 07/08/14 15:36, Stefano Stabellini wrote:
> On Thu, 7 Aug 2014, manish jaggi wrote:
>> Thanks,
>> I manged to do something similar in the meantime. I am seeing a crash after I do /etc/init.d/xencommns start
>>
>> [<ffffffc00038fee4>] clear_bit+0x14/0x30
>> [<ffffffc0003d9ca4>] ack_dynirq+0x44/0x58
>> [<ffffffc0000e6a34>] handle_edge_irq+0x74/0x178
>> [<ffffffc0003dc0e8>] evtchn_fifo_handle_events+0x280/0x288
>> [<ffffffc0003d8f50>] __xen_evtchn_do_upcall+0x68/0xd0
>> [<ffffffc0003d8fc0>] xen_hvm_evtchn_do_upcall+0x8/0x18
>> [<ffffffc00009271c>] xen_arm_callback+0x4c/0x68
>> [<ffffffc0000e7560>] handle_percpu_devid_irq+0x88/0x120
>> [<ffffffc0000e38b4>] generic_handle_irq+0x24/0x40
>> [<ffffffc000084890>] handle_IRQ+0x40/0xa8
>> [<ffffffc000081348>] gic_handle_irq+0x50/0xa0
>>
>> I found that consume_one_event calls handle_irq_for_port which gets IRQ=7 in case of a crash.
>> What is the use of IRQ 7 ?
>> IRQ1 is UART which i saw in cat /proc/interrupts
>
> What kernel version are you using?
On arm64, 3.14 was buggy. This was fixed in 3.15-rc6.
>
> It looks like the FIFO event channel is not properly initialized.
> You could try switching to the old style 2-level ABI:
There's a kernel command line options for this: xen.fifo_events=0
David
next prev parent reply other threads:[~2014-08-07 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 8:23 How to display dom0 kernel printk on hvc0 manish jaggi
2014-08-07 12:44 ` 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 [this message]
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=53E394BC.5000506@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=manish.jaggi@caviumnetworks.com \
--cc=manishjaggi.oss@gmail.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.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).