recent head having significantly less "avail memory"

2021-09-13 Thread Guido Falsi via freebsd-current
Hi, I updated head recently and today I noticed a difference which looks wrong. At boodt the new head shows signifcantly less avail memory than before, around 3 GiB less. I moved from commit 71fbc6faed6 [1] where I got: Aug 28 22:03:03 marvin kernel: real memory = 17179869184 (16384 MB) Aug

Re: -CURRENT compilation time

2021-09-07 Thread Mark Millard via freebsd-current
> From: David Chisnall > Date: Tue, 7 Sep 2021 14:51:21 +0100 > On 06/09/2021 20:34, Wolfram Schneider wrote: > > With the option WITHOUT_TOOLCHAIN=yes the world build time is 2.5 > > times faster (real or user+sys), down from 48 min to 19.5 min real > > time. > > Note that building LLVM with th

Re: EFI/loader show garbage in console when set to some resolution in loader.conf

2021-09-06 Thread Toomas Soome via freebsd-current
> On 6. Sep 2021, at 19:44, Karel Gardas wrote: > > Hello, > > I'm attempting to set EFI console resolution in loader to 1920x1920. This is > working fine on all 3 tested* combinations when interrupting loader with '3' > key and then > issueing 'gop set 11' command and then 'boot' command. >

Re: -CURRENT compilation time

2021-09-06 Thread Guido Falsi via freebsd-current
On 06/09/21 10:08, Jeremie Le Hen wrote: Hey, I want to build -CURRENT again from sources. It's been a long time since I hadn't done that. I'm shocked by the compilation time. I started the whole thing on Friday night and Monday morning it's still in stage 4.2 (building libraries). Through occa

Re: PAM module for loading ZFS keys on login

2021-09-05 Thread Greg via freebsd-current
On September 5, 2021 4:54:26 PM GMT+03:00, Eric McCorkle wrote: >All, > >This patch creates a new PAM module that will load a ZFS key upon a >successful login: https://reviews.freebsd.org/D31844. It will use the >user's auth token as the key argument to loading a ZFS encryption key on >a user

Re: FreeBSD-13-STABLE: lib/libsecureboot/verify_file.c: error: use of undeclared identifier 'SOPEN_MAX'

2021-09-03 Thread Toomas Soome via freebsd-current
> On 3. Sep 2021, at 18:59, FreeBSD User wrote: > > Hello, > > enabling > > WITH_BEARSSL > > in src.conf renders buildworld on 13-STABLE to fail, but not on > 14-CURRENT. > > > > This is the difference between the sources, obviously 14-CURRENT contains the > correct > definition of S

Re: Call for participation

2021-09-03 Thread Faraz Vahedi via freebsd-current
Hey Warner, Count me in, please. Cheers, Faraz On Thu, Sep 02, 2021 at 08:43:21AM -0600, Warner Losh wrote: > Greetings, > > As teased on twitter, now that summer is over, it's a good time to start > working on the next steps with git. When we moved to git, we knew a number > of things would co

Re: PATH: /usr/local before or after /usr ?

2021-08-15 Thread Willem Jan Withagen via freebsd-current
On 16-7-2021 18:46, Ian Lepore wrote: On Fri, 2021-07-16 at 09:01 -0600, Alan Somers wrote: FreeBSD has always placed /usr/local/X after /usr/X in the default PATH. AFAICT that convention began with SVN revision 37 "Initial import of 386BSD 0.1 othersrc/etc". Why is that? It would make sense t

Re: dumpdev AUTO in rc.conf does not work

2021-08-08 Thread Daniel Morante via freebsd-current
freebsd-current wrote: Hello, I am running 14.0-CURRENT using the snapshot from 2021-08-05.__ It looks as if setting dumpdev="AUTO" in /etc/rc.conf has no effect on enabling kernel crash dumps. root@callisto:~ # uname -a FreeBSD callisto 14.0-CURRENT FreeBSD 14.0-CURRENT #0 ma

dumpdev AUTO in rc.conf does not work

2021-08-07 Thread Daniel Morante via freebsd-current
Hello, I am running 14.0-CURRENT using the snapshot from 2021-08-05.  It looks as if setting dumpdev="AUTO" in /etc/rc.conf has no effect on enabling kernel crash dumps. root@callisto:~ # uname -a FreeBSD callisto 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n248478-f3a3b061216: Thu Aug  5 06:0

