Hi!
On Mon, Oct 21, 2024 at 01:00:31AM -0700, Gleb Smirnoff wrote:
T> This is an automated email to inform you that the October 2024 stabilization
week
T> started with FreeBSD/main at main-n273082-525a177c1657, which was tagged as
T> main-stabweek-2024-Oct.
At Netflix testing we didn't encount
On 22 Oct 2024, at 19:37, Gleb Smirnoff wrote:
>
> On Mon, Oct 21, 2024 at 01:00:31AM -0700, Gleb Smirnoff wrote:
> T> This is an automated email to inform you that the October 2024
> stabilization week
> T> started with FreeBSD/main at main-n273082-525a177c1657, which was tagged as
> T> main-st
hello,
i thought i should mentioned that after upgrading to
FreeBSD 15.0-CURRENT #3 lf/main-n269068-2cff93ced1d: Wed Oct 23 02:48:20
BST 2024
srcma...@hemlock.eden.le-fay.org:/data/build/obj/freebsd/data/build/src/freebsd/lf/main/amd64.amd64/sys/GENERIC
which is based on
commit 53314e34d5e8
Hi,
Since 2 or 3 weeks I start experiencing system freezes on an
and64 Lenovo Thinkbook laptop I'm using as my daily desktop PC.
I'm running FreeBSD current using pkg base_weekly to grab
updates (currently main-n273070-6d42d5dbdd67).
The full hardware details are here:
https://wiki.freebsd.org/
A couple of low-hanging-fruit suggestions.
Can you ping the machine if it is frozen? This will indicate if the whole
kernel is frozen or for example only the video part.
If you can ping it, can you ssh to the machine? Or is an existing ssh
connection maybe still usable to diagnose further.
Did
The only solution that I found was to delete /usr/obj/... and build from
scratch.
Cheers
David Wolfskill escreveu (segunda, 21/10/2024 à(s)
21:36):
> On Mon, Oct 21, 2024 at 08:02:50PM +0100, void wrote:
> > On Sun, Oct 20, 2024 at 05:14:29AM -0700, David Wolfskill wrote:
> >
> > > This is in m
