NetBSD Problem Report #53773

From martin@duskware.de  Mon Dec 10 16:58:34 2018
Return-Path: <martin@duskware.de>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 3B3467A183
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 10 Dec 2018 16:58:34 +0000 (UTC)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: xfwm4 crashes with composititing enabled
X-Send-Pr-Version: 3.95

>Number:         53773
>Category:       lib
>Synopsis:       xfwm4 crashes with composititing enabled
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    lib-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Dec 10 17:00:00 +0000 2018
>Last-Modified:  Tue Dec 11 00:55:01 +0000 2018
>Originator:     Martin Husemann
>Release:        NetBSD 8.99.27
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD night-owl.duskware.de 8.99.27 NetBSD 8.99.27 (NIGHT-OWL) #638: Fri Dec 7 12:24:17 CET 2018 martin@night-owl.duskware.de:/usr/src/sys/arch/amd64/compile/NIGHT-OWL amd64
Architecture: x86_64
Machine: amd64
>Description:

(Might be a pkg problem, but filing against base libmesa for now)

As soon as I enable compositing (the default is on!) for xfwm4, the window
manager crashes on my machine.

Core was generated by `xfwm4'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f7fe5c1010a in ?? ()
#1  0x00007f7fe4e5879d in _mesa_map_function_spec (spec=0x7f7fe518c90b "", 
    spec@entry=0x7f7fe518c8d2 "iiiiiip") at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/main/remap.c:109
#2  0x00007f7fe4e588e7 in _mesa_do_init_remap_table (size=747, remap=0x7f7fe5186b60, pool=<optimized out>)
    at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/main/remap.c:203
#3  _mesa_init_remap_table () at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/main/remap.c:217
#4  0x00007f7fe4eb895c in one_time_init (ctx=0x7f7ff67a1000)
    at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/main/context.c:423
#5  _mesa_initialize_context (ctx=ctx@entry=0x7f7ff67a1000, api=api@entry=API_OPENGL_COMPAT, 
    visual=visual@entry=0x7f7fffffdc10, share_list=share_list@entry=0x0, 
    driverFunctions=driverFunctions@entry=0x7f7fffffd650)
    at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/main/context.c:1104
#6  0x00007f7fe4eb91f3 in _mesa_create_context (api=api@entry=API_OPENGL_COMPAT, 
    visual=visual@entry=0x7f7fffffdc10, share_list=share_list@entry=0x0, 
    driverFunctions=driverFunctions@entry=0x7f7fffffd650)
    at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/main/context.c:1225
#7  0x00007f7fe4d6ab06 in st_create_context (api=api@entry=API_OPENGL_COMPAT, 
    pipe=pipe@entry=0x7f7ff73ab000, visual=visual@entry=0x7f7fffffdc10, share=share@entry=0x0, 
    options=options@entry=0x7f7fffffdd48)
    at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/state_tracker/st_context.c:266
#8  0x00007f7fe4d67e32 in st_api_create_context (stapi=<optimized out>, smapi=0x7f7ff7b44c40, 
    attribs=0x7f7fffffdd20, error=0x7f7fffffdd1c, shared_stctxi=0x0)
    at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/state_tracker/st_manager.c:665
#9  0x00007f7fe4cb6d45 in dri_create_context (api=<optimized out>, visual=0x7f7ff7b45ab0, 
    cPriv=0x7f7ff7334fd0, major_version=<optimized out>, minor_version=<optimized out>, 
    flags=<optimized out>, notify_reset=false, error=0x7f7fffffde3c, sharedContextPrivate=0x0)
    at /usr/xsrc/external/mit/MesaLib/dist/src/gallium/state_trackers/dri/dri_context.c:112
#10 0x00007f7fe4cbcfbd in driCreateContextAttribs (screen=0x7f7ff7b44b90, api=api@entry=0, 
    config=0x7f7ff7b45ab0, shared=<optimized out>, num_attribs=num_attribs@entry=0, 
    attribs=attribs@entry=0x0, error=error@entry=0x7f7fffffde3c, data=0x7f7ff73a10b0)
    at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/drivers/dri/common/dri_util.c:435
#11 0x00007f7fe4cbd0ea in driCreateNewContextForAPI (data=<optimized out>, shared=<optimized out>, 
    config=<optimized out>, api=0, screen=<optimized out>)
    at /usr/xsrc/external/mit/MesaLib/dist/src/mesa/drivers/dri/common/dri_util.c:464


Display is:

radeon0 at pci1 dev 0 function 0: vendor 1002 product 68e0 (rev. 0x00)
radeon0: info: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used)
radeon0: info: GTT: 1024M 0x0000000020000000 - 0x000000005FFFFFFF
kern info: [drm] Detected VRAM RAM=200M, BAR=256M
kern info: [drm] RAM width 64bits DDR
Zone  kernel: Available graphics memory: 1124686 kiB
kern info: [drm] radeon: 512M of VRAM memory ready
kern info: [drm] radeon: 1024M of GTT memory ready.
kern info: [drm] Loading CEDAR Microcode
kern info: [drm] Internal thermal controller without fan control
kern info: [drm] radeon: dpm initialized
kern info: [drm] GART: num cpu pages 262144, num gpu pages 262144
kern info: [drm] PCIE GART of 1024M enabled (table at 0x000000000025E000).
radeon0: info: WB enabled
radeon0: info: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0x0xffff963ad67d2c00
radeon0: info: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0x0xffff963ad67d2c0c
radeon0: info: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0x0xffffad0065fdc418
kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
kern info: [drm] Driver supports precise vblank timestamp query.
radeon0: info: radeon: MSI limited to 32-bit
radeon0: interrupting at ioapic0 pin 16 (radeon0)
..
radeondrmkmsfb0 at radeon0
radeondrmkmsfb0: framebuffer at 0xffffad0066608000, size 1600x900, depth 32, stride 6400
wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0

>How-To-Repeat:
see above

>Fix:
n/a

>Audit-Trail:
From: matthew green <mrg@eterna.com.au>
To: gnats-bugs@NetBSD.org
Cc: lib-bug-people@netbsd.org, gnats-admin@netbsd.org,
    netbsd-bugs@netbsd.org
Subject: re: lib/53773: xfwm4 crashes with composititing enabled
Date: Tue, 11 Dec 2018 11:51:52 +1100

 i'm not sure this is the same, but the GPU is the same generation
 (CEDAR).  i had an uncommon crash in mesa where it would be accessing
 some allocated space but the allocation was smaller than expected,
 in the few cases i debugged closer, the accessses were 128 bytes
 after the end of the actual mapping.  i was guessing some mmap size
 is being truncated and the final page is missed, but i was not able
 to figure out where these allocations were created.

 i saw crashes in firefox and mpv mostly, but ksudoku also crashed
 at least once.

 i ended up putting a radeon3650 card in my desktop.  (it was also
 silent, and benchmarks roughly 1.5x the speed of the newer CEDAR.)


 .mrg.

Home	PR Database Search