[Bug 67591] Mouse is displayed in portion of screen only since commit d6e4db15, i.e. 3.12+

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Sat Dec 28 10:05:18 PST 2013


https://bugzilla.kernel.org/show_bug.cgi?id=67591

Andre Müller <andre.muller at web.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|v3.12+ (commit d6e4db15)    |v3.12+ (commit d6e4db15)
                   |... -rc5                    |... 3.13-rc5

--- Comment #5 from Andre Müller <andre.muller at web.de> ---
(In reply to Andre Müller from comment #0)
> The X (hardware) cursor is often not displayed.
> The cursor is only displayed at all in a rectangle that looks
> suspiciously to be 640x480 in size, located in the top left.
> There are other restrictions, though.
> The cursor is never displayed but in the leftmost terminal or below it.
> But not below a second terminal to the right.
> When closing that second terminal, the 640x480 visibility is restored.

Actually, in pre-rc1 versions, mouse visibility was always limited
to the outer edge of a terminal if it existed, yet never exceeding
the 640x460 visibility. 
Don't think it matters, but trying to be precise.

> There is a warning in the dmesg:
> 
> [...]
> [    0.321336] [drm] Wrong MCH_SSKPD value: 0x16040307
> [    0.321342] [drm] This can cause pipe underruns and display issues.
> [    0.321344] [drm] Please upgrade your BIOS to fix this.
> [    0.382191] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit
> banging on pin 5
> [...]
> 
> The BIOS has the latest available firmware though.
> 
> Linux-3.12 is fine, also this warning does not show.
> Anything below 3.12, as well as stable until 3.12.6 are fine.

This was a plain coincidence. The message is contained in the dmesg
of the last working commit as well. Sorry for the red herring.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list