[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20181120071424.672f6b58@xeon-e3>
Date: Tue, 20 Nov 2018 07:14:24 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: netdev@...r.kernel.org
Subject: Fw: [Bug 201735] New: serial8250: too much work for irq4
Begin forwarded message:
Date: Tue, 20 Nov 2018 07:09:26 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.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@...workplumber.org
Reporter: rms200x@...il.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.
Powered by blists - more mailing lists