From: Bjorn Helgaas <helgaas@kernel.org>
To: Grzegorz Halat <ghalat@redhat.com>
Cc: stefan.buehler@tik.uni-stuttgart.de,
sean.v.kelley@linux.intel.com, 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
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: Mon, 26 Sep 2022 16:17:24 -0500 [thread overview]
Message-ID: <20220926211724.GA1625628@bhelgaas> (raw)
In-Reply-To: <20220923192030.162412-1-ghalat@redhat.com>
On Fri, Sep 23, 2022 at 09:20:30PM +0200, Grzegorz Halat wrote:
> 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?
I think Sean has moved on and isn't available to work this issue.
To help whoever *can* work on it, would you mind attaching the
complete dmesg log and "sudo lspci -vv" output for your system? Then
we can potentially tweak the quirk to not break your system.
Bjorn
next prev parent reply other threads:[~2022-09-26 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 19:29 [PATCH v2 0/2] pci: Add boot interrupt quirk mechanism for Xeon chipsets Sean V Kelley
2020-02-20 19:29 ` [PATCH v2 1/2] " Sean V Kelley
2020-02-20 19:29 ` [PATCH v2 2/2] Documentation:PCI: Add background on Boot Interrupts Sean V Kelley
2020-02-27 22:49 ` [PATCH v2 0/2] pci: Add boot interrupt quirk mechanism for Xeon chipsets Bjorn Helgaas
[not found] ` <b2da25c8-121a-b241-c028-68e49bab0081@tik.uni-stuttgart.de>
2020-11-25 11:54 ` 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) Thomas Gleixner
2020-11-25 13:41 ` Stefan Bühler
2020-11-26 23:45 ` Thomas Gleixner
2020-11-27 9:17 ` Stefan Bühler
2020-11-30 10:48 ` Thomas Gleixner
2022-09-23 19:20 ` Grzegorz Halat
2022-09-26 21:17 ` Bjorn Helgaas [this message]
2022-09-28 8:34 ` 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) #forregzbot Thorsten Leemhuis
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=20220926211724.GA1625628@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=ghalat@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kar.hin.ong@ni.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sassmann@kpanic.de \
--cc=sean.v.kelley@linux.intel.com \
--cc=stefan.buehler@tik.uni-stuttgart.de \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).