From nobody Tue Jul 15 01:36:50 2025 X-Original-To: freebsd-questions@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 4bh1zV1Fp9z61kMP for ; Tue, 15 Jul 2025 01:38:14 +0000 (UTC) (envelope-from humo3302@gmail.com) Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bh1zT3qNqz3m6m for ; Tue, 15 Jul 2025 01:38:13 +0000 (UTC) (envelope-from humo3302@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-311c95ddfb5so3931523a91.2 for ; Mon, 14 Jul 2025 18:38:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1752543487; x=1753148287; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=HKkm5jlcHbX/HDh1ZyfI2uWdkc6MPaQuNUUBapePre8=; b=If1DuJEY9zczvssL4CSnIPmXfCOwgMxyBbkm2/IVfD5crevsQpEyOpJzQKK8HfFBWc g/xRPcquOGLub459UMlh7yNO2d/VudVlQ5nvq4dWIwCjHICH7q4XewetlwU+7LqP6voE 0SzSpoZDGqtv2grOaNr2XL4aaOJjvnQw3jEksz16h4d2fIsiOgVanphUcT1sNsAGRCJR XxTVBSPB6zrvuIG67qk8RhejvWSRnI8A2FwV90SMnbVst0A1bEo4llJwBfxzhOciz1wG qnX+BR4nndJBlp14d0g53QerXfJQFH/C+DY1WGpqMJFXkUUpropss4A6uleY3MDETGLw Ud5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752543487; x=1753148287; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=HKkm5jlcHbX/HDh1ZyfI2uWdkc6MPaQuNUUBapePre8=; b=ZtBQvZSnS5Yw3on789tdqmNPc48U4pWe76R20GdZRJq2knqua9xEEDG+OzVOP/Xrv7 qIVNeYZFxuJriXjmvRtnIbD24pXejVTL48uwzfOMi+TX7Q9cAdSD58KvzWBwqCDiN9BN R0EAC2OaPlzmANe3SIYYFOW5zxW92KfNaN75zSn3bHf0lmQrcNZumoKP9TNOOFXCddtU QQt+cB7sbRhSNvcvkN9aNOOsOlLuuBC8pi2EPeQzYdLtHifrL5zFkh7DJ4+H97yXwzXS vo7Kam4icjQ5KK/4TNQ/m4687PifRmFkWBOLFQncDZyce7sD+X3NI1ssvPV2XpR6RREQ mTug== X-Forwarded-Encrypted: i=1; AJvYcCWLLQ4GKZpkJFGByWzLD1Sgc4OgEh1onTEFbhsEZJJbHipe9W2flOVvJGqumo3QAaDbzb2t7pPRO5YjUSPG6cOE3w==@freebsd.org X-Gm-Message-State: AOJu0YyUGZ1/1xdiYSwAnt9JrLq5zPtjE6Xc3ihsRJw+d1xZvQeuZkpF QQetFV0oy0ysiMI2z2Owg6HAvMNBge78Iy7QQk7mgbuSMoQGnpQP+op2VN8UbE+oVuOpFbtkIwW +pr/n/Sh6RetoYAWGuNT32lxz3suufthi4ane X-Gm-Gg: ASbGncum8ds4p56/vSBF0vHL7AKyvaQEPjL9Av614LLYV5VV/6Pz4StLhupYqWS+S7I yAvy+oBjTbLgxu8edZpL4nWZAfj5J8xFt4T/urfjIMIN3379T0l9YXeNmU8ZlDWny8VqSdB7nie TCZek/+Y7HcSQTwanstbzYVWxQ91Tmq25ob+l1/perhgI+wtQkatfxZzX+TTVTmOEtcouDSC4Lp I5rGnSQzQ== X-Google-Smtp-Source: AGHT+IGk6U7YpySLZUY4bzwOYCfUvi78uZPiJVJYpFSVDOVLQttNbkNLU6AJPOBetUsddVtqeVLZf7i7kYtFYGFmk6M= X-Received: by 2002:a17:90b:58c8:b0:315:9cae:bd8 with SMTP id 98e67ed59e1d1-31c4cd87c8dmr21599060a91.23.1752543487021; Mon, 14 Jul 2025 18:38:07 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Mauricio Date: Mon, 14 Jul 2025 21:36:50 -0400 X-Gm-Features: Ac12FXwFYS2Mz1SMdOIFi5Ye_NjjERDJNmCNgAXzD31ZaxqkyLqY_EQPb_YFt70 Message-ID: Subject: Re: HP Laptop freezes while using Xorg sporadically. To: "Edward Sanford Sutton, III" , freebsd-questions Content-Type: multipart/alternative; boundary="000000000000ff569d0639edd38a" X-Rspamd-Queue-Id: 4bh1zT3qNqz3m6m X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] --000000000000ff569d0639edd38a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > Have you used other versions of FreeBSD or another operating system > without issue or is this a new-to-you computer with no known history > good or bad? I have used another FreeBSD version where this didn't happen. 14.2 RELEASE specifically. Other systems like GNU/Linux had never presented that kind of error on this machine. > Have you tried different versions of graphics/drm-*-kmod packages? I > assume you installed them from the kmods repository but is that correct? I haven't tried any other versions of drm packages by now. And that's correct. I've installed it with the "FreeBSD-kmods" repo they added on this version. > Do you have swap configured? If so, how much? 12GB enabled for this laptop. I know, maybe a bit too much. But the system handbook still recommends the double of RAM space for swap. I guess they have a reason... I will try to compile the drm package from ports to see if that helps with this problem. On the other things you pointed out: I will check on the Tests suite and will probably try testing the other drm packages. Oh and yeah, those mounting warnings got there because of forced shutdowns since the system don't respond to the power button correcly when it freezes= . I will try to keep y'all updated. On Mon, Jul 14, 2025 at 11:37=E2=80=AFAM Edward Sanford Sutton, III < mirror176@hotmail.com> wrote: > On 7/13/25 18:43, Mauricio wrote: > > I have an HP 255-G7 Laptop running FreeBSD 14.3 RELEASE which every now > > and then freezes entirely while using Xorg. When the laptop freezes, th= e > > only thing that gives me a response is mouse and graphic tablet movemen= t. > > Have you used other versions of FreeBSD or another operating system > without issue or is this a new-to-you computer with no known history > good or bad? > Have you tried different versions of graphics/drm-*-kmod packages? I > assume you installed them from the kmods repository but is that correct? > Trying some versions requires an older or newer FreeBSD version but it > might still help track down if it is a graphics driver bug that is > introduced or fixed in a newer version. > Is your BIOS up to date? HP's changelog of BIOS updates is too vague > to know if there are relevant fixes but you may want to look at > > https://support.hp.com/us-en/drivers/swdetails/hp-255-g7-notebook-pc/mode= l/24381328/swItemId/ob-345901-1 > (if I got the right machine) or even reach out to them for further > update changes. > > > At that point, I can't jump to a virtual console with > CTRL+ALT+FUNCTIONKEY. > > I can't even shut the computer down by pressing the shutdown button for > > less than a second as I usually do. > > But trying to do both things makes the disk activity light indicator > > start blinking a lot for a moment. > > Do you have swap configured? If so, how much? I've seen systems get > very slow and even hang when the was no swap and too much memory > pressure instead of just closing out processes as expected but haven't > tested such scenarios on 14.3. > > > The laptop doesn't seem to get back to work even after half an hour of > > waiting or more. > > Something that i have been noticing is that the freeze seems to be > > triggered by an increase of resources use. I noticed that because the > > freezing starts usually after opening a program like a terminal emulato= r > > while there are already some programs running in other windows. It also > > happened one time while trying to use my laptop while copying 23GBs of > > data in a virtual console. > > If you can narrow it down to a repeatable sequence then you could > more easily collect data from the occurrence. You could also try to push > the system into an expected bad state and preemptively use ctrl+alt+f1 > to see if anything shows up on the terminal during failure. > Are you able to reproduce without X running? > FreeBSD has a tests suite which runs through a series of checks. It > can take a long time to run, some tests will likely normally fail, and > some won't run until additional packages are installed. You can have it > run multiple tests in parallel which saves a massive amount of time but > then test results become more inconsistent. I normally reboot after > running it as it some some of the tests leave the system in a strange > state. Keeping logs of the results could help identify regressions with > new FreeBSD versions (tests and the OS both get reworked; its not always > clear at a glance if it is a new but broken test vs an old test started > failing that caused error count to go up) or help spot intermittent and > special case hardware failures. > There are other non-FreeBSD hardware tests that may be worth running. > Some are stand alone tools that boot separately like memtest86 but > others may need a Windows/Linux install to run from. You can look into > tests that overclockers use to verify system stability; overclock or > not, an unstable system may still show with the tools. These tools will > stress the system in ways that the FreeBSD test suite does not. I even > more recently found a system was intermittently but regularly crashing > while restoring a ZFS backup (resolved by slightly lowering clock > frequencies but most laptops don't offer such control). > Maybe useful to monitor temperatures too if the issue is not > repeatable. Physically cleaning even light dust off of hardware can also > stabilize some intermittent hardware that isn't overheating. > > > I leave some routine files here for you to check up if you feel the nee= d > > of it: > > > > dmesg output: https://pastebin.com/C27M5K0F < > https://pastebin.com/C27M5K0F> > > Probably just from incorrect shutdowns but I noticed disk mounting / > listed pending error; could run through SMART tests/checks and make sure > filesystem does fully clean up with correct shutdown or fsck. > > > rc.conf: https://pastebin.com/9wX0sKsa > > loader.conf: https://pastebin.com/wBrdL8NL < > https://pastebin.com/wBrdL8NL> > > > > As always, thanks to whoever that takes the time to help me with this. > > > > > --000000000000ff569d0639edd38a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Have you used other versions of FreeBSD or another op= erating system
> without issue or is this a new-to-you computer with= no known history
> good or bad?

