subject:"\[error\] Drm \-> amdgpu Unrecoverable Machine Check"

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2020-01-02 Thread Yusuf Altıparmak

Hello Christian,

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;

pci0: pcie@ffe24 {
reg = <0xf 0xfe24 0 0x1>;
ranges = <0x0200 0 0xe000 0x2 0x0 0x0 0x1000
 0x0100 0 0x0 0xf 0xf800 0x0 0x0001>;
pcie@0 {
ranges = <0x0200 0 0xe000
 0x0200 0 0xe000
 0 0x1000

 0x0100 0 0x
 0x0100 0 0x
 0 0x0001>;
};
};

pci1: pcie@ffe25 { // GPU CONNECTED TO THIS ONE
reg = <0xf 0xfe25 0 0x1>;
ranges = <0x0200 0 0xe000 0x2 0x1000 0x1 0x
 0x0100 0 0 0xf 0xf801 0 0x0001>;
pcie@0 {
ranges = <0x0200 0 0xe000
 0x0200 0 0xe000
 0x1 0x

 0x0100 0 0x
 0x0100 0 0x
 0 0x0001>;
};
};

pci2: pcie@ffe26 {
reg = <0xf 0xfe26 0 0x1>;
ranges = <0x0200 0 0xe000 0x3 0x2000 0 0x1000 // 0x3
0x2000 actually it must be 0x3 0x1000 because I gave 4 GB to pci1
but I also added 256 MB empty area between them. So it started from 0x3
0x2000
 0x0100 0 0x 0xf 0xf802 0 0x0001>;
pcie@0 {
ranges = <0x0200 0 0xe000
 0x0200 0 0xe000
 0 0x1000

 0x0100 0 0x
 0x0100 0 0x
 0 0x0001>;
};
};

pci3: pcie@ffe27 {
reg = <0xf 0xfe27 0 0x1>;
ranges = <0x0200 0 0xe000 0x3 0x3000 0 0x1000
 0x0100 0 0x 0xf 0xf803 0 0x0001>;
pcie@0 {
ranges = <0x0200 0 0xe000
 0x0200 0 0xe000
 0 0x1000

 0x0100 0 0x
 0x0100 0 0x
 0 0x0001>;
};
};



Yusuf Altıparmak , 3 Ara 2019 Sal, 22:20 tarihinde
şunu yazdı:

>
> 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.
>>
>
> Hmm this makes my job easier it seems.
>
>
>> 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?
>>
>> What could maybe work is VGA emulation, which essentially means text
>> only. But no guarantee for that this really works as expected.
>>
>> 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.
>
>
>
>> I am just wondering, does modern gaming motherboards have more than 4GB
>> PCIe buffer for this job ?
>>
>> They don't, resources are dynamically assigned instead.
>>
>> 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.
>>
>> 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.
>>
>> This way you can easily have 10 GPUs connected to your CPU.
>>
>> 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.
>
>
>
>> The problem you have here is that U-config doesn't do this resource
>> assignment automatically and you need to configure it manually.
>>
>
> 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.
>
> Best Regards.
>
>
>
>> Am 03.12.19 um 13:50 schrieb Yusuf Altıparmak:
>>
>>
>> Hi Christian,
>>
>>> 0001f000
>>>
>>> Exactly as I thought. The hardware does support BAR resize, but
>>> unfortunately 256MB is already the minimum.
>>>
>>> Sorry, but there isn't anything I could do from the GPU drivers point of
>>> view.
>>>
>>
>> Yes unfortunately there is nothing remained to about GPU side.
>>
>> 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.
>>>
>>>
>> 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

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-03 Thread Christian König


Right now I am trying to increase MMIO size config to 512 MB
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.


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?
What could maybe work is VGA emulation, which essentially means text 
only. But no guarantee for that this really works as expected.


I am just wondering, does modern gaming motherboards have more than 
4GB PCIe buffer for this job ?

They don't, resources are dynamically assigned instead.

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.


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.


This way you can easily have 10 GPUs connected to your CPU.

The problem you have here is that U-config doesn't do this resource 
assignment automatically and you need to configure it manually.


Regards,
Christian.

Am 03.12.19 um 13:50 schrieb Yusuf Altıparmak:


Hi Christian,


0001f000

Exactly as I thought. The hardware does support BAR resize, but
unfortunately 256MB is already the minimum.

Sorry, but there isn't anything I could do from the GPU drivers
point of view.


Yes unfortunately there is nothing remained to about GPU side.

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.


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.


But you definitely got an interesting use case here :)


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



Am 03.12.19 um 11:31 schrieb Yusuf Altıparmak:

Hello Christian,
My "setpci -s 0001:01:00.0 ECAP15+4.l ECAP15+8.l" output is;

0001f000
0820

Regards.



Yusuf Altıparmak mailto:yusufalti1...@gmail.com>>, 2 Ara 2019 Pzt, 19:31
tarihinde şunu yazdı:

Most likely not. There is support for resizing the VRAM
BAR, but usually you can only make it larger and not smaller.
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.


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 ?

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.
Sorry, no idea if that is correct or not. You need to ask
NXP for help with that.


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.

Thank you for your interest Christian.
Regards .