Re: awk behaviour?

2021-07-29 Thread Michael Butler via freebsd-current
On 7/29/21 6:09 AM, Michael Gmelin wrote: On Wed, 28 Jul 2021 16:02:30 -0400 Ed Maste wrote: On Wed, 28 Jul 2021 at 15:15, Michael Butler via freebsd-current wrote: What prompted the question was my (obviously poor) attempt to debug and resolve this failure when attempting to build a

Information for freebsd-current@FreeBSD.org

2021-07-29 Thread freebsd-current+owner
Hi, this is the Mlmmj program managing the mailing list. Here is some information about the list. You can subscribe to the following versions: - The normal version: Every time a post is sent to the list, subscribers receive a copy of it. Subscribe by emailing . - The digest version: Subscr

Re: awk behaviour?

2021-07-28 Thread Michael Butler via freebsd-current
On 7/28/21 1:36 PM, Warner Losh wrote: On Wed, Jul 28, 2021 at 11:31 AM Michael Butler via freebsd-current < freebsd-current@freebsd.org> wrote: I tripped over this while trying to build a local release .. imb@toshi:/home/imb> pkg --version | awk -F. '{print $$1 * 1 + $

Re: awk behaviour?

2021-07-28 Thread Michael Butler via freebsd-current
NVM .. it's the escaping of '$' .. On 7/28/21 1:29 PM, Michael Butler via freebsd-current wrote: I tripped over this while trying to build a local release .. imb@toshi:/home/imb> pkg --version | awk -F. '{print $$1 * 1 + $$2 * 100 + $$3}' 10001 imb@toshi:/ho

awk behaviour?

2021-07-28 Thread Michael Butler via freebsd-current
I tripped over this while trying to build a local release .. imb@toshi:/home/imb> pkg --version | awk -F. '{print $$1 * 1 + $$2 * 100 + $$3}' 10001 imb@toshi:/home/imb> pkg --version 1.17.1 Is this expected? imb

Re: boot hangs after installworld at FreeBSD 14.0-CURRENT main-n248198-72f7ddb587a

2021-07-25 Thread Dennis Clarke via freebsd-current
On 7/25/21 11:54, Warner Losh wrote: > On Sun, Jul 25, 2021 at 3:30 AM Gary Jennejohn wrote: > >> I updated my FBSD-14 tree yesterday. >> >> uname -a shows FreeBSD 14.0-CURRENT #5 main-n248198-72f7ddb587a. >> >> Did a buildkernel and a clean buildworld yesterday. >> >> This morning I booted the n

Re: PATH: /usr/local before or after /usr ?

2021-07-16 Thread Cameron Katri via freebsd-current
On Fri, Jul 16, 2021 at 10:11:41AM -0600, Alan Somers wrote: > Ugh, that's a good example. I was thinking more about interactive > programs, like say /usr/bin/vi vs editors/vim. Hypothetically how would > one solve the conflict if /usr/local/bin came before /usr/bin ? Install > binutils's binari

Re: PATH: /usr/local before or after /usr ?

2021-07-16 Thread Cameron Katri via freebsd-current
On Fri, Jul 16, 2021 at 09:01:49AM -0600, Alan Somers wrote: > FreeBSD has always placed /usr/local/X after /usr/X in the default PATH. > AFAICT that convention began with SVN revision 37 "Initial import of 386BSD > 0.1 othersrc/etc". Why is that? It would make sense to me that > /usr/local/X sho

Re: lost high resolution console with lastest snapshot

2021-07-06 Thread Toomas Soome via freebsd-current
nts. >> >> >> On Tue, 6 Jul 2021 14:42:26 +0200 (CEST) >> Ronald Klop wrote: >> >>> Maybe your previous install did not use UEFI? >>> >>> Ronald. >>> >>> >>> Van: Toomas Soome via freebsd-current >>>

Re: lost high resolution console with lastest snapshot

2021-07-06 Thread Toomas Soome via freebsd-current
> On 6. Jul 2021, at 14:49, Nuno Teixeira wrote: > > Hello, > > gop get says: > --- > EDID 1920x1080 > mode 0 > --- > > When I try other modes it sometimes decreases res. > > I remember that high res was working until now. > Maybe a bug? GOP set/get/list is the only interface with uefi gr

Re: lost high resolution console with lastest snapshot

