Re: amd-staging-drm-next breaks suspend

2022-01-20 Thread Bert Karwatzki
022 8:12 PM > > To: Alex Deucher > > Cc: Chris Hixon ; Zhuo, Qingqing > > (Lillian) ; Das, Nirmoy > > ; amd-gfx@lists.freedesktop.org; Scott Bruce > > ; Limonciello, Mario > > ; Kazlauskas, Nicholas > > > > Subject: Re: amd-staging-drm-next breaks susp

Re: amd-staging-drm-next breaks suspend

2022-01-20 Thread Ma, Jun
amd-gfx On Behalf Of Bert > Karwatzki > Sent: Thursday, January 20, 2022 5:52 AM > To: amd-gfx@lists.freedesktop.org > Cc: Chris Hixon ; Zhuo, Qingqing (Lillian) > ; Scott Bruce ; Limonciello, Mario > ; Alex Deucher ; > Kazlauskas, Nicholas > Subject: amd-

RE: amd-staging-drm-next breaks suspend

2022-01-19 Thread Chen, Guchun
er ; Kazlauskas, Nicholas Subject: amd-staging-drm-next breaks suspend I just tested drm-staging-drm-next with HEAD f1b2924ee6929cb431440e6f961f06eb65d52beb: Going into suspend leads to a hang again: This is probably caused by [ 1.310551] trying to bind memory to uninitialized GART ! and/or [ 3.97

RE: amd-staging-drm-next breaks suspend

2022-01-19 Thread Kim, Jonathan
x Deucher > Cc: Chris Hixon ; Zhuo, Qingqing > (Lillian) ; Das, Nirmoy > ; amd-gfx@lists.freedesktop.org; Scott Bruce > ; Limonciello, Mario > ; Kazlauskas, Nicholas > > Subject: Re: amd-staging-drm-next breaks suspend > > [CAUTION: External Email] > > Unfortunat

Re: amd-staging-drm-next breaks suspend

2022-01-19 Thread Bert Karwatzki
7]  driver_register+0x8f/0xe0 > > > [    1.312598]  ? 0xffffc1696000 > > > [    1.312599]  do_one_initcall+0x44/0x1d0 > > > [    1.312602]  ? kmem_cache_alloc_trace+0x103/0x240 > > > [    1.312604]  do_init_module+0x5c/0x270 > > > [    1.312606]  __do_sys_fini

Re: amd-staging-drm-next breaks suspend

2022-01-19 Thread Alex Deucher
05 eb a5 66 0f 1f 44 00 > > 00 > > 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 > > 0f > > 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c7 57 0c 00 f7 d8 64 89 01 > > 48 > > [1.312617] RSP: 002b:7fff9c9d5bc8 EFLAGS: 0246 ORIG_R

Re: amd-staging-drm-next breaks suspend

2022-01-19 Thread Bert Karwatzki
12620] R10: 0013 R11: 0246 R12: > 7ff4ee6d > [    1.312620] R13: R14: 55aca9cf9ab0 R15: > 55aca9cf9230 > [    1.312622] ---[ end trace c4fc99f16e2a1eb7 ]--- > > In both cases there's a similar error message for the oth GPU in the

Re: amd-staging-drm-next breaks suspend

2022-01-19 Thread Bert Karwatzki
> > > Sent: Wednesday, January 19, 2022 15:52 > > > To: amd-gfx@lists.freedesktop.org > > > Cc: Limonciello, Mario ; Kazlauskas, > > > Nicholas > > > ; Zhuo, Qingqing (Lillian) > > > ; Scott Bruce ; Alex > > > Deucher > &

Re: amd-staging-drm-next breaks suspend

2022-01-19 Thread Das, Nirmoy
Hixon Subject: amd-staging-drm-next breaks suspend I just tested drm-staging-drm-next with HEAD f1b2924ee6929cb431440e6f961f06eb65d52beb: Going into suspend leads to a hang again: This is probably caused by [ 1.310551] trying to bind memory to uninitialized GART ! and/or [ 3.976438] trying to bind

amd-staging-drm-next breaks suspend

2022-01-19 Thread Bert Karwatzki
I just tested drm-staging-drm-next with HEAD f1b2924ee6929cb431440e6f961f06eb65d52beb: Going into suspend leads to a hang again: This is probably caused by [ 1.310551] trying to bind memory to uninitialized GART ! and/or [ 3.976438] trying to bind memory to uninitialized GART ! Here's the complet

RE: amd-staging-drm-next breaks suspend

2022-01-19 Thread Limonciello, Mario
[Public] > -Original Message- > From: Bert Karwatzki > Sent: Wednesday, January 19, 2022 15:52 > To: amd-gfx@lists.freedesktop.org > Cc: Limonciello, Mario ; Kazlauskas, Nicholas > ; Zhuo, Qingqing (Lillian) > ; Scott Bruce ; Alex Deucher > ; Chris Hixon > Su