Am 02.12.19 um 14:32 schrieb Yusuf Altıparmak:




I attached my dts file.

System is working fine when GPU is not plugged in.
*
*
*This is the last console log before freeze:*
[drm] amdgpu kernel modesetting enabled.
[drm] initializing kernel modesetting
(POLARIS12 0x1002:0x6987 0x1787:0x2389 0x80).
[drm] register mmio base: 0x2020
fsl-fman-port ffe488000.port fm1-gb0: renamed
from eth0
[drm] register mmio size: 262144
[drm] add ip block number 0 
[drm] add ip block number 1 
[drm] add ip block number 2 
[drm] add ip block number 3 
[drm] add ip block number 4 
[drm] add ip block number 5 
[drm] add ip block number 6 
[drm] add ip

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-03 Thread Yusuf Altıparmak

Hi Christian,

> 0001f000
>
> Exactly as I thought. The hardware does support BAR resize, but
> unfortunately 256MB is already the minimum.
>
> Sorry, but there isn't anything I could do from the GPU drivers point of
> view.
>

Yes unfortunately there is nothing remained to about GPU side.

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.
>
>
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.



> But you definitely got an interesting use case here :)
>

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


Am 03.12.19 um 11:31 schrieb Yusuf Altıparmak:
>
> Hello Christian,
> My "setpci -s 0001:01:00.0 ECAP15+4.l ECAP15+8.l" output is;
>
> 0001f000
>
> 0820
>
> Regards.
>
>
>
> Yusuf Altıparmak , 2 Ara 2019 Pzt, 19:31
> tarihinde şunu yazdı:
>
>> Most likely not. There is support for resizing the VRAM BAR, but usually
>>> you can only make it larger and not smaller.
>>> 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.
>>>
>>
>> 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 ?
>>
>>
>>
>>> 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.
>>> Sorry, no idea if that is correct or not. You need to ask NXP for help
>>> with that.
>>>
>>>
>> 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.
>>
>> Thank you for your interest Christian.
>> Regards .
>>
>>
>>>
>>> Am 02.12.19 um 14:32 schrieb Yusuf Altıparmak:


> I attached my dts file.
>
> System is working fine when GPU is not plugged in.
>
> *This is the last console log before freeze:*
> [drm] amdgpu kernel modesetting enabled.
>
> [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6987
> 0x1787:0x2389 0x80).
> [drm] register mmio base: 0x2020
>
> fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0
>
> [drm] register mmio size: 262144
>
> [drm] add ip block number 0 
>
> [drm] add ip block number 1 
>
> [drm] add ip block number 2 
>
> [drm] add ip block number 3 
>
> [drm] add ip block number 4 
>
> [drm] add ip block number 5 
>
> [drm] add ip block number 6 
>
> [drm] add ip block number 7 
>
> [drm] add ip block number 8 
>
> [drm] UVD is enabled in VM mode
>
> [drm] UVD ENC is enabled in VM mode
>
> [drm] VCE enabled in VM mode
>
> ATOM BIOS: 113-ER16BFC-001
>
> [drm] GPU posting now...
>
> Disabling lock debugging due to kernel taint
>
> Machine check in kernel mode.
>
> Caused by (from MCSR=a000): Load Error Report
>
> Guarded Load Error Report
>
> Kernel panic - not syncing: Unrecoverable Machine check
>
> CPU: 1 PID: 2023 Comm: udevd Tainted: G   M
>  4.19.26+gc0c2141 #1
> Call Trace:
>
>
>
> ___
> amd-gfx mailing 
> listamd-gfx@lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/amd-gfx
>  
> 
>
>
>

 Christian König , 2 Ara 2019 Pzt,
 15:28 tarihinde şunu yazdı:

> Hi Yusuf,
>
> Am 02.12.19 um 12:41 schrieb Yusuf Altıparmak:
>
> My embedded board is freezing when I put E9171 on PCIe. What is the
> meaning of Unrecoverable Machine Check error about GPU?
>
>
> Well see the explanation on Wikipedia for example:
> https://en.wikipedia.org/wiki/Machine-check_exception
>

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-03 Thread Christian König


Hi Yusuf,


0001f000
Exactly as I thought. The hardware does support BAR resize, but 
unfortunately 256MB is already the minimum.


Sorry, but there isn't anything I could do from the GPU drivers point of 
view.


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.


But you definitely got an interesting use case here :)

Regards,
Christian.

Am 03.12.19 um 11:31 schrieb Yusuf Altıparmak:

Hello Christian,
My "setpci -s 0001:01:00.0 ECAP15+4.l ECAP15+8.l" output is;

0001f000
0820

Regards.



Yusuf Altıparmak >, 2 Ara 2019 Pzt, 19:31 tarihinde 
şunu yazdı:


Most likely not. There is support for resizing the VRAM BAR,
but usually you can only make it larger and not smaller.
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.


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 ?

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.
Sorry, no idea if that is correct or not. You need to ask NXP
for help with that.


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.

Thank you for your interest Christian.
Regards .



Am 02.12.19 um 14:32 schrieb Yusuf Altıparmak:




I attached my dts file.