2021-07-06 Thread Toomas Soome via freebsd-current
> On 6. Jul 2021, at 14:07, Nuno Teixeira wrote: > > I forgot to say that dmesg show vt resolution: > > --- > (...) > FreeBSD clang version 12.0.1 (g...@github.com:llvm/llvm-project.git > llvmorg-12.0.1-rc2-0-ge7dac564cd0e) > WARNING: WITNESS option enabled, expect reduced performance. > ==>

Re: usr/share/man/man8/apmd.8.gz missing during install arm.armv7 install of main-n247723-6329ca325e02 because of 0a0f7486413c

2021-07-05 Thread Mark Millard via freebsd-current
On 2021-Jul-5, at 13:29, Fernando Apesteguía wrote: > On Mon, Jul 5, 2021 at 8:48 AM Fernando Apesteguía > wrote: >> >> >> >> El lun., 5 jul. 2021 4:59, Mark Millard escribió: >>> >>> The following commit seems to have proken installation >>> by being incomplete: >>> >>> . . . >>> committ

Re: usr/share/man/man8/apmd.8.gz missing during install arm.armv7 install of main-n247723-6329ca325e02 because of 0a0f7486413c

2021-07-04 Thread Mark Millard via freebsd-current
On 2021-Jul-4, at 19:59, Mark Millard wrote: > The following commit seems to have proken installation > by being incomplete: > > . . . > committer Fernando Apesteguía 2021-06-30 > 07:57:51 + > commit0a0f7486413c147d56808b38055c40c64cff61f5 (patch) > . . . > man: Build man

usr/share/man/man8/apmd.8.gz missing during install arm.armv7 install of main-n247723-6329ca325e02 because of 0a0f7486413c

2021-07-04 Thread Mark Millard via freebsd-current
The following commit seems to have proken installation by being incomplete: . . . committer Fernando Apesteguía 2021-06-30 07:57:51 + commit 0a0f7486413c147d56808b38055c40c64cff61f5 (patch) . . . man: Build manpages for all architectures Building and installing architecture-specifi

Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot

2021-07-02 Thread Mark Millard via freebsd-current
On 2021-Jul-2, at 08:38, Chuck Tuffli wrote: > On Thu, Jun 24, 2021 at 11:50 PM Mark Millard via freebsd-current > wrote: >> >> I've given up on figuring any useful out for this example. >> I've also not had a repeat so far. >> >> I

Re: Changes to backtrace() ??

2021-07-02 Thread Willem Jan Withagen via freebsd-current
On 2-7-2021 12:17, Tobias Kortkamp wrote: On Fri, Jul 02, 2021 at 11:52:14AM +0200, Willem Jan Withagen via freebsd-current wrote: Hi, Have there been changes in the backtrace() calls? I recently upgraded my current server, and now the Ceph backtrace test starts to fail It looks like it

Changes to backtrace() ??

2021-07-02 Thread Willem Jan Withagen via freebsd-current
Hi, Have there been changes in the backtrace() calls? I recently upgraded my current server, and now the Ceph backtrace test starts to fail It looks like it is implemented in the llvm code. So it could be that something is off in that code. --WjW Program terminated with signal SIGSEGV, Seg

Missing OptionalObsoleteFiles.inc entries for googletest

2021-06-28 Thread Cameron Katri via freebsd-current
Hello, I just set `WITHOUT_GOOGLETEST` in my src.conf then ran `make delete-old` to get rid of the files it left, but it seems OptionalObsoleteFiles.inc doesn't have entries for /usr/tests/lib/googletest/gtest_main/gtest_skip_in_environment_setup_test /usr/tests/lib/googletest/gtest_main/

Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot

2021-06-24 Thread Mark Millard via freebsd-current
I've given up on figuring any useful out for this example. I've also not had a repeat so far. I'm progressing to much more recent commits for the environment to be based on as well. The primary aarch64 system for my access is switching to be a HoneyComb. The Optane was moved to the HoneyComb. =

Re: git: 790a6be5a169 - main - Export various 128 bit long double functions from libgcc_s.so.1

2021-06-14 Thread Mark Millard via freebsd-current
Dimitry Andric dim at FreeBSD.org wrote on Mon Jun 14 19:17:40 UTC 2021 : > The branch main has been updated by dim: > > URL: > https://cgit.FreeBSD.org/src/commit/?id=790a6be5a1699291c6da87871426d0c56dedcc89 > > > commit 790a6be5a1699291c6da87871426d0c56dedcc89 > Author: Dimitry Andric >

