Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp3778045pxt; Tue, 10 Aug 2021 11:06:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw/5YoAs+2ikwkjwMN798Nfq1Y9ErsjvZ12DCe/RFoSSXc2RUKqEccgFLcKrOfbckyhrON6 X-Received: by 2002:a5d:8b17:: with SMTP id k23mr464756ion.17.1628618767650; Tue, 10 Aug 2021 11:06:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628618767; cv=none; d=google.com; s=arc-20160816; b=DiG5+AcD6o18UAKZVo4oElxVQNTqtqdYfILjGO/1HHk9eYhSCLRAYMXOQ4pW0rQEBD 0v0AITttL57fN5EdHdgDxQHInemCHpp94cvF4wYJCVFlOxSAtx798J0S6vNNSTZgkH7x lwu8ihc++IvXALwnmAFVObJxG+uD5MrD5OW9WTNztice56Q1MRhb8INyhZtdKrYS4aIX T2l9e69pJ/3BPStWehNgD6yfKqXe3Fb3RNkw019TMn1JM2QddXvkhKVKrJatZ55lVuDd 63mJyz0rDNs1S+ZHIlPR0LUsiUmSe/yAOvVMt3GqA3g/eMHpecd49tcsb5lWe5INOymQ RiFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=IJw8kQ7EWG4lKsfLjzvpdow8AkllW2MvPsFp1DnLxis=; b=jPGfWFdOJ6D0DvKG9xbBNQH2LnJz7tUJDCN3dV1MMQNbVf6xz6snXqitF924lHvD3l yFLbbxQgZw3Xp1UC2XCkk/kXJCqZa7Q+VKfu5/h9ACyKjNXcBsrDQ+Z/j1qkHgWecHld h4gF5Jrtw/eqaSyqMN5JYw+xIYZXnCS1+ub5DluoUzxKgh23sFyvtvlTQPXYyZR8INDG cUAmkr1TaJjch6iw84qgIt6AIzwVIbiQzBRL1H8xio/y91uOUUdfIYB889YGswyPxlNK 50ziAr8ML4ISzacF1W7JCXb+2XpRxNHQYVNA+K6gg6aBybtDvnA+f7zkddxGGIusVaME SVvg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Sd53KfRb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y9si1141036ilv.82.2021.08.10.11.05.54; Tue, 10 Aug 2021 11:06:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Sd53KfRb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238830AbhHJSEb (ORCPT + 99 others); Tue, 10 Aug 2021 14:04:31 -0400 Received: from mail.kernel.org ([198.145.29.99]:59202 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238737AbhHJR75 (ORCPT ); Tue, 10 Aug 2021 13:59:57 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 97A6D61214; Tue, 10 Aug 2021 17:46:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1628617603; bh=s0g1xmmZwpz0X/vZ9KJFPr4XM+vbvQa7yuAIxalVp1c=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Sd53KfRbsY+jnG9Y3HMrm4v1ryuKTG6zaq2jPL/bKy3m8PrO43wEYRcHbiEV/Gays 3IzzeKjoYxC7RjJOzHwxpWrw0SgwNCoYYQ6uzZSBSZURwCqYKIQtKuTFu/DmzcDMTP fvglvxpgDA/mhWPCzH8Q1PxVyRQdVvG7ZkLV8HD8= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Ralf Ramsauer , Andy Shevchenko , Mario Kleiner Subject: [PATCH 5.13 130/175] serial: 8250_pci: Avoid irq sharing for MSI(-X) interrupts. Date: Tue, 10 Aug 2021 19:30:38 +0200 Message-Id: <20210810173005.233962033@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210810173000.928681411@linuxfoundation.org> References: <20210810173000.928681411@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Mario Kleiner commit 341abd693d10e5f337a51f140ae3e7a1ae0febf6 upstream. This attempts to fix a bug found with a serial port card which uses an MCS9922 chip, one of the 4 models for which MSI-X interrupts are currently supported. I don't possess such a card, and i'm not experienced with the serial subsystem, so this patch is based on what i think i found as a likely reason for failure, based on walking the user who actually owns the card through some diagnostic. The user who reported the problem finds the following in his dmesg output for the relevant ttyS4 and ttyS5: [ 0.580425] serial 0000:02:00.0: enabling device (0000 -> 0003) [ 0.601448] 0000:02:00.0: ttyS4 at I/O 0x3010 (irq = 125, base_baud = 115200) is a ST16650V2 [ 0.603089] serial 0000:02:00.1: enabling device (0000 -> 0003) [ 0.624119] 0000:02:00.1: ttyS5 at I/O 0x3000 (irq = 126, base_baud = 115200) is a ST16650V2 ... [ 6.323784] genirq: Flags mismatch irq 128. 00000080 (ttyS5) vs. 00000000 (xhci_hcd) [ 6.324128] genirq: Flags mismatch irq 128. 00000080 (ttyS5) vs. 00000000 (xhci_hcd) ... Output of setserial -a: /dev/ttyS4, Line 4, UART: 16650V2, Port: 0x3010, IRQ: 127 Baud_base: 115200, close_delay: 50, divisor: 0 closing_wait: 3000 Flags: spd_normal skip_test This suggests to me that the serial driver wants to register and share a MSI/MSI-X irq 128 with the xhci_hcd driver, whereas the xhci driver does not want to share the irq, as flags 0x00000080 (== IRQF_SHARED) from the serial port driver means to share the irq, and this mismatch ends in some failed irq init? With this setup, data reception works very unreliable, with dropped data, already at a transmission rate of only a 16 Bytes chunk every 1/120th of a second, ie. 1920 Bytes/sec, presumably due to rx fifo overflow due to mishandled or not used at all rx irq's? See full discussion thread with attempted diagnosis at: https://psychtoolbox.discourse.group/t/issues-with-iscan-serial-port-recording/3886 Disabling the use of MSI interrupts for the serial port pci card did fix the reliability problems. The user executed the following sequence of commands to achieve this: echo 0000:02:00.0 | sudo tee /sys/bus/pci/drivers/serial/unbind echo 0000:02:00.1 | sudo tee /sys/bus/pci/drivers/serial/unbind echo 0 | sudo tee /sys/bus/pci/devices/0000:02:00.0/msi_bus echo 0 | sudo tee /sys/bus/pci/devices/0000:02:00.1/msi_bus echo 0000:02:00.0 | sudo tee /sys/bus/pci/drivers/serial/bind echo 0000:02:00.1 | sudo tee /sys/bus/pci/drivers/serial/bind This resulted in the following log output: [ 82.179021] pci 0000:02:00.0: MSI/MSI-X disallowed for future drivers [ 87.003031] pci 0000:02:00.1: MSI/MSI-X disallowed for future drivers [ 98.537010] 0000:02:00.0: ttyS4 at I/O 0x3010 (irq = 17, base_baud = 115200) is a ST16650V2 [ 103.648124] 0000:02:00.1: ttyS5 at I/O 0x3000 (irq = 18, base_baud = 115200) is a ST16650V2 This patch attempts to fix the problem by disabling irq sharing when using MSI irq's. Note that all i know for sure is that disabling MSI irq's fixed the problem for the user, so this patch could be wrong and is untested. Please review with caution, keeping this in mind. Fixes: 8428413b1d14 ("serial: 8250_pci: Implement MSI(-X) support") Cc: Ralf Ramsauer Cc: stable Reviewed-by: Andy Shevchenko Signed-off-by: Mario Kleiner Link: https://lore.kernel.org/r/20210729043306.18528-1-mario.kleiner.de@gmail.com Signed-off-by: Greg Kroah-Hartman --- drivers/tty/serial/8250/8250_pci.c | 1 + 1 file changed, 1 insertion(+) --- a/drivers/tty/serial/8250/8250_pci.c +++ b/drivers/tty/serial/8250/8250_pci.c @@ -3970,6 +3970,7 @@ pciserial_init_ports(struct pci_dev *dev if (pci_match_id(pci_use_msi, dev)) { dev_dbg(&dev->dev, "Using MSI(-X) interrupts\n"); pci_set_master(dev); + uart.port.flags &= ~UPF_SHARE_IRQ; rc = pci_alloc_irq_vectors(dev, 1, 1, PCI_IRQ_ALL_TYPES); } else { dev_dbg(&dev->dev, "Using legacy interrupts\n");