From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 81644] Random crashes on RadeonSI with Chromium. Date: Tue, 05 Aug 2014 15:32:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1599066151==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3E1E46E221 for ; Tue, 5 Aug 2014 08:32:00 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1599066151== Content-Type: multipart/alternative; boundary="1407252720.c0Ac3300.6952"; charset="us-ascii" --1407252720.c0Ac3300.6952 Date: Tue, 5 Aug 2014 15:32:00 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=81644 --- Comment #39 from jackdachef@gmail.com --- (In reply to comment #38) > (In reply to comment #32) > > R600_DEBUG=sb,sbsafemath,nollvm chromium-browser > > Those debugging options only have an effect with the r600g driver, not with > radeonsi. > are the other ways to temporarily disable LLVM for debugging in radeonsi ? gentoo ebuilds force users to compile mesa & radeonsi with llvm - so that seemingly is the only way of operation with these kind of chipsets/cards ? > > > radeonsi isn't the only chipset family affected: intel cards hd2000, hd3000, > > hd4000; gm45, gm965, i915 (sandybridge, ivybridge, haswell, etc.), or other > > radeons are also affected in different ways > > r600g issues might be related, but most definitely not Intel GPU ones. so things are implemented *that* differently between intel & radeon drivers ? -- You are receiving this mail because: You are the assignee for the bug. --1407252720.c0Ac3300.6952 Date: Tue, 5 Aug 2014 15:32:00 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 39 on bug 81644 from 
(In reply to comment #38)
> (In reply to comment #32)
> > R600_DEBUG=sb,sbsafemath,nollvm chromium-browser
> 
> Those debugging options only have an effect with the r600g driver, not with
> radeonsi.
> 

are the other ways to temporarily disable LLVM for debugging in radeonsi ?

gentoo ebuilds force users to compile mesa & radeonsi with llvm - so that
seemingly is the only way of operation with these kind of chipsets/cards ?


> 
> > radeonsi isn't the only chipset family affected: intel cards hd2000, hd3000,
> > hd4000; gm45, gm965, i915 (sandybridge, ivybridge, haswell, etc.), or other
> > radeons are also affected in different ways
> 
> r600g issues might be related, but most definitely not Intel GPU ones.

so things are implemented *that* differently between intel & radeon drivers ?

You are receiving this mail because:
  • You are the assignee for the bug.
--1407252720.c0Ac3300.6952-- --===============1599066151== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1599066151==--