From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 84500] [radeonsi] radeon 0000:01:00.0: Packet0 not allowed!
Date: Thu, 02 Oct 2014 03:29:31 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1911095650=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 1ECDE6E033
for ; Wed, 1 Oct 2014 20:29:31 -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
--===============1911095650==
Content-Type: multipart/alternative; boundary="1412220571.23BA3f3b0.19612"; charset="UTF-8"
--1412220571.23BA3f3b0.19612
Date: Thu, 2 Oct 2014 03:29:30 +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=3D84500
--- Comment #7 from Michel D=C3=A4nzer ---
> [25322.031213] 0x0000000b
This value is written to the R_028A3C_VGT_GROUP_VECT_1_FMT_CNTL register.
However, the driver only ever writes 0 to that register, in si_init_config(=
).
> [25322.031214] 0x00000000 <---
> [25322.031215] 0x00000295
> [25322.031215] 0x00000080
> [25322.031216] 0x00000040
> [25322.031217] 0x00000002
The values after the arrow look like the following series of register write=
s to
R_028A54_VGT_GS_PER_ES and the two following registers.
So, it looks like the value for the R_028A3C_VGT_GROUP_VECT_1_FMT_CNTL regi=
ster
and the following PKT3_SET_CONTEXT_REG header were scribbled over with the
value 0x0000000b00000000. Looks like memory corruption to me.
Running firefox in valgrind or with something like the GCC / clang address
sanitizers might give a clue, but might be painful.
--=20
You are receiving this mail because:
You are the assignee for the bug.
--1412220571.23BA3f3b0.19612
Date: Thu, 2 Oct 2014 03:29:31 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Comment=
# 7
on bug 84500<=
/a>
from Michel D=C3=A4nzer
> [25322.031213] 0x0000000b
This value is written to the R_028A3C_VGT_GROUP_VECT_1_FMT_CNTL register.
However, the driver only ever writes 0 to that register, in si_init_config(=
).
> [25322.031214] 0x00000000 <---
> [25322.031215] 0x00000295
> [25322.031215] 0x00000080
> [25322.031216] 0x00000040
> [25322.031217] 0x00000002
The values after the arrow look like the following series of register write=
s to
R_028A54_VGT_GS_PER_ES and the two following registers.
So, it looks like the value for the R_028A3C_VGT_GROUP_VECT_1_FMT_CNTL regi=
ster
and the following PKT3_SET_CONTEXT_REG header were scribbled over with the
value 0x0000000b00000000. Looks like memory corruption to me.
Running firefox in valgrind or with something like the GCC / clang address
sanitizers might give a clue, but might be painful.
You are receiving this mail because:
=20=20=20=20=20=20
- You are the assignee for the bug.
--1412220571.23BA3f3b0.19612--
--===============1911095650==
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
--===============1911095650==--