From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Luís Mendes" <luis.p.mendes@gmail.com>
Cc: linux-pci@vger.kernel.org, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: Regression with commit PCI: mvebu: Convert to PCI emulated bridge config space
Date: Tue, 18 Dec 2018 14:47:02 +0100 [thread overview]
Message-ID: <20181218144702.752d97cd@windsurf> (raw)
In-Reply-To: <CAEzXK1o9L-bVRGBpAo+a_wYqXZh6_zuebF221Bd8=b-DTL1Q9g@mail.gmail.com>
Hello,
On Tue, 18 Dec 2018 12:31:51 +0000, Luís Mendes wrote:
> I've been running Linux on a armhf with an AMD gpu card and since this
> commit, in linux 4.20, the amdgpu driver causes a kernel oops and fails to
> initialize when calling pci_map_rom, which then fails on a call to
> ioremap_page_range. If I revert the patch from commit
>
> 1f08673eef1236f7d02d93fcf596bb8531ef0d12
> <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.20-rc7&id=1f08673eef1236f7d02d93fcf596bb8531ef0d12>
> then
> amdgpu successfully initializes.
>
> The kernel oops follows in attachment.
Thanks for the bug report! I have an idea of what could be causing
this, I've cooked a patch, I'm doing a build test. I of course won't be
able to test it as I don't have amdgpu hardware, but I'll share the
patch with you for testing.
Note: I'm not sure where you found <linux-pci@atrey.karlin.mff.cuni.cz>
to be the address of the linux-pci mailing list, it's really
linux-pci@vger.kernel.org.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-18 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEzXK1o9L-bVRGBpAo+a_wYqXZh6_zuebF221Bd8=b-DTL1Q9g@mail.gmail.com>
[not found] ` <CAEzXK1po4ik1oHdwVvVMWEqh8KMdAMY7sxv9OR2bYs54qV6EyA@mail.gmail.com>
2018-12-18 13:42 ` Fwd: Regression with commit PCI: mvebu: Convert to PCI emulated bridge config space Luís Mendes
2018-12-18 13:47 ` Thomas Petazzoni [this message]
2018-12-18 14:34 ` Thomas Petazzoni
2018-12-18 15:42 ` Luís Mendes
2018-12-18 20:37 ` Thomas Petazzoni
2018-12-18 23:13 ` Luís Mendes
2019-01-08 10:48 ` Thomas Petazzoni
[not found] ` <CAEzXK1oQd1YNZ5pyNXA76h-3CbBRxmTke=Z-SRusyfqL=Wd8eA@mail.gmail.com>
2019-01-09 8:15 ` Thomas Petazzoni
[not found] ` <CAEzXK1oHqOb3pojfX7JqrirxjOFj=UZZfi6tNNO4y6yC3u9LAA@mail.gmail.com>
2019-02-04 11:09 ` Luís Mendes
2019-02-12 13:41 ` Thomas Petazzoni
2019-02-13 11:34 ` Luís Mendes
2019-02-13 12:33 ` Thomas Petazzoni
2019-02-13 13:24 ` Luís Mendes
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=20181218144702.752d97cd@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=luis.p.mendes@gmail.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