From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Jason Cooper <jason@lakedaemon.net>,
Russell King <linux@armlinux.org.uk>,
vtolkm@googlemail.com,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-arm-kernel@lists.infradead.org
Subject: [Bug 209833] New: BAR error updating
Date: Fri, 23 Oct 2020 13:05:56 -0500 [thread overview]
Message-ID: <20201023180556.GA669920@bjorn-Precision-5520> (raw)
----- Forwarded message from bugzilla-daemon@bugzilla.kernel.org -----
Date: Fri, 23 Oct 2020 17:17:28 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: bjorn@helgaas.com
Subject: [Bug 209833] New: BAR error updating
Message-ID: <bug-209833-41252@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209833
Bug ID: 209833
Summary: BAR error updating
Product: Drivers
Version: 2.5
Kernel Version: 5.5.19 - 5.9.1
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: PCI
Assignee: drivers_pci@kernel-bugs.osdl.org
Reporter: vtolkm@googlemail.com
Regression: No
Created attachment 293153
--> https://bugzilla.kernel.org/attachment.cgi?id=293153&action=edit
accumulated kernel log messages
device: Turris Omnia (armv7l)
lspci >
00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6820 (rev 04)
02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless
Network Adapter (rev ff)
03:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter
(PCI-Express) (rev 01)
----
Since kernel 5.5.x this error exhibits:
BAR 0: error updating
It appears to be a regression from 5.4 where the error does not exhibits -
enclosed accumulated kernel logs.
It may or may not cause issues for the atheros drivers as mentioned in bug
209751.
I have tried to narrow it further down to a particular commit from the 5.5
branch but unfortunately the kernel does not compile then.
--
You are receiving this mail because:
You are watching the assignee of the bug.
----- End forwarded message -----
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-10-23 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201023180556.GA669920@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vtolkm@googlemail.com \
/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