From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 63935] TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! Date: Thu, 16 May 2013 13:09:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1576847534==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A0DDDE63D1 for ; Thu, 16 May 2013 06:09:56 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1576847534== Content-Type: multipart/alternative; boundary="1368709796.fc021.3094"; charset="us-ascii" --1368709796.fc021.3094 Date: Thu, 16 May 2013 13:09:56 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D63935 --- Comment #15 from Christian K=C3=B6nig --- (In reply to comment #14) > Try booting into runlevel 3 with radeon kms (radeon.modeset=3D0 on the ke= rnel > command line in grub, etc.), then manually load radeon with kms enabled > (modprobe -r radeon; modprobe radeon modeset=3D1). Already tried that, doesn't work either. The good news is that I can reproduce the problem, and it indeed looks like= the firmware image gets corrupted. But that seems to always happen not only when the image is loaded from initrd. Going to investigate further. --=20 You are receiving this mail because: You are the assignee for the bug. --1368709796.fc021.3094 Date: Thu, 16 May 2013 13:09:56 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 15 on bug 63935<= /a> from Christian K=C3=B6nig 
(In reply to comment #=
14)
> Try booting into runlevel 3 with radeon kms (rad=
eon.modeset=3D0 on the kernel
> command line in grub, etc.), then manually load radeon with kms enabled
> (modprobe -r radeon; modprobe radeon modeset=3D1).

Already tried that, doesn't work either.

The good news is that I can reproduce the problem, and it indeed looks like=
 the
firmware image gets corrupted. But that seems to always happen not only when
the image is loaded from initrd.

Going to investigate further.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1368709796.fc021.3094-- --===============1576847534== 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 --===============1576847534==--