System is working fine when GPU is not plugged in.
*
*
*This is the last console log before freeze:*
[drm] amdgpu kernel modesetting enabled.
[drm] initializing kernel modesetting (POLARIS12
0x1002:0x6987 0x1787:0x2389 0x80).
[drm] register mmio base: 0x2020
fsl-fman-port ffe488000.port fm1-gb0: renamed from
eth0
[drm] register mmio size: 262144
[drm] add ip block number 0 
[drm] add ip block number 1 
[drm] add ip block number 2 
[drm] add ip block number 3 
[drm] add ip block number 4 
[drm] add ip block number 5 
[drm] add ip block number 6 
[drm] add ip block number 7 
[drm] add ip block number 8 
[drm] UVD is enabled in VM mode
[drm] UVD ENC is enabled in VM mode
[drm] VCE enabled in VM mode
ATOM BIOS: 113-ER16BFC-001
[drm] GPU posting now...
Disabling lock debugging due to kernel taint
Machine check in kernel mode.
Caused by (from MCSR=a000): Load Error Report
Guarded Load Error Report
Kernel panic - not syncing: Unrecoverable Machine
check
CPU: 1 PID: 2023 Comm: udevd Tainted: G   M
 4.19.26+gc0c2141 #1
Call Trace:





___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org  

https://lists.freedesktop.org/mailman/listinfo/amd-gfx  





Christian König mailto:ckoenig.leichtzumer...@gmail.com>>, 2 Ara 2019
Pzt, 15:28 tarihinde şunu yazdı:

Hi Yusuf,

Am 02.12.19 um 12:41 schrieb Yusuf Altıparmak:

My embedded board is freezing when I put E9171 on
PCIe. What is the meaning of Unrecoverable Machine
Check error about GPU?


Well see the explanation on Wikipedia for example:
https://en.wikipedia.org/wiki/Machine-check_exception



In general it means you have messed up something in
your hardware configuration.


Could PCIe settings in .dts file

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-03 Thread Yusuf Altıparmak

Hello Christian,
My "setpci -s 0001:01:00.0 ECAP15+4.l ECAP15+8.l" output is;

0001f000

0820

Regards.



Yusuf Altıparmak , 2 Ara 2019 Pzt, 19:31 tarihinde
şunu yazdı:

> Most likely not. There is support for resizing the VRAM BAR, but usually
>> you can only make it larger and not smaller.
>> 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.
>>
>
> 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 ?
>
>
>
>> 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.
>> Sorry, no idea if that is correct or not. You need to ask NXP for help
>> with that.
>>
>>
> 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.
>
> Thank you for your interest Christian.
> Regards .
>
>
>>
>> Am 02.12.19 um 14:32 schrieb Yusuf Altıparmak:
>>>
>>>
 I attached my dts file.

 System is working fine when GPU is not plugged in.

 *This is the last console log before freeze:*
 [drm] amdgpu kernel modesetting enabled.

 [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6987
 0x1787:0x2389 0x80).
 [drm] register mmio base: 0x2020

 fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0

 [drm] register mmio size: 262144

 [drm] add ip block number 0 

 [drm] add ip block number 1 

 [drm] add ip block number 2 

 [drm] add ip block number 3 

 [drm] add ip block number 4 

 [drm] add ip block number 5 

 [drm] add ip block number 6 

 [drm] add ip block number 7 

 [drm] add ip block number 8 

 [drm] UVD is enabled in VM mode

 [drm] UVD ENC is enabled in VM mode

 [drm] VCE enabled in VM mode

 ATOM BIOS: 113-ER16BFC-001

 [drm] GPU posting now...

 Disabling lock debugging due to kernel taint

 Machine check in kernel mode.

 Caused by (from MCSR=a000): Load Error Report

 Guarded Load Error Report

 Kernel panic - not syncing: Unrecoverable Machine check

 CPU: 1 PID: 2023 Comm: udevd Tainted: G   M
  4.19.26+gc0c2141 #1
 Call Trace:



 ___
 amd-gfx mailing 
 listamd-gfx@lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/amd-gfx
  
 



>>>
>>> Christian König , 2 Ara 2019 Pzt,
>>> 15:28 tarihinde şunu yazdı:
>>>
 Hi Yusuf,

 Am 02.12.19 um 12:41 schrieb Yusuf Altıparmak:

 My embedded board is freezing when I put E9171 on PCIe. What is the
 meaning of Unrecoverable Machine Check error about GPU?


 Well see the explanation on Wikipedia for example:
 https://en.wikipedia.org/wiki/Machine-check_exception
 

 In general it means you have messed up something in your hardware
 configuration.

 Could PCIe settings in .dts file cause this problem?


 Possible, but rather unlikely. My best guess is that it is some problem
 with the power supply.

 If it is, is there any sample PCIe configuration for E9171?


 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.

 Regards,
 Christian.

>>>
>>>
>>> Hi Christian,
>>>
>>> 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.
>>>
>>> [5.512922] [drm] amdgpu kernel modesetting enabled.
>>> [5.517065] [drm] initializing kernel modesetting (POLARIS12
>>> 0x1002:0x6987 0x1787:0x2389 0x80).
>>> [5.524507] amdgpu 0001:01:00.0: Fatal error during GPU init
>>> [5.529296] amdgpu: probe of 0001:01:00.0 failed with error -12
>>>
>>> Then I

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-02 Thread Yusuf Altıparmak

