From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
Subject: [Bug 68835] New: Unknown opcode 0x43 + protection fault
on a Graphics Blaster Riva TNT card
Date: Mon, 02 Sep 2013 09:20:02 +0000
Message-ID:
Priority
medium
Bug ID
68835
Assignee
nouveau@lists.freedesktop.org
Summary
Unknown opcode 0x43 + protection fault on a Graphics Blaster Riva TNT card
QA Contact
xorg-team@lists.x.org
Severity
normal
Classification
Unclassified
OS
Linux (All)
Reporter
mauromol@tiscali.it
Hardware
x86 (IA32)
Status
NEW
Version
unspecified
Component
Driver/nouveau
Product
xorg
Created attachment 85048 [details]
dmesg output: system boot + a couple of S3 suspensions + a S4 hibernation
Opening this as suggested in bug #67161 comment #6.
Running Fedora 19 with a live USB on an old system with Creative Labs Graphics
Blaster Riva TNT:
Linux localhost 3.9.5-301.fc19.i686 #1 SMP Tue Jun 11 20:01:50 UTC 2013 i686
i686 i386 GNU/Linux
If I run dmesg I see some errors like:
[ 5.213896] nouveau E[ VBIOS][0000:01:00.0] 0x012e[ ]: unknown opcode 0x43
or:
[ 99.820645] nouveau E[ PGRAPH][0000:01:00.0] NOTIFY nsource:
PROTECTION_ERROR nstatus: PROTECTION_FAULT
[ 99.820677] nouveau E[ PGRAPH][0000:01:00.0] ch 1 [X[666]] subc 2 class
0x0042 mthd 0x0180 data 0x00003a04
[ 99.820697] nouveau E[ PGRAPH][0000:01:00.0] NOTIFY nsource:
PROTECTION_ERROR nstatus: PROTECTION_FAULT
[ 99.820714] nouveau E[ PGRAPH][0000:01:00.0] ch 1 [X[666]] subc 6 class
0x0044 mthd 0x0180 data 0x00003a04
[ 99.820732] nouveau E[ PGRAPH][0000:01:00.0] NOTIFY nsource:
PROTECTION_ERROR nstatus: PROTECTION_FAULT
[ 99.820749] nouveau E[ PGRAPH][0000:01:00.0] ch 1 [X[666]] subc 6 class
0x0043 mthd 0x0180 data 0x00003a04
[ 99.821101] nouveau E[ PGRAPH][0000:01:00.0] NOTIFY nsource:
PROTECTION_ERROR nstatus: PROTECTION_FAULT
[ 99.821121] nouveau E[ PGRAPH][0000:01:00.0] ch 1 [X[666]] subc 6 class
0x0019 mthd 0x0180 data 0x00003a04
The "unknown opcode" error appears at boot and waking up from S3/S4.
Regarding the protection fault lines, it seems like they appeared on boot and
on one of the wakeups from S3.