xsrc/49155: openchrome hardware cursor always invisible

To: xsrc-manager%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost
Subject: xsrc/49155: openchrome hardware cursor always invisible
From: jdbaker%mylinuxisp.com@localhost
Date: Tue, 26 Aug 2014 20:55:00 +0000 (UTC)

>Number:         49155
>Category:       xsrc
>Synopsis:       openchrome hardware cursor always invisible
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    xsrc-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 26 20:55:00 +0000 2014
>Originator:     John D. Baker
>Release:        NetBSD/i386-7.99.1 after 24-Aug-2014 06:14 UTC
>Organization:
>Environment:
NetBSD neoware 7.99.1 NetBSD 7.99.1 (NEOWARE) #5: Sun Aug 24 20:25:53 CDT 2014  
sysop%verthandi.technoskunk.fur@localhost:/d0/build/current/obj/i386/sys/arch/i386/compile/NEOWARE
 i386

>Description:
With xsrc after 24-Aug-2014 06:14 UTC, or with pkgsrc/modular Xorg,
machines using the "openchrome" driver with defaults (no "xorg.conf"
never display the mouse cursor.  At best one can watch elements of their
graphical environment for changes as the "point" enters/exits their
region of the display.  Then, click and hope.

Some relevant information about the problem machine:

NetBSD 7.99.1 (NEOWARE) #5: Sun Aug 24 20:25:53 CDT 2014
        
sysop%verthandi.technoskunk.fur@localhost:/d0/build/current/obj/i386/sys/arch/i386/compile/NEOWARE
total memory = 1015 MB
avail memory = 992 MB
kern.module.path=/stand/i386/7.99.1/modules
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
Neoware Systems Inc. Thin Client ( )
mainbus0 (root)
ACPI: RSDP 0xf66c0 000014 (v00 CLE266)
[...]
pchb0 at pci0 dev 0 function 0: VIA Technologies VT8623 (Apollo CLE266) CPU-PCI 
Bridge (rev. 0x00)
agp0 at pchb0: aperture at 0xe4000000, size 0x4000000
ppb0 at pci0 dev 1 function 0: VIA Technologies VT8633 (Apollo Pro 266) CPU-AGP 
Bridge (rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga0 at pci1 dev 0 function 0: VIA Technologies VT8623 (Apollo CLE266) VGA 
Controller (rev. 0x03)
wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
viadrm0 at vga0: VIA CLE266
viadrm0: AGP at 0xe4000000 64MB
viadrm0: Initialized via 2.11.1 20070202
[...]
viadrm0: interrupting at irq 3
error: [drm:pid1786:via_initialize] *ERROR* called again without calling cleanup
viadrm0: interrupting at irq 3
error: [drm:pid1786:via_initialize] *ERROR* called again without calling cleanup

Those last two messages are emitted upon starting the X server.

Messages from "xdm.log":

xdm info (pid 1719): Starting
xdm error (pid 1719): XDMCP socket multicast join to ff02::12b failed, errno 49
xdm info (pid 1719): Starting X server on :0

X.Org X Server 1.10.6
Release Date: 2011-07-08
X Protocol Version 11, Revision 0
Build Operating System: NetBSD/i386  - 
Current Operating System: NetBSD neoware 7.99.1 NetBSD 7.99.1 (NEOWARE) #5: Sun 
Aug 24 20:25:53 CDT 2014  
sysop%verthandi.technoskunk.fur@localhost:/d0/build/current/obj/i386/sys/arch/i386/compile/NEOWARE
 i386
Build Date: 01 August 2011  01:01:00AM
 
Current version of pixman: 0.32.6
        Before reporting problems, check http://wiki.X.Org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 25 13:54:53 2014
(==) Using config file: "/etc/X11/xorg.conf"
5242880 bytes of DRI memory allocated at 0, handle 3590305519
262144 bytes of DRI memory allocated at 500000, handle 1480669007
32 bytes of DRI memory allocated at 540000, handle 1472412176
32 bytes of DRI memory allocated at 540020, handle 417593920
2097152 bytes of DRI memory allocated at 540040, handle 3573791857
(EE) CHROME(0): [drm] Failed to initialize DMA ring-buffer: 14
4194304 bytes of DRI memory allocated at 0, handle 2518973601
635904 bytes of DRI memory allocated at 740040, handle 311576802
Freed 7602240 (pool 4)

ERROR!  sizeof(VIADRIRec) does not match passed size from device driver
(EE) AIGLX error: Calling driver entry point failed
(EE) AIGLX: reverting to software rendering
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:            Couldn't lookup keysym
>                   Symbol interpretation ignored
> Error:            Couldn't lookup keysym
>                   Symbol interpretation ignored
Errors from xkbcomp are not fatal to the X server
xdm info (pid 1807): sourcing /etc/X11/xdm/Xsetup_0
xdm info (pid 1807): sourcing /etc/X11/xdm/GiveConsole
xdm info (pid 2259): executing session /etc/X11/xdm/Xsession
xdm info (pid 1807): sourcing /etc/X11/xdm/TakeConsole
XIO:  fatal IO error 35 (Resource temporarily unavailable) on X server ":0"
      after 150 requests (126 known processed) with 0 events remaining.
Freed 0 (pool 2)
Freed 5242880 (pool 4)
Freed 5505056 (pool 4)
Freed 0 (pool 4)
Freed 5505088 (pool 4)
DRM failed to free for handle 3573791857.
6 XSELINUXs still allocated at reset
SCREEN: 0 objects of 144 bytes = 0 total bytes 0 private allocs
DEVICE: 0 objects of 24 bytes = 0 total bytes 0 private allocs
CLIENT: 0 objects of 152 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 32 bytes = 0 total bytes 0 private allocs
PIXMAP: 2 objects of 76 bytes = 152 total bytes 0 private allocs
GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 2 objects, 152 bytes, 0 allocs
3 SELECTIONs still allocated at reset
WINDOW: 0 objects of 32 bytes = 0 total bytes 0 private allocs
PIXMAP: 2 objects of 76 bytes = 152 total bytes 0 private allocs
GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 2 objects, 152 bytes, 0 allocs
2 PIXMAPs still allocated at reset
PIXMAP: 2 objects of 76 bytes = 152 total bytes 0 private allocs
GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 2 objects, 152 bytes, 0 allocs
1 DAMAGEs still allocated at reset
TOTAL: 0 objects, 0 bytes, 0 allocs
1 PICTUREs still allocated at reset
TOTAL: 0 objects, 0 bytes, 0 allocs
xdm info (pid 1719): Starting X server on :0
5242880 bytes of DRI memory allocated at 0, handle 996843650
262144 bytes of DRI memory allocated at 500000, handle 3216592767
32 bytes of DRI memory allocated at 540000, handle 4102126024
32 bytes of DRI memory allocated at 540020, handle 2026899629
2097152 bytes of DRI memory allocated at 540040, handle 2799616957
(EE) CHROME(0): [drm] Failed to initialize DMA ring-buffer: 14
4194304 bytes of DRI memory allocated at 0, handle 3149155326

ERROR!  sizeof(VIADRIRec) does not match passed size from device driver
(EE) AIGLX error: Calling driver entry point failed
(EE) AIGLX: reverting to software rendering
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:            Couldn't lookup keysym
>                   Symbol interpretation ignored
> Error:            Couldn't lookup keysym
>                   Symbol interpretation ignored
Errors from xkbcomp are not fatal to the X server
xdm info (pid 642): sourcing /etc/X11/xdm/Xsetup_0
xdm info (pid 642): sourcing /etc/X11/xdm/GiveConsole
xdm info (pid 2073): executing session /etc/X11/xdm/Xsession


If the full Xorg.0.log is helpful, I'll post in a followup.
>How-To-Repeat:
Start X server with "-retro" option on system using Via UniChrome
hardware ("openchrome" Xorg driver).  Or start full Xsession which
should cause mouse cursor to be redrawn.  Fail to observe a mouse
cursor, but note behavior of graphical elements under the point.
>Fix:
Workaround:

Use a minimal "xorg.conf" which includes

  Option     "SWCursor"                   # [<bool>]

in the "Device" section.

Follow-Ups:
- re: xsrc/49155: openchrome hardware cursor always invisible
  - From: matthew green

Prev by Date: NetBSD Nightly Trouble Ticket Report
Next by Date: re: xsrc/49155: openchrome hardware cursor always invisible
Previous by Thread: kern/49154: Can't find boot device if net-booted from sk(4) gigabit ethernet, prompts for root device
Next by Thread: re: xsrc/49155: openchrome hardware cursor always invisible
Indexes:

Home | Main Index | Thread Index | Old Index