>
> Most likely not. There is support for resizing the VRAM BAR, but usually
> you can only make it larger and not smaller.
> 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.
>

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 ?



> 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.
> Sorry, no idea if that is correct or not. You need to ask NXP for help
> with that.
>
>
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.

Thank you for your interest Christian.
Regards .


>
> Am 02.12.19 um 14:32 schrieb Yusuf Altıparmak:
>>
>>
>>> I attached my dts file.
>>>
>>> System is working fine when GPU is not plugged in.
>>>
>>> *This is the last console log before freeze:*
>>> [drm] amdgpu kernel modesetting enabled.
>>>
>>> [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6987
>>> 0x1787:0x2389 0x80).
>>> [drm] register mmio base: 0x2020
>>>
>>> fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0
>>>
>>> [drm] register mmio size: 262144
>>>
>>> [drm] add ip block number 0 
>>>
>>> [drm] add ip block number 1 
>>>
>>> [drm] add ip block number 2 
>>>
>>> [drm] add ip block number 3 
>>>
>>> [drm] add ip block number 4 
>>>
>>> [drm] add ip block number 5 
>>>
>>> [drm] add ip block number 6 
>>>
>>> [drm] add ip block number 7 
>>>
>>> [drm] add ip block number 8 
>>>
>>> [drm] UVD is enabled in VM mode
>>>
>>> [drm] UVD ENC is enabled in VM mode
>>>
>>> [drm] VCE enabled in VM mode
>>>
>>> ATOM BIOS: 113-ER16BFC-001
>>>
>>> [drm] GPU posting now...
>>>
>>> Disabling lock debugging due to kernel taint
>>>
>>> Machine check in kernel mode.
>>>
>>> Caused by (from MCSR=a000): Load Error Report
>>>
>>> Guarded Load Error Report
>>>
>>> Kernel panic - not syncing: Unrecoverable Machine check
>>>
>>> CPU: 1 PID: 2023 Comm: udevd Tainted: G   M
>>>  4.19.26+gc0c2141 #1
>>> Call Trace:
>>>
>>>
>>>
>>> ___
>>> amd-gfx mailing 
>>> listamd-gfx@lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>>  
>>> 
>>>
>>>
>>>
>>
>> Christian König , 2 Ara 2019 Pzt,
>> 15:28 tarihinde şunu yazdı:
>>
>>> Hi Yusuf,
>>>
>>> Am 02.12.19 um 12:41 schrieb Yusuf Altıparmak:
>>>
>>> My embedded board is freezing when I put E9171 on PCIe. What is the
>>> meaning of Unrecoverable Machine Check error about GPU?
>>>
>>>
>>> Well see the explanation on Wikipedia for example:
>>> https://en.wikipedia.org/wiki/Machine-check_exception
>>> 
>>>
>>> In general it means you have messed up something in your hardware
>>> configuration.
>>>
>>> Could PCIe settings in .dts file cause this problem?
>>>
>>>
>>> Possible, but rather unlikely. My best guess is that it is some problem
>>> with the power supply.
>>>
>>> If it is, is there any sample PCIe configuration for E9171?
>>>
>>>
>>> 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.
>>>
>>> Regards,
>>> Christian.
>>>
>>
>>
>> Hi Christian,
>>
>> 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.
>>
>> [5.512922] [drm] amdgpu kernel modesetting enabled.
>> [5.517065] [drm] initializing kernel modesetting (POLARIS12
>> 0x1002:0x6987 0x1787:0x2389 0x80).
>> [5.524507] amdgpu 0001:01:00.0: Fatal error during GPU init
>> [5.529296] amdgpu: probe of 0001:01:00.0 failed with error -12
>>
>> 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.
>>
>> *this is lspci -v when GPU is plugged and

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-02 Thread Christian König


Hi Yusuf,

Am 02.12.19 um 15:20 schrieb Yusuf Altıparmak:


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.


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?


Most likely not. There is support for resizing the VRAM BAR, but usually 
you can only make it larger and not smaller.


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.



Then I canged 256 MB to 4GB in .dtsi and U-boot conf file.

How did you do this? Is your memory layout consistent?

See when you just changed one end address you might need to adjust
other addresses as well.

Regards,
Christian.

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?".


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.




*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.

*


Sorry, no idea if that is correct or not. You need to ask NXP for help 
with that.


Regards,
Christian.



#ifdef CONFIG_PCI
/* controller 1, direct to uli, tgtid 3, Base address 2 */
#ifdef CONFIG_PCIE1
#define CONFIG_SYS_PCIE1_MEM_VIRT *0x8000*
#define CONFIG_SYS_PCIE1_MEM_BUS 0xe000
#define CONFIG_SYS_PCIE1_MEM_PHYS 0xcull
#define CONFIG_SYS_PCIE1_MEM_SIZE *0x1000 /* 256M */*
#define CONFIG_SYS_PCIE1_IO_VIRT 0xf800
#define CONFIG_SYS_PCIE1_IO_BUS 0x
#define CONFIG_SYS_PCIE1_IO_PHYS *0xff800ull*
#define CONFIG_SYS_PCIE1_IO_SIZE *0x0001 /* 64k */*
#endif

