From: Emmanuel Lacour <elacour@easter-eggs.com>
To: kvm@vger.kernel.org
Subject: Re: virtio_net hang
Date: Sat, 22 Nov 2008 15:20:10 +0100 [thread overview]
Message-ID: <20081122142009.GA9467@easter-eggs.com> (raw)
In-Reply-To: <20081121083823.GB3721@easter-eggs.com>
On Fri, Nov 21, 2008 at 09:38:23AM +0100, Emmanuel Lacour wrote:
>
> I continue to have this problem with this setup:
>
> - host 2.6.27.4, kvm-78, intel, debian etch 64bits
> - guest 2.6.27.6, debian sarge 32 bits, e1000, 2 vcpus
>
> up/down of interface is enough to recover.
>
Today I had a trace on this problem (first time), maybe this can help:
Nov 21 14:34:42 foo kernel: [58345.000104] ------------[ cut here ]------------
Nov 21 14:34:42 foo kernel: [58345.000617] WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0x164/0x1fd()
Nov 21 14:34:42 foo kernel: [58345.001374] NETDEV WATCHDOG: eth0 (e1000): transmit timed out
Nov 21 14:34:42 foo kernel: [58345.001825] Modules linked in: nfsd auth_rpcgss exportfs ac battery ipv6 nfs lockd nfs_acl sunrpc nf_nat_ftp nf_conntrack_ftp xt_tcpudp iptable_mangle iptable_nat nf_nat ipt_REJECT xt_limit nf_conntrack_ipv4 xt_state nf_conntrack ipt_LOG ipt_ULOG iptable_filter ip_tables x_tables dm_mod sd_mod snd_pcsp virtio_balloon snd_pcm snd_timer snd soundcore floppy snd_page_alloc psmouse serio_raw virtio_pci i2c_piix4 button i2c_core evdev ext3 jbd mbcache ide_cd_mod cdrom ide_disk ata_generic ata_piix libata scsi_mod dock piix ide_core uhci_hcd e1000 usbcore thermal processor fan thermal_sys
Nov 21 14:34:42 foo kernel: [58345.022597] Pid: 0, comm: swapper Not tainted 2.6.27.6 #1
Nov 21 14:34:42 foo kernel: [58345.023027] [<c0126295>] warn_slowpath+0x58/0x70
Nov 21 14:34:42 foo kernel: [58345.023470] [<c028e96b>] ip_output+0x8e/0x90
Nov 21 14:34:42 foo kernel: [58345.029292] [<c028e3ab>] ip_local_out+0x15/0x17
Nov 21 14:34:42 foo kernel: [58345.030231] [<c028ec1d>] ip_queue_xmit+0x2b0/0x2f7
Nov 21 14:34:42 foo kernel: [58345.030684] [<c01169c7>] pvclock_get_nsec_offset+0xb/0x59
Nov 21 14:34:42 foo kernel: [58345.031163] [<c0116a79>] pvclock_clocksource_read+0x1a/0x2d
Nov 21 14:34:42 foo kernel: [58345.031642] [<c01169c7>] pvclock_get_nsec_offset+0xb/0x59
Nov 21 14:34:42 foo kernel: [58345.032130] [<c0116a79>] pvclock_clocksource_read+0x1a/0x2d
Nov 21 14:34:42 foo kernel: [58345.032608] [<c01169c7>] pvclock_get_nsec_offset+0xb/0x59
Nov 21 14:34:42 foo kernel: [58345.033080] [<c01169c7>] pvclock_get_nsec_offset+0xb/0x59
Nov 21 14:34:42 foo kernel: [58345.033570] [<c01169c7>] pvclock_get_nsec_offset+0xb/0x59
Nov 21 14:34:42 foo kernel: [58345.034036] [<c0116a79>] pvclock_clocksource_read+0x1a/0x2d
Nov 21 14:34:42 foo kernel: [58345.034506] [<c027e572>] dev_watchdog+0x164/0x1fd
Nov 21 14:34:42 foo kernel: [58345.034951] [<c0139cf7>] __atomic_notifier_call_chain+0x10/0x13
Nov 21 14:34:42 foo kernel: [58345.035455] [<c02d4c73>] _spin_lock_bh+0xf/0x12
Nov 21 14:34:42 foo kernel: [58345.035898] [<c012d9a4>] timer_stats_account_timer+0x22/0x27
Nov 21 14:34:42 foo kernel: [58345.036384] [<c012dfcf>] run_timer_softirq+0x11f/0x183
Nov 21 14:34:42 foo kernel: [58345.036840] [<c027e40e>] dev_watchdog+0x0/0x1fd
Nov 21 14:34:42 foo kernel: [58345.037278] [<c01390dc>] hrtimer_interrupt+0x136/0x15e
Nov 21 14:34:42 foo kernel: [58345.037736] [<c012a53f>] __do_softirq+0x69/0xd3
Nov 21 14:34:42 foo kernel: [58345.038172] [<c012a5ed>] do_softirq+0x44/0x52
Nov 21 14:34:42 foo kernel: [58345.038608] [<c012a67e>] irq_exit+0x38/0x6c
Nov 21 14:34:42 foo kernel: [58345.039035] [<c01106f1>] smp_apic_timer_interrupt+0x2a/0x33
Nov 21 14:34:42 foo kernel: [58345.039518] [<c0104434>] apic_timer_interrupt+0x28/0x30
Nov 21 14:34:42 foo kernel: [58345.039980] [<c0116560>] native_safe_halt+0x2/0x3
Nov 21 14:34:42 foo kernel: [58345.040443] [<c0109196>] default_idle+0x2e/0x54
Nov 21 14:34:42 foo kernel: [58345.040886] [<c01020ff>] cpu_idle+0xc4/0xf7
Nov 21 14:34:42 foo kernel: [58345.041310] =======================
Nov 21 14:34:42 foo kernel: [58345.041692] ---[ end trace 934a9cb836d2434b ]---
Nov 21 14:34:42 foo kernel: [58345.080575] e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
next prev parent reply other threads:[~2008-11-22 14:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 12:27 virtio_net hang Emmanuel Lacour
2008-11-13 13:04 ` Daniel P. Berrange
2008-11-13 13:15 ` Emmanuel Lacour
2008-11-13 15:12 ` Mark McLoughlin
2008-11-13 15:24 ` Emmanuel Lacour
2008-11-14 9:23 ` Emmanuel Lacour
2008-11-14 18:26 ` Mark McLoughlin
2008-11-18 18:37 ` Emmanuel Lacour
2008-11-18 18:48 ` Emmanuel Lacour
2008-11-19 13:13 ` Mark McLoughlin
2008-11-19 19:03 ` Mark McLoughlin
2008-11-20 11:36 ` Emmanuel Lacour
2008-11-21 8:38 ` Emmanuel Lacour
2008-11-22 14:20 ` Emmanuel Lacour [this message]
2008-11-21 14:44 ` Guido Günther
2008-11-20 11:34 ` Emmanuel Lacour
2008-11-13 18:27 ` Fabio Coatti
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=20081122142009.GA9467@easter-eggs.com \
--to=elacour@easter-eggs.com \
--cc=kvm@vger.kernel.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