Re: amdgpu 0000:84:00.0: gpu post error! \\ Fatal error during GPU init

[Dennis Schridde <dennis.schridde-axtXthT+lymYbFdUjOg7S7NAH6kLmebB@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 2560 bytes --]

Hello Alex et al.!

On Donnerstag, 13. April 2017 22:16:50 CEST Dennis Schridde wrote:
> On Donnerstag, 13. April 2017 17:30:45 CEST Deucher, Alexander wrote:
> > > [   17.692746] amdgpu 0000:84:00.0: enabling device (0000 -> 0003)
> > > [   17.692940] [drm] initializing kernel modesetting (TONGA
> > > 0x1002:0x6929
> > > 0x1002:0x0334 0x00).
> > > [   17.692963] [drm] register mmio base: 0xD0100000
> > > [   17.692964] [drm] register mmio size: 262144
> > > [   17.692970] [drm] doorbell mmio base: 0xF0000000
> > > [   17.692971] [drm] doorbell mmio size: 2097152
> > > [   17.692980] [drm] probing gen 2 caps for device 10b5:8747 =
> > > 8796103/10e
> > > [   17.692981] [drm] probing mlw for device 10b5:8747 = 8796103
> > > [   17.692992] [drm] VCE enabled in physical mode
> > > [   18.648132] ATOM BIOS: C76301
> > > [   18.651758] [drm] GPU posting now...
> > > [   23.661513] [drm:amdgpu_connector_add [amdgpu]] *ERROR* atombios
> > > stuck in
> > > loop for more than 5secs aborting
> > > [   23.673155] [drm:amdgpu_connector_add [amdgpu]] *ERROR* atombios
> > > stuck
> > > executing F250 (len 334, WS 4, PS 0) @ 0xF365
> > > [   23.685453] [drm:amdgpu_connector_add [amdgpu]] *ERROR* atombios
> > > stuck
> > > executing DB34 (len 324, WS 4, PS 0) @ 0xDC2C
> > > [   23.697816] [drm:amdgpu_connector_add [amdgpu]] *ERROR* atombios
> > > stuck
> > > executing BCDE (len 254, WS 0, PS 4) @ 0xBDB4
> > > [   23.710137] [drm:amdgpu_connector_add [amdgpu]] *ERROR* atombios
> > > stuck
> > > executing B832 (len 143, WS 0, PS 8) @ 0xB8A9
> > > [   23.722451] amdgpu 0000:84:00.0: gpu post error!
> > > [   23.727950] amdgpu 0000:84:00.0: Fatal error during GPU init
> > 
> > Posting the GPU is failing.  The is the initial basic asic setup that is
> > required before anything else can happen.  There seem to be timeouts
> > waiting for some register states.  Is there anything special about your
> > setup?  Can you try a vanilla kernel?
> 
> I don't think there is anything special. At least not that I am aware of.
> Dell R730xd with one AMD FirePro S7150X2 and 2 Mellanox ConnectX-4 Dual
> Port cards. Apart from the modifications shown in the commit log, I made no
> changes to the CoreOS Container Linux 1381 development version. The kernel
> is now unpatched, stock 4.10.9. Please find the logs of the unpatched /
> vanilla kernel attached.

Is this information enough / what you had in mind? How can I aid in debugging 
this further? Are there some command line flags I shall pass to the kernel or 
configuration flags I shall set?

--Dennis

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 681 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

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