/* controller 2, Slot 2, tgtid 2, Base address 201000 */
#ifdef CONFIG_PCIE2
#define CONFIG_SYS_PCIE2_MEM_VIRT *0x9000*
#define CONFIG_SYS_PCIE2_MEM_BUS 0xe000
#define CONFIG_SYS_PCIE2_MEM_PHYS 0xc1000ull
#define CONFIG_SYS_PCIE2_MEM_SIZE*0x1 /* 4GB */*
#define CONFIG_SYS_PCIE2_IO_VIRT 0xf801
#define CONFIG_SYS_PCIE2_IO_BUS 0x
#define CONFIG_SYS_PCIE2_IO_PHYS 0xff801ull
#define CONFIG_SYS_PCIE2_IO_SIZE *0x0010 /* 1M */*
#endif

/* controller 3, Slot 1, tgtid 1, Base address 202000 */
#ifdef CONFIG_PCIE3
#define CONFIG_SYS_PCIE3_MEM_VIRT *0x19000 /* I changed this to 
0x19000 instead of 0xa000 because PCIE2 end adress is changed. 
End adress is to 4 GB (0x1 hex so I added 0x9000 with 
1) */*

#define CONFIG_SYS_PCIE3_MEM_BUS 0xe000
#define CONFIG_SYS_PCIE3_MEM_PHYS 0xd1000ull
#define CONFIG_SYS_PCIE3_MEM_SIZE 0x1000 /* 256M */
#define CONFIG_SYS_PCIE3_IO_VIRT 0xf811
#define CONFIG_SYS_PCIE3_IO_BUS 0x
#define CONFIG_SYS_PCIE3_IO_PHYS *0xff811ull /* Did same things 
for IO *

#define CONFIG_SYS_PCIE3_IO_SIZE 0x0001 /* 64k */
#endif

/* controller 4, Base address 203000 */
#ifdef CONFIG_PCIE4
#define CONFIG_SYS_PCIE4_MEM_VIRT *0x2 /* SAME STEP WITH 
PCIE3. This time I added with 256 MB (0x1000) */*

#define CONFIG_SYS_PCIE4_MEM_BUS 0xe000
#define CONFIG_SYS_PCIE4_MEM_PHYS 0xd2000ull
#define CONFIG_SYS_PCIE4_MEM_SIZE 0x1000 /* 256M */
#define CONFIG_SYS_PCIE4_IO_VIRT 0xf812
#define CONFIG_SYS_PCIE4_IO_BUS 0x
#define CONFIG_SYS_PCIE4_IO_PHYS *0xff812ull /* Did same things 
for IO *

#define CONFIG_SYS_PCIE4_IO_SIZE 0x0001 /* 64k */
#endif




Am 02.12.19 um 14:32 schrieb Yusuf Altıparmak:




I attached my dts file.

System is working fine when GPU is not plugged in.
*
*
*This is the last console log before freeze:*
[drm] amdgpu kernel modesetting enabled.
[drm] initializing kernel modesetting (POLARIS12
0x1002:0x6987 0x1787:0x2389 0x80).
[drm] register mmio base: 0x2020
fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0
[drm] register mmio size: 262144
[drm] add ip block number 0 
[drm] add ip block number 1 
[drm] add ip block number 2 
[drm] add ip block number 3 
[drm] add ip block number 4 
[drm] add ip block number 5 
[drm] add ip block number 6 
[drm] add ip block number 7 
[drm] add ip block number 8 
[drm] UVD is enabled in VM mode
[drm] UVD ENC is enabled in VM mode
[drm] VCE enabled in VM mode

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-02 Thread Yusuf Altıparmak

> 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.
>

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?



> Then I canged 256 MB to 4GB in .dtsi and U-boot conf file.
>
> How did you do this? Is your memory layout consistent?
>
> See when you just changed one end address you might need to adjust other
> addresses as well.
>
> Regards,
> Christian.
>

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?".


*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.*

#ifdef CONFIG_PCI
/* controller 1, direct to uli, tgtid 3, Base address 2 */
#ifdef CONFIG_PCIE1
#define CONFIG_SYS_PCIE1_MEM_VIRT *0x8000*
#define CONFIG_SYS_PCIE1_MEM_BUS 0xe000
#define CONFIG_SYS_PCIE1_MEM_PHYS 0xcull
#define CONFIG_SYS_PCIE1_MEM_SIZE *0x1000 /* 256M */*
#define CONFIG_SYS_PCIE1_IO_VIRT 0xf800
#define CONFIG_SYS_PCIE1_IO_BUS 0x
#define CONFIG_SYS_PCIE1_IO_PHYS *0xff800ull*
#define CONFIG_SYS_PCIE1_IO_SIZE *0x0001 /* 64k */*
#endif

