Bug 635026

Summary: nvaf chipset needs 'nouveau.noaccel=1'
Product: [Fedora] Fedora Reporter: Will Woods <wwoods>
Component: kernelAssignee: Ben Skeggs <bskeggs>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: xorg-x11-drv-nouveau-0.0.16-14.20101010git8c8f15c.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-25 02:11:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/messages during nvaf acceleration failure none

Description Will Woods 2010-09-17 15:55:43 UTC
Created attachment 448036 [details]
/var/log/messages during nvaf acceleration failure

The drm-nouveau-nva3-noaccel.patch disables acceleration for certain chipsets - a3, a5, a8. My nvaf system seems to behave quite badly with accel turned on: the screen is drawn without any text, for instance. 

A lot of PGRAPH_ILLEGAL_CLASS/MTHD messages appear in syslog from nouveau - for example:

Allocating FIFO number 3
nouveau_channel_alloc: initialised FIFO 3
PGRAPH_ILLEGAL_CLASS - Ch 3/7 Class 0x8597 Mthd 0x0000 Data 0x00000000:0x00000e20
PGRAPH_ILLEGAL_MTHD - Ch 3/7 Class 0x8597 Mthd 0x1558 Data 0x00000000:0x00000001
[etc]

Adding 'case 0xaf:' to the switch statement added in drm-nouveau-nva3-noaccel.patch makes the system usable again.

I'm attaching the logs in hopes that they might be useful to trace the actual problem - since the system doesn't actually lock up, this might be a different problem from a3/a5/a8 - but in the meantime I'm guessing we will need noaccel=1 for nvaf.

Comment 1 Will Woods 2010-09-17 15:56:40 UTC
Oh - obviously putting 'nouveau.noaccel=1' on the boot commandline is an effective workaround.

Comment 2 Fedora Update System 2010-09-19 22:25:59 UTC
xorg-x11-drv-nouveau-0.0.16-12.20100920gitf1ac413.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-12.20100920gitf1ac413.fc14

Comment 3 Fedora Update System 2010-09-20 18:40:51 UTC
xorg-x11-drv-nouveau-0.0.16-12.20100920gitf1ac413.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-nouveau'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-12.20100920gitf1ac413.fc14

Comment 4 Fedora Update System 2010-10-09 02:55:41 UTC
xorg-x11-drv-nouveau-0.0.16-12.20100920gitf1ac413.fc14.1 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-nouveau'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-12.20100920gitf1ac413.fc14.1

Comment 5 Fedora Update System 2010-10-11 01:00:07 UTC
xorg-x11-drv-nouveau-0.0.16-13.20101010git8c8f15c.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-13.20101010git8c8f15c.fc14

Comment 6 Fedora Update System 2011-04-10 23:39:53 UTC
xorg-x11-drv-nouveau-0.0.16-14.20101010git8c8f15c.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-14.20101010git8c8f15c.fc14

Comment 7 Fedora Update System 2011-11-25 02:11:53 UTC
xorg-x11-drv-nouveau-0.0.16-14.20101010git8c8f15c.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.