Bug 88558

Summary:	radeonsi crash with mesa 10.4.2
Product:	Mesa	Reporter:	Hannu <hannu.tmp>
Component:	Drivers/Gallium/radeonsi	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	medium
Version:	10.4
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	journalctl crash report

Description Hannu 2015-01-18 16:11:40 UTC

Created attachment 112425 [details]
journalctl crash report

This is the same hardware as in bug 85647, may be related or not. Attached crash report.

mesa 10.4.2-2 from debian package

linux kernel 3.19-rc4 with patches mentioned in this message applied:

-------------------------------
--- Comment #223 from Michel Dänzer <michel at daenzer.net> ---
(In reply to fdb4c415 from comment #222)


There's a good chance that a newer upstream version of Mesa would help for your
problem, if not fix it completely.

For those still having problems, the kernel patches
http://lists.freedesktop.org/archives/dri-devel/2015-January/074968.html and
http://lists.freedesktop.org/archives/dri-devel/2015-January/074969.html might
be worth a try.
-------------------------------


Jan 18 16:41:35  kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x04124802
Jan 18 16:41:35  kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00096D20
Jan 18 16:41:35  kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12048002
Jan 18 16:41:35  kernel: VM fault (0x02, vmid 9) at page 617760, read from TC (72)
Jan 18 16:41:35  kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x04124802
Jan 18 16:41:35  kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00096B20
Jan 18 16:41:35  kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12048002
Jan 18 16:41:35  kernel: VM fault (0x02, vmid 9) at page 617248, read from TC (72)

and so on

Comment 1 Michel Dänzer 2015-01-19 04:01:44 UTC

Did this happen when you were doing anything in particular?

Comment 2 Hannu 2015-01-19 06:20:02 UTC

(In reply to Michel Dänzer from comment #1)
> Did this happen when you were doing anything in particular?

I wasn't using the computer myself and didn't pay attention to it, probably it crashed while playing in steam or watching flash video. I'll see if it can be reproduced with the same video testing as in bug 85647.

Those VM_CONTEXT1_PROTECTION_FAULT_ADDR messages start at 16:41 and then at 17:17 it says "ring 3 stalled" and at that point screen went black, SSH into the box worked and I could get the journalctl report.

Jan 18 16:41:35  kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x04124802
Jan 18 16:41:35  kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00096D20
Jan 18 16:41:35  kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12048002
Jan 18 16:41:35  kernel: VM fault (0x02, vmid 9) at page 617760, read from TC (72)
----------------------
Jan 18 17:17:19  kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x00b24801
Jan 18 17:17:19  kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0FD37C05
Jan 18 17:17:19  kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12048001
Jan 18 17:17:19  kernel: VM fault (0x01, vmid 9) at page 265518085, read from TC (72)
Jan 18 17:17:29  kernel: radeon 0000:01:00.0: ring 3 stalled for more than 10191msec

Comment 3 Hannu 2015-02-13 15:18:04 UTC

This has shown it's symptoms only once, I can not reproduce it. May be there is some uninitialized register or variable in southern islands code that produces these random crashes here and there?

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.