/* controller 2, Slot 2, tgtid 2, Base address 201000 */
#ifdef CONFIG_PCIE2
#define CONFIG_SYS_PCIE2_MEM_VIRT *0x9000*
#define CONFIG_SYS_PCIE2_MEM_BUS 0xe000
#define CONFIG_SYS_PCIE2_MEM_PHYS 0xc1000ull
#define CONFIG_SYS_PCIE2_MEM_SIZE* 0x1 /* 4GB */*
#define CONFIG_SYS_PCIE2_IO_VIRT 0xf801
#define CONFIG_SYS_PCIE2_IO_BUS 0x
#define CONFIG_SYS_PCIE2_IO_PHYS 0xff801ull
#define CONFIG_SYS_PCIE2_IO_SIZE *0x0010 /* 1M */*
#endif

/* controller 3, Slot 1, tgtid 1, Base address 202000 */
#ifdef CONFIG_PCIE3
#define CONFIG_SYS_PCIE3_MEM_VIRT *0x19000 /* I changed this to
0x19000 instead of 0xa000 because PCIE2 end adress is changed. End
adress is to 4 GB (0x1 hex so I added 0x9000 with 1) */*
#define CONFIG_SYS_PCIE3_MEM_BUS 0xe000
#define CONFIG_SYS_PCIE3_MEM_PHYS 0xd1000ull
#define CONFIG_SYS_PCIE3_MEM_SIZE 0x1000 /* 256M */
#define CONFIG_SYS_PCIE3_IO_VIRT 0xf811
#define CONFIG_SYS_PCIE3_IO_BUS 0x
#define CONFIG_SYS_PCIE3_IO_PHYS *0xff811ull /* Did same things for IO *
#define CONFIG_SYS_PCIE3_IO_SIZE 0x0001 /* 64k */
#endif

/* controller 4, Base address 203000 */
#ifdef CONFIG_PCIE4
#define CONFIG_SYS_PCIE4_MEM_VIRT *0x2 /* SAME STEP WITH PCIE3.
This time I added with 256 MB (0x1000) */*
#define CONFIG_SYS_PCIE4_MEM_BUS 0xe000
#define CONFIG_SYS_PCIE4_MEM_PHYS 0xd2000ull
#define CONFIG_SYS_PCIE4_MEM_SIZE 0x1000 /* 256M */
#define CONFIG_SYS_PCIE4_IO_VIRT 0xf812
#define CONFIG_SYS_PCIE4_IO_BUS 0x
#define CONFIG_SYS_PCIE4_IO_PHYS *0xff812ull /* Did same things for IO *
#define CONFIG_SYS_PCIE4_IO_SIZE 0x0001 /* 64k */
#endif




Am 02.12.19 um 14:32 schrieb Yusuf Altıparmak:
>
>
>> I attached my dts file.
>>
>> System is working fine when GPU is not plugged in.
>>
>> *This is the last console log before freeze:*
>> [drm] amdgpu kernel modesetting enabled.
>>
>> [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6987
>> 0x1787:0x2389 0x80).
>> [drm] register mmio base: 0x2020
>>
>> fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0
>>
>> [drm] register mmio size: 262144
>>
>> [drm] add ip block number 0 
>>
>> [drm] add ip block number 1 
>>
>> [drm] add ip block number 2 
>>
>> [drm] add ip block number 3 
>>
>> [drm] add ip block number 4 
>>
>> [drm] add ip block number 5 
>>
>> [drm] add ip block number 6 
>>
>> [drm] add ip block number 7 
>>
>> [drm] add ip block number 8 
>>
>> [drm] UVD is enabled in VM mode
>>
>> [drm] UVD ENC is enabled in VM mode
>>
>> [drm] VCE enabled in VM mode
>>
>> ATOM BIOS: 113-ER16BFC-001
>>
>> [drm] GPU posting now...
>>
>> Disabling lock debugging due to kernel taint
>>
>> Machine check in kernel mode.
>>
>> Caused by (from MCSR=a000): Load Error Report
>>
>> Guarded Load Error Report
>>
>> Kernel panic - not syncing: Unrecoverable Machine check
>>
>> CPU: 1 PID: 2023 Comm: udevd Tainted: G   M  4.19.26+gc0c2141
>> #1
>> Call Trace:
>>
>>
>>
>> ___
>> amd-gfx mailing 
>> listamd-gfx@lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>  
>>

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-02 Thread Christian König


Hi Yusuf,

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.


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.



Then I canged 256 MB to 4GB in .dtsi and U-boot conf file.

How did you do this? Is your memory layout consistent?

See when you just changed one end address you might need to adjust other 
addresses as well.


Regards,
Christian.

Am 02.12.19 um 14:32 schrieb Yusuf Altıparmak:




I attached my dts file.

System is working fine when GPU is not plugged in.
*
*
*This is the last console log before freeze:*
[drm] amdgpu kernel modesetting enabled.
[drm] initializing kernel modesetting (POLARIS12 0x1002:0x6987
0x1787:0x2389 0x80).
[drm] register mmio base: 0x2020
fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0
[drm] register mmio size: 262144
[drm] add ip block number 0 
[drm] add ip block number 1 
[drm] add ip block number 2 
[drm] add ip block number 3 
[drm] add ip block number 4 
[drm] add ip block number 5 
[drm] add ip block number 6 
[drm] add ip block number 7 
[drm] add ip block number 8 
[drm] UVD is enabled in VM mode
[drm] UVD ENC is enabled in VM mode
[drm] VCE enabled in VM mode
ATOM BIOS: 113-ER16BFC-001
[drm] GPU posting now...
Disabling lock debugging due to kernel taint
Machine check in kernel mode.
Caused by (from MCSR=a000): Load Error Report
Guarded Load Error Report
Kernel panic - not syncing: Unrecoverable Machine check
CPU: 1 PID: 2023 Comm: udevd Tainted: G   M    4.19.26+gc0c2141 #1
Call Trace:





___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org  
https://lists.freedesktop.org/mailman/listinfo/amd-gfx  





Christian König >, 2 Ara 2019 Pzt, 15:28 
tarihinde şunu yazdı:


Hi Yusuf,

Am 02.12.19 um 12:41 schrieb Yusuf Altıparmak:

My embedded board is freezing when I put E9171 on PCIe. What is
the meaning of Unrecoverable Machine Check error about GPU?


Well see the explanation on Wikipedia for example:
https://en.wikipedia.org/wiki/Machine-check_exception



In general it means you have messed up something in your hardware
configuration.


Could PCIe settings in .dts file cause this problem?


Possible, but rather unlikely. My best guess is that it is some
problem with the power supply.


If it is, is there any sample PCIe configuration for E9171?


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.

Regards,
Christian.



Hi Christian,

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.


[    5.512922] [drm] amdgpu kernel modesetting enabled.
[    5.517065] [drm] initializing kernel modesetting (POLARIS12 
0x1002:0x6987 0x1787:0x2389 0x80).

[    5.524507] amdgpu 0001:01:00.0: Fatal error during GPU init
[    5.529296] amdgpu: probe of 0001:01:00.0 failed with error -12

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.


*this is lspci -v when GPU is plugged and Memory size is 256 MB.*

root@t1042d4rdb-64b:~# lspci -v
:00:00.0 PCI bridge: Freescale Semiconductor Inc Device 0824 (rev 
11) (prog-if 00 [Normal decode])
        Device tree node: 
/sys/firmware/devicetree/base/pcie@ffe24/pcie@0

        Flags: bus master, fast devsel, latency 0, IRQ 20
        Memory at  (32-bit, non-prefetchable)

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-02 Thread Yusuf Altıparmak

>
>
> I attached my dts file.
>
> System is working fine when GPU is not plugged in.
>
> *This is the last console log before freeze:*
> [drm] amdgpu kernel modesetting enabled.
>
> [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6987
> 0x1787:0x2389 0x80).
> [drm] register mmio base: 0x2020
>
> fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0
>
> [drm] register mmio size: 262144
>
> [drm] add ip block number 0 
>
> [drm] add ip block number 1 
>
> [drm] add ip block number 2 
>
> [drm] add ip block number 3 
>
> [drm] add ip block number 4 
>
> [drm] add ip block number 5 
>
> [drm] add ip block number 6 
>
> [drm] add ip block number 7 
>
> [drm] add ip block number 8 
>
> [drm] UVD is enabled in VM mode
>
> [drm] UVD ENC is enabled in VM mode
>
> [drm] VCE enabled in VM mode
>
> ATOM BIOS: 113-ER16BFC-001
>
> [drm] GPU posting now...
>
> Disabling lock debugging due to kernel taint
>
> Machine check in kernel mode.
>
> Caused by (from MCSR=a000): Load Error Report
>
> Guarded Load Error Report
>
> Kernel panic - not syncing: Unrecoverable Machine check
>
> CPU: 1 PID: 2023 Comm: udevd Tainted: G   M  4.19.26+gc0c2141
> #1
> Call Trace:
>
>
>
> ___
> amd-gfx mailing 
> listamd-gfx@lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/amd-gfx
>
>
>

Christian König , 2 Ara 2019 Pzt, 15:28
tarihinde şunu yazdı:

> Hi Yusuf,
>
> Am 02.12.19 um 12:41 schrieb Yusuf Altıparmak:
>
> My embedded board is freezing when I put E9171 on PCIe. What is the
> meaning of Unrecoverable Machine Check error about GPU?
>
>
> Well see the explanation on Wikipedia for example:
> https://en.wikipedia.org/wiki/Machine-check_exception
>
> In general it means you have messed up something in your hardware
> configuration.
>
> Could PCIe settings in .dts file cause this problem?
>
>
> Possible, but rather unlikely. My best guess is that it is some problem
> with the power supply.
>
> If it is, is there any sample PCIe configuration for E9171?
>
>
> 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.
>
> Regards,
> Christian.
>


Hi Christian,

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.

[5.512922] [drm] amdgpu kernel modesetting enabled.
[5.517065] [drm] initializing kernel modesetting (POLARIS12
0x1002:0x6987 0x1787:0x2389 0x80).
[5.524507] amdgpu 0001:01:00.0: Fatal error during GPU init
[5.529296] amdgpu: probe of 0001:01:00.0 failed with error -12

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.

*this is lspci -v when GPU is plugged and Memory size is 256 MB.*

