Bug 541628 - mouse cursor problems.
Summary: mouse cursor problems.
Keywords:
Status: CLOSED DUPLICATE of bug 537065
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 12
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: card_NV84
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-26 14:47 UTC by David Woodhouse
Modified: 2010-01-15 06:47 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-02 03:49:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
X log _without_ problem (226.99 KB, text/plain)
2009-11-28 06:32 UTC, David Woodhouse
no flags Details

Description David Woodhouse 2009-11-26 14:47:25 UTC
After a week or so of uptime, my cursor movement starts to get very jerky and I see these messages:

[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image

kernel-2.6.31.6-140.fc12.x86_64
xorg-x11-drv-nouveau-0.0.15-17.20091105gite1c2efd.fc12.x86_64

Comment 1 David Woodhouse 2009-11-26 16:24:12 UTC
I killed X and it failed to restart.

[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 2
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386c1000
[drm] nouveau 0000:01:00.0: Allocating FIFO number 2
[drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2
[drm:drm_mode_getfb] *ERROR* invalid framebuffer id
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386c1000
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386c2000
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386c1000
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386c2000
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor

Comment 2 Michael Breuer 2009-11-27 19:56:49 UTC
Hi David,

Can you provide the X.log from when this happened and let us know what hardware you're using?

Thanks in advance.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 David Woodhouse 2009-11-28 06:32:24 UTC
Created attachment 374353 [details]
X log _without_ problem

I don't recall there being anything interesting in Xorg.log when this happened, but it's gone now so I can't check. Will post the log when it happens again, but here's a current one where the problem hasn't happened yet.

Hardware is a MacBookPro4,1 with:
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev a1)

Comment 4 Michael Breuer 2009-11-28 18:44:30 UTC
Ben,

Looks like this has happened before:
http://lists.freedesktop.org/archives/nouveau/2009-August/003471.html


This bug has been triaged



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 David Woodhouse 2009-11-29 12:58:22 UTC
Happened again today.

Nov 29 12:44:49 macbook kernel: [drm] nouveau 0000:01:00.0: EvoCh 0 Mthd 0x0000 Data 0x00000400 (0x0002 0x01)
Nov 29 12:52:33 macbook kernel: [drm] nouveau 0000:01:00.0: no space while setting cursor image
Nov 29 12:52:33 macbook kernel: [drm] nouveau 0000:01:00.0: no space while unhiding cursor
Nov 29 12:52:34 macbook kernel: [drm] nouveau 0000:01:00.0: no space while setting cursor image
Nov 29 12:52:34 macbook kernel: [drm] nouveau 0000:01:00.0: no space while unhiding cursor
Nov 29 12:52:34 macbook kernel: [drm] nouveau 0000:01:00.0: no space while setting cursor image

Absolutely nothing in Xorg.0.log since the last monitor probe.

Comment 6 Michael Breuer 2009-11-29 18:45:29 UTC
Ben,

Looking into this, it seems either a 2.6.30 regression (from the report to the nouveau mailing list), or likewise, a longer term issue first revealed by the warnings introduced in 2.6.30.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 David Woodhouse 2009-11-29 18:55:32 UTC
When I killed X, I didn't get a text console back -- I could still see the contents of the screen from when X was running.

Starting X again failed, although the screen did go blank when I tried.

[drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 2
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386e1000
[drm] nouveau 0000:01:00.0: Allocating FIFO number 2
[drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2
[drm:drm_mode_getfb] *ERROR* invalid framebuffer id
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386e1000
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386e2000
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386e1000
[drm] nouveau 0000:01:00.0: no space while disconnecting SOR
[drm] nouveau 0000:01:00.0: no space while hiding cursor
[drm] nouveau 0000:01:00.0: no space while blanking crtc
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc ffff8801386e2000
[drm] nouveau 0000:01:00.0: no space while setting cursor image
[drm] nouveau 0000:01:00.0: no space while unhiding cursor
[drm] nouveau 0000:01:00.0: no space while setting cursor image

Comment 8 Adam Williamson 2009-12-01 19:58:49 UTC
Ben, you may remember I used to see an issue like this on my system (with that card you bought the same one as). I haven't seen that for a while...

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 9 Ben Skeggs 2009-12-01 22:54:50 UTC
Yeah, I used to see this reported on a few systems, but not at all for a long time and  was never able to reproduce consistently (or at all on most cards!).

Will track it down eventually :)

Comment 10 Ben Skeggs 2009-12-02 03:49:50 UTC
Marking this as a dup of 537065...

*** This bug has been marked as a duplicate of bug 537065 ***


Note You need to log in before you can comment on or make changes to this bug.