Bug 23092 - Syslog flooded with "nouveau 0000:01:00.0: Unhandled PFIFO_INTR - 0x00000010"
Summary: Syslog flooded with "nouveau 0000:01:00.0: Unhandled PFIFO_INTR - 0x00000010"
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-02 11:04 UTC by Julien Ozog
Modified: 2011-12-05 10:59 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (30.37 KB, text/plain)
2009-08-02 12:32 UTC, Julien Ozog
no flags Details
Xorg.log (179.16 KB, text/plain)
2009-08-02 12:32 UTC, Julien Ozog
no flags Details
Xorg.log with correct libglx (133.33 KB, text/plain)
2009-08-02 23:56 UTC, Julien Ozog
no flags Details

Description Julien Ozog 2009-08-02 11:04:57 UTC
Hi, I try to use Nouveau for the first time today. Everything seems to work fine, except that my syslog is flooded with this message :
"kernel: nouveau 0000:01:00.0: Unhandled PFIFO_INTR - 0x00000010"

In the previous 3 hours, this message has been logged ~25000 times.

It seems related with my activity, with an empty desktop and doing nothing, the message still print but much less often. As soon as I began typing or opening a menu, the message is logged as much as 50 times per second.

I use DDX, libdrm and DRM snapshots from today. DRM comes from the master-compat branch (commit 	4ea84bc8aeaccc57958b8fb2847965d52b6bda72).
I don't use KMS.
Composite is enabled and used with metacity.

X.Org X Server 1.6.3
Linux 2.6.30.3

My card is :
PCI:*(0:1:0:0) 10de:0407:14c0:0025 nVidia Corporation G84 [GeForce 8600M GT] rev 161, Mem @ 0xc6000000/16777216, 0xd0000000/268435456, 0xc4000000/33554432, I/O @ 0x00002000/128
Comment 1 Peter Hjalmarsson 2009-08-02 12:20:07 UTC
There are some info missing I think.

It would help if you could dmesg > file.log and attach file.log, attach your /var/log/Xorg.log. Also tell us if you are trying to use the mesa gallium3d nouveau driver which because of its incomplete (and unsupported) state are know to generate this kind of messages.
Comment 2 Julien Ozog 2009-08-02 12:32:09 UTC
Created attachment 28268 [details]
dmesg
Comment 3 Julien Ozog 2009-08-02 12:32:40 UTC
Created attachment 28269 [details]
Xorg.log
Comment 4 Julien Ozog 2009-08-02 12:35:25 UTC
I have attached the requested log files. I don't use Mesa / Gallium3D.
Comment 5 Peter Hjalmarsson 2009-08-02 20:49:41 UTC
From Xorg.log

(II) Module glx: vendor="NVIDIA Corporation"
	compiled for 4.0.2, module version = 1.0.0
	Module class: X.Org Server Extension
(II) NVIDIA GLX Module  185.18.14  Wed May 27 03:09:07 PDT 2009

(EE) NOUVEAU(0): [dri] GlxSetVisualConfigs not found.
(EE) NOUVEAU(0):       NVIDIA's glx present, or glx not loaded.

(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)


This means there are residues left after a earlier install of nvidias binary blob. You may have to remove those files and reinstall the package providing glx and dri for your distribution as these can and does interfere with nouveau.
Comment 6 Julien Ozog 2009-08-02 23:56:59 UTC
Created attachment 28279 [details]
Xorg.log with correct libglx

Oops, sorry, I didn't see that. Same problem with the correct libglx, here is the new Xorg.log.
Comment 7 Michal Suchanek 2010-03-12 06:24:01 UTC
I had similar messages when vesafb was activated before loading the nouveau module.

Setting vga=normal on the kernel command line resolved the issue for me.
Comment 8 Marcin Slusarz 2010-10-13 11:58:01 UTC
Can you please test current Nouveau? If the bug still occurs please attach kernel log from boot to start of the flood.
Comment 9 Marcin Slusarz 2011-12-05 10:59:28 UTC
I think we fixed it sometime ago with fb handover fixes. Marking as RESOLVED FIXED. If you can still reproduce it, please reopen.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.