root@t1042d4rdb-64b:~# lspci -v
:00:00.0 PCI bridge: Freescale Semiconductor Inc Device 0824 (rev 11)
(prog-if 00 [Normal decode])
Device tree node: /sys/firmware/devicetree/base/pcie@ffe24
/pcie@0
Flags: bus master, fast devsel, latency 0, IRQ 20
Memory at  (32-bit, non-prefetchable)
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: - [size=64K]
Memory behind bridge: e000-efff [size=256M]
Prefetchable memory behind bridge: None
Capabilities: [44] Power Management version 3
Capabilities: [4c] Express Root Port (Slot-), MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: pcieport

0001:00:00.0 PCI bridge: Freescale Semiconductor Inc Device 0824 (rev 11)
(prog-if 00 [Normal decode])
Device tree node: /sys/firmware/devicetree/base/pcie@ffe25
/pcie@0
Flags: bus master, fast devsel, latency 0, IRQ 21
Memory at  (32-bit, non-prefetchable)
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: - [size=64K]
Memory behind bridge: e000-efff [size=256M]
Prefetchable memory behind bridge: None
Capabilities: [44] Power Management version 3
Capabilities: [4c] Express Root Port (Slot-), MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: pcieport

0001:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Lexa [Radeon E9171 MCM] (rev 80) (prog-if 00 [VGA controller])
Subsystem: Hightech Information System Ltd. Device 2389
Flags: fast devsel, IRQ 41
Memory at c1000 (64-bit, prefetchable) [size=256M]
Memory at  (64-bit,

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-02 Thread Christian König


Hi Yusuf,

Am 02.12.19 um 12:41 schrieb Yusuf Altıparmak:
My embedded board is freezing when I put E9171 on PCIe. What is the 
meaning of Unrecoverable Machine Check error about GPU?


Well see the explanation on Wikipedia for example: 
https://en.wikipedia.org/wiki/Machine-check_exception


In general it means you have messed up something in your hardware 
configuration.



Could PCIe settings in .dts file cause this problem?


Possible, but rather unlikely. My best guess is that it is some problem 
with the power supply.



If it is, is there any sample PCIe configuration for E9171?


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.


Regards,
Christian.


I attached my dts file.

System is working fine when GPU is not plugged in.
*
*
*This is the last console log before freeze:*
[drm] amdgpu kernel modesetting enabled.
[drm] initializing kernel modesetting (POLARIS12 0x1002:0x6987 
0x1787:0x2389 0x80).

[drm] register mmio base: 0x2020
fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0
[drm] register mmio size: 262144
[drm] add ip block number 0 
[drm] add ip block number 1 
[drm] add ip block number 2 
[drm] add ip block number 3 
[drm] add ip block number 4 
[drm] add ip block number 5 
[drm] add ip block number 6 
[drm] add ip block number 7 
[drm] add ip block number 8 
[drm] UVD is enabled in VM mode
[drm] UVD ENC is enabled in VM mode
[drm] VCE enabled in VM mode
ATOM BIOS: 113-ER16BFC-001
[drm] GPU posting now...
Disabling lock debugging due to kernel taint
Machine check in kernel mode.
Caused by (from MCSR=a000): Load Error Report
Guarded Load Error Report
Kernel panic - not syncing: Unrecoverable Machine check
CPU: 1 PID: 2023 Comm: udevd Tainted: G   M  4.19.26+gc0c2141 #1
Call Trace:

___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx


___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

[error] Drm -> amdgpu Unrecoverable Machine Check

2019-12-02 Thread Yusuf Altıparmak

My embedded board is freezing when I put E9171 on PCIe. What is the meaning
of Unrecoverable Machine Check error about GPU?

Could PCIe settings in .dts file cause this problem? If it is, is there any
sample PCIe configuration for E9171? I attached my dts file.

System is working fine when GPU is not plugged in.

*This is the last console log before freeze:*
[drm] amdgpu kernel modesetting enabled.

[drm] initializing kernel modesetting (POLARIS12 0x1002:0x6987
0x1787:0x2389 0x80).
[drm] register mmio base: 0x2020

fsl-fman-port ffe488000.port fm1-gb0: renamed from eth0

[drm] register mmio size: 262144

[drm] add ip block number 0 

[drm] add ip block number 1 

[drm] add ip block number 2 

[drm] add ip block number 3 

[drm] add ip block number 4 

[drm] add ip block number 5 

[drm] add ip block number 6 

[drm] add ip block number 7 

[drm] add ip block number 8 

[drm] UVD is enabled in VM mode

[drm] UVD ENC is enabled in VM mode

[drm] VCE enabled in VM mode

ATOM BIOS: 113-ER16BFC-001

[drm] GPU posting now...

Disabling lock debugging due to kernel taint

Machine check in kernel mode.

Caused by (from MCSR=a000): Load Error Report

Guarded Load Error Report

Kernel panic - not syncing: Unrecoverable Machine check

CPU: 1 PID: 2023 Comm: udevd Tainted: G   M  4.19.26+gc0c2141
#1
Call Trace:


t104xd4rdb.dtsi
Description: Binary data
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

Re: [error] Drm -> amdgpu Unrecoverable Machine Check

[error] Drm -> amdgpu Unrecoverable Machine Check

12 matches

Site Navigation

Mail list logo

Footer information