I hav= e used another FreeBSD version where this didn't happen. 14.2 RELEASE= =C2=A0
specifically. Other systems like GNU/Linux had never prese= nted that kind of
error on this machine.

> Have you tried different versions of graphics/drm-*-kmod packages? I =
> assume you installed them from the kmods repository but is that co= rrect?=C2=A0

I haven't tried any other version= s of drm packages by now. And that's correct.
I've instal= led it with the "FreeBSD-kmods" repo they added on this version.<= /div>

> Do you have swap configured? If so, how much?= =C2=A0
12GB enabled for this laptop. I know, maybe a bit too much= .
But the system handbook still recommends the double of RAM spac= e for swap.
I guess they have a reason...

I will try to compile the drm package from ports to see if that helps wit= h this=C2=A0
problem.

On the other = things you pointed out: I will check on the Tests suite and will
= probably try testing the other drm packages.
Oh and yeah, those m= ounting warnings got there because of forced shutdowns
since the = system don't respond to the power button correcly when it freezes.

I will try to keep y'all updated.



On Mon, Jul 14, 2025 at 11:37=E2=80=AFA= M Edward Sanford Sutton, III <m= irror176@hotmail.com> wrote:
On 7/13/25 18:43, Mauricio wrote:
> I have an HP 255-G7 Laptop running FreeBSD 14.3 RELEASE which every no= w
> and then freezes entirely while using Xorg. When the laptop freezes, t= he
> only thing that gives me a response is mouse and graphic tablet moveme= nt.

