From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Fw: [Bug 201735] New: serial8250: too much work for irq4
Date: Tue, 20 Nov 2018 07:14:24 -0800
Message-ID: <20181120071424.672f6b58@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
To: netdev@vger.kernel.org
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-pl1-f175.google.com ([209.85.214.175]:45405 "EHLO
        mail-pl1-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726554AbeKUBoE (ORCPT
        <rfc822;netdev@vger.kernel.org>); Tue, 20 Nov 2018 20:44:04 -0500
Received: by mail-pl1-f175.google.com with SMTP id a14so1125388plm.12
        for <netdev@vger.kernel.org>; Tue, 20 Nov 2018 07:14:28 -0800 (PST)
Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127])
        by smtp.gmail.com with ESMTPSA id t3sm22849000pgv.31.2018.11.20.07.14.27
        for <netdev@vger.kernel.org>
        (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
        Tue, 20 Nov 2018 07:14:27 -0800 (PST)
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>



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.