Re: Files in /etc containing empty VCSId header

2021-06-10 Thread Cameron Katri via freebsd-current
On 6/10/21 6:26 PM, Kevin Oberman wrote: I have never seen it return anything from /usr/src. It seems to return stuff from /usr/src for me > whereis cc cc: /usr/bin/cc /usr/share/man/man1/cc.1.gz /usr/src/contrib/netbsd-tests/usr.bin/cc Although I question the validity of that response. But

Re: Files in /etc containing empty VCSId header

2021-06-09 Thread Peter Jeremy via freebsd-current
On 2021-Jun-08 17:13:45 -0600, Ian Lepore wrote: >On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wrote: >> There is a command for that which does or use to do a pretty >> decent job of it called whereis(1). Thanks. That looks useful. >revolution > whereis ntp.conf >ntp.conf: >revolution >

Re: OpenZFS imports, status update

2021-06-08 Thread Mark Millard via freebsd-current
tech-lists wrote on Date: Wed, 9 Jun 2021 02:13:07 +0100 : > root_at_desktop:/usr/src# git remote prune freebsd > fatal: 'freebsd' does not appear to be a git repository > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository e

Re: What happen to mailing list archives?

2021-06-07 Thread Mark Millard via freebsd-current
On 2021-Jun-6, at 13:25, Mark Millard wrote: > Baptiste Daroussin wrote on > Date: Sun, 6 Jun 2021 10:53:49 +0200 : > >> What has happended: >> plan A: we migrated everything off mailman/pipermail seamlessly with >> redirection >> and so on. We patched the new archiver to produce the same file

Re: What happen to mailing list archives?

2021-06-06 Thread Mark Millard via freebsd-current
Baptiste Daroussin wrote on Date: Sun, 6 Jun 2021 10:53:49 +0200 : > What has happended: > plan A: we migrated everything off mailman/pipermail seamlessly with > redirection > and so on. We patched the new archiver to produce the same file names has > pipermail > > Plan A worked fine up to a li

Unable to unsubscribe from freebsd-current@FreeBSD.org

2021-06-03 Thread freebsd-current+help
Hi, this is the Mlmmj program managing the mailing list. You were unable to be unsubscribed from the list because you are not subscribed. If you are receiving messages, perhaps a different email address is subscribed. To find out which address you are subscribed with, refer to the message welcom

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

2021-06-01 Thread Mark Millard via freebsd-current
Cy Schubert wrote on: Date: Tue, 01 Jun 2021 14:02:06 -0700 : > Can you provide me with a backtrace, using the bt command, please. That was in the original message from David W. A copy was in the reply that you sent to the list as well: > > (gdb) bt > > #0 0x010fb34f in wpa_sm_rx_eapo

Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot

2021-05-29 Thread Mark Millard via freebsd-current
On 2021-May-29, at 01:15, Mark Millard wrote: > On 2021-May-23, at 00:46, Mark Millard via freebsd-current at freebsd.org> wrote: > >> On 2021-May-23, at 00:08, Mark Millard via freebsd-current > at freebsd.org> wrote: >> >>> On 2021-May-22, at 22:16,

Better color support in diff(1) and ls(1)

2021-05-29 Thread Cameron Katri via freebsd-current
Hello,     I just submitted two differentials, D30545 and D30547, for color support in diff(1) and underline support in ls(1) respectively. While I was submitting these I also noticed that .arcconfig is still configured to submit differentials to the subversion repo, not the git one. - Camer

Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot

2021-05-29 Thread Mark Millard via freebsd-current
On 2021-May-23, at 00:46, Mark Millard via freebsd-current wrote: > On 2021-May-23, at 00:08, Mark Millard via freebsd-current at freebsd.org> wrote: > >> On 2021-May-22, at 22:16, Warner Losh wrote: >> >>> On Sat, May 22, 2021 at 10:44 PM Mark Milla

Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot

2021-05-23 Thread Mark Millard via freebsd-current
On 2021-May-23, at 00:08, Mark Millard via freebsd-current wrote: > On 2021-May-22, at 22:16, Warner Losh wrote: > >> On Sat, May 22, 2021 at 10:44 PM Mark Millard via freebsd-arm >> wrote: >> # mount -onoatime 192.168.1.187:/usr/ports/ /mnt/ >> # diff -r /us

Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot

