From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 121091] New: guest os kernel report "virtio_net virtio0:
input.0:id 0 is not a head!" and then kernel block
Date: Tue, 28 Jun 2016 04:22:41 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.29.136]:41634 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1750704AbcF1EWp (ORCPT );
Tue, 28 Jun 2016 00:22:45 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id CC3BA20260
for ; Tue, 28 Jun 2016 04:22:43 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org [172.20.200.51])
by mail.kernel.org (Postfix) with ESMTP id 0BCF02022D
for ; Tue, 28 Jun 2016 04:22:42 +0000 (UTC)
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=121091
Bug ID: 121091
Summary: guest os kernel report "virtio_net virtio0: input.0:id
0 is not a head!" and then kernel block
Product: Virtualization
Version: unspecified
Kernel Version: 3.18
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: yuewenyuan31837@126.com
Regression: No
environment:
host kernel version: 3.14.23
QEMU emulator version: 2.1.3
guest os kernel version: 3.18.20
reproduce problem:
1.start vm with 2vcpus
2.attach interface
3.detach interface
cpu stack:
crash> bt
PID: 0 TASK: ffffffff81818450 CPU: 0 COMMAND: "swapper/0"
[exception RIP: virtnet_poll+60]
RIP: ffffffff81330386 RSP: ffff88007fc03e88 RFLAGS: 00000246
RAX: dead000000100100 RBX: ffff88007a6af808 RCX: 0000000000000100
RDX: dead000000200200 RSI: 0000000000000000 RDI: 0000000000000246
RBP: 0000000000000000 R8: 0000000000000000 R9: 00000000ffffffff
R10: 00000000ffffffff R11: ffff88007a6af808 R12: 0000000000000040
R13: ffff88007a6af800 R14: 0000000000000103 R15: ffff88007fc13990
CS: 0010 SS: 0018
#0 [ffff88007fc03eb0] net_rx_action at ffffffff81373640
#1 [ffff88007fc03f10] __do_softirq at ffffffff8104de17
#2 [ffff88007fc03f70] irq_exit at ffffffff8104e0de
#3 [ffff88007fc03f80] do_IRQ at ffffffff8100ee6b
--- ---
#4 [ffffffff81803e48] ret_from_intr at ffffffff8143466d
[exception RIP: native_safe_halt+2]
RIP: ffffffff8103b923 RSP: ffffffff81803ef0 RFLAGS: 00000246
RAX: 0000000000000000 RBX: ffff88007fc0da00 RCX: 00000000ffffffff
RDX: ffffffff81842f00 RSI: 0000000000000000 RDI: ffffffff81800000
RBP: 0000000000000000 R8: 0000000000000000 R9: 0000000000000000
R10: 000000000000b464 R11: 000000000000b464 R12: 0000000000000000
R13: 0000000101432bf8 R14: 00004d52b5fe5100 R15: 0000000000000017
ORIG_RAX: ffffffffffffff1e CS: 0010 SS: 0018
#5 [ffffffff81803ef0] default_idle at ffffffff810153a9
#6 [ffffffff81803f00] cpu_startup_entry at ffffffff81075463
#7 [ffffffff81803f60] start_kernel at ffffffff818d1efb
#8 [ffffffff81803f78] early_idt_handler_array at ffffffff818d1117
#9 [ffffffff81803f98] early_idt_handler_array at ffffffff818d1117
#10 [ffffffff81803fb0] x86_64_start_kernel at ffffffff818d15fe
I revert the commit 78fd1d0ab072d4d9b5f0b7c14a1516665170b565 and this problem
will not happen again. Guest os with kernel 3.19 and 4.0 was tested, and this
problem is still there.
--
You are receiving this mail because:
You are watching the assignee of the bug.