<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c, branch v4.12.9</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v4.12.9</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v4.12.9'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2017-05-05T22:15:21+00:00</updated>
<entry>
<title>drm/amdgpu: fix mutex list null pointer reference</title>
<updated>2017-05-05T22:15:21+00:00</updated>
<author>
<name>Pixel Ding</name>
<email>Pixel.Ding@amd.com</email>
</author>
<published>2017-04-25T08:47:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=db2c2a9798d266fd1d7c950b3937793b05533bf4'/>
<id>urn:sha1:db2c2a9798d266fd1d7c950b3937793b05533bf4</id>
<content type='text'>
Fix NULL pointer reference.

Signed-off-by: Pixel Ding &lt;Pixel.Ding@amd.com&gt;
Signed-off-by: Xiangliang Yu &lt;Xiangliang.Yu@amd.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu:fix waiting on dirty fence</title>
<updated>2017-05-05T22:12:42+00:00</updated>
<author>
<name>Monk Liu</name>
<email>Monk.Liu@amd.com</email>
</author>
<published>2017-05-01T08:15:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=236763d340d6190c56554caee61c2bd5cfdf5217'/>
<id>urn:sha1:236763d340d6190c56554caee61c2bd5cfdf5217</id>
<content type='text'>
if bo-&gt;shadow is NULL (race issue:BO shadow was just released
and gpu-reset kick in but BO hasn't yet) recover_vram_from_shadow
won't set @next, so the following "fence=next"
will wrongly use a fence pointer which may already dirty.
fixing it by set next to NULL prior to recover_vram_from_shadow

Signed-off-by: Monk Liu &lt;Monk.Liu@amd.com&gt;
Reviewed-by: Chunming Zhou&lt;david1.zhou@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu: validate shadow before restoring from it</title>
<updated>2017-04-28T21:33:08+00:00</updated>
<author>
<name>Roger.He</name>
<email>Hongbo.He@amd.com</email>
</author>
<published>2017-04-21T05:08:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=82521316395a37a2ec1d7e396c055f3c7de9d93b'/>
<id>urn:sha1:82521316395a37a2ec1d7e396c055f3c7de9d93b</id>
<content type='text'>
Reviewed-by: Chunming Zhou &lt;david1.zhou@amd.com&gt;
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Roger.He &lt;Hongbo.He@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu: Fix use of interruptible waiting</title>
<updated>2017-04-28T21:33:06+00:00</updated>
<author>
<name>Alex Xie</name>
<email>AlexBin.Xie@amd.com</email>
</author>
<published>2017-04-24T17:53:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=1d28479776fe932c32bda2366501fb2408557397'/>
<id>urn:sha1:1d28479776fe932c32bda2366501fb2408557397</id>
<content type='text'>
1. The signal interrupt can affect the expected behaviour.
2. There is no good mechanism to handle the corresponding error.

Signed-off-by: Alex Xie &lt;AlexBin.Xie@amd.com&gt;
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu: Fix use of interruptible waiting</title>
<updated>2017-04-28T21:33:05+00:00</updated>
<author>
<name>Alex Xie</name>
<email>AlexBin.Xie@amd.com</email>
</author>
<published>2017-04-24T17:52:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=7a6901d7d7e49ad50d477cd8f8ef79d079b5c6c5'/>
<id>urn:sha1:7a6901d7d7e49ad50d477cd8f8ef79d079b5c6c5</id>
<content type='text'>
1. The signal interrupt can affect the expected behaviour.
2. There is no mechanism to handle the corresponding error.

Signed-off-by: Alex Xie &lt;AlexBin.Xie@amd.com&gt;
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu: Fix use of interruptible waiting</title>
<updated>2017-04-28T21:33:05+00:00</updated>
<author>
<name>Alex Xie</name>
<email>AlexBin.Xie@amd.com</email>
</author>
<published>2017-04-24T17:30:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=8ab25b4f51ffd2f859afaffa191d50a1eda4128f'/>
<id>urn:sha1:8ab25b4f51ffd2f859afaffa191d50a1eda4128f</id>
<content type='text'>
If amdgpu_bo_reserve function is interrupted by signal,
amdgpu_bo_kunmap function is not called.

Signed-off-by: Alex Xie &lt;AlexBin.Xie@amd.com&gt;
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu: fix gpu reset crash</title>
<updated>2017-04-28T21:32:56+00:00</updated>
<author>
<name>Chunming Zhou</name>
<email>David1.Zhou@amd.com</email>
</author>
<published>2017-04-24T09:09:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=51687759be93fbc553f2727e86be25c38126ba93'/>
<id>urn:sha1:51687759be93fbc553f2727e86be25c38126ba93</id>
<content type='text'>
[  413.687439] BUG: unable to handle kernel NULL pointer dereference at 0000000000000548
[  413.687479] IP: [&lt;ffffffff8109b175&gt;] to_live_kthread+0x5/0x60
[  413.687507] PGD 1efd12067
[  413.687519] PUD 1efd11067
[  413.687531] PMD 0

[  413.687543] Oops: 0000 [#1] SMP
[  413.687557] Modules linked in: amdgpu(OE) ttm(OE) drm_kms_helper(E) drm(E) i2c_algo_bit(E) fb_sys_fops(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) rpcsec_gss_krb5(E) nfsv4(E) nfs(E) fscache(E) snd_hda_codec_realtek(E) snd_hda_codec_generic(E) snd_hda_codec_hdmi(E) snd_hda_intel(E) eeepc_wmi(E) snd_hda_codec(E) asus_wmi(E) snd_hda_core(E) sparse_keymap(E) snd_hwdep(E) video(E) snd_pcm(E) snd_seq_midi(E) joydev(E) snd_seq_midi_event(E) snd_rawmidi(E) snd_seq(E) snd_seq_device(E) snd_timer(E) kvm(E) irqbypass(E) crct10dif_pclmul(E) snd(E) crc32_pclmul(E) ghash_clmulni_intel(E) soundcore(E) aesni_intel(E) aes_x86_64(E) lrw(E) gf128mul(E) glue_helper(E) ablk_helper(E) cryptd(E) shpchp(E) serio_raw(E) i2c_piix4(E) 8250_dw(E) i2c_designware_platform(E) i2c_designware_core(E) mac_hid(E) binfmt_misc(E)
[  413.687894]  parport_pc(E) ppdev(E) lp(E) parport(E) nfsd(E) auth_rpcgss(E) nfs_acl(E) lockd(E) grace(E) sunrpc(E) autofs4(E) hid_generic(E) usbhid(E) hid(E) psmouse(E) ahci(E) r8169(E) mii(E) libahci(E) wmi(E)
[  413.687989] CPU: 13 PID: 1134 Comm: kworker/13:2 Tainted: G           OE   4.9.0-custom #4
[  413.688019] Hardware name: System manufacturer System Product Name/PRIME B350-PLUS, BIOS 0606 04/06/2017
[  413.688089] Workqueue: events amd_sched_job_timedout [amdgpu]
[  413.688116] task: ffff88020f9657c0 task.stack: ffffc90001a88000
[  413.688139] RIP: 0010:[&lt;ffffffff8109b175&gt;]  [&lt;ffffffff8109b175&gt;] to_live_kthread+0x5/0x60
[  413.688171] RSP: 0018:ffffc90001a8bd60  EFLAGS: 00010282
[  413.688191] RAX: ffff88020f0073f8 RBX: ffff88020f000000 RCX: 0000000000000000
[  413.688217] RDX: 0000000000000001 RSI: ffff88020f9670c0 RDI: 0000000000000000
[  413.688243] RBP: ffffc90001a8bd78 R08: 0000000000000000 R09: 0000000000001000
[  413.688269] R10: 0000006051b11a82 R11: 0000000000000001 R12: 0000000000000000
[  413.688295] R13: ffff88020f002770 R14: ffff88020f004838 R15: ffff8801b23c2c60
[  413.688321] FS:  0000000000000000(0000) GS:ffff88021ef40000(0000) knlGS:0000000000000000
[  413.688352] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  413.688373] CR2: 0000000000000548 CR3: 00000001efd0f000 CR4: 00000000003406e0
[  413.688399] Stack:
[  413.688407]  ffffffff8109b304 ffff88020f000000 0000000000000070 ffffc90001a8bdf0
[  413.688439]  ffffffffa05ce29d ffffffffa052feb7 ffffffffa07b5820 ffffc90001a8bda0
[  413.688470]  ffffffff00000018 ffff8801bb88f060 0000000001a8bdb8 ffff88021ef59280
[  413.688502] Call Trace:
[  413.688514]  [&lt;ffffffff8109b304&gt;] ? kthread_park+0x14/0x60
[  413.688555]  [&lt;ffffffffa05ce29d&gt;] amdgpu_gpu_reset+0x7d/0x670 [amdgpu]
[  413.688589]  [&lt;ffffffffa052feb7&gt;] ? drm_printk+0x97/0xa0 [drm]
[  413.688643]  [&lt;ffffffffa0698136&gt;] amdgpu_job_timedout+0x46/0x50 [amdgpu]
[  413.688700]  [&lt;ffffffffa06969e7&gt;] amd_sched_job_timedout+0x17/0x20 [amdgpu]
[  413.688727]  [&lt;ffffffff81095493&gt;] process_one_work+0x153/0x3f0
[  413.688751]  [&lt;ffffffff81095c5b&gt;] worker_thread+0x12b/0x4b0
[  413.688773]  [&lt;ffffffff8100392e&gt;] ? do_syscall_64+0x6e/0x180
[  413.688795]  [&lt;ffffffff81095b30&gt;] ? rescuer_thread+0x350/0x350
[  413.688818]  [&lt;ffffffff8100392e&gt;] ? do_syscall_64+0x6e/0x180
[  413.688839]  [&lt;ffffffff8109b423&gt;] kthread+0xd3/0xf0
[  413.688858]  [&lt;ffffffff8109b350&gt;] ? kthread_park+0x60/0x60
[  413.688881]  [&lt;ffffffff817e1ee5&gt;] ret_from_fork+0x25/0x30
[  413.688901] Code: 25 40 d3 00 00 48 8b 80 48 05 00 00 48 89 e5 5d 48 8b 40 c8 48 c1 e8 02 83 e0 01 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 &lt;48&gt; 8b b7 48 05 00 00 55 48 89 e5 48 85 f6 74 31 8b 97 f8 18 00
[  413.689045] RIP  [&lt;ffffffff8109b175&gt;] to_live_kthread+0x5/0x60
[  413.689064]  RSP &lt;ffffc90001a8bd60&gt;
[  413.689076] CR2: 0000000000000548
[  413.697985] ---[ end trace 0a314a64821f84e9 ]---

The root cause is some ring doesn't have scheduler, like KIQ ring

Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Chunming Zhou &lt;David1.Zhou@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu: fix indent</title>
<updated>2017-04-28T21:32:54+00:00</updated>
<author>
<name>Roger.He</name>
<email>Hongbo.He@amd.com</email>
</author>
<published>2017-04-21T06:24:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=23d2e5049c080abda50810d21c8be20b5d65d191'/>
<id>urn:sha1:23d2e5049c080abda50810d21c8be20b5d65d191</id>
<content type='text'>
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Roger.He &lt;Hongbo.He@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>Revert "drm/amd/amdgpu: Set VCE/UVD off during late init"</title>
<updated>2017-04-28T21:32:48+00:00</updated>
<author>
<name>Alex Deucher</name>
<email>alexander.deucher@amd.com</email>
</author>
<published>2017-04-24T17:51:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=7ad87b96962a01830b0751d11a389b4039eb4460'/>
<id>urn:sha1:7ad87b96962a01830b0751d11a389b4039eb4460</id>
<content type='text'>
This leads to hangs on init.

This reverts commit d1aff8ec49c3ece05cee9b6e63d44e96a420b068.
</content>
</entry>
<entry>
<title>drm/amdgpu: fix coding style and printing in amdgpu_doorbell_init</title>
<updated>2017-04-28T21:32:41+00:00</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2017-03-06T12:34:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=8972e5d26996e3f04e1cf29b7d7edd3ec5614bf2'/>
<id>urn:sha1:8972e5d26996e3f04e1cf29b7d7edd3ec5614bf2</id>
<content type='text'>
Based on commit "drm/radeon: remove useless and potentially wrong message".

The size of the info printing is incorrect and the PCI subsystems prints
the same info on boot anyway.

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Reviewed-by: Edward O'Callaghan &lt;funfunctor@folklore1984.net&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
</feed>