2021-05-23 Thread Mark Millard via freebsd-current
On 2021-May-22, at 22:16, Warner Losh wrote: > On Sat, May 22, 2021 at 10:44 PM Mark Millard via freebsd-arm > wrote: > # mount -onoatime 192.168.1.187:/usr/ports/ /mnt/ > # diff -r /usr/ports/ /mnt/ | more > nvme0: cpl does not map to outstanding cmd > cdw0: sqhd:0020 sqid:0003 cid:007

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-16 Thread Henri Hennebert via freebsd-current
itHub (2.0i). Henri If I disable it at the boot console then it's fine. -adrian _______ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-c

Re: FYI for aarch64 main [14] running a mid March version: I ended up with [usb{usbus2}] stuck at (near) 100% cpu

2021-05-14 Thread Mark Millard via freebsd-current
done Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done Waiting (max 60 seconds) for system thread `bufspacedaemon-3' to stop... done Waiting (max 60 seconds) for system thread `bufspacedaem

Re: FYI for aarch64 main [14] running a mid March version: I ended up with [usb{usbus2}] stuck at (near) 100% cpu

2021-05-14 Thread Mark Millard via freebsd-current
system software and >> such: >> >> # ~/fbsd-based-on-what-freebsd-main.sh >> FreeBSD FBSDmacch 14.0-CURRENT FreeBSD 14.0-CURRENT >> mm-src-n245445-def0058cc690 GENERIC-NODBG arm64 aarch64 145 145 >> def0058cc690 (HEAD -> mm-src) mm-src snapshot for mm's patched build in git >> context. >> merge-base: 7381bbee29df959e88ec59866cf2878263e7f3b2 >> merge-base: CommitDate: 2021-03-12 20:29:42 + >> 7381bbee29df (freebsd/main, freebsd/HEAD, pure-src, main) cam: Run all >> XPT_ASYNC ccbs in a dedicated thread >> n245444 (--first-parent --count for merge-base) >> >> The system was a MACCHIATObin Double Shot. > === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-14 Thread Henri Hennebert via freebsd-current
nvestigate this last problem can you send kenv | grep smbios.system and dmesg|grep rtsx for the setup that work for you. Thanks Henri Best Regards, Marc Veldman _______ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listin

Re: More rtsx issues (13.0-R system) was: Re: CURRENT crashes at early boot on Lenovo T540p...

2021-05-14 Thread Henri Hennebert via freebsd-current
nabled ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected ecap 0003[148] = Serial 1 0001004ce000 ecap 0018[158] = LTR 1 ecap 001e[160] = L1 PM Substates 1 // Lev Serebryakov ___ freebsd-current@freebsd.org mailing list https://lists

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-14 Thread Henri Hennebert via freebsd-current
- KDB: enter: panic Both panics are "debuggable", as keyboard is working in ddb and crash dump could be created. And I'm not sure, that GIANT in 2021 is good thing. Please test the 2.0h version from GitHub. Henri _______ freebsd-current

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-14 Thread Henri Hennebert via freebsd-current
On 5/13/21 7:25 PM, Marc Veldman wrote: On 13 May 2021, at 17:56, Henri Hennebert wrote: On 5/13/21 5:51 PM, Lev Serebryakov wrote: On 13.05.2021 18:38, Henri Hennebert via freebsd-current wrote: This seems a good news. Can you replace sys/dev/rtsx.c by the latest version (2.0g) from

FYI for aarch64 main [14] running a mid March version: I ended up with [usb{usbus2}] stuck at (near) 100% cpu

2021-05-13 Thread Mark Millard via freebsd-current
The system was a MACCHIATObin Double Shot. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
On 5/13/21 5:51 PM, Lev Serebryakov wrote: On 13.05.2021 18:38, Henri Hennebert via freebsd-current wrote: This seems a good news. Can you replace sys/dev/rtsx.c by the latest version (2.0g) from https://github.com/hlh-restart/rtsx I reduce the DELAY to 25 and make some other updates

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
st version (2.0g) from https://github.com/hlh-restart/rtsx I reduce the DELAY to 25 and make some other updates waiting in the pipeline. Thank you for your time Henri ___________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailma

Re: vt: efifb / fb+kms resolutions and fonts — how to?

