From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 201735] New: serial8250: too much work for irq4
Date: Tue, 20 Nov 2018 07:14:24 -0800 [thread overview]
Message-ID: <20181120071424.672f6b58@xeon-e3> (raw)
Begin forwarded message:
Date: Tue, 20 Nov 2018 07:09:26 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 201735] New: serial8250: too much work for irq4
https://bugzilla.kernel.org/show_bug.cgi?id=201735
Bug ID: 201735
Summary: serial8250: too much work for irq4
Product: Networking
Version: 2.5
Kernel Version: 4.4.0-116-generic
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: rms200x@gmail.com
Regression: No
Created attachment 279549
--> https://bugzilla.kernel.org/attachment.cgi?id=279549&action=edit
LSHW log
Virtual machines loosing network access randomly. What happens when issue is
present:
- Network device on guest machine is lost. It's impossible to access machine.
- Virsh console available for connection. PING from affected guest is
available but with massive packet loss (20% ~ 70%).
- Networking restart from the guest does not resolve problem.
- When virsh editing and setting to: <cpu mode='host-passthrough'/> issue
seems to be resolved (after reboot).
Such issue observed on SUPERMICRO server. LSHW report attached.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-11-21 1:44 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=20181120071424.672f6b58@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@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