From nobody Mon Jul 03 21:43:11 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Qvztm4Qr5z4lDPw for ; Mon, 3 Jul 2023 21:43:12 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Qvztm41sRz3QgK; Mon, 3 Jul 2023 21:43:12 +0000 (UTC) (envelope-from mhorne@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1688420592; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c84YqOnBD9qxytllxE9VgolHOmIbyoJsLT4qeipV77w=; b=fKZUONXPGEt+mV4VlSi6JC4q7VMOfcHhcEBJhr0ZOaPuV6KMfNBT14dtHpZcdwGX+y+/w+ DmJgvzBWDBe+cD7p9l+3eLoLnR7sBrryBrTVVk/SVaJLXX7o0GVaQBBZx97V5xbQe8jYKq A8UkKhw8qbKcIKE25iphUsAJsX87ymZO0gSeNcuCfys+zQ/ZCV/EggaqleiMwqQcp6wNZz H2kFiE1juqR3fWkSnR3X6zTCsZVIxWnQmIxnEuQ2+U9kBkisqAF8jxTZkUfptZaKjE9ezW xNSo2sI5uYkVmBdrTQ6APyI7hDGHvfexXHkIjX5uwSOpsURouZ4T2jboNQDHhA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1688420592; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c84YqOnBD9qxytllxE9VgolHOmIbyoJsLT4qeipV77w=; b=sezh3mlZKaKvuvg9fxR2oA1/UZgH0B/CJccyixchfsqxUN/Vy/ZSBhSJij72criwf9w+M9 lB34xRNoJhDzif0VHQF13dUZ0y2OkkZft76zu35/la6aSSkz7z5MUT2CQ96H7D8dq2ObXb AxOINBLdNSiiz1Uo1OaKbjG1oqqMouU1H1AHjVzGbC0GX80PR+jPaM7RuYW+S0CQx3Zqyf BqEP5N6v5a3iCBIvug69HLfsIOBF9dgUi2RbjE5x2Le128Re1tgpebZHPyHiftZ4/xchrI LDhQdScwykRwjSJSdtpy8H6trDCYv41aLcOwo00Um1H9FX9sj8BbMadsIV6oiQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1688420592; a=rsa-sha256; cv=none; b=KnAzu93zb/I4DnroGeYK4ZI/TSMzJ48JvnRJZRjT3X2BBDX3TbmXgD4aPiUPqJYJ0iubAg +9g6fpr974bU9PXNVKTsRhVXAj6+LP/47457EfMnEGYuCSVwN6D7DW7Q2Z5SV9SuBwDLHv 8WKgAQIZmFmQdik+KQneTfqjjThLu6z5XBn4Rf4nPKv1+9TP538e6FbqGm0gE1KI5hjXt/ EkBRLvn2weFT2x3az3eWdgWTL5D4TSmULx8kH43y3Xmc6tb/y0mRptFxYkBoz0WhXWAMmp 4yqvyuEOdKjh0qbwkf4n9EctqmRWvOiXWHraKaoLvE1A7M0br/ut7Ym07IHCQQ== Received: from [192.168.1.151] (host-173-212-76-127.public.eastlink.ca [173.212.76.127]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: mhorne) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Qvztm1v6zz1CP1; Mon, 3 Jul 2023 21:43:12 +0000 (UTC) (envelope-from mhorne@freebsd.org) Message-ID: Date: Mon, 3 Jul 2023 18:43:11 -0300 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: System lockups on 14-current with Plasma 5 Content-Language: en-CA To: Patrick McMunn , freebsd-current@freebsd.org References: From: Mitchell Horne In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N On 7/3/23 18:20, Patrick McMunn wrote: > I was just wondering if anyone else has experienced random freezes where > everything except the mouse cursor becomes completely unresponsive. > > This began when I would come to my computer in the morning and find the > screen black and the system in sleep mode. It would not wake up to > keypresses or mouse movement. So I disabled power management in Plasma > 5. This still happened after disabling power management, so I disabled > the screensaver. That's when I would come to find my computer in the > morning with the screen still on, but as soon as I would click on > anything, everything but the cursor would freeze. At first, I thought it > would happen only after being idle a long time. But then it began to > happen while actively using the system after even a short time like less > than an hour. It progressively became more frequent over a few days > until it would happen immediately upon logging into Plasma 5. > > I originally installed 14-current onto a spare laptop hard drive that I > installed on a secondary SATA port on my desktop just so I could test > it. But after these issues occurred, I suspected a faulty hard drive and > decided to install 14-current onto my main hard drive in a separate > partition alongside Windows 10 and Gentoo. I went ahead and disabled > sleep power management and the screensaver on the new installation. But > I soon began  to experience random lockups during use. > > I installed Gnome 3, LXQT, and Cinnamon desktops to try as alternatives. > Maybe I haven't tested enough, but I have yet to experience any lockups > with these other desktop environments. > > I had previously run Plasma 5 from quarterly on 13.2-release without any > lockups. So maybe it's an issue with Plasma 5 from the latest repo. It's > hard to know since there apparently is no quarterly repo available for > 14-current. So it's unclear whether the issue is with the latest Plasma > 5 or some compatibility issue with Plasma 5 on 14-current that I did not > experience on 13.2-release. Hi, I experienced some similar symptoms a while back on -current with KDE. After some investigation I found that the system was panicking due to some failed debug assertion triggered by the nvidia graphics driver. As a result, the system would drop to the debugger, but was unable to switch virtual terminals, so it appeared to hang. My solution was just to start running the GENERIC-NODEBUG kernel instead. Does the system respond to network pings after the lock-up occurs? If not then perhaps you are experiencing this type of silent panic. You can set the debug.debugger_on_panic sysctl value to 0, which should result in an immediate reboot+kernel dump when such a panic occurs. Hope it helps. Mitchell