2021-05-13 Thread Toomas Soome via freebsd-current
you can test this with loadfont /boot/fonts/gallant.fnt, gallant is not listed in the index (because it has much smaller number of glyphs compared to terminus). If KMS will set different resolution and the default font is not good, then vidcontrol command can be used to load better one. hope this helps, toomas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
with panic! What do you mean? Does it display "card present" before the interrupt ? _______ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
On 5/13/21 3:30 PM, Lev Serebryakov wrote: On 13.05.2021 15:48, Henri Hennebert via freebsd-current wrote: rtsx0: <2.0c .> rtsx0: Card present mmc0: on rtsx0 rtsx0: Interrupt card inserted/removed rtsx0: Card absent ... This must be the culprit this change from present/absent

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
On 5/13/21 2:40 PM, Lev Serebryakov wrote: On 13.05.2021 15:13, Henri Hennebert via freebsd-current wrote: I’m not sure if this is an interesting data point or not, but a warm boot without the card inserted succeeds after a cold boot with the card inserted.   It could explain, why my tests

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
hing in my case. Does iwm0 / mmc0 is shown during boot? can you try a verbose boot (boot -s) if you can't see the verbose output which is too fast on the display: try a boot -p Henri PS Thanks for your time _______ freebsd-current@fr

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
resent/absent status, a taskqueue is scheduled. I am digging there... Thanks for your time! henri ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
path" gave different results! With a "cold" boot and without a card inserted did you see something like: rtsx0: <2.0c Realtek ... rtsx0: Card present mmc0: on rtsx0 rtsx0: Interrupt card inserted/removed rtsx0: Card absent ___________ free

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-13 Thread Henri Hennebert via freebsd-current
laptop. I’ve put my diagnostics in this thread, with the SVN revision in which it seems to have broken. https://docs.freebsd.org/cgi/getmsg.cgi?fetch=327822+0+archive/2020/freebsd-current/20201227.freebsd-current I your first message on the thread I see "mmc0: detached" do you have th

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-12 Thread Henri Hennebert via freebsd-current
broken. https://docs.freebsd.org/cgi/getmsg.cgi?fetch=327822+0+archive/2020/freebsd-current/20201227.freebsd-current I your first message on the thread I see "mmc0: detached" do you have the previous lines of the dmesg? This is what I can see on the display: (Copied by hand, so t

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-12 Thread Henri Hennebert via freebsd-current
On 5/12/21 5:04 PM, Marc Veldman wrote: Unfortunately I can only say “me too”, but on a different Lenovo laptop. I’ve put my diagnostics in this thread, with the SVN revision in which it seems to have broken. https://docs.freebsd.org/cgi/getmsg.cgi?fetch=327822+0+archive/2020/freebsd-current

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-12 Thread Henri Hennebert via freebsd-current
On 5/12/21 5:04 PM, Marc Veldman wrote: Unfortunately I can only say “me too”, but on a different Lenovo laptop. I’ve put my diagnostics in this thread, with the SVN revision in which it seems to have broken. https://docs.freebsd.org/cgi/getmsg.cgi?fetch=327822+0+archive/2020/freebsd-current

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-12 Thread Henri Hennebert via freebsd-current
On 5/12/21 2:46 PM, Lev Serebryakov wrote: On 12.05.2021 13:01, Henri Hennebert via freebsd-current wrote: It would be fine if you can test the driver with dev.rtsx.0.inversion=1 in loader.conf and see it it solve the problem. the output of sysctl dev.rtsx  and kenv | grep smbios.system would

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-12 Thread Henri Hennebert via freebsd-current
em. the output of sysctl dev.rtsx and kenv | grep smbios.system would be useful BTW is a dummy card inserted in the SD slot? Thank for your time Henri -- wbr, Sergey _______ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/l

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

2021-05-07 Thread Henri Hennebert via freebsd-current
3.0 Henri _______ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: zpool list -p 's FREE vs. zfs list -p's AVAIL ? FREE-AVAIL == 6_675_374_080 (199G zroot pool)

2021-05-05 Thread Mark Millard via freebsd-current
On 2021-May-5, at 17:01, Yuri Pankov wrote: > Mark Millard via freebsd-current wrote: >> Context: >> >> # gpart show -pl da0 >> => 40 468862048da0 GPT (224G) >> 40 532480 da0p1 efiboot0 (260M) >> 532520 2

zpool list -p 's FREE vs. zfs list -p's AVAIL ? FREE-AVAIL == 6_675_374_080 (199G zroot pool)

