Bug 64819

Summary:	GPU fault detected flood at A8-5600K Trinity 7560D
Product:	Mesa	Reporter:	p00h <p00hzone>
Component:	Drivers/Gallium/r600	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	dmesg.log

Description p00h 2013-05-21 09:41:51 UTC

Created attachment 79612 [details]
dmesg.log

I have exactly similar bug as described at https://bugs.freedesktop.org/show_bug.cgi?id=59089 with Trinity 7560D at A8-5600K.

I'm using latest git drivers. As that bug marked as fixed should i claim that my problem is unrelated and caused by hardware and/or other malfunctions?

My problem consists of NOT log flood only, but the whole machine usually freezes and nothing except hard reboot can fix this. Problem detects in both idle and high load mode. The temperature of APU is about 20-40C.

#uname -a
Linux multiseat 3.9.2-1-gpgpu

#lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Trinity [Radeon HD 7560D]

Comment 1 Alex Deucher 2013-05-21 12:55:49 UTC

What version of mesa are you using?  This might be a duplicate of bug 62959.  Make sure your kernel has this patch:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=466476dfdcafbb4286ffa232a3a792731b9dc852

Comment 2 p00h 2013-05-21 18:28:07 UTC

mesa: 9.1.2
ati-dri: 9.1.2
The kernel has this patch already.
I have several machines with the same problem, all of them shipped with A8-5600K.

Comment 3 Alex Deucher 2013-05-21 19:28:03 UTC

Does mesa from git master work any better?  You might also try disabling hyperz (set env var R600_HYPERZ=0).

Comment 4 p00h 2013-05-21 20:46:51 UTC

I'll try it and make an report after

Comment 5 GitLab Migration User 2019-09-18 19:03:11 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/439.

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.