=C2=A0 =C2=A0Have you used other versions of FreeBSD or another operating s= ystem
without issue or is this a new-to-you computer with no known history
good or bad?
=C2=A0 =C2=A0Have you tried different versions of graphics/drm-*-kmod packa= ges? I
assume you installed them from the kmods repository but is that correct? Trying some versions requires an older or newer FreeBSD version but it
might still help track down if it is a graphics driver bug that is
introduced or fixed in a newer version.
=C2=A0 =C2=A0Is your BIOS up to date? HP's changelog of BIOS updates is= too vague
to know if there are relevant fixes but you may want to look at
https://support.hp.com/us-en/drivers/swdetails/hp-255-g7-notebook-pc/mo= del/24381328/swItemId/ob-345901-1
(if I got the right machine) or even reach out to them for further
update changes.

> At that point, I can't jump to a virtual console with CTRL+ALT+FUN= CTIONKEY.
> I can't even shut the computer down by pressing the shutdown butto= n for
> less than a second as I usually do.
> But trying to do both things makes the disk activity light indicator <= br> > start blinking a lot for a moment.

=C2=A0 =C2=A0Do you have swap configured? If so, how much? I've seen sy= stems get
very slow and even hang when the was no swap and too much memory
pressure instead of just closing out processes as expected but haven't =
tested such scenarios on 14.3.

