NetBSD Problem Report #57105

From mlelstv@arnold.localdomain  Sat Dec 10 16:29:28 2022
Return-Path: <mlelstv@arnold.localdomain>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_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 4E1711A921F
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 10 Dec 2022 16:29:28 +0000 (UTC)
Message-Id: <20221210162925.934F3BC15D@arnold.localdomain>
Date: Sat, 10 Dec 2022 17:29:25 +0100 (CET)
From: mlelstv@netbsd.org
Reply-To: mlelstv@netbsd.org
To: gnats-bugs@NetBSD.org
Subject: random Xorg crashes
X-Send-Pr-Version: 3.95

>Number:         57105
>Category:       xsrc
>Synopsis:       random Xorg crashes
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    xsrc-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Dec 10 16:30:01 +0000 2022
>Closed-Date:    
>Last-Modified:  Tue Nov 07 09:16:25 +0000 2023
>Originator:     Michael van Elst
>Release:        NetBSD 9.99.108
>Organization:

>Environment:


System: NetBSD arnold 9.99.108 NetBSD 9.99.108 (EGGHED64) #64: Sat Dec 10 14:15:08 UTC 2022 mlelstv@slowpoke:/home/netbsd-current/obj.evbarm64-el/scratch/netbsd-current/src/sys/arch/evbarm/compile/EGGHED64 evbarm
Architecture: aarch64
Machine: evbarm
>Description:

After updating to latest Xorg and pixman the X server can be crashed
easily by scrolling in an xterm, e.g. by running 'dmesg' to produce
output.

This is a dumb genfb display, no drm or other magic involved.

Restoring Xorg and libpixman* from Oct 29th makes it stable again.

>How-To-Repeat:
Scroll in xterm.
>Fix:


>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: tnn@NetBSD.org
State-Changed-When: Mon, 06 Nov 2023 22:58:55 +0000
State-Changed-Why:
I think I have this problem when using xf86-video-wsfb.
If you can still reproduce this, could you test if running
Xorg with the "-dumbSched" option makes it stable again?
I think the new smart scheduling code in Xorg triggers some
aarch64 specific signal handling and/or setcontext(2) bug.


From: Michael van Elst <mlelstv@serpens.de>
To: gnats-bugs@netbsd.org
Cc: xsrc-manager@netbsd.org, netbsd-bugs@netbsd.org, gnats-admin@netbsd.org,
	tnn@NetBSD.org, mlelstv@netbsd.org
Subject: Re: xsrc/57105 (random Xorg crashes)
Date: Tue, 7 Nov 2023 07:09:04 +0100

 On Mon, Nov 06, 2023 at 10:58:56PM +0000, tnn@NetBSD.org wrote:
 > Synopsis: random Xorg crashes
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: tnn@NetBSD.org
 > State-Changed-When: Mon, 06 Nov 2023 22:58:55 +0000
 > State-Changed-Why:
 > I think I have this problem when using xf86-video-wsfb.
 > If you can still reproduce this, could you test if running
 > Xorg with the "-dumbSched" option makes it stable again?
 > I think the new smart scheduling code in Xorg triggers some
 > aarch64 specific signal handling and/or setcontext(2) bug.

 I think the problem was removed by un-merging pixman 0.42.2 and
 re-merging 0.38.4 a few days later.


 Greetings,
 -- 
                                 Michael van Elst
 Internet: mlelstv@serpens.de
                                 "A potential Snark may lurk in every tree."

State-Changed-From-To: feedback->open
State-Changed-By: tnn@NetBSD.org
State-Changed-When: Tue, 07 Nov 2023 09:16:25 +0000
State-Changed-Why:
Feedback provided. (Perhaps should be closed?)


>Unformatted:

Home	PR Database Search