From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 197097] New: Kernel panic in interrupt [virtio_net]
Date: Sun, 01 Oct 2017 16:10:32 +0000 [thread overview]
Message-ID: <bug-197097-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=197097
Bug ID: 197097
Summary: Kernel panic in interrupt [virtio_net]
Product: Virtualization
Version: unspecified
Kernel Version: 4.13.4-1.el6.elrepo.x86_64
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: svimik@gmail.com
Regression: No
Created attachment 258683
--> https://bugzilla.kernel.org/attachment.cgi?id=258683&action=edit
stacktrace screenshot
Hello!
Getting kernel panics on multiple servers. Since it mentions kvm_* functions
and [virtio_net], I decided to report it to Virtualization (correct me if I'm
wrong).
Unfortunately I'm still struggling with making kdump work, so the trace
screenshot is all I have at this moment. The only hope is that this stacktrace
means something to the guys that wrote the code.
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2017-10-01 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-197097-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.