From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Vrabel <david.vrabel@citrix.com>
Subject: Re: xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B,
 I/O virt. enabled, start vm -> Kernel panic
Date: Tue, 20 May 2014 17:20:10 +0100
Message-ID: <537B80BA.5070806@citrix.com>
References: <20140517174642.GA26466@white.maniscorse>	<537B2B06.7080102@citrix.com>
	<1400581122.28239.7.camel@kazak.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1400581122.28239.7.camel@kazak.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>, David Vrabel <david.vrabel@citrix.com>
Cc: Jo Mills <jo@maniscorse.co.uk>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On 20/05/14 11:18, Ian Campbell wrote:
> On Tue, 2014-05-20 at 11:14 +0100, David Vrabel wrote:
>> On 17/05/14 18:46, Jo Mills wrote:
>>>
>>>     [  498.336430] ---[ end trace b9630577ecf84cd8 ]---
>>>     [  498.340053] Kernel panic - not syncing: Fatal exception in interrupt
>>>     (XEN) Domain 0 crashed: 'noreboot' set - not rebooting.
>>
>> We need the full backtrace from the kernel.
> 
> It was in the attached serial console log. I've pasted what I think is
> the relevant bit below.

Ah. I hadn't noticed the attachment.

> [  485.048066] d-con vm-13-disk2: PingAck did not arrive in time.
> [  486.876191] e1000 0000:04:02.0 eth2: Detected Tx Unit Hang
> [  486.876191]   Tx Queue             <0>
> [  486.876191]   TDH                  <a5>
> [  486.876191]   TDT                  <b5>
> [  486.876191]   next_to_use          <b5>
> [  486.876191]   next_to_clean        <a5>
> [  486.876191] buffer_info[next_to_clean]
> [  486.876191]   time_stamp           <10000b439>
> [  486.876191]   next_to_watch        <a6>
> [  486.876191]   jiffies              <10000b67f>
> [  486.876191]   next_to_watch.status <0>

This looks like an e1000 driver/hardware problem.  It doesn't
immediately look Xen specific.

David