From nobody Fri Nov 11 03:36:49 2022 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 4N7ksW3gKbz4d9Kj for ; Fri, 11 Nov 2022 03:37:03 +0000 (UTC) (envelope-from sr@genyosha.net) Received: from ns4.genyosha.net (ns4.genyosha.net [50.53.250.75]) (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 (2048 bits) client-digest SHA256) (Client CN "float.home.genyosha.net", Issuer "float.home.genyosha.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N7ksV4yl6z3mkg for ; Fri, 11 Nov 2022 03:37:02 +0000 (UTC) (envelope-from sr@genyosha.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of sr@genyosha.net designates 50.53.250.75 as permitted sender) smtp.mailfrom=sr@genyosha.net; dmarc=none Received: from dragon.home.genyosha.net (ops.genyosha.net [50.53.250.77]) by ns4.genyosha.net (8.16.1/8.16.1) with ESMTPS id 2AB3asS6031438 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 Nov 2022 19:36:54 -0800 (PST) (envelope-from sr@genyosha.net) Received: from dragon.home.genyosha.net (localhost [127.0.0.1]) by dragon.home.genyosha.net (8.14.7/8.14.7) with ESMTP id 2AB3anf6015819; Thu, 10 Nov 2022 19:36:49 -0800 Received: (from sr@localhost) by dragon.home.genyosha.net (8.14.7/8.14.7/Submit) id 2AB3anw5015818; Thu, 10 Nov 2022 19:36:49 -0800 Date: Thu, 10 Nov 2022 19:36:49 -0800 From: Steve Rikli To: freebsd-current@FreeBSD.org Cc: louis.freebsd@xs4all.nl Subject: Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT) Message-ID: References: <001901d8f543$1dab2900$59017b00$@xs4all.nl> <01051bc5-07fd-95c5-1309-6358a8f971e5@FreeBSD.org> 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 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <01051bc5-07fd-95c5-1309-6358a8f971e5@FreeBSD.org> X-Greylist: inspected by milter-greylist-4.6.4 (ns4.genyosha.net [50.53.250.75]); Thu, 10 Nov 2022 19:36:55 -0800 (PST) for IP:'50.53.250.77' DOMAIN:'ops.genyosha.net' HELO:'dragon.home.genyosha.net' FROM:'sr@genyosha.net' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (ns4.genyosha.net [50.53.250.75]); Thu, 10 Nov 2022 19:36:55 -0800 (PST) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-current@FreeBSD.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:20055, ipnet:50.53.0.0/16, country:US]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEMAIL_CC(0.00)[xs4all.nl]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[genyosha.net]; SUBJECT_HAS_QUESTION(0.00)[] X-Rspamd-Queue-Id: 4N7ksV4yl6z3mkg X-ThisMailContainsUnwantedMimeParts: N On Thu, Nov 10, 2022 at 10:21:24PM -0500, Alexander Motin wrote: > On 10.11.2022 15:29, louis.freebsd@xs4all.nl wrote: > > I am still desperately trying to stop FreeBSD from sleeping, but I > > simply do not manage. > > > > It is really very annoying that I have to restart the machine every 10 > > minutes, when I am working via SSH. > > > > So if any one has a solution, it would be very much appreciated! > > > > It should ….. be possible to kill / stop ACPI some how 😊 > > > > If absolutely not possible in the actual build 😊, a cron job restarting > > the timer every 5 minutes perhaps !!??? > > I've never used it, so just an idea, but there is sysctl > kern.suspend_blocked that being set to 1 seems should block suspend > requests. You may try to set it and see what happen. > > > It is possible perhaps … that GNOME is initiating this, despite that the > > GUI powersetting is screenblank β€œNEVER”. > > It is not a screen blank. Gnome site tells: > https://help.gnome.org/users/gnome-help/stable/power-autosuspend.html.en > > > Whatever is causing the problem, the settings should be such that ^no > > whatever program^ should not be capable to initiate the sleepmode. > > Does the system suspends if you do not start Gnome? For example if you boot > into single-user mode and leave the system there? It would be the easiest > test probably. This sounds somewhat like the Gnome gdm3 behavior that causes some(?) Linuxes to suspend & sleep after 20 minutes (ymmv?) by default if gdm3 is running. E.g. https://wiki.debian.org/Suspend IME it didn't matter if user was logged in to desktop or not, the mere presence of a running gdm3 process was enough to trigger the behavior unless it was disabled. My FreeBSD's without gdm3 don't see this. Obviously there's no Linux systemD in-play here, but along the lines Alexander suggests, you might try stopping any running gdm3 processes and see if the sleep behavior persists. That would at least give some hint as to the vicinity of the problem. sr.