On 05/25/2018 07:23 PM, Christian König wrote:
Am 25.05.2018 um 11:51 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 05:35 PM, Christian König wrote:
Am 25.05.2018 um 10:23 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 03:54 PM, Christian König wrote:
Am 25.05.2018 um 09:20 schrieb Zhang, Jerry
Am 25.05.2018 um 11:51 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 05:35 PM, Christian König wrote:
Am 25.05.2018 um 10:23 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 03:54 PM, Christian König wrote:
Am 25.05.2018 um 09:20 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 02:44 PM, Christian
On 05/25/2018 05:35 PM, Christian König wrote:
Am 25.05.2018 um 10:23 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 03:54 PM, Christian König wrote:
Am 25.05.2018 um 09:20 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 02:44 PM, Christian König wrote:
NAK, that probably just fixed the symptom
Am 25.05.2018 um 10:23 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 03:54 PM, Christian König wrote:
Am 25.05.2018 um 09:20 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 02:44 PM, Christian König wrote:
NAK, that probably just fixed the symptom but not the underlying
problem.
Somebody is
On 05/25/2018 03:54 PM, Christian König wrote:
Am 25.05.2018 um 09:20 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 02:44 PM, Christian König wrote:
NAK, that probably just fixed the symptom but not the underlying problem.
Somebody is accessing the page array when it should never be accessed.
Am 25.05.2018 um 09:20 schrieb Zhang, Jerry (Junwei):
On 05/25/2018 02:44 PM, Christian König wrote:
NAK, that probably just fixed the symptom but not the underlying
problem.
Somebody is accessing the page array when it should never be accessed.
If prime import as GTT bo by default(now it's
On 05/25/2018 02:44 PM, Christian König wrote:
NAK, that probably just fixed the symptom but not the underlying problem.
Somebody is accessing the page array when it should never be accessed.
If prime import as GTT bo by default(now it's CPU bo), it would happens quickly
when GTT sg bo
NAK, that probably just fixed the symptom but not the underlying problem.
Somebody is accessing the page array when it should never be accessed.
How did you manage to trigger this?
Regards,
Christian.
Am 25.05.2018 um 07:41 schrieb Junwei Zhang:
[ 632.679861] BUG: unable to handle kernel
[ 632.679861] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 632.679892] IP: drm_prime_sg_to_page_addr_arrays+0x52/0xb0 [drm]
[ 632.680011] Call Trace:
[ 632.680082] amdgpu_ttm_tt_populate+0x3e/0xa0 [amdgpu]
[ 632.680092] ttm_tt_populate.part.7+0x22/0x60 [amdttm]
[