2021-05-05 Thread Mark Millard via freebsd-current
arly 2018-Mar) _______ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS rename with associated snapshot present: odd error message

2021-05-05 Thread Mark Millard via freebsd-current
On 2021-May-5, at 05:28, Mark Millard wrote: > On 2021-May-5, at 02:47, Andriy Gapon wrote: > >> On 05/05/2021 01:59, Mark Millard via freebsd-current wrote: >>> I had a: >>> # zfs list -tall >>> NAME USED AVAIL

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files? [aarch64 test did not reproduce the issue]

2021-05-05 Thread Mark Millard via freebsd-current
y run a 'target cortex-a7 (so: armv7) from aarch64' test > next. That was the context for the original discovery and > report. > > The armv7 builds and installs get the same sort of diff results as the aarch64 ones. So it does not look like I can readily reproduce the problem files that had differences. Given the time it takes to run the experiments, I would not expect to reproduce the problem on any given timescale. I'll stop the reporting as I go along in my activities --unless I end up with a repetition of the problem. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS rename with associated snapshot present: odd error message

2021-05-05 Thread Mark Millard via freebsd-current
On 2021-May-5, at 02:47, Andriy Gapon wrote: > On 05/05/2021 01:59, Mark Millard via freebsd-current wrote: >> I had a: >> # zfs list -tall >> NAME USED AVAIL REFER MOUNTPOINT >> . . . >> zroot/DESTDIRs/13_0R-CA72

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files? [aarch64 test did not reproduce the issue]

2021-05-04 Thread Mark Millard via freebsd-current
n a 'target cortex-a7 (so: armv7) from aarch64' test next. That was the context for the original discovery and report. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

ZFS rename with associated snapshot present: odd error message

2021-05-04 Thread Mark Millard via freebsd-current
139 === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: should bsdinstall work?

2021-05-04 Thread Mark Millard via freebsd-current
; root at generic > :~ # > > worth submitting a PR? or is bsdinstall legacy and I need to use some > other method. I've not tried releng/12.2 yet. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) _______

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files? [Ignore recent test: -dirty vs. checked-in usage difference]

2021-05-04 Thread Mark Millard via freebsd-current
accidentally discovered the presence of the few files with differences. My new experiments were different and I'd not though of needing to vary the procedure to get you the right evidence. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) __

diffoscope's odd UnicodeDecodeError error message: reason found

