From: Richard Rogalski <rrogalski@tutanota.com>
To: Linux Pci <linux-pci@vger.kernel.org>
Subject: SPARC64: getting "no compatible bridge window" errors :/
Date: Sun, 25 Sep 2022 18:59:23 +0200 (CEST) [thread overview]
Message-ID: <NCp_h9j--3-2@tutanota.com> (raw)
Hello!!
I hope this is the right place for this. In my dmesg output, I get things like:
```
pci 0000:04:00.0: can't claim VGA legacy [mem 0x000a0000-0x000bffff]: no compatible bridge window
pci 0000:06:00.0: can't claim VGA legacy [mem 0x000a0000-0x000bffff]: no compatible bridge window
pci 0000:06:00.1: can't claim BAR 0 [mem 0x84110200000-0x84110203fff 64bit]: no compatible bridge window
```
I opened a bug for amdgpu [here](https://gitlab.freedesktop.org/drm/amd/-/issues/2169) but looking further into it I think it is caused by deeper PCIe problems :\
https://gitlab.freedesktop.org/drm/amd/uploads/cbf47807972c8a990bb2a8cdbb39ad9e/8C7CA9QNG dmesg log
https://gitlab.freedesktop.org/drm/amd/uploads/6a799425dea50febd82f8bc11e54433a/ll.txt lspci -vv
https://gitlab.freedesktop.org/drm/amd/uploads/7d4a794b1f7d67a1ffcdee5dfdec3ad6/config.txt kernel .config
There's a tad more info attached to that bug if needed :D
I greatly appreciate your time (:
next reply other threads:[~2022-09-25 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 16:59 Richard Rogalski [this message]
2022-09-26 17:11 ` SPARC64: getting "no compatible bridge window" errors :/ Bjorn Helgaas
2022-10-03 22:35 ` Bjorn Helgaas
2022-10-10 21:36 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2022-10-21 3:47 Richard Rogalski
2022-10-24 18:14 ` Bjorn Helgaas
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=NCp_h9j--3-2@tutanota.com \
--to=rrogalski@tutanota.com \
--cc=linux-pci@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.