Re: [Xen-devel] xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B, I/O virt. enabled, start vm -> Kernel panic

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Thu, May 22, 2014 at 11:03:27AM +0100, Jo Mills wrote:
> On Thu, May 22, 2014 at 05:47:45AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Wed, May 21, 2014 at 10:42:30AM +0100, David Vrabel wrote:
> > > On 20/05/14 19:41, Jo Mills wrote:
> > > > On Tue, May 20, 2014 at 05:20:10PM +0100, David Vrabel wrote:
> > > >> 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
> > > > 
> > > > Hi David et al,
> > > > 
> > > > Many thanks for your replies and for your time spent looking into this 
> > > > problem.  
> > > > 
> > > > I probably should have mentioned in my report that when BIOS settings:
> > > > 
> > > >     Intel(R) Virtualization Technology
> > > >     Intel(R) VT for Directed I/O
> > > >     
> > > > are enabled, creating VMs that do not use a pci passthrough device 
> > > > works just fine.  It's only when I try and create a VM that does use a 
> > > > pci passthrough device that the crash happens.  Whether this is 
> > > > relevant or not I'm not competent enough to say.
> > > 
> > > It's not obviously related since it's a device/driver in dom0 that's
> > > broken.  I would suggest asking the e1000 maintainers if the Tx Unit
> > > Hang debug output hints at anything.
> > 
> > Lets CC them.
> > 
> > The thread is also available at:
> > http://lists.xen.org/archives/html/xen-devel/2014-05/msg02259.html
> > 
> > Thank you!
> 
> 
> Hi Konrad et al,

Hey!
> 
> I mailed e1000-devel@xxxxxxxxxxxxxxxxxxxxx last night:
> 
>     Date: Wed, 21 May 2014 21:18:26 +0100
>     To: e1000-devel <e1000-devel@xxxxxxxxxxxxxxxxxxxxx>
>     User-Agent: Mutt/1.5.21 (2010-09-15)
>     From: Jo Mills <jo@xxxxxxxxxxxxxxxx>
>     Subject: linux-image-3.13-1-amd64  3.13.10-1, Intel M/B, \
>                     I/O virt. enabled, start vm -> e1000 "Tx Unit Hang"
> 
> with the same information as I raised with xen-devel.  I did think 
> carefully about CC'ing xen-devel, but decided it probably wasn't 
> reasonable to include yet another copy of my bug report here. I was 
> going to update the xen-devel list when I heard back from the e1000 
> maintainers. 
> 

Oh!
> Thanks again for your interest and support,

Sure, just want to make sure we get to the bottom of this.

> 
> Best regards,
> 
> Jo.

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