Resolved: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d

After the update to main-n269261-1e6db7be6921, head built & booted OK. FreeBSD 15.0-CURRENT #45 main-n269261-1e6db7be6921: Wed Apr 10 11:11:50 UTC 2024 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1500018 1500018 Peace, david -- David H. Wolfskill

Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d

On Tue, Apr 09, 2024 at 09:18:49AM -0700, Gleb Smirnoff wrote: > ... > D> db> > > This should be fixed by just pushed e205fd318a296ffdb7392486cdcec7f660fcffcf. Thanks! :-) > Sorry for that! > Glad it's idenitfied & addressed. [Sorry for delay; commute this morning was a bit more

Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d

Machine had been running: FreeBSD 15.0-CURRENT #43 main-n269202-4e7aa03b7076: Mon Apr 8 11:19:58 UTC 2024 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1500018 1500018 This was an in-place source update, after updating sources to

Re: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed?

On Mon, Apr 01, 2024 at 10:51:10PM -0700, Kevin Oberman wrote: > > I have a T16 and ran into that issue. It may be that BIOS changes have > broken things, but I found that, by default, the F keys control volume, > screen brightness, and many other things. I can use Fn+F[1-12] to perform >

Re: Request for Testing: TCP RACK

On Mon, Mar 18, 2024 at 07:26:10AM -0500, Mike Karels wrote: > ... > >> It would be so nice that we can have a sysctl tunnable for this patch > >> so we could do more tests without recompiling kernel. > > Thanks for testing! > > > > @gallatin: can you come up with a patch that is acceptable for

Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b

[Closing the loop on this -- dhw] On Tue, Jan 30, 2024 at 06:49:32AM -0800, David Wolfskill wrote: > The machines where I track head (& stable/14) daily get powered off once > they have finished their work for the day; this is done via "poweroff". > ... > | > | Th

Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b

On Wed, Jan 31, 2024 at 07:53:07AM -0600, Mike Karels wrote: > On 31 Jan 2024, at 7:18, Olivier Cochard-Labbé wrote: > ... > > Same problem here. > > I would check 9cdf326b4faef97f0d3314b5dd693308ac494d48, it changed > shutdown ordering. > Yes; I have been corresponding with Andriy, and

Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b

On Tue, Jan 30, 2024 at 03:49:54PM +, Gary Jennejohn wrote: > ... > I use 'shutdown -p now' and it's never failed to power down my computers. > I could say the same about "poweroff", up to the main-n267808-197944948e62 -> main-n267841-0b3f9e435f2b transition. And I probably wouldn't

Re: 'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b

On Tue, Jan 30, 2024 at 03:56:16PM +0100, Tomek CEDRO wrote: > On Tue, Jan 30, 2024 at 3:49 PM David Wolfskill wrote: > > The machines where I track head (& stable/14) daily get powered off once > > they have finished their work for the day; this is done via "powe

'poweroff' seems to (only) halt as of main-n267841-0b3f9e435f2b

The machines where I track head (& stable/14) daily get powered off once they have finished their work for the day; this is done via "poweroff". I noticed (this morning) that one of them never actually powered off yesterday. After today's exercises (including the reboot & subsequent poweroff), I

Re: Problem building world on current

On Thu, Dec 28, 2023 at 04:05:49PM +0100, Santiago Martinez wrote: > Hi Everyone, I'm having issues building world from current (just now). > > Same header missing on multiple parts. > > Best regards. > > Santiago > It might be useful to know: * What you are running at the time; * what

Re: kernel: psm: keyboard controller failed at git revision 3334a537ed38

On Wed, Dec 27, 2023 at 11:44:37PM +0300, Ruslan Makhmatkhanov wrote: >Hello, >I updated my tree to revision 3334a537ed38, made buildworld and kernel >as usual. > >Booting with new kernel leads to keyboard not working at system login >prompt and the message "kernel: psm:

Re: [resolved] After update to main-n266611-49a83b94395a: panic: bus_generic_rman_activate_resource

