From: Jo Mills <jo@maniscorse.co.uk>
To: David Vrabel <david.vrabel@citrix.com>
Cc: alexander.h.duyck@intel.com,
Ian Campbell <Ian.Campbell@citrix.com>,
donald.c.skidmore@intel.com, mitch.a.williams@intel.com,
bruce.w.allan@intel.com, jesse.brandeburg@intel.com,
xen-devel@lists.xen.org, gregory.v.rose@intel.com,
john.ronciak@intel.com, jeffrey.t.kirsher@intel.com,
carolyn.wyborny@intel.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: Sun, 8 Jun 2014 16:15:17 +0100 [thread overview]
Message-ID: <20140608151517.GA4292@white.maniscorse> (raw)
In-Reply-To: <20140602182506.GE4240@white.maniscorse>
Hi David et al,
Just to try something, I swapped the e1000e NIC for an r8169 NIC and
tried again. The realtek device did not bounce up and down like the
Intel one did, and although ifconfig said the device was up and the
link LED on the card showed a connection, device seemed to be utterly
dead (no reply to/from ping). Then I got the same crash as with the
Intel card:
root@vm-server-22:~# [ 1057.824018] ------------[ cut here ]------------
[ 1057.824033] WARNING: at /build/linux-5U_ZPM/linux-3.2.57/net/sched/sch_generic.c:256 dev_watchdog+0xf2/0x151()
[ 1057.824041] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
[ 1057.824049] Modules linked in: r8169 mii evdev snd_pcm snd_page_alloc snd_timer snd soundcore pcspkr coretemp xen_pcifront ext3 mbcache jbd dm_mod xen_blkfront
[ 1057.824089] Pid: 0, comm: swapper/0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.57-3+deb7u2
[ 1057.824098] Call Trace:
[ 1057.824103] <IRQ> [<ffffffff81046cd9>] ? warn_slowpath_common+0x78/0x8c
[ 1057.824118] [<ffffffff81046d85>] ? warn_slowpath_fmt+0x45/0x4a
[ 1057.824127] [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
[ 1057.824135] [<ffffffff812a7839>] ? netif_tx_lock+0x40/0x75
[ 1057.824143] [<ffffffff812a79a9>] ? dev_watchdog+0xf2/0x151
[ 1057.824150] [<ffffffff810524f8>] ? run_timer_softirq+0x19a/0x261
[ 1057.824158] [<ffffffff812a78b7>] ? netif_tx_unlock+0x49/0x49
[ 1057.824167] [<ffffffff8109138a>] ? handle_irq_event+0x40/0x52
[ 1057.824176] [<ffffffff8104c36e>] ? __do_softirq+0xb9/0x177
[ 1057.824185] [<ffffffff8121c1bd>] ? __xen_evtchn_do_upcall+0x24a/0x287
[ 1057.824194] [<ffffffff81356e6c>] ? call_softirq+0x1c/0x30
[ 1057.824203] [<ffffffff8100fa21>] ? do_softirq+0x3c/0x7b
[ 1057.824208] [<ffffffff8104c5d6>] ? irq_exit+0x3c/0x99
[ 1057.824217] [<ffffffff8121d57d>] ? xen_evtchn_do_upcall+0x27/0x32
[ 1057.824225] [<ffffffff81356ebe>] ? xen_do_hypervisor_callback+0x1e/0x30
[ 1057.824233] <EOI> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
[ 1057.824243] [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
[ 1057.824252] [<ffffffff8100675a>] ? xen_safe_halt+0xc/0x13
[ 1057.824258] [<ffffffff81014614>] ? default_idle+0x47/0x7f
[ 1057.824265] [<ffffffff8100d24c>] ? cpu_idle+0xaf/0xf2
[ 1057.824274] [<ffffffff816abb36>] ? start_kernel+0x3b8/0x3c3
[ 1057.824282] [<ffffffff816ad4df>] ? xen_start_kernel+0x412/0x418
[ 1057.824289] ---[ end trace eee1d2411f3779ca ]---
[ 1057.842587] r8169 0000:00:00.0: eth0: link up
Oh hum,
Any suggestions etc. all very gratefully received,
Best regards,
Jo.
prev parent reply other threads:[~2014-06-08 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 17:46 xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B, I/O virt. enabled, start vm -> Kernel panic Jo Mills
2014-05-19 10:58 ` Jan Beulich
2014-05-19 11:03 ` Ian Campbell
2014-05-20 10:14 ` David Vrabel
2014-05-20 10:18 ` Ian Campbell
2014-05-20 16:20 ` David Vrabel
2014-05-20 18:41 ` Jo Mills
2014-05-21 9:42 ` David Vrabel
2014-05-22 9:47 ` Konrad Rzeszutek Wilk
[not found] ` <20140522094744.GA8264@localhost.localdomain>
2014-05-22 10:03 ` Jo Mills
[not found] ` <20140522100327.GG7332@white.maniscorse>
2014-05-23 15:50 ` Konrad Rzeszutek Wilk
[not found] ` <20140523155015.GC5209@phenom.dumpdata.com>
2014-06-01 16:18 ` Jo Mills
2014-06-02 9:34 ` David Vrabel
2014-06-02 18:25 ` Jo Mills
2014-06-08 15:15 ` Jo Mills [this message]
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=20140608151517.GA4292@white.maniscorse \
--to=jo@maniscorse.co.uk \
--cc=Ian.Campbell@citrix.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=david.vrabel@citrix.com \
--cc=donald.c.skidmore@intel.com \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=xen-devel@lists.xen.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).