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: Sat, 27 Sep 2014 11:14:36 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1773530338==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 8C31B6E302 for ; Sat, 27 Sep 2014 04:14:36 -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 --===============1773530338== Content-Type: multipart/alternative; boundary="1411816476.aB043.21864"; charset="us-ascii" --1411816476.aB043.21864 Date: Sat, 27 Sep 2014 11:14:36 +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=3D81644 --- Comment #126 from Christian K=C3=B6nig --- (In reply to comment #119) > Small question Alex Deucher or Christian may answer: is it normal ring 5 = is > completely in a different GPU's memory address area? > [ 9.353518] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr > 0x00000000c0000c00 and cpu addr 0xffff880411a25c00 > [ 9.353519] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr > 0x00000000c0000c04 and cpu addr 0xffff880411a25c04 > [ 9.353521] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr > 0x00000000c0000c08 and cpu addr 0xffff880411a25c08 > [ 9.353522] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr > 0x00000000c0000c0c and cpu addr 0xffff880411a25c0c > [ 9.353524] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr > 0x00000000c0000c10 and cpu addr 0xffff880411a25c10 > [ 9.356425] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr > 0x0000000000075a18 and cpu addr 0xffffc90015fb5a18 >=20 > rings 0 to 4 are all in the same gpu address subset, but not ring 5? Yes that's perfectly normal. Ring 5 is the UVD ring and that needs to have = it's fence in the first 256MB of VRAM. --=20 You are receiving this mail because: You are the assignee for the bug. --1411816476.aB043.21864 Date: Sat, 27 Sep 2014 11:14:36 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comme= nt # 126 on bug 81644<= /a> from Christian K=C3=B6nig 
(In reply to comment =
#119)
> Small question Alex Deucher or Christian may ans=
wer: is it normal ring 5 is
> completely in a different GPU's memory address area?
> [    9.353518] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
> 0x00000000c0000c00 and cpu addr 0xffff880411a25c00
> [    9.353519] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr
> 0x00000000c0000c04 and cpu addr 0xffff880411a25c04
> [    9.353521] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr
> 0x00000000c0000c08 and cpu addr 0xffff880411a25c08
> [    9.353522] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
> 0x00000000c0000c0c and cpu addr 0xffff880411a25c0c
> [    9.353524] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr
> 0x00000000c0000c10 and cpu addr 0xffff880411a25c10
> [    9.356425] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
> 0x0000000000075a18 and cpu addr 0xffffc90015fb5a18
>=20
> rings 0 to 4 are all in the same gpu address subset, but not ring 5?

Yes that's perfectly normal. Ring 5 is the UVD ring and that needs to have =
it's
fence in the first 256MB of VRAM.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1411816476.aB043.21864-- --===============1773530338== 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 --===============1773530338==--