NetBSD Problem Report #49155

From www@NetBSD.org  Tue Aug 26 20:50:57 2014
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id CFC0CB68E3
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 26 Aug 2014 20:50:57 +0000 (UTC)
Message-Id: <20140826205055.DB06CB6971@mollari.NetBSD.org>
Date: Tue, 26 Aug 2014 20:50:55 +0000 (UTC)
From: jdbaker@mylinuxisp.com
Reply-To: jdbaker@consolidated.net
To: gnats-bugs@NetBSD.org
Subject: openchrome hardware cursor always invisible
X-Send-Pr-Version: www-1.0

>Number:         49155
>Notify-List:    jdbaker@consolidated.net
>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
>Last-Modified:  Tue Jan 29 06:31:41 +0000 2019
>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:/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:/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:/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.

>Release-Note:

>Audit-Trail:
From: matthew green <mrg@eterna.com.au>
To: gnats-bugs@NetBSD.org
Cc: xsrc-manager@netbsd.org, gnats-admin@netbsd.org,
    netbsd-bugs@netbsd.org
Subject: re: xsrc/49155: openchrome hardware cursor always invisible
Date: Wed, 27 Aug 2014 10:53:08 +1000

 can you try this without viadrm attached?  just to see if it works...

 thanks.

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: re: xsrc/49155: openchrome hardware cursor always invisible
Date: Tue, 26 Aug 2014 21:45:55 -0500 (CDT)

 On Wed, 27 Aug 2014, matthew green wrote:

 >  can you try this without viadrm attached?  just to see if it works...

 With "viadrm" diabled, the X server fails to start.

 NetBSD 7.99.1 (NEOWARE) #5: Sun Aug 24 20:25:53 CDT 2014
         sysop@verthandi.technoskunk.fur:/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
 userconf: configure system autoconfiguration:
 uc> disable viadrm
 [ 46] viadrm* disabled
 uc> exit
 [...]
 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
 drm at vga0 not configured


 $ cat /var/log/xdm.log                                   
 xdm info (pid 1624): Starting
 xdm error (pid 1624): XDMCP socket multicast join to ff02::12b failed, errno 49
 xdm info (pid 1624): 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:/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: Tue Aug 26 21:30:39 2014
 (==) Using default built-in configuration (21 lines)
 (EE) CHROME(0): [drm] Failed to open DRM device for pci:0001:01:00.0: Device not configured
 Linear memory allocation failed
 DRM memory allocation failed -12
 Segmentation fault at address 0x10

 Fatal server error:
 Caught signal 11 (Segmentation fault). Server aborting


 Please consult the The X.Org Foundation support 
          at http://wiki.X.Org
  for help. 
 Please also check the log file at "/var/log/Xorg.0.log" for additional information.

 xdm error (pid 1624): server unexpectedly died
 xdm error (pid 1624): Server for display :0 can't be started, session disabled


 I don't see an option to disable DRI in the server/device configuration.

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: xsrc/49155: openchrome hardware cursor always invisible
Date: Tue, 10 Jul 2018 19:32:31 -0500 (CDT)

 With the recent changes surrounding "viadrm"->"viadrmums", I should
 dig this machine out and see if the issue in this PR may have been
 (silently) addressed.

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: xsrc/49155: openchrome hardware cursor always invisible
Date: Wed, 11 Jul 2018 20:52:50 -0500 (CDT)

 On Tue, 10 Jul 2018, John D. Baker wrote:

 > With the recent changes surrounding "viadrm"->"viadrmums", I should
 > dig this machine out and see if the issue in this PR may have been
 > (silently) addressed.

 No, the problem remains.  No visible mouse cursor.  Will check that
 the "Option SWCursor" still provides a workaround.

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From: Andrius V <vezhlys@gmail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: xsrc/49155: openchrome hardware cursor always invisible
Date: Thu, 12 Jul 2018 10:29:37 +0300

 Hi,

 The same problem exists in my machine too (CN400 chipset, UniChrome
 Pro), including viadrmums. Software cursor works.
 On Thu, Jul 12, 2018 at 4:55 AM John D. Baker <jdbaker@mylinuxisp.com> wrote:
 >
 > The following reply was made to PR xsrc/49155; it has been noted by GNATS.
 >
 > From: "John D. Baker" <jdbaker@mylinuxisp.com>
 > To: gnats-bugs@NetBSD.org
 > Cc:
 > Subject: Re: xsrc/49155: openchrome hardware cursor always invisible
 > Date: Wed, 11 Jul 2018 20:52:50 -0500 (CDT)
 >
 >  On Tue, 10 Jul 2018, John D. Baker wrote:
 >
 >  > With the recent changes surrounding "viadrm"->"viadrmums", I should
 >  > dig this machine out and see if the issue in this PR may have been
 >  > (silently) addressed.
 >
 >  No, the problem remains.  No visible mouse cursor.  Will check that
 >  the "Option SWCursor" still provides a workaround.
 >
 >  --
 >  |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 >  |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 >  | X  No HTML/proprietary data in email.   BSD just sits there and works!
 >  |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645
 >

From: maya@netbsd.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: xsrc/49155: openchrome hardware cursor always invisible
Date: Thu, 12 Jul 2018 08:44:44 +0000

 I think that our copy of the via driver might not do hardware cursor
 yet, at least there are no code references if I am searching correctly.

 The person creating the xorg openchrome driver is also working on a
 kernel side driver update (for linux), and he added support for it.
 (for the curious, his repositories are here:
 https://cgit.freedesktop.org/openchrome/ )

 At least from random searching it is probably a big deal to have a
 hardware cursor, but we don't have one so we should probably force
 swcursor somewhere/detect better.

 (or: updating the xorg driver without the kernel driver proved to be a
 bad idea in this case)

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: xsrc/49155: openchrome hardware cursor always invisible
Date: Thu, 12 Jul 2018 16:08:26 -0500 (CDT)

 On Wed, 11 Jul 2018, John D. Baker wrote:

 > On Tue, 10 Jul 2018, John D. Baker wrote:
 > 
 > > With the recent changes surrounding "viadrm"->"viadrmums", I should
 > > dig this machine out and see if the issue in this PR may have been
 > > (silently) addressed.
 > 
 > No, the problem remains.  No visible mouse cursor.  Will check that
 > the "Option SWCursor" still provides a workaround.

 "Option SWCursor" produces a working (visible) mouse cursor.  The
 following minimal "xorg.conf" file (clipped from the builtin config
 written to "/var/log/Xorg.0.log" and edited to suit) is sufficient
 if the monitor/screen/display is otherwise properly detected:


 Section "Device"
         Identifier      "Builtin Default openchrome Device 0"
         Option     "SWCursor"           	# [<bool>]
         Driver  "openchrome"
 EndSection


 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.