From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: How to display dom0 kernel printk on hvc0 Date: Thu, 7 Aug 2014 16:01:16 +0100 Message-ID: <53E394BC.5000506@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFPCO-0005VT-00 for xen-devel@lists.xenproject.org; Thu, 07 Aug 2014 15:01:48 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini , manish jaggi Cc: Ian Campbell , Vijay Kilari , manish.jaggi@caviumnetworks.com, Julien Grall , stefano.stabellini@citrix.com, xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org 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 >> >> [] clear_bit+0x14/0x30 >> [] ack_dynirq+0x44/0x58 >> [] handle_edge_irq+0x74/0x178 >> [] evtchn_fifo_handle_events+0x280/0x288 >> [] __xen_evtchn_do_upcall+0x68/0xd0 >> [] xen_hvm_evtchn_do_upcall+0x8/0x18 >> [] xen_arm_callback+0x4c/0x68 >> [] handle_percpu_devid_irq+0x88/0x120 >> [] generic_handle_irq+0x24/0x40 >> [] handle_IRQ+0x40/0xa8 >> [] 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