From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 79980] Random radeonsi crashes Date: Wed, 03 Sep 2014 05:25:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2073620636==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C1BE96E4CF for ; Tue, 2 Sep 2014 22:25:22 -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 --===============2073620636== Content-Type: multipart/alternative; boundary="1409721922.26d24cF4.14211"; charset="us-ascii" --1409721922.26d24cF4.14211 Date: Wed, 3 Sep 2014 05:25:22 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=79980 --- Comment #124 from Grigori Goronzy --- I can very quickly, almost deterministically, hang the GPU (radeonsi, Cape Verde) with the following command: > LIBGL_ALWAYS_SOFTWARE=1 mpv --fs --vo=opengl:sw /path/to/some_video this works on both 3.16.0 and 3.17rc3. Try seeking, it often happens directly after a seek. In most cases, the hang is unrecoverable and crashes the kernel after some "atombios stuck in a loop" messages. Very strange indeed, software rendered glxgears doesn't cause this. Can anyone verify? A somewhat reliable test case might be a good start to finally fixing this. -- You are receiving this mail because: You are the assignee for the bug. --1409721922.26d24cF4.14211 Date: Wed, 3 Sep 2014 05:25:22 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 124 on bug 79980 from 
I can very quickly, almost deterministically, hang the GPU (radeonsi, Cape
Verde) with the following command:

> LIBGL_ALWAYS_SOFTWARE=1 mpv --fs --vo=opengl:sw /path/to/some_video

this works on both 3.16.0 and 3.17rc3. Try seeking, it often happens directly
after a seek. In most cases, the hang is unrecoverable and crashes the kernel
after some "atombios stuck in a loop" messages. Very strange indeed, software
rendered glxgears doesn't cause this.

Can anyone verify? A somewhat reliable test case might be a good start to
finally fixing this.

You are receiving this mail because:
  • You are the assignee for the bug.
--1409721922.26d24cF4.14211-- --===============2073620636== 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 --===============2073620636==--