All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Rogalski <rrogalski@tutanota.com>
To: helgaas@kernel.org
Cc: alexander.deucher@amd.com, davem@davemloft.net,
	lijo.lazar@amd.com, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, rrogalski@tutanota.com,
	sparclinux@vger.kernel.org
Subject: Re: SPARC64: getting "no compatible bridge window" errors :/
Date: Fri, 21 Oct 2022 05:47:59 +0200 (CEST)	[thread overview]
Message-ID: <NEsdtVI--3-9@tutanota.com> (raw)

Hello, very very sorry about the late reply. Life has been hectic. Also, not sure if this is how I reply to one of these, sorry if I screwed it up :)

> This is great, thanks a lot for your report!  Is this a regression?

Believe it or not, I am a brand new SPARC user :). So I can't say right now. Should I try a few old kernel releases to check?

> Any chance you could collect a dmesg log with "ofpci_debug=1"?

https://gitlab.freedesktop.org/drm/amd/uploads/0ed3c92921d7f88b06654b5f46e9756d/dmesg

> Do the devices we complain about (NICs and storage HBAs 09:00.0, 
> 09:00.1, 0d:00.0, 0d:00.1, 0e:00.0, 0f:00.0, 0001:03:00.0, 
> 0001:03:00.1, 0001:0:00.0, 0001:0a:00.1) work?

Well, I don't have any fiber optic equipment: these just came with the server. Also it has wayy too many NICs. I can't quite say.
However... for the HBAs, that's where my root is :O. This is mildly concerning :D.


             reply	other threads:[~2022-10-21  3:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  3:47 Richard Rogalski [this message]
2022-10-24 18:14 ` SPARC64: getting "no compatible bridge window" errors :/ Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2022-09-25 16:59 Richard Rogalski
2022-09-26 17:11 ` Bjorn Helgaas
2022-10-03 22:35   ` Bjorn Helgaas
2022-10-10 21:36     ` 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=NEsdtVI--3-9@tutanota.com \
    --to=rrogalski@tutanota.com \
    --cc=alexander.deucher@amd.com \
    --cc=davem@davemloft.net \
    --cc=helgaas@kernel.org \
    --cc=lijo.lazar@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sparclinux@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.