From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Antonio Terceiro <antonio.terceiro@linaro.org>
Cc: Robin Murphy <robin.murphy@arm.com>, Takashi Iwai <tiwai@suse.de>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: snd-cmipci oops during probe on arm64 (current mainline, pre-6.6-rc1)
Date: Wed, 6 Sep 2023 23:29:46 -0300 [thread overview]
Message-ID: <ZPk1mpbSeK7+eVs2@geday> (raw)
In-Reply-To: <ZPjGuCdmPgqznc5t@linaro.org>
On Wed, Sep 06, 2023 at 03:36:40PM -0300, Antonio Terceiro wrote:
> On Wed, Sep 06, 2023 at 01:49:16PM +0100, Robin Murphy wrote:
> > It's blowing up trying to access PCI I/O space, which has apparently ended
> > up in the indirect access mechanism without that being configured correctly.
> > That is definitely an issue down somewhere between the PCI layer and the
> > system firmware. Does the system even have an I/O space window? Some arm64
> > machines don't. I guess we might not have got as far as probing a driver if
> > the I/O BAR couldn't be assigned at all, but either way something's not gone
> > right.
>
> I'm pretty sure I saw reports of people using PCI GPUs on this machine,
> but I would need to confirm.
>
> What info would I need to gather from the machine in order to figure
> this out?
Antonio, please see:
https://community.amperecomputing.com/t/amd-gpus-on-the-altra-devkit-and-other-altras-patches-available-now/336/11
You have a quirky PCIe controller it seems. You'll have to go through
the errata and then some.
Good Luck,
Geraldo Nascimento
WARNING: multiple messages have this Message-ID (diff)
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Antonio Terceiro <antonio.terceiro@linaro.org>
Cc: Robin Murphy <robin.murphy@arm.com>, Takashi Iwai <tiwai@suse.de>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: snd-cmipci oops during probe on arm64 (current mainline, pre-6.6-rc1)
Date: Wed, 6 Sep 2023 23:29:46 -0300 [thread overview]
Message-ID: <ZPk1mpbSeK7+eVs2@geday> (raw)
In-Reply-To: <ZPjGuCdmPgqznc5t@linaro.org>
On Wed, Sep 06, 2023 at 03:36:40PM -0300, Antonio Terceiro wrote:
> On Wed, Sep 06, 2023 at 01:49:16PM +0100, Robin Murphy wrote:
> > It's blowing up trying to access PCI I/O space, which has apparently ended
> > up in the indirect access mechanism without that being configured correctly.
> > That is definitely an issue down somewhere between the PCI layer and the
> > system firmware. Does the system even have an I/O space window? Some arm64
> > machines don't. I guess we might not have got as far as probing a driver if
> > the I/O BAR couldn't be assigned at all, but either way something's not gone
> > right.
>
> I'm pretty sure I saw reports of people using PCI GPUs on this machine,
> but I would need to confirm.
>
> What info would I need to gather from the machine in order to figure
> this out?
Antonio, please see:
https://community.amperecomputing.com/t/amd-gpus-on-the-altra-devkit-and-other-altras-patches-available-now/336/11
You have a quirky PCIe controller it seems. You'll have to go through
the errata and then some.
Good Luck,
Geraldo Nascimento
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-09-07 2:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 22:01 snd-cmipci oops during probe on arm64 (current mainline, pre-6.6-rc1) Antonio Terceiro
2023-09-05 22:01 ` Antonio Terceiro
2023-09-06 6:10 ` Takashi Iwai
2023-09-06 6:10 ` Takashi Iwai
2023-09-06 12:49 ` Robin Murphy
2023-09-06 12:49 ` Robin Murphy
2023-09-06 18:36 ` Antonio Terceiro
2023-09-06 18:36 ` Antonio Terceiro
2023-09-06 19:03 ` Geraldo Nascimento
2023-09-06 19:03 ` Geraldo Nascimento
2023-09-06 20:37 ` Robin Murphy
2023-09-06 20:37 ` Robin Murphy
2023-09-06 21:00 ` Geraldo Nascimento
2023-09-06 21:00 ` Geraldo Nascimento
2023-09-06 19:52 ` Robin Murphy
2023-09-06 19:52 ` Robin Murphy
2023-09-07 0:41 ` Antonio Terceiro
2023-09-07 0:41 ` Antonio Terceiro
2023-09-07 12:22 ` Robin Murphy
2023-09-07 12:22 ` Robin Murphy
2023-09-07 2:29 ` Geraldo Nascimento [this message]
2023-09-07 2:29 ` Geraldo Nascimento
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=ZPk1mpbSeK7+eVs2@geday \
--to=geraldogabriel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=antonio.terceiro@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robin.murphy@arm.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=will@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.