On Sun, Nov 26, 2023 at 04:36:33AM +0900, Tomoaki AOKI wrote: > Hi. > > Not tested, but does upgrading to commit ed88eef140a1 [1] and later > help? (I'm still at commit 5d4f897f88ed on main.) > > [1] > https://cgit.freebsd.org/src/commit/?id=ed88eef140a1c3d57d546f409c216806dd3da809 > > Regards.

Re: After update to main-n266611-49a83b94395a: panic: bus_generic_rman_activate_resource

On Sun, Nov 26, 2023 at 04:36:33AM +0900, Tomoaki AOKI wrote: > Hi. > > Not tested, but does upgrading to commit ed88eef140a1 [1] and later > help? (I'm still at commit 5d4f897f88ed on main.) > > [1] > https://cgit.freebsd.org/src/commit/?id=ed88eef140a1c3d57d546f409c216806dd3da809 > > Regards.

After update to main-n266611-49a83b94395a: panic: bus_generic_rman_activate_resource

After I saw this with both my headless "build machine" and a laptop (and verified that there were no more recent commits to main), I figured it might be worth reporting. This was after a source update from: FreeBSD 15.0-CURRENT #473 main-n266588-2a35f3cdf63d-dirty: Fri Nov 24 13:11:48 UTC 2023

"make installworld" fails for main-n265819-af5e348c61da

This is for an in-place source update; machine is currently running: freebeast(15.0-C)[15] uname -aUK FreeBSD freebeast.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #427 main-n265811-38ecc80b2a4e: Sun Oct 8 17:42:28 UTC 2023

Re: problems on new -current install with pkg/ssl

On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg > for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and

Re: debug.verbose_sysinit=1

On Sun, Jun 25, 2023 at 09:20:40PM +0100, Graham Perrin wrote: > When debug.verbose_sysinit=1 is set in loader.conf(5), is normal to _not_ > have BOOT and copyright messages? It's normal (in that situation) to require a higher value in kern.msgbufsize if you want the entire dmesg output saved in

Re: Build failure for radlib.o during main-n263767-764464af4968 -> main-n263782-59833b089e78 src update

On Sat, Jun 24, 2023 at 09:09:00AM -0700, David Wolfskill wrote: > On Sat, Jun 24, 2023 at 10:39:57AM -0400, Ed Maste wrote: > > ... > > > : "OPENSSL_API_COMPAT expresses an impossible API compatibility level" > > > # error "OPENSSL_API_COMPAT

Re: Build failure for radlib.o during main-n263767-764464af4968 -> main-n263782-59833b089e78 src update

On Sat, Jun 24, 2023 at 10:39:57AM -0400, Ed Maste wrote: > ... > > : "OPENSSL_API_COMPAT expresses an impossible API compatibility level" > > # error "OPENSSL_API_COMPAT expresses an impossible API compatibility > > level" > >^ > > This could be a dependency issue; would you check if

Build failure for radlib.o during main-n263767-764464af4968 -> main-n263782-59833b089e78 src update

Running: FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #405 main-n263767-764464af4968: Fri Jun 23 11:42:14 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400091 1400091 after updating sources to main-n263782-59833b089e78,

Build failure in usr.sbin/bhyvectl; sources at main-n263112-ad513b4dba3e

This is from an in-place source update from main-n263073-634a770a5e16 to main-n263112-ad513b4dba3e: ... Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/ncurses/dump_entry.o Building

Re: Buildworld failure at main-n261978-44312c28fe2d in /usr/src/usr.sbin/bhyve

Resolved by 76fa62b5232e67ef10476cf1329aaceb9cbc2ff5; ref. https://cgit.freebsd.org/src/commit/?id=76fa62b5232e67ef10476cf1329aaceb9cbc2ff5 Peace, david -- David H. Wolfskill da...@catwhisker.org Putin claimed he wanted to avoid expansion of NATO. See how well THAT

Buildworld failure at main-n261978-44312c28fe2d in /usr/src/usr.sbin/bhyve

Running: freebeast(14.0-C)[4] uname -aUK FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #328 main-n261961-7ae0972c7b8c: Mon Apr 3 11:41:40 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400085 1400085 in meta mode after

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote: > looks like we may need another 'unclean' workaround for this? > > Warner > > On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote: > ... > > I had this problem also. After deleting obj/usr the buildworld succeeded. > > >

Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

Running: FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #275 main-n259988-48dc9150ac36: Tue Jan 10 12:20:47 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 and performing an in-place source update to main-n260011-40bb52c89b87

Re: cant login after make installworld: pam_opie.so.6 not found

On Tue, Jan 03, 2023 at 09:39:31PM +, Ivan Quitschal wrote: > ... > I am having a problem here after doing a: > make installworld > and > make delete-old-libs > > now I cant login (only thru single user) > looks like the "make delete-old-libs" has deleted that lib pam_opie.so.6 and > now I

Build error in FreeBSD head, main-n259058-105019e0d6c -> main-n259061-b1258b76435

And the only commit after main-n259061-b1258b76435 so far is 004bb636ca65f3239da284c20abb7f9d1d953dee, which claims: | tcp: Move sysctl OIDs related to ECN to tcp_ecn. | Keep all ECN related code in (mostly) one place. | | No functional change. I'm seeing: ... building shared library

Re: Problem with NVIDIA drivers 390 and 470 on current

On Sun, Sep 25, 2022 at 11:30:07PM -0300, Nilton Jose Rizzo wrote: > Hi all, > > I'm updated my box to last 14-current today and I get error on ports > compialtion. > Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266561 Peace, david -- David H. Wolfskill

Re: Good practices with bectl

On Wed, Sep 21, 2022 at 11:27:06AM +0200, Alexander Leidinger wrote: > ... > make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old delete-old-libs > > Usually I replace the delete-old-libs with check-old, as I don't want > to blindly delete them (some ports may depend on them... at

panic after update from main-n258027-c9baa974717a to main-n258075-5b5b7e2ca2fa

Not reproducible on reboot; only happened on one machine (main laptop) out of 3 that I updated this morning. No dump. :-/ A screenshot, a copy of the full dmesg.boot from the immediately-following successful (verbose) boot, and a copy of the uname output: FreeBSD 14.0-CURRENT #589

Re: A kernel crash after compiling a fresh kernel

On Wed, Jun 08, 2022 at 08:50:28AM +0200, Hans Petter Selasky wrote: > Hi, > > Does this patch fix your issue? > > --HPS > (As you noted later, that patch had been committed to head by the time I got around to checking, as: commit ce2525c8108a830d08d75771621d1bc580edd82c (HEAD -> main,

Re: A kernel crash after compiling a fresh kernel

On Tue, Jun 07, 2022 at 09:37:52PM -0400, Oleg Lelchuk wrote: > The 14-CURRENT running a fresh kernel crashes with these messages: > > __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 > 55 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct > pcpu, >

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, Jun 06, 2022 at 09:46:21AM +, Filippo Moretti wrote: > > Is it now safe to attempt updating current with UFS?SincerelyFilippo > Yes. Kirk committed a fix: commit bc218d89200faa021def77732f3d9fde4f4dee13 Author: Kirk McKusick Date: Tue May 31 19:55:54 2022 -0700 Two

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 08:06:32AM -0600, Warner Losh wrote: > ... > > On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > > > ... > > > Does loader_4th have same issue? > > > > > > > I don't know; I hadn't tried it. I will do so later today & report > > back. > > > > So if it's

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 05:16:57AM -0700, Alastair Hogge wrote: > ... > I have not been able to use a new /boot/loader.efi (following -CURRENT) > since > mid to late 2021, and your symptoms look the same; fortunately, I found > bug > report 264282[0] last night, which I think is related. Yamagi

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 05:16:57AM -0700, Alastair Hogge wrote: > ... > I have not been able to use a new /boot/loader.efi (following -CURRENT) > since > mid to late 2021, and your symptoms look the same; fortunately, I found > bug > report 264282[0] last night, which I think is related. Yamagi

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 03:26:45AM -0700, David Wolfskill wrote: > On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > > ... > > Does loader_4th have same issue? > > > > I don't know; I hadn't tried it. I will do so later today & report > ba

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > ... > Does loader_4th have same issue? > I don't know; I hadn't tried it. I will do so later today & report back. Thanks! Peace, david -- David H. Wolfskill da...@catwhisker.org "Putin is a

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Sun, May 29, 2022 at 06:59:34PM -0600, Warner Losh wrote: > Sorry for top posting... > > Did you upgrade your boot blocks? Thanks for the reply! Hmmm Well, every time I rebuild FreeBSD head, the last step just after "make installworld" and before the reboot is: # gpart bootcode -b

Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

-- but only on one machine (of the 3 that I use for daily tracking head (and stable/12 & stable/13) -- the build machine ("freebeast"). Each is amd64, using ... venerable ... BIOS/MBR & UFS -- stuff that has generally been functionally stable for the last couple of decades. So for yesterday and

Re: pciconf -lbvV crashes kernel main-8d72c409c

On Sun, Feb 06, 2022 at 12:19:59AM +, Michael Jung wrote: > Dump header from device: /dev/ada0p2 > Architecture: amd64 > Architecture Version: 2 > As a reality check, I just tried the "pciconf -lbvV" command on my newer laptop, which was running: FreeBSD g1-48.catwhisker.org

Re: panic main-n252563-eb815a741940: Bad tailq NEXT(0xfffffe001d7a3ad8->tqh_last) != NULL

On Fri, Jan 21, 2022 at 04:32:56AM -0800, David Wolfskill wrote: > This is for main-n252563-eb815a741940, after an update from yesterday's > main-n252546-e0282802a6ec: > > FreeBSD 14.0-CURRENT #401 main-n252546-e0282802a6ec: Thu Jan 20 04:15:42 PST > 2022 > r...@g1-51.catw

panic main-n252563-eb815a741940: Bad tailq NEXT(0xfffffe001d7a3ad8->tqh_last) != NULL

This is for main-n252563-eb815a741940, after an update from yesterday's main-n252546-e0282802a6ec: FreeBSD 14.0-CURRENT #401 main-n252546-e0282802a6ec: Thu Jan 20 04:15:42 PST 2022 r...@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1400048 1400048 Screenshots

Re: latest current fails to boot.

On Wed, Sep 22, 2021 at 02:39:37PM +0200, Johan Hendriks wrote: > I did a git pull this morning and it fails to boot. > I hangs at Setting hostid : 0x917bf354 > > This is a vm running on vmware. > If i boot the old kernel from yesterday it boots normally. > > uname -a > FreeBSD

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

On Tue, Sep 07, 2021 at 10:13:23AM +0200, Jakob Alvermark wrote: > ... > wlan0 does not associate after boot. (This is with iwm, AC 9260) > > My workaround is simply 'ifconfig wlan0 up'. > > After a few seconds wpa_supplicant associates and another few secods > later I have a DHCP IP address.

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

On Sun, Sep 05, 2021 at 02:22:58PM +0100, Graham Perrin wrote: > > > … I note that the subject update also included updates to > > contrib/wpa/wpa_supplicant, as well as some files in sys/net80211, > > but I have not started chasing that down. … > > Can you share relevant lines from your

wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

Sorry I hadn't noticed this yesterday (so I could have repported it then), but after updating the "head" slice of my laptopp from: FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021

Re: Encrypted swap partition no longer encrypted

On Fri, Aug 27, 2021 at 11:10:26AM +0200, Ronald Klop wrote: > Hi, > > For encrypted swap you can put ".eli" behind the device name in fstab. > > So change "/dev/ada0p2" to "/dev/ada0p2.eli" in the new fstab and reboot. > NB: after encryption is enabled the device is not available as dumpdev >

Re: Panic with no keyboard after update to main-n248404-60fb9e10c74c

On Sun, Aug 01, 2021 at 05:03:32PM +0300, Konstantin Belousov wrote: > On Sun, Aug 01, 2021 at 06:01:56AM -0700, David Wolfskill wrote: > > Once I was able to complete the "make installworld" after updating > > from main-n248391-f7f76c200a8c to main-n248404-60fb9e10c74c,

Panic with no keyboard after update to main-n248404-60fb9e10c74c

Once I was able to complete the "make installworld" after updating from main-n248391-f7f76c200a8c to main-n248404-60fb9e10c74c, the subsequent reboot yielded a panic with the keyboard inoperable. I needed to power-cycle the laptop to get it to respond; once I did, I tried requesting that the

Re: git: 99feb137f5f6 - main - `make buildworld' with time logging for each stage

On Sun, Aug 01, 2021 at 02:35:22PM +0200, Wolfram Schneider wrote: > Hi David, > > Thanks for the investigation. I will prepare a fix soon. Cool; thanks. That said, the actual reboot got a panic with the keyboard inoperable, so there are likely other issues. I'll try to get some information on

Re: git: 99feb137f5f6 - main - `make buildworld' with time logging for each stage

I believe that src/Makefile.inc1 needs a tweak to add "time" to the list of "Required install tools to be saved in a scratch dir for safety" -- something like: diff --git a/Makefile.inc1 b/Makefile.inc1 index 3d54a088d070..213b32a97ed3 100644 --- a/Makefile.inc1 +++ b/Makefile.inc1 @@ -1300,7

Re: Wake from sleep with nvidia-modeset

On Thu, Jul 29, 2021 at 06:15:19PM +0100, Graham Perrin wrote: > nvidia-driver-460.84 from ports, nvidia-modeset, NVIDIA Quadro K1100M > (GK107GLM), HP ZBook 17 G2, KDE Plasma. > > > > An initial wake from sleep was almost entirely successful, one

wpa_supplicant: SIGBUS after main-n247052-d40cd26a86a7 -> main-n247092-ec7b47fc81b2

Reading symbols from /usr/obj/usr/src/amd64.amd64/usr.sbin/wpa/wpa_supplicant/wpa_supplicant... (No debugging symbols found in /usr/obj/usr/src/amd64.amd64/usr.sbin/wpa/wpa_supplicant/wpa_supplicant) [New LWP 100168] Core was generated by `/usr/sbin/wpa_supplicant -s -B -i wlan0 -c

Re: Build fails with Filesize limit exceeded

On Fri, May 28, 2021 at 01:11:06PM +0200, Jakob Alvermark wrote: > Hi, > > > Building -current fails like this: > > --- kerberos5/lib/libasn1__L --- > Building > /usr/obj/usr/src/amd64.amd64/kerberos5/lib/libasn1/asn1_kx509_asn1.x > Building >

panic: device_unbusy: called for non-busy device iichid0

This was on the new(er) laptop with which I have been experimenting; it uses iichid to controll/access the built-in mouse/touchpad. The machine was running: FreeBSD g1-48.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #252 main-n246951-38e7025a60b2: Wed May 26 04:56:25 PDT 2021

Build fail updating from n246398-388c0cde1029 -> n246413-c78ad207baed

Per the ERROR_META_FILE: # Meta data file /common/S4/obj/usr/src/amd64.amd64/sbin/sysctl/sysctl.o.meta CMD cc -target x86_64-unknown-freebsd14.0 --sysroot=/common/S4/obj/usr/src/amd64.amd64/tmp -B/common/S4/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-common -fPIE -std=gnu99

Re: DHCP no longer working for em(4)

On Tue, Apr 27, 2021 at 12:19:32PM +0100, Graham Perrin wrote: > DHCP recently stopped working for em0. > > HP EliteBook 8570p, recently probed: > > > Any ideas? > > For what its worth, the problem _might_ have begun after a package > upgrade

"etcupdate -p" vs. $OLDTREE?

After the set of updates to etcupdate (main-n246232-0611aec3cf3a .. main-n246235-ba30215ae0ef), I find that "etcupdate -B -p" is working as expected, but after the following "make installworld", a subsequent "etcupdate -B" chugs along for a bit, then stops, whining: No previous tree to compare

Re: Problem building x11/nvidia-driver; ref. n245494-6827435548d2

On Wed, Mar 17, 2021 at 02:11:48PM +0100, Gary Jennejohn wrote: > ... > Well, I have obj under my home directory and do all my builds as a > normal user rather than as root. I suspect that's why it always fails > for me. Root owns /usr/src and /usr/ports. Hmm... I won't claim a causal

Re: Problem building x11/nvidia-driver; ref. n245494-6827435548d2

On Wed, Mar 17, 2021 at 01:18:37PM +0100, Gary Jennejohn wrote: > On Wed, 17 Mar 2021 05:08:50 -0700 > David Wolfskill wrote: > ... > > Indeed, it appears that the n245494-6827435548d2 change was intended to > > fix the issue that I am now just seeing. > > ... >

Problem building x11/nvidia-driver; ref. n245494-6827435548d2

My laptop is currently running main-n245489-15b82e00a164; after updating sources to n245498-096a84721670, I am performing a source-based update. A simialr update on my build machine (which is headless, and thus does not use anything related to X11) was successful. The laptop is set up to rebuild

Re: Recent if_wg work: Should DIAGNOSTIC imply KASSERT is available?

On Mon, Mar 15, 2021 at 07:36:51AM -0500, Kyle Evans wrote: > On Mon, Mar 15, 2021 at 6:20 AM David Wolfskill wrote: > ... > > So: Is DIAGNOSTIC intended to necessarily imply that KASSERT is > > available for use? > > > > This is fixed in ff92a03616c5, thanks f

Recent if_wg work: Should DIAGNOSTIC imply KASSERT is available?

For my laptop, the kernel config includes GENERIC, does not have options INVARIANTS but does have options DIAGNOSTIC which has not been a problem until today. In src/sys/dev/if_wg/wg_noise.c, as of main-n245465-16b2290447de, I see: ... 778 static void 779

Re: Asus E45M1-M PRO (panic: malloc(M_WAITOK) with sleeping prohibited)

On Thu, Mar 11, 2021 at 07:57:36PM -0800, Alastair Hogge wrote: > Turns out, EFI boot stopped working. The following boots but fails with > ... > umass0: SCSI over Bulk-Only; quirks = 0x4001 > umass0:6:0: Attached to scbus6 > Root mount waiting for: usbus5 CAM > panic: malloc(M_WAITOK) with

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

On Wed, Mar 10, 2021 at 08:25:00AM -0700, Warner Losh wrote: > ... > > Also (as yesterday), neither laptop exhibited a problem after the > > corresponding update. > > > > Yes it "works" without invariants. I'm working on a better fix that isn't > such a huge game of whack-a-mole that defers the

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

On Tue, Mar 09, 2021 at 04:04:56PM -0700, Warner Losh wrote: > On Tue, Mar 9, 2021 at 2:46 PM David Wolfskill wrote: > ... > > uma_zalloc_debug: zone "malloc-1024"umass0 on uhub2 > > with the following non-sleepable locks held: > > umass0: on usbus0 &g

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

On Tue, Mar 09, 2021 at 04:04:56PM -0700, Warner Losh wrote: > ... > > The build nmachine (still?) panics: > > ... > I'm willing to "poke at it" a bit, given a hint or two... > > OK. I know what's happening here. disk_create() posts an event and also > expects to sleep to get memory. I can fix

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

On Tue, Mar 09, 2021 at 01:23:16PM -0800, David Wolfskill wrote: > On Tue, Mar 09, 2021 at 01:53:37PM -0700, Warner Losh wrote: > > ... > > The following reviews should fix this. It introduces a no-wait variant for > > disk_alloc(), provides a way to free allocated, b

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

On Tue, Mar 09, 2021 at 01:53:37PM -0700, Warner Losh wrote: > ... > The following reviews should fix this. It introduces a no-wait variant for > disk_alloc(), provides a way to free allocated, but not created, disks and > changes CAM to use the new routines and take some care for not leaking

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

On Tue, Mar 09, 2021 at 04:09:18AM -0800, David Wolfskill wrote: > ... > I can afford to leave it that way for a bit, in case anyone has > suggestions for poking at it to get more information. I expect to > be attempting the same upgrade on a couple of laptops -- after they >

"panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

Just did a source-based update from: FreeBSD 14.0-CURRENT #1205 main-n245338-221622ec0c8e: Mon Mar 8 03:49:58 PST 2021 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 145 145 to: FreeBSD 14.0-CURRENT #1206 main-n245363-b3dac3913dc9: Tue Mar

Re: HEADS-UP: PIE enabled by default on main

On Thu, Feb 25, 2021 at 09:22:43PM -0500, Ed Maste wrote: > On Thu, 25 Feb 2021 at 19:23, John Kennedy wrote: > > > > Not sure if Ed Maste just wants to make sure that all the executables > > are rebuilt as PIE (vs hit-and-miss) or there is a sneaker corner-case that > > he knows about. > >

/usr/local/lib/compat no longer searched?

This is after an update from main-n244973-c02a28754bc2 -> main-n245005-77e1ccbee3ed. Before the update: ldconfig -r | grep curses 51:-lncursesw.9 => /lib/libncursesw.so.9 811:-lncursesw.8 => /usr/local/lib/compat/libncursesw.so.8 812:-lncurses.8 =>

Re: testers needed: loader: use display pixel density for font autoselection

I will plan on testing later today, using the laptop that has a mouse that doesn't work under FreeBSD. :-} As time permits between meeetings & stuff... Peace, david -- David H. Wolfskill da...@catwhisker.org It is supremely disingenuous to claim a lack of

Re: svnlite behaviour changed?

On Tue, Jan 26, 2021 at 09:52:15AM +, M - Krasznai András wrote: > Good morning! > > I regularly sync my FreeBSD source tree with the central repository using svn > update. I use a one-lis script to synchonize, which sends the output of svn > to a file, and also copies to the console. This

Re: Getting /usr/src to match specific git hash?

On Sun, Jan 24, 2021 at 11:14:45AM -0800, Steve Kargl wrote: > ... > Any advice on how to jump, say, 4 days ahead of the current > date of the src/ tree? That is, I have src/ that should > correspond to 24 Dec 2020. How do I jump to 28 Dec 2020? I (happen to) track FreeBSD head, stable/12 (and

Re: Which branch in git is 13.0-current?

On Sun, Jan 24, 2021 at 06:11:04AM -0600, donaldwillin...@gmail.com wrote: > I'm happy the number was changed. To many, the number "13" is > considered to be bad luck. > It was not "changed" for that reason. It's a natural progression from 11 to 12 to 13 to 14 (to 15 ...). It's the way

Re: Which branch in git is 13.0-current?

On Sat, Jan 23, 2021 at 07:52:57PM -0600, Donald Willinger wrote: > Look for 14-current. There is no more 13. as I understand it. > head is 14. stable/13 and stable/12 also exist: FreeBSD freebeast.catwhisker.org 12.2-STABLE FreeBSD 12.2-STABLE #1144 stable/12-c243280-g4493b69d4aa: Sat

Re: Which branch in git is 13.0-current?

On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote: > ... > > That is correct, 13-stable has been branched from 13-current which has now > > been bumped to 14-current. > > Because it's a major version change going from 13 to 14, pkg is a bit > > agitated regarding the ABI. > > So

wlan0 (iwn(4)) needed encouragement to associate

After this morning's update of head from: FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #124 main-c256006-g8ca9ff4f28d2-dirty: Sat Jan 16 05:47:48 PST 2021 r...@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1300135 1300135 to: FreeBSD

Re: Current kernel build broken with linuxkpi?

On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote: > > Hans Petter Selasky : > > > You need to update that DRM port you are using before the issue > > will be fixed. > > I'm confused. > I have drm-current-kmod listed in PORTS_MODULES; things on that > list get built

Re: Laptop ACPI poweroff failed after main-c255826 -> main-c255850

On Wed, Jan 13, 2021 at 04:07:35PM +0200, Andriy Gapon wrote: > ... > > I believe that this is evidence in favor of a "race condition" diagnosis. > > (In precisely what, I don't know,) > > I haven't followed source changes too closely as of recent. > It might be a good idea to check for recent

Re: Laptop ACPI poweroff failed after main-c255826 -> main-c255850

On Tue, Jan 12, 2021 at 07:37:28AM -0800, David Wolfskill wrote: > On Tue, Jan 12, 2021 at 05:31:30PM +0200, Andriy Gapon wrote: > > On 2021-01-11 14:55, David Wolfskill wrote: > > > pci3: unknown notify 0x2 > > > ACPI Error: AE_ERROR, Thread 12 could not acquire Mu

Re: Laptop ACPI poweroff failed after main-c255826 -> main-c255850

On Tue, Jan 12, 2021 at 05:31:30PM +0200, Andriy Gapon wrote: > On 2021-01-11 14:55, David Wolfskill wrote: > > pci3: unknown notify 0x2 > > ACPI Error: AE_ERROR, Thread 12 could not acquire Mutex > > [ACPI_MTX_Caches] (0c4) (20201113/utmutex-434) > > Looks like t

Re: Laptop ACPI poweroff failed after main-c255826 -> main-c255850

On Mon, Jan 11, 2021 at 04:55:13AM -0800, David Wolfskill wrote: > At the conclusion of each morning's "update cycle," I have (for > some time) been in the habit of powering the laptop off, leaving > it powered off for about 15 seconds, then powering it back up. (The > b

Laptop ACPI poweroff failed after main-c255826 -> main-c255850

At the conclusion of each morning's "update cycle," I have (for some time) been in the habit of powering the laptop off, leaving it powered off for about 15 seconds, then powering it back up. (The build machine also gets powered off, but doesn't get powered back up until a bit before midnight.)

Re: src: continued use of Subversion for getting updates

On Sat, Jan 09, 2021 at 10:23:56AM -0500, Frank Seltzer wrote: > ... > Is there a cookbook guide to converting to git from svn for people who just > want to checkout source to buildworld and keep the ports tree up to date? > While it is not a cookbook, I wrote up what I do at

Re: Problem compiling custom kernel

On Sat, Jan 09, 2021 at 02:33:58PM +, Filippo Moretti wrote: > I tried to compile my custom kernel but I did get the following error,I > enclose the beginning of dmesg output.So far I could always build kernel > STING.I did switch to git and previously I could build it without >

Re: Reinstalling libncurses.so.9

On Thu, Jan 07, 2021 at 03:58:07AM -0800, David Wolfskill wrote: > ... > > I think the commit message explains everything: > > > > https://cgit.freebsd.org/src/commit/?id=821aa63a09402935da0a73abf20ba0441562aa07 > > > > Seems to me that an update to the misc

Re: Reinstalling libncurses.so.9

On Thu, Jan 07, 2021 at 11:24:25AM +0100, Herbert J. Skuhra wrote: > On Thu, 07 Jan 2021 11:07:57 +0100, Filippo Moretti wrote: > > > > I just upgraded current and was prompted to delete libncurses.so.9 > > which I did.I could not find another version in lib so I need to > > reinstall

Re: boot loader blank screen

On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: > ... > > the 58661b3ba9eb should hopefully fix the loader text mode issue, it would > > be cool if you can verify:) > > > > thanks, > > toomas > > I think, I got it fixed (at least idwer did confirm for his system, thanks). > If

Re: CURRENT, usr/src on git, howto "mergemaster"?

On Mon, Jan 04, 2021 at 10:30:28AM -0800, Enji Cooper wrote: > ... > Adding to this: it has no maintainer, it’s less featureful, and it lacks > tests. Once I switched to etcupdate a few years back I never looked back at > mergemaster. > > I honestly think it should be deprecated in 13.x and

Re: CURRENT, usr/src on git, howto "mergemaster"?

On Mon, Jan 04, 2021 at 05:22:10AM -0800, Jeffrey Bouquet wrote: > ... > after checking out stable/12 with git, here a > # cd /usr/src/usr.sbin/mergemaster > # sh ./mergemaster.sh -piPcv > > and then answering 'l' for left for most merges > it seems to have sufficed. > This was before

Re: CURRENT, usr/src on git, howto "mergemaster"?

On Mon, Jan 04, 2021 at 12:35:28PM +0100, Hartmann, O. wrote: > Now, since /usr/src has been siwtched to git on several boxes and the former > svn tag > $FreeBSD$ seem not valid/useful anymore, how am I (or any other here) > supposed to > "mergemaster"? > > I did a full "mergemaster -CUFi"

Blank ttyv0 on reboot after update from c255519-g8929690a6359 tp c255545-g82397d791966

This is on my laptop. No clue yet -- I'll start looking at the changes once the rest of my smoke-test is done, but it seemed to boot OK & switch to graphics mode so I have some thing I can still use. Yesterday: FreeBSD g1-55.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #108

Re: etcupdate, svnlite, documentation etc. following the transition of source to Git

On Sat, Jan 02, 2021 at 03:43:04PM +, Graham Perrin wrote: > ... > >> In this context, is `cd /usr/src` still true? > > If you clone the repository to /usr/src instead of e.g. > > /usr/src/freebsd-current. > > Thanks again. > > I imagine that use cases will _eventually_ include trios of

Re: # Fssh_packet_write_wait: Connection to 77.183.250.3 port 22: Broken pipe

On Wed, Dec 30, 2020 at 08:04:03AM +0100, Hartmann, O. wrote: > ... > > # Fssh_packet_write_wait: Connection to XXX.XXX.XXX.XXX port 22: Broken pipe > > The backend is in most cases a CURRENT, 12.1-RELENG or 12.2-RELENG or > 12-STABLE server. A > couple of months ago we moved from 11.3-RELENG

Re: git and the loss of revision numbers

On Mon, Dec 28, 2020 at 04:56:39PM -0800, John-Mark Gurney wrote: > monochrome wrote this message on Mon, Dec 28, 2020 at 19:38 -0500: > > what would be the git command for reverting source to a previous version > > using these numbers? for example, with svn and old numbers: > > svnlite update

  1   2   3   4   5   6   7   8   9   >