<div dir="ltr"><div>Hello Christian,</div><div><br></div><div>I solved this problem weeks ago. The problem was, the system I use could only give 256 MB address range but GPU was demanding more. Even if I give 4 GB, PCIe slot is only having 256 MB, nothing more. I put a empty area that is between PCIe2 ( GPU was connected to this) and PCIe3 and everything worked fine ( I moved forward the start adress of next PCIe device) . If anyone encounters same problem, here is a sample Device Tree Source for linux;</div><div><br></div><div>pci0: pcie@ffe240000 {<br> reg = <0xf 0xfe240000 0 0x10000>;<br> ranges = <0x02000000 0 0xe0000000 0x2 0x0 0x0 0x10000000<br> 0x01000000 0 0x0 0xf 0xf8000000 0x0 0x00010000>;<br> pcie@0 {<br> ranges = <0x02000000 0 0xe0000000<br> 0x02000000 0 0xe0000000<br> 0 0x10000000<br><br> 0x01000000 0 0x00000000<br> 0x01000000 0 0x00000000<br> 0 0x00010000>;<br> };<br> };<br><br> pci1: pcie@ffe250000 { // GPU CONNECTED TO THIS ONE<br> reg = <0xf 0xfe250000 0 0x10000>;<br> ranges = <0x02000000 0 0xe0000000 0x2 0x10000000 0x1 0x00000000<br> 0x01000000 0 0 0xf 0xf8010000 0 0x00010000>;<br> pcie@0 {<br> ranges = <0x02000000 0 0xe0000000<br> 0x02000000 0 0xe0000000<br> 0x1 0x00000000<br><br> 0x01000000 0 0x00000000<br> 0x01000000 0 0x00000000<br> 0 0x00010000>;<br> };<br> };<br><br> pci2: pcie@ffe260000 {<br> reg = <0xf 0xfe260000 0 0x10000>;<br> ranges = <0x02000000 0 0xe0000000 0x3 0x20000000 0 0x10000000 // 0x3 0x20000000 actually it must be 0x3 0x10000000 because I gave 4 GB to pci1 but I also added 256 MB empty area between them. So it started from 0x3 0x20000000<br> 0x01000000 0 0x00000000 0xf 0xf8020000 0 0x00010000>;<br> pcie@0 {<br> ranges = <0x02000000 0 0xe0000000<br> 0x02000000 0 0xe0000000<br> 0 0x10000000<br><br> 0x01000000 0 0x00000000<br> 0x01000000 0 0x00000000<br> 0 0x00010000>;<br> };<br> };<br><br> pci3: pcie@ffe270000 {<br> reg = <0xf 0xfe270000 0 0x10000>;<br> ranges = <0x02000000 0 0xe0000000 0x3 0x30000000 0 0x10000000<br> 0x01000000 0 0x00000000 0xf 0xf8030000 0 0x00010000>;<br> pcie@0 {<br> ranges = <0x02000000 0 0xe0000000<br> 0x02000000 0 0xe0000000<br> 0 0x10000000<br><br> 0x01000000 0 0x00000000<br> 0x01000000 0 0x00000000<br> 0 0x00010000>;<br> };<br> };<br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Yusuf Altıparmak <<a href="mailto:yusufalti1997@gmail.com">yusufalti1997@gmail.com</a>>, 3 Ara 2019 Sal, 22:20 tarihinde şunu yazdı:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div>What you could try as well is to use the size 320MB for the MMIO.
Those ranges usually don't need to be a power of two (only the
BARs itself are a power of two) and this way it might even be
easier to fit everything together.<br></div></div></blockquote><div><br></div><div>Hmm this makes my job easier it seems.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div>
<blockquote type="cite">By the way I wonder how can I get at least
VGA output from GPU. Maybe I can get a text console on screen or
something like X server? Do you have any recommendations?</blockquote>
What could maybe work is VGA emulation, which essentially means
text only. But no guarantee for that this really works as
expected.<br>
<br></div></div></blockquote><div>It's a well known board and U-boot is the most popular bootloader in embedded world it seems. I think I am not the only one who tries to connect a GPU from PCIe so I think there must be some config variables that enables VGA emulation, or some kind of packages.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div>
<blockquote type="cite">I am just wondering, does modern gaming
motherboards have more than 4GB PCIe buffer for this job ?</blockquote>
They don't, resources are dynamically assigned instead.<br>
<br>
See on x86 you usually have 1GB 32-bit address space where the
BIOS shuffles all the mandatory devices it sees at boot time into.
<br>
<br>
Then when the motherboard has multiple PEG slots the BIOS also
configures a 64-bit address space which is usually rather huge
(256GB-1TB). Since the the VRAM and the doorbell BAR are 64bit
BARs on the GPU they can be mapped into that as well.<br>
<br>
This way you can easily have 10 GPUs connected to your CPU.<br>
<br></div></div></blockquote><div><div>Ah that was a clear answer. So the adress that CPU uses after mapping is actully an imaginary/virtual adress. It depends on the operating systems bit configuration. If I am not wrong, those addresses are adding on previous one meanwhile PCIe is mapping with endpoint device. </div><div></div></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div>
The problem you have here is that U-config doesn't do this
resource assignment automatically and you need to configure it
manually.<br></div></div></blockquote><div><br></div><div>Yes. By the way, thanks for your answers Christian. I am a newbie to embedded world. I have been dealing with these stuffs for 3 months. I couldn't get the answers I seek from google. Your answers were more clear and understandable. </div><div><br></div><div>Best Regards.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div>
Am 03.12.19 um 13:50 schrieb Yusuf Altıparmak:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr"><br>
</div>
Hi Christian,<br>
<div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div>
<blockquote type="cite">0001f000</blockquote>
Exactly as I thought. The hardware does support BAR
resize, but unfortunately 256MB is already the
minimum.<br>
<br>
Sorry, but there isn't anything I could do from the
GPU drivers point of view.<br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Yes unfortunately there is nothing remained to about
GPU side. <br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div> The only good news I have is that
256M+2M+512K+128K=260M address space should be enough
for the GPU to work, maybe that makes things a bit
simpler.<br>
<br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Right now I am trying to increase MMIO size config to
512 MB, I hope that should help me. By the way I wonder
how can I get at least VGA output from GPU. Maybe I can
get a text console on screen or something like X server?
Do you have any recommendations? I tried this GPU with my
own Ubuntu 18.04 and its special driver. Everything worked
fine.</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div> But you definitely got an interesting use case
here :)</div>
</div>
</blockquote>
<div><br>
</div>
<div>This is the worlds the most interesting use case I
think. I can't increase MMIO size because U-boot freezes.
I can't decrease it to 256 MB again because driver does
not accept :D. I am just wondering, does modern gaming
motherboards have more than 4GB PCIe buffer for this job ?
:D<br>
</div>
<div><br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div> Am 03.12.19 um 11:31 schrieb Yusuf Altıparmak:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hello Christian,</div>
<div>My "setpci -s 0001:01:00.0 ECAP15+4.l
ECAP15+8.l" output is;</div>
<div><br>
</div>
<div>0001f000
<br>
00000820 <br>
</div>
<div><br>
</div>
<div>Regards.<br>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Yusuf Altıparmak
<<a href="mailto:yusufalti1997@gmail.com" target="_blank">yusufalti1997@gmail.com</a>>,
2 Ara 2019 Pzt, 19:31 tarihinde şunu yazdı:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">Most likely not.
There is support for resizing the VRAM
BAR, but usually you can only make it
larger and not smaller.<br>
Please give me the output of "sudo
setpci -s 0001:01:00.0 ECAP15+4.l
ECAP15+8.l" if you want to double check
that.<br>
</div>
</blockquote>
<div><br>
</div>
<div>Okay I'll try it tomorrow. What does
the " sudo setpci -s 0001:01:00.0
ECAP15+4.l ECAP15+8.l" command exactly do
?</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> Well you rather
need to ask if anybody has sample PCIe
configuration for GPUs in general. That
problem is not really E9171 related. You
might want to ask NXP for that maybe.<br>
Sorry, no idea if that is correct or
not. You need to ask NXP for help with
that.<br>
<br>
</div>
</blockquote>
<div><br>
</div>
<div>Okay no problem. At least I know what
is the missing point now. The problem is
probably because of the .dtsi and u-boot
config files. Memory ranges are
overwriting like you said. I'll ask nxp to
take some sample PCIe configuration for
GPUs.</div>
<div><br>
</div>
<div>Thank you for your interest Christian.</div>
<div>Regards .<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div> Am 02.12.19 um 14:32
schrieb Yusuf Altıparmak:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"><br>
<blockquote type="cite">I
attached my dts
file.<br>
<div>
<div><br>
</div>
<div>System is
working fine
when GPU is
not plugged
in.</div>
<div><b><br>
</b></div>
<div><b>This is
the last
console log
before freeze:</b></div>
<div>[drm]
amdgpu kernel
modesetting
enabled.
</div>
[drm]
initializing
kernel
modesetting
(POLARIS12
0x1002:0x6987
0x1787:0x2389
0x80). <br>
[drm] register
mmio base:
0x20200000
<br>
fsl-fman-port
ffe488000.port
fm1-gb0: renamed
from eth0
<br>
[drm] register
mmio size:
262144
<br>
[drm] add ip
block number 0
<vi_common>
<br>
[drm] add ip
block number 1
<gmc_v8_0>
<br>
[drm] add ip
block number 2
<tonga_ih>
<br>
[drm] add ip
block number 3
<powerplay>
<br>
[drm] add ip
block number 4
<dm>
<br>
[drm] add ip
block number 5
<gfx_v8_0>
<br>
[drm] add ip
block number 6
<sdma_v3_0>
<br>
[drm] add ip
block number 7
<uvd_v6_0>
<br>
[drm] add ip
block number 8
<vce_v3_0>
<br>
[drm] UVD is
enabled in VM
mode
<br>
[drm] UVD ENC is
enabled in VM
mode
<br>
[drm] VCE
enabled in VM
mode
<br>
ATOM BIOS:
113-ER16BFC-001
<br>
[drm] GPU
posting now...
<br>
Disabling lock
debugging due to
kernel taint
<br>
Machine check in
kernel mode.
<br>
Caused by (from
MCSR=a000): Load
Error Report
<br>
Guarded Load
Error Report
<br>
Kernel panic -
not syncing:
Unrecoverable
Machine check
<br>
CPU: 1 PID: 2023
Comm: udevd
Tainted: G M
4.19.26+gc0c2141
#1 <br>
Call Trace:
<br>
</div>
</blockquote>
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<blockquote type="cite">
<div dir="ltr">
<br>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
amd-gfx mailing list
<a href="mailto:amd-gfx@lists.freedesktop.org" target="_blank">amd-gfx@lists.freedesktop.org</a>
<a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=02%7C01%7Cchristian.koenig%40amd.com%7C561d9d3206ff46d338ad08d777ef717c%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637109742603335427&sdata=DstGsDW0X7ennQoF1vg%2FYLGAStF4p1dAeMFhzsAFc1I%3D&reserved=0" target="_blank">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a></pre>
</blockquote>
<br>
</div>
</blockquote>
<div>
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Christian
König <<a href="mailto:ckoenig.leichtzumerken@gmail.com" target="_blank">ckoenig.leichtzumerken@gmail.com</a>>, 2 Ara
2019 Pzt, 15:28
tarihinde şunu
yazdı:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div>Hi Yusuf,<br>
<br>
Am 02.12.19 um
12:41 schrieb
Yusuf
Altıparmak:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>My
embedded board
is freezing
when I put
E9171 on PCIe.
What is the
meaning of
Unrecoverable
Machine Check
error about
GPU? <br>
</div>
</div>
</blockquote>
<br>
Well see the
explanation on
Wikipedia for
example: <a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FMachine-check_exception&data=02%7C01%7Cchristian.koenig%40amd.com%7C561d9d3206ff46d338ad08d777ef717c%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637109742603345420&sdata=NtHiZmL7me4JRZR4L9KHZzpD8Zcn6caURVvtiDSgHsE%3D&reserved=0" target="_blank">https://en.wikipedia.org/wiki/Machine-check_exception</a><br>
<br>
In general it
means you have
messed up
something in
your hardware
configuration.<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>Could
PCIe settings
in .dts file
cause this
problem?</div>
</div>
</blockquote>
<br>
Possible, but
rather unlikely.
My best guess is
that it is some
problem with the
power supply.<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div> If it
is, is there
any sample
PCIe
configuration
for E9171?</div>
</div>
</blockquote>
<br>
The E9171 is
just a PCIe
device, so the
dtsi is actually
rather
uninteresting.
What we really
need is a full
dmesg and maybe
lspci output
would help as
well.<br>
<br>
Regards,<br>
Christian.</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>Hi Christian,</div>
<div><br>
</div>
<div>At first, I am
using NXP
T1042D4RDB-64B
which has 256 MB
PCIe buffer
according to its.
PCIe memory range
was arranged to
256 MB in .dts
file and in U-boot
configuration
file. Driver was
giving error with
exit code -12
(OUT_OF_MEMORY).
But I was able to
reach the linux
console. <br>
</div>
<div><br>
</div>
<div>[ 5.512922]
[drm] amdgpu
kernel modesetting
enabled.<br>
[ 5.517065]
[drm] initializing
kernel modesetting
(POLARIS12
0x1002:0x6987
0x1787:0x2389
0x80).<br>
[ 5.524507]
amdgpu
0001:01:00.0:
Fatal error during
GPU init<br>
[ 5.529296]
amdgpu: probe of
0001:01:00.0
failed with error
-12<br>
</div>
<div> <br>
</div>
</div>
Then I canged 256 MB
to 4GB in .dtsi and
U-boot conf file. I
also changed 64KB I/O
size to 1MB . When I
do this, I wasn't able
to reach the linux
console because board
was freezing. But
driver was successfull
at this time. I
already mentioned
successfull driver
console logs up.<br>
</div>
<div><br>
</div>
<div>
<div><b>this is lspci
-v when GPU is
plugged and Memory
size is 256 MB.</b></div>
<div><br>
</div>
<div>root@t1042d4rdb-64b:~#
lspci -v<br>
0000:00:00.0 PCI
bridge: Freescale
Semiconductor Inc
Device 0824 (rev 11)
(prog-if 00 [Normal
decode])<br>
Device tree
node:
/sys/firmware/devicetree/base/pcie@ffe240000/pcie@0<br>
Flags: bus
master, fast devsel,
latency 0, IRQ 20<br>
Memory at
<ignored>
(32-bit,
non-prefetchable)<br>
Bus:
primary=00,
secondary=01,
subordinate=01,
sec-latency=0<br>
I/O behind
bridge:
00000000-0000ffff
[size=64K]<br>
Memory
behind bridge:
e0000000-efffffff
[size=256M]<br>
Prefetchable
memory behind
bridge: None<br>
Capabilities: [44]
Power Management
version 3<br>
Capabilities: [4c]
Express Root Port
(Slot-), MSI 00<br>
Capabilities: [100]
Advanced Error
Reporting<br>
Kernel
driver in use:
pcieport<br>
<br>
0001:00:00.0 PCI
bridge: Freescale
Semiconductor Inc
Device 0824 (rev 11)
(prog-if 00 [Normal
decode])<br>
Device tree
node:
/sys/firmware/devicetree/base/pcie@ffe250000/pcie@0<br>
Flags: bus
master, fast devsel,
latency 0, IRQ 21<br>
Memory at
<ignored>
(32-bit,
non-prefetchable)<br>
Bus:
primary=00,
secondary=01,
subordinate=01,
sec-latency=0<br>
I/O behind
bridge:
00000000-0000ffff
[size=64K]<br>
Memory
behind bridge:
e0000000-efffffff
[size=256M]<br>
Prefetchable
memory behind
bridge: None<br>
Capabilities: [44]
Power Management
version 3<br>
Capabilities: [4c]
Express Root Port
(Slot-), MSI 00<br>
Capabilities: [100]
Advanced Error
Reporting<br>
Kernel
driver in use:
pcieport<br>
<br>
0001:01:00.0 VGA
compatible
controller: Advanced
Micro Devices, Inc.
[AMD/ATI] Lexa
[Radeon E9171 MCM]
(rev 80) (prog-if 00
[VGA controller])<br>
Subsystem:
Hightech Information
System Ltd. Device
2389<br>
Flags: fast
devsel, IRQ 41<br>
Memory at
c10000000 (64-bit,
prefetchable)
[size=256M]<br>
Memory at
<ignored>
(64-bit,
prefetchable)<br>
I/O ports at
1100 [size=256]<br>
Memory at
<ignored>
(32-bit,
non-prefetchable)<br>
Expansion
ROM at
<ignored>
[disabled]<br>
Capabilities: [48]
Vendor Specific
Information: Len=08
<?><br>
Capabilities: [50]
Power Management
version 3<br>
Capabilities: [58]
Express Legacy
Endpoint, MSI 00<br>
Capabilities: [a0]
MSI: Enable-
Count=1/1 Maskable-
64bit+<br>
Capabilities: [100]
Vendor Specific
Information: ID=0001
Rev=1 Len=010
<?><br>
Capabilities: [150]
Advanced Error
Reporting<br>
Capabilities: [200]
Resizable BAR
<?><br>
Capabilities: [270]
Secondary PCI
Express <?><br>
Capabilities: [2b0]
Address Translation
Service (ATS)<br>
Capabilities: [2c0]
Page Request
Interface (PRI)<br>
Capabilities: [2d0]
Process Address
Space ID (PASID)<br>
Capabilities: [320]
Latency Tolerance
Reporting<br>
Capabilities: [328]
Alternative
Routing-ID
Interpretation (ARI)<br>
Capabilities: [370]
L1 PM Substates<br>
Kernel
modules: amdgpu<br>
<br>
0001:01:00.1 Audio
device: Advanced
Micro Devices, Inc.
[AMD/ATI] Device
aae0<br>
Subsystem:
Hightech Information
System Ltd. Device
aae0<br>
Flags: bus
master, fast devsel,
latency 0, IRQ 17<br>
Memory at
<ignored>
(64-bit,
non-prefetchable)<br>
Capabilities: [48]
Vendor Specific
Information: Len=08
<?><br>
Capabilities: [50]
Power Management
version 3<br>
Capabilities: [58]
Express Legacy
Endpoint, MSI 00<br>
Capabilities: [a0]
MSI: Enable-
Count=1/1 Maskable-
64bit+<br>
Capabilities: [100]
Vendor Specific
Information: ID=0001
Rev=1 Len=010
<?><br>
Capabilities: [150]
Advanced Error
Reporting<br>
Capabilities: [328]
Alternative
Routing-ID
Interpretation (ARI)<br>
<br>
0002:00:00.0 PCI
bridge: Freescale
Semiconductor Inc
Device 0824 (rev 11)
(prog-if 00 [Normal
decode])<br>
Device tree
node:
/sys/firmware/devicetree/base/pcie@ffe260000/pcie@0<br>
Flags: bus
master, fast devsel,
latency 0, IRQ 22<br>
Memory at
<ignored>
(32-bit,
non-prefetchable)<br>
Bus:
primary=00,
secondary=01,
subordinate=01,
sec-latency=0<br>
I/O behind
bridge:
00000000-0000ffff
[size=64K]<br>
Memory
behind bridge:
e0000000-efffffff
[size=256M]<br>
Prefetchable
memory behind
bridge: None<br>
Capabilities: [44]
Power Management
version 3<br>
Capabilities: [4c]
Express Root Port
(Slot-), MSI 00<br>
Capabilities: [100]
Advanced Error
Reporting<br>
Kernel
driver in use:
pcieport<br>
<br>
0003:00:00.0 PCI
bridge: Freescale
Semiconductor Inc
Device 0824 (rev 11)
(prog-if 00 [Normal
decode])<br>
Device tree
node:
/sys/firmware/devicetree/base/pcie@ffe270000/pcie@0<br>
Flags: bus
master, fast devsel,
latency 0, IRQ 23<br>
Memory at
<ignored>
(32-bit,
non-prefetchable)<br>
Bus:
primary=00,
secondary=01,
subordinate=01,
sec-latency=0<br>
I/O behind
bridge:
00000000-0000ffff
[size=64K]<br>
Memory
behind bridge:
e0000000-efffffff
[size=256M]<br>
Prefetchable
memory behind
bridge: None<br>
Capabilities: [44]
Power Management
version 3<br>
Capabilities: [4c]
Express Root Port
(Slot-), MSI 00<br>
Capabilities: [100]
Advanced Error
Reporting<br>
Kernel
driver in use:
pcieport</div>
<div><br>
</div>
</div>
<div><b>AND This is PCIe
dmesg message when
memory range is
256MB. It's also
giving same message
when memory range is
arranged as 4GB;</b></div>
<div><br>
</div>
<div>PCI host bridge
/pcie@ffe240000
ranges:<br>
MEM
0x0000000c00000000..0x0000000c0fffffff
->
0x00000000e0000000 <br>
IO
0x0000000ff8000000..0x0000000ff800ffff
->
0x0000000000000000<br>
/pcie@ffe240000:
PCICSRBAR @ 0xff000000<br>
setup_pci_atmu: end of
DRAM 200000000<br>
/pcie@ffe240000: Setup
64-bit PCI DMA window<br>
/pcie@ffe240000:
WARNING: Outbound
window cfg leaves gaps
in memory map.
Adjusting the memory
map could reduce
unnecessary bounce
buffering.<br>
/pcie@ffe240000: DMA
window size is
0xe0000000<br>
Found FSL PCI host
bridge at
0x0000000ffe250000.
Firmware bus number:
0->1<br>
PCI host bridge
/pcie@ffe250000
ranges:<br>
MEM
0x0000000c10000000..0x0000000c1fffffff
->
0x00000000e0000000 <br>
IO
0x0000000ff8010000..0x0000000ff801ffff
->
0x0000000000000000<br>
/pcie@ffe250000:
PCICSRBAR @ 0xff000000<br>
setup_pci_atmu: end of
DRAM 200000000<br>
/pcie@ffe250000: Setup
64-bit PCI DMA window<br>
/pcie@ffe250000:
WARNING: Outbound
window cfg leaves gaps
in memory map.
Adjusting the memory
map could reduce
unnecessary bounce
buffering.<br>
/pcie@ffe250000: DMA
window size is
0xe0000000<br>
Found FSL PCI host
bridge at
0x0000000ffe260000.
Firmware bus number:
0->0<br>
PCI host bridge
/pcie@ffe260000
ranges:<br>
MEM
0x0000000c20000000..0x0000000c2fffffff
->
0x00000000e0000000 <br>
IO
0x0000000ff8020000..0x0000000ff802ffff
->
0x0000000000000000<br>
/pcie@ffe260000:
PCICSRBAR @ 0xff000000<br>
setup_pci_atmu: end of
DRAM 200000000<br>
/pcie@ffe260000: Setup
64-bit PCI DMA window<br>
/pcie@ffe260000:
WARNING: Outbound
window cfg leaves gaps
in memory map.
Adjusting the memory
map could reduce
unnecessary bounce
buffering.<br>
/pcie@ffe260000: DMA
window size is
0xe0000000<br>
Found FSL PCI host
bridge at
0x0000000ffe270000.
Firmware bus number:
0->0<br>
PCI host bridge
/pcie@ffe270000
ranges:<br>
MEM
0x0000000c30000000..0x0000000c3fffffff
->
0x00000000e0000000 <br>
IO
0x0000000ff8030000..0x0000000ff803ffff
->
0x0000000000000000<br>
/pcie@ffe270000:
PCICSRBAR @ 0xff000000<br>
setup_pci_atmu: end of
DRAM 200000000<br>
/pcie@ffe270000: Setup
64-bit PCI DMA window<br>
/pcie@ffe270000:
WARNING: Outbound
window cfg leaves gaps
in memory map.
Adjusting the memory
map could reduce
unnecessary bounce
buffering.<br>
/pcie@ffe270000: DMA
window size is
0xe0000000<br>
iommu: Adding device
ff6000000.qman-portal
to group 0<br>
iommu: Adding device
ff6004000.qman-portal
to group 1<br>
iommu: Adding device
ff6008000.qman-portal
to group 2<br>
iommu: Adding device
ff600c000.qman-portal
to group 3<br>
iommu: Adding device
ff6010000.qman-portal
to group 4<br>
iommu: Adding device
ff6014000.qman-portal
to group 5<br>
iommu: Adding device
ff6018000.qman-portal
to group 6<br>
iommu: Adding device
ff601c000.qman-portal
to group 7<br>
iommu: Adding device
ff6020000.qman-portal
to group 8<br>
iommu: Adding device
ff6024000.qman-portal
to group 9<br>
iommu: Adding device
ffe100300.dma to group
10<br>
iommu: Adding device
ffe101300.dma to group
11<br>
iommu: Adding device
ffe114000.sdhc to
group 12<br>
iommu: Adding device
ffe210000.usb to group
13<br>
iommu: Adding device
ffe211000.usb to group
14<br>
iommu: Adding device
ffe220000.sata to
group 15<br>
iommu: Adding device
ffe221000.sata to
group 16<br>
iommu: Adding device
ffe318000.qman to
group 17<br>
iommu: Adding device
ffe31a000.bman to
group 18<br>
iommu: Adding device
ffe240000.pcie to
group 19<br>
iommu: Adding device
ffe250000.pcie to
group 20<br>
iommu: Adding device
ffe260000.pcie to
group 21<br>
iommu: Adding device
ffe270000.pcie to
group 22<br>
iommu: Adding device
ffe140000.qe to group
23<br>
software IO TLB:
mapped [mem
0xfbfff000-0xfffff000]
(64MB)<br>
PCI: Probing PCI
hardware<br>
fsl-pci
ffe240000.pcie: PCI
host bridge to bus
0000:00<br>
pci_bus 0000:00: root
bus resource [io
0x8000080000010000-0x800008000001ffff]
(bus address
[0x0000-0xffff])<br>
pci_bus 0000:00: root
bus resource [mem
0xc00000000-0xc0fffffff]
(bus address
[0xe0000000-0xefffffff])<br>
pci_bus 0000:00: root
bus resource [bus 00]<br>
iommu: Removing device
ffe240000.pcie from
group 19<br>
iommu: Adding device
0000:00:00.0 to group
24<br>
pci 0000:00:00.0:
bridge configuration
invalid ([bus 00-00]),
reconfiguring<br>
pci 0000:00:00.0: PCI
bridge to [bus 01-ff]<br>
fsl-pci
ffe250000.pcie: PCI
host bridge to bus
0001:00<br>
pci_bus 0001:00: root
bus resource [io
0x8000080000021000-0x8000080000030fff]
(bus address
[0x0000-0xffff])<br>
pci_bus 0001:00: root
bus resource [mem
0xc10000000-0xc1fffffff]
(bus address
[0xe0000000-0xefffffff])<br>
pci_bus 0001:00: root
bus resource [bus
00-01]<br>
iommu: Removing device
ffe250000.pcie from
group 20<br>
iommu: Adding device
0001:00:00.0 to group
19<br>
pci 0001:01:00.0:
enabling Extended Tags<br>
pci 0001:01:00.0:
4.000 Gb/s available
PCIe bandwidth,
limited by 5 GT/s x1
link at 0001:00:00.0
(capable of 63.008
Gb/s with 8 GT/s x8
link)<br>
iommu: Adding device
0001:01:00.0 to group
19<br>
pci 0001:01:00.1:
enabling Extended Tags<br>
iommu: Adding device
0001:01:00.1 to group
19<br>
pci 0001:00:00.0: PCI
bridge to [bus 01-ff]<br>
fsl-pci
ffe260000.pcie: PCI
host bridge to bus
0002:00<br>
pci_bus 0002:00: root
bus resource [io
0x8000080000032000-0x8000080000041fff]
(bus address
[0x0000-0xffff])<br>
pci_bus 0002:00: root
bus resource [mem
0xc20000000-0xc2fffffff]
(bus address
[0xe0000000-0xefffffff])<br>
pci_bus 0002:00: root
bus resource [bus 00]<br>
iommu: Removing device
ffe260000.pcie from
group 21<br>
iommu: Adding device
0002:00:00.0 to group
20<br>
pci 0002:00:00.0:
bridge configuration
invalid ([bus 00-00]),
reconfiguring<br>
pci 0002:00:00.0: PCI
bridge to [bus 01-ff]<br>
fsl-pci
ffe270000.pcie: PCI
host bridge to bus
0003:00<br>
pci_bus 0003:00: root
bus resource [io
0x8000080000043000-0x8000080000052fff]
(bus address
[0x0000-0xffff])<br>
pci_bus 0003:00: root
bus resource [mem
0xc30000000-0xc3fffffff]
(bus address
[0xe0000000-0xefffffff])<br>
pci_bus 0003:00: root
bus resource [bus 00]<br>
iommu: Removing device
ffe270000.pcie from
group 22<br>
iommu: Adding device
0003:00:00.0 to group
21<br>
pci 0003:00:00.0:
bridge configuration
invalid ([bus 00-00]),
reconfiguring<br>
pci 0003:00:00.0: PCI
bridge to [bus 01-ff]<br>
PCI: Cannot allocate
resource region 0 of
device 0000:00:00.0,
will remap<br>
PCI: Cannot allocate
resource region 0 of
device 0001:00:00.0,
will remap<br>
PCI: Cannot allocate
resource region 2 of
device 0001:01:00.0,
will remap<br>
PCI: Cannot allocate
resource region 5 of
device 0001:01:00.0,
will remap<br>
PCI: Cannot allocate
resource region 6 of
device 0001:01:00.0,
will remap<br>
PCI: Cannot allocate
resource region 0 of
device 0001:01:00.1,
will remap<br>
PCI: Cannot allocate
resource region 0 of
device 0002:00:00.0,
will remap<br>
PCI: Cannot allocate
resource region 0 of
device 0003:00:00.0,
will remap<br>
pci 0000:00:00.0: BAR
0: no space for [mem
size 0x01000000]<br>
pci 0000:00:00.0: BAR
0: failed to assign
[mem size 0x01000000]<br>
pci 0000:00:00.0: PCI
bridge to [bus 01]<br>
pci 0000:00:00.0:
bridge window [io
0x8000080000010000-0x800008000001ffff]<br>
pci 0000:00:00.0:
bridge window [mem
0xc00000000-0xc0fffffff]<br>
pci_bus 0000:00: Some
PCI device resources
are unassigned, try
booting with
pci=realloc<br>
pci 0001:00:00.0: BAR
0: no space for [mem
size 0x01000000]<br>
pci 0001:00:00.0: BAR
0: failed to assign
[mem size 0x01000000]<br>
pci 0001:00:00.0: BAR
9: no space for [mem
size 0x00200000 64bit
pref]<br>
pci 0001:00:00.0: BAR
9: failed to assign
[mem size 0x00200000
64bit pref]<br>
pci 0001:01:00.0: BAR
2: no space for [mem
size 0x00200000 64bit
pref]<br>
pci 0001:01:00.0: BAR
2: failed to assign
[mem size 0x00200000
64bit pref]<br>
pci 0001:01:00.0: BAR
5: no space for [mem
size 0x00040000]<br>
pci 0001:01:00.0: BAR
5: failed to assign
[mem size 0x00040000]<br>
pci 0001:01:00.0: BAR
6: no space for [mem
size 0x00020000 pref]<br>
pci 0001:01:00.0: BAR
6: failed to assign
[mem size 0x00020000
pref]<br>
pci 0001:01:00.1: BAR
0: no space for [mem
size 0x00004000 64bit]<br>
pci 0001:01:00.1: BAR
0: failed to assign
[mem size 0x00004000
64bit]<br>
pci 0001:00:00.0: PCI
bridge to [bus 01]<br>
pci 0001:00:00.0:
bridge window [io
0x8000080000021000-0x8000080000030fff]<br>
pci 0001:00:00.0:
bridge window [mem
0xc10000000-0xc1fffffff]<br>
pci_bus 0001:00: Some
PCI device resources
are unassigned, try
booting with
pci=realloc<br>
pci 0002:00:00.0: BAR
0: no space for [mem
size 0x01000000]<br>
pci 0002:00:00.0: BAR
0: failed to assign
[mem size 0x01000000]<br>
pci 0002:00:00.0: PCI
bridge to [bus 01]<br>
pci 0002:00:00.0:
bridge window [io
0x8000080000032000-0x8000080000041fff]<br>
pci 0002:00:00.0:
bridge window [mem
0xc20000000-0xc2fffffff]<br>
pci_bus 0002:00: Some
PCI device resources
are unassigned, try
booting with
pci=realloc<br>
pci 0003:00:00.0: BAR
0: no space for [mem
size 0x01000000]<br>
pci 0003:00:00.0: BAR
0: failed to assign
[mem size 0x01000000]<br>
pci 0003:00:00.0: PCI
bridge to [bus 01]<br>
pci 0003:00:00.0:
bridge window [io
0x8000080000043000-0x8000080000052fff]<br>
pci 0003:00:00.0:
bridge window [mem
0xc30000000-0xc3fffffff]<br>
pci_bus 0003:00: Some
PCI device resources
are unassigned, try
booting with
pci=realloc<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
amd-gfx mailing list
<a href="mailto:amd-gfx@lists.freedesktop.org" target="_blank">amd-gfx@lists.freedesktop.org</a>
<a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=02%7C01%7Cchristian.koenig%40amd.com%7C561d9d3206ff46d338ad08d777ef717c%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637109742603345420&sdata=PO02mQtDBnkAdNfCn%2Fp7QmKX8IbJ7zke8edrfhsM6Mg%3D&reserved=0" target="_blank">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a></pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote></div></div>
</blockquote></div>