Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Grzegorz Halat <ghalat@redhat.com>
To:     stefan.buehler@tik.uni-stuttgart.de, sean.v.kelley@linux.intel.com
Cc:     bhelgaas@google.com, bp@alien8.de, corbet@lwn.net,
        gregkh@linuxfoundation.org, kar.hin.ong@ni.com,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-pci@vger.kernel.org, mingo@redhat.com, sassmann@kpanic.de,
        tglx@linutronix.de, x86@kernel.org,
        Grzegorz Halat <ghalat@redhat.com>
Subject: Re: boot interrupt quirk (also in 4.19.y) breaks serial ports (was: [PATCH v2 0/2] pci: Add boot interrupt quirk mechanism for Xeon chipsets)
Date:   Fri, 23 Sep 2022 21:20:30 +0200
Message-Id: <20220923192030.162412-1-ghalat@redhat.com>
In-Reply-To: <b2da25c8-121a-b241-c028-68e49bab0081@tik.uni-stuttgart.de>
References: <b2da25c8-121a-b241-c028-68e49bab0081@tik.uni-stuttgart.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi,

On Wed, Sep 16 2020 at 12:12, Stefan Bühler wrote:
> this quirk breaks our serial ports PCIe card (i.e. we don't see any
> output from the connected devices; no idea whether anything we send
> reaches them):

I have the same problem, also with a PCI serial adapter from Oxford Semiconductor.
I've bisected the kernel and it was introduced in b88bf6c3b6ff.
When the system is booted with "pci=noioapicquirk" then the PCI card works fine.
The CPU is Intel Xeon E5-2680 v3 @ 2.50GHz.

Sean, do you have any news about this issue?

Grzegorz