NetBSD Problem Report #58217

From www@netbsd.org  Tue Apr 30 13:32:00 2024
Return-Path: <www@netbsd.org>
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 0D1951A9238
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 30 Apr 2024 13:32:00 +0000 (UTC)
Message-Id: <20240430133158.B1CB51A923A@mollari.NetBSD.org>
Date: Tue, 30 Apr 2024 13:31:58 +0000 (UTC)
From: jmclists@jmcunx.com
Reply-To: jmclists@jmcunx.com
To: gnats-bugs@NetBSD.org
Subject: Under heavy load, Xorg screen gets corrupted
X-Send-Pr-Version: www-1.0

>Number:         58217
>Category:       port-amd64
>Synopsis:       Under heavy load, Xorg screen gets corrupted
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    port-amd64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 30 13:35:00 +0000 2024
>Originator:     John McCue
>Release:        10.0 amd64, Thinkpad T420
>Organization:
>Environment:
NetBSD neutron.jmcunx.com 10.0 NetBSD 10.0 (GENERIC) #0: Thu Mar 28 08:33:33 UTC 2024  mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>Description:
When a heavy process has run for a while, Xorg screen gets corrupted.  95% of the time exiting and restarting X will correct.  But artifacts will eventually reappear until the process ends.  Usually happens after the process has been executing for about 1 hour.

dmesg, Xlog.0.log and indent /netbsd is here:

    https://dmesgd.nycbug.org/index.cgi?do=view&id=7725

Screen print is here:

    https://www.jmcunx.com/data/jmcnetbsd.jpg

The issue occurs when verifying a sha256 using cksum(1) on a 43G Text File.  But other heavy processes that execute for a long time can cause the same problem.

>How-To-Repeat:
Start a heavy process that will run for more than an hour.

The easiest way is to verify a SHA256 cksum on a extremely File (see description above).

>Fix:
If I exit X and go back in, the issue will resolve itself.  But if the process is still executing, the artifacts will re-appear after a period of time.

Home	PR Database Search