Bug 593695
| Summary: | kernel: [drm] nouveau 0000:01:00.0: no space while (un)hiding cursor | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jóhann B. Guðmundsson <johannbg> | ||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 13 | CC: | airlied, ajax, bskeggs | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-05-19 22:09:27 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: |
|
||||||||
Created attachment 415131 [details]
/var/log/messages
*** This bug has been marked as a duplicate of bug 537065 *** |
Created attachment 415130 [details] Xorg log file Description of problem: Dual monitor setup. On the right monitor the mouse pointer is visible move it to the left one it vanishes with the following errors appearing in /var/log/messages . ( Mouse is working pointer simply not visible on the left screen ) May 19 13:22:39 valhalla kernel: [drm] nouveau 0000:01:00.0: EvoCh 0 Mthd 0x0000 Data 0x00000400 (0x0002 0x01) May 19 13:43:41 valhalla kernel: [drm] nouveau 0000:01:00.0: no space while unhiding cursor May 19 13:43:41 valhalla kernel: [drm] nouveau 0000:01:00.0: no space while hiding cursor Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-0.0.16-6.20100423git13c1043.fc13.x86_64 How reproducible: Did update which updated the nouveau driver this started to happen ca 2hours later hence not sure the update triggered this bug.. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: