Bug 60555

Summary:	[r300g] RADEON_NO_TCL=1 hardlock
Product:	Mesa	Reporter:	Pavel Ondračka <pavel.ondracka>
Component:	Drivers/Gallium/r300	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	trivial
Priority:	lowest
Version:	git
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Pavel Ondračka 2013-02-09 18:07:15 UTC

This is not really a bug as normal user will never encounter this, just some nuisance I discovered when I tried to investigate bug 60552 a little bit.

When RADEON_NO_TCL=1 is used (which is useful in diagnosing compiler bugs), the whole machine sometimes hardlocks. App from bug 60552 is a good way to reproduce this.

This debug option should be either fixed, or if it no longer considered useful, then it should be removed. 

BTW this was working not a year ago, so I can probably run a bisect if needed.

Comment 1 Pavel Ondračka 2013-02-09 18:09:11 UTC

Yeah, of course this is with the gallium driver :-(

Comment 2 Marek Olšák 2013-02-10 01:56:10 UTC

85efb2fff0d4de56c31e414fd05a37d212211d might be the culprit, but AFAIK there is no r500 hardware without TCL (the commit only affects r500). I'm not interested in fixing this, because nobody probably uses the env var (except you and me).

If somebody with a no-TCL chipset experienced hardlocks, that would be a different story.

Comment 3 GitLab Migration User 2019-09-18 18:51:42 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/351.

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.