NetBSD Problem Report #57387
From jmclists@jmcunx.com Mon May 1 18:03:25 2023
Return-Path: <jmclists@jmcunx.com>
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 B0B621A9238
for <gnats-bugs@gnats.NetBSD.org>; Mon, 1 May 2023 18:03:25 +0000 (UTC)
Message-Id: <ZE/+4ruSDAzwQ1Hu@neutron.jmcunx.com>
Date: Mon, 1 May 2023 14:03:14 -0400
From: John McCue <jmclists@jmcunx.com>
To: gnats-bugs@NetBSD.org
Subject: External Monitor corruption, 10.0 BETA
>Number: 57387
>Category: port-amd64
>Synopsis: External Monitor corruption
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: port-amd64-maintainer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon May 01 18:05:00 +0000 2023
>Closed-Date: Sun Mar 17 01:30:29 +0000 2024
>Last-Modified: Sun Mar 17 01:30:29 +0000 2024
>Originator: John McCue
>Release: NetBSD 10.0_BETA
>Organization:
just me
>Environment:
see File netbsd_ident.txt in
https://github.com/jmcunx/nconfig/blob/main/netbsd_ident.txt
System: NetBSD neutron.jmcunx.com 10.0_BETA NetBSD 10.0_BETA (GENERIC) #0: Tue Apr 25 16:17:59 UTC 2023 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
Architecture: x86_64
Machine: amd64
>Description:
Under heavy load, the screen for my External Monitor
gets corrupted. The monitor is an ACER Model V276HL.
This is on a Thinkpad T420.
https://github.com/jmcunx/nconfig
contains various configs and a screen print.
This does not occur when using only the Laptop Screen.
>How-To-Repeat:
Start a long running process with a high CPU load,
usually within 1 hour corruption starts.
Config files with a screen print can be seen in:
https://github.com/jmcunx/nconfig
>Fix:
I need kill my background process and restart X,
I know of no other fix.
>Release-Note:
>Audit-Trail:
From: John McCue <jmclists@jmcunx.com>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-amd64/57387
Date: Mon, 1 May 2023 15:53:10 -0400
I tried other tests and noticed the following:
1. X11/picom has no effect, some sites said it would help.
2. This is the interesting, I kicked off my heavy process
and it was executing without corrupting X for a while.
I then started gvim(1) 9.0.960 and instantly X was corrupted.
I wonder if it could be related to gtk3 ?
From: John McCue <jmclists@jmcunx.com>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-amd64/57387
Date: Mon, 1 May 2023 16:38:34 -0400
I decided to remove package:
vim-gtk3-9.0.0960
and installed
vim-motif-9.0.0960
That made no difference, the issue also occurred with
vim-motif-9.0.0960
From: John McCue <jmclists@jmcunx.com>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-amd64/57387
Date: Sat, 16 Mar 2024 14:46:22 -0400
I would recommend this be closed.
After testing through the various RCs, I believe the issue
has something to do with xdm(8) and X Org.
When I use startx(1), all works fine, when I run via xdm(8)
the issue will occur after a heavy process has been executing
after about 1 hour.
I will create a new PR after additional testing on RC6 if I
think one is needed.
Thanks
John
State-Changed-From-To: open->closed
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Sun, 17 Mar 2024 01:30:29 +0000
State-Changed-Why:
closed by submitter's request
>Unformatted:
10.0_BETA NetBSD 10.0_BETA (GENERIC) #0: Tue Apr 25 16:17:59 UTC 2023
(Contact us)
$NetBSD: query-full-pr,v 1.47 2022/09/11 19:34:41 kim Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2024
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.