On Tue, 18 Mar 2025, Gleb Smirnoff wrote:
On Tue, Mar 18, 2025 at 08:14:31AM -0700, David Wolfskill wrote:
D> It completed successfully:
D>
D> g1-48(15.0-C)[1] uname -aUK
D> FreeBSD g1-48.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #262
main-n275998-82589f926b52: Tue Mar 18 14:17:34 UTC 2025
r...@g1-48.catwhisker.org:/common/S3/obj/usr/src/amd64.amd64/sys/CANARY amd64
1500034 1500034
D>
D> Specifically:
D> * I used the slice on the laptop where I had done the "git bisect"
D> * I first issued "git bisect reset"
D> * Then "git pull" to bring /usr/src up to main-n275998-82589f926b52
D> * The "git revert 19df0c5abcb9d4e951e610b6de98d4d8a00bd5f9
D> * Then the usual buildworld, kernel. installworld stuff
D> * Reboot
This needs to be fixed ASAP, it blocks FreeBSD CURRENT usage on laptops.
Well the good news is that I am typing from one so not all is lost.
The better news is that it's 3 I have rebuilt since Friday; two with
a completely clean main + drm-kmod branch 6.1-lts built along with
the kernel straight from the new github checkout full pkg update,
started X typing in an xterm today.
Even ressurected one with a "broken" display and no battery just for
this. Different vendors (HP, Lenovo, Dell; 16-32G memory, all i915kms).
FreeBSD 15.0-CURRENT #0 main-n276000-c22b297062e1: Wed Mar 19 01:33:13 UTC 2025
GENERIC amd64
Given the change (conditionally) swaps a malloc for a contigmalloc (it could
swap it entirely and it shouldn't matter) and doesn't even touch the KBI
it is still hard to believe to be the bug.
If this is not fixed by weekend, I will push revert of
19df0c5abcb9d4e951e610b6de98d4d8a00bd5f9, to get tree in a good shape
before beginning of the stabweek.
Stab week is for finding and fixing regressions; before that I would
worry about all the people doing pkg base updates over the weekend
as bapt pointed out for an iwlwifi chnage the other week.
Also given it's been 3-4 days I would assume if it hit badly we'd have
more reports from the occasional people updating main.
I would love to hear from anyone else if they had updated since Friday
whether they can see the problem or not, as that might then help to
narrow this down.
I'll try to work with David tomrorow to figure out what the problem
might be for him. It's almost 4AM in some parts of the worlds now
and I'll stop.
Lots of health,
/bz
--
Bjoern A. Zeeb r15:7