2021-05-04 Thread Mark Millard via freebsd-current
line 293, in load return loads(fp.read(), File "/usr/local/lib/python3.7/codecs.py", line 504, in read newchars, decodedbytes = self.decode(data, self.errors) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 18: invalid start byte Not exactly an obvious erro

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files? [Ignore recent test: -dirty vs. checked-in usage difference]

2021-05-04 Thread Mark Millard via freebsd-current
. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-uns

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

2021-05-04 Thread Mark Millard via freebsd-current
00018 29 100 8 [29] .strtab STRTAB 51c8 0363 0 0 1 > 50c4-000050b8 == 0xC Note: 0xC+0x4 == 0x10 (the size), so the last 4 bytes of .gnu_debuglink > For all I know, some i

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

2021-05-04 Thread Mark Millard via freebsd-current
the 4 might accidentally match sometimes. The addition offset after .gnu_debuglink's file offset does vary (0xC and 0x10 above). The content of those differences do not look like file path components, for example the 0x08 byte. I do build with: # Avoid stripping but do not

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

2021-05-04 Thread Mark Millard via freebsd-current
ars, decodedbytes = self.decode(data, self.errors) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 18: invalid start byte === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Problem compiling harfbuzz

2021-05-04 Thread Filippo Moretti via freebsd-current
RRENT FreeBSD 14.0-CURRENT #24 main-n246214-78ffcb86d98: Tue Apr 20 17:51:50 CEST 2021 root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64 regardsFilippo ___________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

2021-05-04 Thread Mark Millard via freebsd-current
On 2021-May-3, at 21:27, Mark Millard wrote: > On 2021-May-3, at 19:26, Mark Millard wrote: > >> On 2021-May-3, at 10:51, Mark Millard wrote: >> >>> On 2021-May-3, at 07:47, Ed Maste wrote: >>> >>>> On Thu, 29 Apr 2021 at 02:

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

2021-05-03 Thread Mark Millard via freebsd-current
On 2021-May-3, at 19:26, Mark Millard wrote: > On 2021-May-3, at 10:51, Mark Millard wrote: > >> On 2021-May-3, at 07:47, Ed Maste wrote: >> >>> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current >>> wrote: >>>> >>>

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

2021-05-03 Thread Mark Millard via freebsd-current
On 2021-May-3, at 10:51, Mark Millard wrote: > On 2021-May-3, at 07:47, Ed Maste wrote: > >> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current >> wrote: >>> >>> Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and >>> /usr

Re: WSLg update on 1-5-2021 - BSD / WSL

2021-05-03 Thread Pete Wright via freebsd-current
-- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

2021-05-03 Thread Mark Millard via freebsd-current
On 2021-May-3, at 07:47, Ed Maste wrote: > On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current > wrote: >> >> Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and >> /usr/obj/DESTDIRs/13_0R-CA7-poud/sbin/ping differ >> Files /usr/obj/DESTDIRs/1

Re: bectl, chroot, pkg upgrade, no record of the upgrade in /var/log/messages

2021-05-02 Thread Toomas Soome via freebsd-current
t; > <2021-05-02 10:48 messages without a record of recent pkg upgrade.txt> > _______ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubsc

Re: Problems with realtek NIC

2021-05-01 Thread Greg Rivers via freebsd-current
On Saturday, 1 May 2021 16:45:03 CDT Stefan Esser wrote: > Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current: > > On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote: > >> I using a FreeBSD 14-Current and get random error with my NIC. The > >> wa

Re: Problems with realtek NIC

2021-05-01 Thread Greg Rivers via freebsd-current
n ports: net/realtek-re-kmod -- Greg _______ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-05-01 Thread Mark Millard via freebsd-current
rk Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS going forward, on stable/13 vs. main: question

2021-04-30 Thread Mark Millard via freebsd-current
/13.* might not handle? > > The implication would be that such a mix of boot > environments on the same zpool or media might not > be a good idea over time: main might be better > separated so the ZFS versioning is independent > between 13 and 14. > === Mark Millard marklmi

ZFS going forward, on stable/13 vs. main: question

2021-04-30 Thread Mark Millard via freebsd-current
parated so the ZFS versioning is independent between 13 and 14. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscr

Re: Review Request for D25705 and D25711

2021-04-30 Thread Faraz Vahedi via freebsd-current
On Mon, Apr 19, 2021 at 07:44:13PM +, Faraz Vahedi via freebsd-hackers wrote: > Dear hackers and committers, > > I have sent two small patches on freebsd-version(1) and > freebsd-update(8), D25705 and D25711 respectively, to > add -j flag for supporting jails. > I think they are both somewhat

FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

2021-04-28 Thread Mark Millard via freebsd-current
ht notice and care about such differences. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send an

Re: (D29934) Reorder commented steps in UPDATING following sequential order. (was: etcupdate -p vs. root on zfs (and bectl use and such): no /usr/src/etc/master.passwd (for example))

2021-04-25 Thread Mark Millard via freebsd-current
On 2021-Apr-25, at 08:14, Graham Perrin wrote: > On 23/04/2021 08:39, Mark Millard via freebsd-current wrote: > >> [3] > > > With regard to mounting ZFS file systems in single user mode > > What's currently footnote 3 will pr

Despite the documentation, "etcupdate extract" handles -D destdir (and its contribution to the default workdir)

2021-04-24 Thread Mark Millard via freebsd-current
j/DESTDIRs/13_0R-CA7-for-chroot/var/db/etcupdate/ I have not checked on if "etcupdate build" has a similar issue vs. not. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___________ freebsd-current@freebsd.org mailing

https://artifact.ci.freebsd.org/snapshot/stable-13/?C=M&O=D messed up dates and HASHID-only use make things extremely hard to find "in time order"

2021-04-23 Thread Mark Millard via freebsd-current
_____ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

etcupdate -p vs. root on zfs (and bectl use and such): no /usr/src/etc/master.passwd (for example)

2021-04-23 Thread Mark Millard via freebsd-current
ng / writable at this stage either.) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

base compiler & build options

2021-04-22 Thread Filippo Moretti via freebsd-current
toWITHOUT_LLVM_TARGET_ALLWITH_LLVM_TARGET_X86sincerelyFilippo ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

13.0-RELEASE bsdinstall failure : looked for MANIFEST in wrong place (not with *.txz files)

2021-04-16 Thread Mark Millard via freebsd-current
llard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

<    1   2   3   4   >