<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Yusuf,<br>
<br>
Am 02.12.19 um 15:20 schrieb Yusuf Altıparmak:<br>
</div>
<blockquote type="cite"
cite="mid:CAGzVRjzELaG_CToBxUWzh+kadp3qUQY6RQSGHMO1W1eSs+d-_w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<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> That is an expected result. 256MB is not enough for
the VRAM BAR and the doorbell BAR to fit into. But you
can still use VGA emulation that way if I'm not
completely mistaken.<br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Hmm, then what procedure should I follow to take a VGA
output. It seems Graphic Card does not have a VGA output.
And isn't there any way to use this GPU with a 256MB
buffered PCIe?<br>
</div>
</div>
</div>
</blockquote>
<br>
Most likely not. There is support for resizing the VRAM BAR, but
usually you can only make it larger and not smaller.<br>
<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>
<br>
<blockquote type="cite"
cite="mid:CAGzVRjzELaG_CToBxUWzh+kadp3qUQY6RQSGHMO1W1eSs+d-_w@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<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">Then I canged 256 MB to 4GB in
.dtsi and U-boot conf file.</blockquote>
How did you do this? Is your memory layout consistent?<br>
<br>
See when you just changed one end address you might need
to adjust other addresses as well.<br>
<br>
Regards,<br>
Christian.<br>
</div>
</div>
</blockquote>
<div> </div>
<div>It's not consistent I seems. At first I changed .dtsi
like it's consistent. I only changed PCIe1 Device Memory and
I/O range. It gave same error. Then I also changed PCIe2 and
PCIe3 devices starting adress according to PCIe1 device end
adress in .dtsi. I am not sure I made this correctly or not
but it gave same result again. This is why I asked "If it
is, is there any sample PCIe configuration for E9171?".</div>
</div>
</div>
</blockquote>
<br>
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>
<br>
<blockquote type="cite"
cite="mid:CAGzVRjzELaG_CToBxUWzh+kadp3qUQY6RQSGHMO1W1eSs+d-_w@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote"><b>This is a code piece from my
T104xRDB.h file which is contain PCIe configuration
variables for U-boot. I made changes like it's not
consistent. RAM size is 8 GB.<br>
</b></div>
</div>
</blockquote>
<br>
Sorry, no idea if that is correct or not. You need to ask NXP for
help with that.<br>
<br>
Regards,<br>
Christian.<br>
<br>
<blockquote type="cite"
cite="mid:CAGzVRjzELaG_CToBxUWzh+kadp3qUQY6RQSGHMO1W1eSs+d-_w@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">#ifdef CONFIG_PCI<br>
/* controller 1, direct to uli, tgtid 3, Base address 20000 */<br>
#ifdef CONFIG_PCIE1<br>
#define CONFIG_SYS_PCIE1_MEM_VIRT <b>0x80000000</b><br>
#define CONFIG_SYS_PCIE1_MEM_BUS 0xe0000000<br>
#define CONFIG_SYS_PCIE1_MEM_PHYS 0xc00000000ull<br>
#define CONFIG_SYS_PCIE1_MEM_SIZE <b>0x10000000 /* 256M */</b><br>
#define CONFIG_SYS_PCIE1_IO_VIRT 0xf8000000<br>
#define CONFIG_SYS_PCIE1_IO_BUS 0x00000000<br>
#define CONFIG_SYS_PCIE1_IO_PHYS <b>0xff8000000ull</b><br>
#define CONFIG_SYS_PCIE1_IO_SIZE <b>0x00010000 /* 64k */</b><br>
#endif<br>
<br>
/* controller 2, Slot 2, tgtid 2, Base address 201000 */<br>
#ifdef CONFIG_PCIE2<br>
#define CONFIG_SYS_PCIE2_MEM_VIRT <b>0x90000000</b><br>
#define CONFIG_SYS_PCIE2_MEM_BUS 0xe0000000<br>
#define CONFIG_SYS_PCIE2_MEM_PHYS 0xc10000000ull<br>
#define CONFIG_SYS_PCIE2_MEM_SIZE<b> 0x100000000 /* 4GB */</b><br>
#define CONFIG_SYS_PCIE2_IO_VIRT 0xf8010000<br>
#define CONFIG_SYS_PCIE2_IO_BUS 0x00000000<br>
#define CONFIG_SYS_PCIE2_IO_PHYS 0xff8010000ull<br>
#define CONFIG_SYS_PCIE2_IO_SIZE <b>0x00100000 /* 1M */</b><br>
#endif<br>
<br>
/* controller 3, Slot 1, tgtid 1, Base address 202000 */<br>
#ifdef CONFIG_PCIE3<br>
#define CONFIG_SYS_PCIE3_MEM_VIRT <b>0x190000000 /* I changed
this to 0x190000000 instead of 0xa0000000 because PCIE2 end
adress is changed. End adress is to 4 GB (0x100000000 hex so
I added 0x90000000 with 100000000) */</b><br>
#define CONFIG_SYS_PCIE3_MEM_BUS 0xe0000000<br>
#define CONFIG_SYS_PCIE3_MEM_PHYS 0xd10000000ull<br>
#define CONFIG_SYS_PCIE3_MEM_SIZE 0x10000000 /* 256M */<br>
#define CONFIG_SYS_PCIE3_IO_VIRT 0xf8110000<br>
#define CONFIG_SYS_PCIE3_IO_BUS 0x00000000<br>
#define CONFIG_SYS_PCIE3_IO_PHYS <b>0xff8110000ull /* Did
same things for IO </b><br>
#define CONFIG_SYS_PCIE3_IO_SIZE 0x00010000 /* 64k */<br>
#endif<br>
<br>
/* controller 4, Base address 203000 */<br>
#ifdef CONFIG_PCIE4<br>
#define CONFIG_SYS_PCIE4_MEM_VIRT <b>0x200000000 /* SAME STEP
WITH PCIE3. This time I added with 256 MB (0x10000000) */</b><br>
#define CONFIG_SYS_PCIE4_MEM_BUS 0xe0000000<br>
#define CONFIG_SYS_PCIE4_MEM_PHYS 0xd20000000ull<br>
#define CONFIG_SYS_PCIE4_MEM_SIZE 0x10000000 /* 256M */<br>
#define CONFIG_SYS_PCIE4_IO_VIRT 0xf8120000 <br>
#define CONFIG_SYS_PCIE4_IO_BUS 0x00000000<br>
#define CONFIG_SYS_PCIE4_IO_PHYS <b>0xff8120000ull /* Did
same things for IO </b><br>
#define CONFIG_SYS_PCIE4_IO_SIZE 0x00010000 /* 64k */<br>
#endif</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote"><br>
<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 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" moz-do-not-send="true">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%7C9be244504efb4ff9cc0a08d7772c1630%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637108903547899069&sdata=OL4UKczXinKq5FM3Cid5kYcESkHAl0esXfOB83AUPU8%3D&reserved=0" target="_blank" moz-do-not-send="true">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" moz-do-not-send="true">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%7C9be244504efb4ff9cc0a08d7772c1630%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637108903547909070&sdata=mBxI9LnRBO4iu5oyHc9OrrFj0K10SiOf5%2FztzmNedaI%3D&reserved=0"
target="_blank" moz-do-not-send="true">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 class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
amd-gfx mailing list
<a class="moz-txt-link-abbreviated" href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/amd-gfx">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a></pre>
</blockquote>
<br>
</body>
</html>