From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 79980] Random radeonsi crashes Date: Thu, 31 Jul 2014 15:05:17 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0962833725==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D78A16E1F0 for ; Thu, 31 Jul 2014 08:05:17 -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 --===============0962833725== Content-Type: multipart/alternative; boundary="1406819117.7ff641.9662"; charset="us-ascii" --1406819117.7ff641.9662 Date: Thu, 31 Jul 2014 15:05:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=79980 --- Comment #74 from jackdachef@gmail.com --- (In reply to comment #71) > This bug was originally about a stability regression due to some GPUVM > changes in 3.15. If 3.14 is stable for you but newer kernels are not, then > it may be related. Otherwise, it's probably another issue. See bug 81644 > about stability issues with Chromium specifically. unfortunately 3.14 also isn't entirely stable it mostly is (99%) but here the problem is that very very seldomly X simply crashes, gpu doesn't simply turn black and recovers, so important data can be lost (when being worked on) - couldn't pinpoint the reason yet - the gpu just "reboots" no additional error messages dmesg or Xorg.0.log as far as I know can't say anything about kernel versions prior to that since this card is still a few days old gcc 4.9 also couldn't be the cause, at least with 3.16-rc* kernels and drm-next-3.17-rebased-on-fixes, since I've already added the patch manually and the kernel also isn *NOT* compiled with -Os (optimize for size) it seems to be more of general instability going towards 3.15 and 3.16 - but who I am to ask, I'm just a enthusiast user :P having read about stability issues with the new firmware somewhere how could I test and revert to the old firmware ? would it still work ? simply removing the PITCAIRN_mc2.bin (e.g. for the R9 270X) and leaving the other PITCAIRN files in /lib/firmware ? the graphics driver is loading as a module and not compiled into the kernel or included in initramfs I'd really like to upgrade to 3.16-rc* due to recent changes (especially in connection with Btrfs) an option to disable UVD entirely would have been nice (when still using 5850 and during the new introduction of DPM there was a patch which offered a module parameter to turn it manually off) - would that be an option to further troubleshoot this issue and to exclude UVD from the list of potential causes ? Thanks -- You are receiving this mail because: You are the assignee for the bug. --1406819117.7ff641.9662 Date: Thu, 31 Jul 2014 15:05:17 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 74 on bug 79980 from 
(In reply to comment #71)
> This bug was originally about a stability regression due to some GPUVM
> changes in 3.15.  If 3.14 is stable for you but newer kernels are not, then
> it may be related.  Otherwise, it's probably another issue.  See bug 81644
> about stability issues with Chromium specifically.

unfortunately 3.14 also isn't entirely stable it mostly is (99%) but here the
problem is that very very seldomly X simply crashes, gpu doesn't simply turn
black and recovers, so important data can be lost (when being worked on) -
couldn't pinpoint the reason yet - the gpu just "reboots"

no additional error messages dmesg or Xorg.0.log as far as I know

can't say anything about kernel versions prior to that since this card is still
a few days old


gcc 4.9 also couldn't be the cause, at least with 3.16-rc* kernels and
drm-next-3.17-rebased-on-fixes, since I've already added the patch manually and
the kernel also isn *NOT* compiled with -Os (optimize for size)


it seems to be more of general instability going towards 3.15 and 3.16 - but
who I am to ask, I'm just a enthusiast user :P


having read about stability issues with the new firmware somewhere

how could I test and revert to the old firmware ? would it still work ?

simply removing the PITCAIRN_mc2.bin (e.g. for the R9 270X) and leaving the
other PITCAIRN files in /lib/firmware ?

the graphics driver is loading as a module and not compiled into the kernel or
included in initramfs

I'd really like to upgrade to 3.16-rc* due to recent changes (especially in
connection with Btrfs)

an option to disable UVD entirely would have been nice (when still using 5850
and during the new introduction of DPM there was a patch which offered a module
parameter to turn it manually off) - would that be an option to further
troubleshoot this issue and to exclude UVD from the list of potential causes ?


Thanks

You are receiving this mail because:
  • You are the assignee for the bug.
--1406819117.7ff641.9662-- --===============0962833725== 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 --===============0962833725==--