> The laptop doesn't seem to get back to work even after half an hou= r of
> waiting or more.
> Something that i have been noticing is that the freeze seems to be > triggered by an increase of resources use. I noticed that because the =
> freezing starts usually after opening a program like a terminal emulat= or
> while there are already some programs running in other windows. It als= o
> happened one time while trying to use my laptop while copying 23GBs of=
> data in a virtual console.

=C2=A0 =C2=A0If you can narrow it down to a repeatable sequence then you co= uld
more easily collect data from the occurrence. You could also try to push the system into an expected bad state and preemptively use ctrl+alt+f1
to see if anything shows up on the terminal during failure.
=C2=A0 =C2=A0Are you able to reproduce without X running?
=C2=A0 =C2=A0FreeBSD has a tests suite which runs through a series of check= s. It
can take a long time to run, some tests will likely normally fail, and
some won't run until additional packages are installed. You can have it=
run multiple tests in parallel which saves a massive amount of time but then test results become more inconsistent. I normally reboot after
running it as it some some of the tests leave the system in a strange
state. Keeping logs of the results could help identify regressions with new FreeBSD versions (tests and the OS both get reworked; its not always clear at a glance if it is a new but broken test vs an old test started failing that caused error count to go up) or help spot intermittent and special case hardware failures.
=C2=A0 =C2=A0There are other non-FreeBSD hardware tests that may be worth r= unning.
Some are stand alone tools that boot separately like memtest86 but
others may need a Windows/Linux install to run from. You can look into
tests that overclockers use to verify system stability; overclock or
not, an unstable system may still show with the tools. These tools will stress the system in ways that the FreeBSD test suite does not. I even
more recently found a system was intermittently but regularly crashing
while restoring a ZFS backup (resolved by slightly lowering clock
frequencies but most laptops don't offer such control).
=C2=A0 =C2=A0Maybe useful to monitor temperatures too if the issue is not <= br> repeatable. Physically cleaning even light dust off of hardware can also stabilize some intermittent hardware that isn't overheating.

> I leave some routine files here for you to check up if you feel the ne= ed
> of it:
>
> dmesg output: https://pastebin.com/C27M5K0F <https://pa= stebin.com/C27M5K0F>

=C2=A0 =C2=A0Probably just from incorrect shutdowns but I noticed disk moun= ting /
listed pending error; could run through SMART tests/checks and make sure filesystem does fully clean up with correct shutdown or fsck.

> rc.conf: https://pastebin.com/9wX0sKsa <https://pastebi= n.com/9wX0sKsa>
> loader.conf: https://pastebin.com/wBrdL8NL <https://pas= tebin.com/wBrdL8NL>
>
> As always, thanks to whoever that takes the time to help me with this.=
>


--000000000000ff569d0639edd38a--