Re: TXT Kernel linking failed on -CURRENT

On Wed, Apr 24, 2024 at 01:12:39PM +0500, BSD USER wrote: > linking kernel > ld: error: undefined symbol: ktrcapfail > >>> referenced by vfs_lookup.c > >>>   vfs_lookup.o:(namei) > >>> referenced by vfs_lookup.c > >>>   vfs_lookup.o:(namei_setup) > >>> referenced by

Re: Strange network/socket anomalies since about a month

Alexander Leidinger writes: > Gleb Smirnoff writes: > > I don't have any better idea than ktrace over failing application. > > Yep, I understand that poudriere will produce a lot. > Yes, it does. 4.4 GB just for the start of poudriere until the first > package build fails due to a failed sccache

Re: Strange network/socket anomalies since about a month

Am 2024-04-22 18:12, schrieb Gleb Smirnoff: There were several preparatory commits that were not reverted and one of them had a bug. The bug manifested itself as failure to send(2) zero bytes over unix/stream. It was fixed with e6a4b57239dafc6c944473326891d46d966c0264. Can you please check

TXT Kernel linking failed on -CURRENT

Sorry for HTML-trash from previous mail :) Hi, FreeBSD Community! I have a teach with FreeBSD and use -CURRENT on my test machine. And some days ago after - git pull - make buildworld - make buildkernel There is /etc/src.conf and BSDSERV below, what can cause that error? Thanks for help! My

Kernel linking error on -CURRENT

Hi, FreeBSD Community! I have a teach with FreeBSD and use -CURRENT on my test machine.And some days ago after- git pull- make buildworld- make buildkernel There is /etc/src.conf and BSDSERV below, what can cause that error?Thanks for help! kernel building failed with such

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On 2024-04-24 02:12:41 (+0800), Mark Millard wrote: On Apr 19, 2024, at 07:16, Philip Paeps wrote: On 2024-04-18 23:02:30 (+0800), Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : Not sure where to post this.. The last bulk build for arm64 appears to have

Re: April 2024 stabilization week

Hi FreeBSD/main users & developers, this stabilization week [likely final] status update: * Netflix testing didn't discover any stability issues with main-n269602-dd03eafacba9. * Netflix testing didn't discover any substantial performance degradations. The data is still being analyzed

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Apr 19, 2024, at 07:16, Philip Paeps wrote: > On 2024-04-18 23:02:30 (+0800), Mark Millard wrote: > >> void wrote on >> Date: Thu, 18 Apr 2024 14:08:36 UTC : >> >>> Not sure where to post this.. >>> >>> The last bulk build for arm64 appears to have happened around >>> mid-March on

Re: April 2024 stabilization week

Hi FreeBSD/main users & developers, On Mon, Apr 22, 2024 at 01:00:50AM -0700, Gleb Smirnoff wrote: T> This is an automated email to inform you that the April 2024 stabilization week T> started with FreeBSD/main at main-n269602-dd03eafacba9, which was tagged as T> main-stabweek-2024-Apr. T> T>

Re: llvm and Undefined symbols: ___truncsfbf2 problem

Thank you. I updated my current to recent current and confirmed that julia 1.11.0 beta1 builds and runs with the system clang (18.1.4). On Thu, 18 Apr 2024 00:36:28 +0200 Dimitry Andric wrote: > On 11 Apr 2024, at 15:07, Hiroo Ono wrote: > > > > Hello, > > > > I am trying to update the

Re: Strange network/socket anomalies since about a month

Alexander, On Mon, Apr 22, 2024 at 09:26:59AM +0200, Alexander Leidinger wrote: A> I see a higher failure rate of socket/network related stuff since a while. A> Those failures are transient. Directly executing the same thing again may A> or may not result in success/failure. I'm not able to

Re: Strange network/socket anomalies since about a month

On Apr 22, 2024, at 3:26 AM, Alexander Leidinger wrote: > Hi, > > I see a higher failure rate of socket/network related stuff since a while. > Those failures are transient. Directly executing the same thing again may or > may not result in success/failure. I'm not able to reproduce this at

April 2024 stabilization week

Hi FreeBSD/main users & developers: This is an automated email to inform you that the April 2024 stabilization week started with FreeBSD/main at main-n269602-dd03eafacba9, which was tagged as main-stabweek-2024-Apr. The tag main-stabweek-2024-Apr has been published at

Strange network/socket anomalies since about a month

Hi, I see a higher failure rate of socket/network related stuff since a while. Those failures are transient. Directly executing the same thing again may or may not result in success/failure. I'm not able to reproduce this at will. Sometimes they show up. Examples: - poudriere runs with the

Re: Unfamiliar console message: in prompt_tty(): caught signal 2

On Sun, Apr 21, 2024 at 10:16:55PM +0200, Dag-Erling Smørgrav wrote: > bob prohaska writes: > > Apr 20 22:14:37 www su[30398]: in prompt_tty(): caught signal 2 > > This means someone ran `su` and pressed Ctrl-C instead of entering a > password when prompted. Ahh, that would have been me. Thank

etc/rc.d/nuageinit sometimes missing

I've not managed to track down how yet (ever?), but in two of my upgraded directory trees the etc/rc.d/nuageinit ended up being missing. By contrast, the places that were filled in via "installworld distrib-dirs distribution DB_FROM_SRC=1" usage did have the file. (Installed from the same

libclang_rt.asan_static-aarch64.a and libclang_rt.fuzzer_interceptors-aarch64.a in .../tmp/lib/clang/17/lib/freebsd/ not cleaned out

In my recent FreeBSD update activity, the following files blocked the "delete old things" activity from from deleting the related old 17/ subdirectory tree for clang: -r--r--r-- 1 root wheel - 8378 Mar 2 19:39:47 2024

Re: Unfamiliar console message: in prompt_tty(): caught signal 2

bob prohaska writes: > Apr 20 22:14:37 www su[30398]: in prompt_tty(): caught signal 2 This means someone ran `su` and pressed Ctrl-C instead of entering a password when prompted. DES -- Dag-Erling Smørgrav - d...@freebsd.org

Unfamiliar console message: in prompt_tty(): caught signal 2

On the serial console on a Pi3 v1.1 (so armv7) I just noticed an unfamilar message: Apr 20 22:14:37 www su[30398]: in prompt_tty(): caught signal 2 Several login failures were reported shortly afterward, so the message seems to have been a console message, not from the tip session used to

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On 2024-04-18 23:02:30 (+0800), Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : Not sure where to post this.. The last bulk build for arm64 appears to have happened around mid-March on ampere2. Is it broken? main-armv7 building is broken and the last completed

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Thu, Apr 18, 2024 at 08:02:30AM -0700, Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : Not sure where to post this.. The last bulk build for arm64 appears to have happened around mid-March on ampere2. Is it broken? main-armv7 building is broken and the last

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Apr 18, 2024, at 08:02, Mark Millard wrote: > void wrote on > Date: Thu, 18 Apr 2024 14:08:36 UTC : > >> Not sure where to post this.. >> >> The last bulk build for arm64 appears to have happened around >> mid-March on ampere2. Is it broken? > > main-armv7 building is broken and the

pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : > Not sure where to post this.. > > The last bulk build for arm64 appears to have happened around > mid-March on ampere2. Is it broken? main-armv7 building is broken and the last completed build was the one started on Mon, 19 Feb 2024

Re: llvm and Undefined symbols: ___truncsfbf2 problem

On 11 Apr 2024, at 15:07, Hiroo Ono wrote: > > Hello, > > I am trying to update the lang/julia port to 1.11.0 (currently still in beta > 1). > I seem to ran across this problem initially reported on MacOS. > https://github.com/JuliaLang/julia/issues/52067 > > The llvm team seems to have

llvm and Undefined symbols: ___truncsfbf2 problem

Hello, I am trying to update the lang/julia port to 1.11.0 (currently still in beta 1). I seem to ran across this problem initially reported on MacOS. https://github.com/JuliaLang/julia/issues/52067 The llvm team seems to have patched this problem only for Darwin.

Re: Request for Testing: TCP RACK

(...) Backup server is https://www.rsync.net/ (free 500GB for FreeBSD developers). Nuno Teixeira escreveu (quarta, 10/04/2024 à(s) 13:39): > With base stack I can complete restic check successfully > downloading/reading/checking all files from a "big" remote compressed > backup. > Changing it

Re: Request for Testing: TCP RACK

With base stack I can complete restic check successfully downloading/reading/checking all files from a "big" remote compressed backup. Changing it to RACK stack, it fails. I run this command often because in the past, compression corruption occured and this is the equivalent of restoring backup

Re: Request for Testing: TCP RACK

> On 10. Apr 2024, at 13:40, Nuno Teixeira wrote: > > Hello all, > > @ current 1500018 and fetching torrents with net-p2p/qbittorrent finished > ~2GB download and connection UP until the end: > > --- > Apr 10 11:26:46 leg kernel: re0: watchdog timeout > Apr 10 11:26:46 leg kernel: re0:

Re: Request for Testing: TCP RACK

Hello all, @ current 1500018 and fetching torrents with net-p2p/qbittorrent finished ~2GB download and connection UP until the end: --- Apr 10 11:26:46 leg kernel: re0: watchdog timeout Apr 10 11:26:46 leg kernel: re0: link state changed to DOWN Apr 10 11:26:49 leg dhclient[58810]: New IP

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: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

Le 9 avril 2024 18:06:12 GMT+02:00, FreeBSD User a écrit : >Am Tue, 9 Apr 2024 17:10:52 +0200 >Rainer Hurling schrieb: > >> Am 09.04.24 um 09:20 schrieb Baptiste Daroussin: >> > On Sat 06 Apr 09:23, Rainer Hurling wrote: >> >> Am 06.04.24 um 09:05 schrieb FreeBSD User: >> >>> Hello, >> >>>

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

Cy Schubert writes: > In message , Gleb Smirnoff writes: > > On Tue, Apr 09, 2024 at 07:02:11PM +0200, FreeBSD User wrote: > > F> The crash is still present on the most recent checked out sources as of > mi > > nutes ago. > > F> I just checked out on HEAD the latest commits (see below, just for

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

On Tue, Apr 09, 2024 at 07:02:11PM +0200, FreeBSD User wrote: F> The crash is still present on the most recent checked out sources as of minutes ago. F> I just checked out on HEAD the latest commits (see below, just for the record and to prevent F> being wrong here). F> F> [...] F> commit

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

Am Tue, 9 Apr 2024 09:18:49 -0700 Gleb Smirnoff schrieb: > On Tue, Apr 09, 2024 at 04:47:07AM -0700, David Wolfskill wrote: > D> --- trap 0xc, rip = 0x80b208c5, rsp = 0xfe048c204920, rbp = > 0xfe > D> 048c204960 --- > D> __mtx_lock_flags() at __mtx_lock_flags+0x45/frame

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

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

On Tue, Apr 09, 2024 at 04:47:07AM -0700, David Wolfskill wrote: D> --- trap 0xc, rip = 0x80b208c5, rsp = 0xfe048c204920, rbp = 0xfe D> 048c204960 --- D> __mtx_lock_flags() at __mtx_lock_flags+0x45/frame 0xfe048c204960 D> clnt_vc_create() at clnt_vc_create+0x4f4/frame

Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

Am Tue, 9 Apr 2024 17:10:52 +0200 Rainer Hurling schrieb: > Am 09.04.24 um 09:20 schrieb Baptiste Daroussin: > > On Sat 06 Apr 09:23, Rainer Hurling wrote: > >> Am 06.04.24 um 09:05 schrieb FreeBSD User: > >>> Hello, > >>> > >>> after updating (portmaster and make) ports-mgmt/ports from

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

On Tue, Apr 9, 2024 at 8:04 AM Rick Macklem wrote: > > On Tue, Apr 9, 2024 at 7:46 AM Rick Macklem wrote: > > > > On Tue, Apr 9, 2024 at 4:47 AM David Wolfskill wrote: > > > > > > Machine had been running: > > > > > > FreeBSD 15.0-CURRENT #43 main-n269202-4e7aa03b7076: Mon Apr 8 11:19:58 > >

Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

Am 09.04.24 um 09:20 schrieb Baptiste Daroussin: On Sat 06 Apr 09:23, Rainer Hurling wrote: Am 06.04.24 um 09:05 schrieb FreeBSD User: Hello, after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and 14-STABLE, I can't update several ports: www/apache24

Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

Am 06.04.24 um 09:56 schrieb FreeBSD User: Am Sat, 6 Apr 2024 09:23:30 +0200 Rainer Hurling schrieb: Am 06.04.24 um 09:05 schrieb FreeBSD User: Hello, after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and 14-STABLE, I can't update several ports:

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

On Tue, Apr 9, 2024 at 7:46 AM Rick Macklem wrote: > > On Tue, Apr 9, 2024 at 4:47 AM David Wolfskill wrote: > > > > Machine had been running: > > > > FreeBSD 15.0-CURRENT #43 main-n269202-4e7aa03b7076: Mon Apr 8 11:19:58 UTC > > 2024 > >

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

On Tue, Apr 9, 2024 at 4:47 AM David Wolfskill wrote: > > 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

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: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

On Sat 06 Apr 09:23, Rainer Hurling wrote: > Am 06.04.24 um 09:05 schrieb FreeBSD User: > > Hello, > > > > after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> > > 1.21.0 on CURRENT and > > 14-STABLE, I can't update several ports: > > > > www/apache24 > > databases/redis > >

Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

On Sat 06 Apr 09:05, FreeBSD User wrote: > Hello, > > after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 > on CURRENT and > 14-STABLE, I can't update several ports: > > www/apache24 > databases/redis > > pkg core dumps while performing installation. apache24 and

RFC: Does anyone use the -public/-webnfs NFS exports?

Hi, I have a hunch that no one uses the WebNFS stuff, which is done via exports(5) using the -public or -webnfs exports options. I would like to deprecate these exports options, but thought I'd ask in case anyone uses them? rick

Re: 15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

Mark Millard: > On Mar 30, 2024, at 12:44, Lexi Winter wrote: > > when the problem happens, with USB_DEBUG enabled, the kernel logs: > > > > uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT > > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2 > > Here is my

Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg-static core dumps on some ports

Am Sat, 6 Apr 2024 09:05:00 +0200 FreeBSD User schrieb: > Hello, > > after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 > on CURRENT and > 14-STABLE, I can't update several ports: > > www/apache24 > databases/redis > > pkg core dumps while performing installation.

Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1

Am Thu, 4 Apr 2024 01:14:52 -0500 Kyle Evans schrieb: > On 4/4/24 00:49, FreeBSD User wrote: > > Hello, > > > > I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: > > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 > > > > FreeBSD starting with 14-STABLE seems to use

Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

Am 06.04.24 um 09:05 schrieb FreeBSD User: Hello, after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and 14-STABLE, I can't update several ports: www/apache24 databases/redis pkg core dumps while performing installation. apache24 and redis are ports I

pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

Hello, after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and 14-STABLE, I can't update several ports: www/apache24 databases/redis pkg core dumps while performing installation. apache24 and redis are ports I realized this misbehaviour on ALL 14-STABLE

Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1

On April 4, 2024 07:50:55 FreeBSD User wrote: Hello, I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do not allow me to judge wether the

Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1

On 4/4/24 00:49, FreeBSD User wrote: Hello, I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do not allow me to judge wether the described

Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1

Am Thu, 04 Apr 2024 08:06:26 +0200 (CEST) sth...@nethelp.no schrieb: > >> I have to report to my superiors (we're using 14-STABLE and CURRENT > >> and I do so in private), > >> so I would like to welcome any comment on that. > > > > No it does not affect FreeBSD. > > > > The autoconf script

Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1

>> I have to report to my superiors (we're using 14-STABLE and CURRENT >> and I do so in private), >> so I would like to welcome any comment on that. > > No it does not affect FreeBSD. > > The autoconf script checks that it is running in a RedHat or Debian > package build environment before

Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1

On 04-04-24 05:49, FreeBSD User wrote: Hello, I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094 FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do not allow me to judge whether the

Re: LOR so_snd_sx / nfs

Shouldn't be a problem. The socket used for lookup is AF_UNIX (uses unp_connectat) and the NFS socket will always be UDP or TCP. Different sockets imply different socket locks. At least that's my interpretation, rick On Wed, Apr 3, 2024 at 11:33 AM Bjoern A. Zeeb wrote: > > > NFS root boot of

LOR so_snd_sx / nfs

NFS root boot of a Lab machine; calling wpa_cli: Thilock order reversal: 1st 0x0001d4e1c800 so_snd_sx (so_snd_sx, sx) @ /usr/src/sys/kern/uipc_socket.c:4020 2nd 0xa020cb20e930 nfs (nfs, lockmgr) @ /usr/src/sys/kern/vfs_lookup.c:1083 lock order nfs -> so_snd_sx established at: #0

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

On Tue, Apr 2, 2024 at 11:53 AM Tomoaki AOKI wrote: > On Tue, 02 Apr 2024 08:53:15 -0700 > Chris wrote: > > > On 2024-04-02 04:32, Tomoaki AOKI wrote: > > > On Tue, 02 Apr 2024 00:42:23 -0700 > > > Chris wrote: > > > > > >> On 2024-04-01 22:51, Kevin Oberman wrote: > > >> > On Mon, Apr 1, 2024

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

On Tue, 02 Apr 2024 08:53:15 -0700 Chris wrote: > On 2024-04-02 04:32, Tomoaki AOKI wrote: > > On Tue, 02 Apr 2024 00:42:23 -0700 > > Chris wrote: > > > >> On 2024-04-01 22:51, Kevin Oberman wrote: > >> > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: > >> > > >> >> I experience challenges

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

On 2024-04-02 04:32, Tomoaki AOKI wrote: On Tue, 02 Apr 2024 00:42:23 -0700 Chris wrote: On 2024-04-01 22:51, Kevin Oberman wrote: > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: > >> I experience challenges running FreeBSD on my Alder Lake laptop. >> With some help on the list and Bugzilla, I

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

On Tue, 02 Apr 2024 00:42:23 -0700 Chris wrote: > On 2024-04-01 22:51, Kevin Oberman wrote: > > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: > > > >> I experience challenges running FreeBSD on my Alder Lake laptop. > >> With some help on the list and Bugzilla, I was able to get Graphics > >>

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: Multi cons support has disappeared (on Alder Lake) was: Alt+Fn isn't functional. Has this been removed?

On 2024-04-01 22:51, Kevin Oberman wrote: On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: I experience challenges running FreeBSD on my Alder Lake laptop. With some help on the list and Bugzilla, I was able to get Graphics WiFi at least working. But still wasn't as stable as running on more dated

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

On Mon, Apr 1, 2024 at 3:05 PM Chris wrote: > I experience challenges running FreeBSD on my Alder Lake laptop. > With some help on the list and Bugzilla, I was able to get Graphics > WiFi at least working. But still wasn't as stable as running on > more dated CPU's. As it is; I'm only able to

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

On 2024-04-01 14:57, Michael Gmelin wrote: You never responded to my (and T’s) message - so I assume the suggestions made no difference? Right, and thank you for the reply. I (indirectly) answered it here when I indicated that I had no references to "keyboard settings in my rc.conf(5)". :) Any

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

I experience challenges running FreeBSD on my Alder Lake laptop. With some help on the list and Bugzilla, I was able to get Graphics WiFi at least working. But still wasn't as stable as running on more dated CPU's. As it is; I'm only able to use CURRENT. Beginning of last week, in hopes of

Re: 15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

On Mar 30, 2024, at 12:44, Lexi Winter wrote: > i'm using 15.0 (f66a994d59) on an 4GB RPi4 with a USB<>SATA adapter for > the root disk: > > usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device > ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA (0x174c:0x55aa) > ugen0.3: at usbus0 >

Re: 15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

(...) initial_turbo https://www.raspberrypi.com/documentation/computers/config_txt.html#overclocking Nuno Teixeira escreveu (domingo, 31/03/2024 à(s) 19:59): > Hello, > > If you got a fan in your rpi4 box, you could try to overclock it. > If not, there is a funcionality in config.txt to

Re: 15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

Hello, If you got a fan in your rpi4 box, you could try to overclock it. If not, there is a funcionality in config.txt to overclock it just for a few seconds at boot time. I can't remember the funtion but I'm looking at: https://www.raspberrypi.com/documentation/computers/config_txt.html

Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

Am 2024-03-29 18:21, schrieb Alexander Leidinger: Am 2024-03-29 18:13, schrieb Mark Johnston: On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote: Hi, sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work (see below for the issue). As the monthly

15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

hello, i'm using 15.0 (f66a994d59) on an 4GB RPi4 with a USB<>SATA adapter for the root disk: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA (0x174c:0x55aa) ugen0.3: at usbus0 umass0 on uhub1 umass0: on usbus0 umass0: SCSI over

Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

(For the not working Wifi chip, I use at the moment an USB-Wifi dongle, Realtek RTL8191S WLAN Adapter, which works fine). I also can't get Xorg plus twm up; it says in /var/log/Xorg.0.log at the end: .. REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270, ATI Radeon

Re: Alt+Fn isn't functional. Has this been removed?

On Fri, 29 Mar 2024 19:02:37 -0700 Chris wrote: > I just poured the dist files onto an earlier 15 (after removing > the earlier version). After booting into the new install, I no longer > had any other tty's other than ttyv0. Alt+Fn has no affect, I'm only > getting ttyv0. getty(8) is running,

Re: Alt+Fn isn't functional. Has this been removed?

> On 30. Mar 2024, at 07:30, Chris wrote: > > On 2024-03-29 23:06, Michael Schuster wrote: >> Two ideas: >> - does CTL-ALT-Fn work? > Thanks. But no, I tried that. > >> - perhaps the number of predefined ttys was overwritten/set to 0 somewhere? > I'm only aware of /etc/ttys, and they're all

Re: Alt+Fn isn't functional. Has this been removed?

On 2024-03-29 23:06, Michael Schuster wrote: Two ideas: - does CTL-ALT-Fn work? Thanks. But no, I tried that. - perhaps the number of predefined ttys was overwritten/set to 0 somewhere? I'm only aware of /etc/ttys, and they're all available (uncommented) and ps(1) indicates getty(8) is

Alt+Fn isn't functional. Has this been removed?

I just poured the dist files onto an earlier 15 (after removing the earlier version). After booting into the new install, I no longer had any other tty's other than ttyv0. Alt+Fn has no affect, I'm only getting ttyv0. getty(8) is running, and a ps waux | grep getty shows they're all up. Only

Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

On 3/29/24 16:52, Alexander Leidinger wrote: Hi, sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work (see below for the issue). As the monthly stabilisation pass didn't find obvious issues, it is something related to my setup:  - not a generic kernel  - very modular

Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

Am 2024-03-29 18:13, schrieb Mark Johnston: On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote: Hi, sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work (see below for the issue). As the monthly stabilisation pass didn't find obvious issues, it is

Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote: > Hi, > > sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work > (see below for the issue). As the monthly stabilisation pass didn't find > obvious issues, it is something related to my setup: > - not a

Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

Hi, sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work (see below for the issue). As the monthly stabilisation pass didn't find obvious issues, it is something related to my setup: - not a generic kernel - very modular kernel (as much as possible as a module) -

Re: Request for Testing: TCP RACK

> On 28. Mar 2024, at 15:00, Nuno Teixeira wrote: > > Hello all! > > Running rack @b7b78c1c169 "Optimize HPTS..." very happy on my laptop (amd64)! > > Thanks all! Thanks for the feedback! Best regards Michael > > Drew Gallatin escreveu (quinta, 21/03/2024 à(s) 12:58): > The entire point is

Re: Request for Testing: TCP RACK

Hello all! Running rack @b7b78c1c169 "Optimize HPTS..." very happy on my laptop (amd64)! Thanks all! Drew Gallatin escreveu (quinta, 21/03/2024 à(s) 12:58): > The entire point is to *NOT* go through the overhead of scheduling > something asynchronously, but to take advantage of the fact that

Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

El día miércoles, marzo 27, 2024 a las 03:51:33p. m. +0100, Matthias Apitz escribió: > The WLAN card seems to be: > > none2@pci0:1:0:0: class=0x028000 rev=0x00 hdr=0x00 vendor=0x14c3 > device=0x7961 subvendor=0x1a3b subdevice=0x4680 > vendor = 'MEDIATEK Corp.' > device =

Re: Only 1TB RAM out of 1.5TB on amd64

On Wed, Mar 27, 2024 at 05:55:20PM +0200, Konstantin Belousov wrote: > On Wed, Mar 27, 2024 at 03:01:11AM +0100, Bernd Walter wrote: > > Same Problem with current: > > reeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: Thu Mar 14 02:58:39 UTC > > 2024 > > > > real memory = 1649265344512

Re: Only 1TB RAM out of 1.5TB on amd64

On Wed, Mar 27, 2024 at 03:01:11AM +0100, Bernd Walter wrote: > Same Problem with current: > reeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: Thu Mar 14 02:58:39 UTC 2024 > > real memory = 1649265344512 (1572862 MB) > avail memory = 1057118396416 (1008146 MB) Real memory is really the max

Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

El día miércoles, marzo 27, 2024 a las 10:37:48a. m. +0100, Matthias Apitz escribió: > > Hello, > > I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to > boot FreeBSD with boot verbose messages from an USB key and I'm able to > login. The /var/log/messages are here >

Re: truss -f timeout 2 sleep 10 causes breakage

On Wed, Mar 27, 2024 at 01:00:07PM +0100, Mateusz Guzik wrote: > Top of main, but I reproduced it on stable/14-e64d827d3 as well. > > Mere "timeout 2 sleep 10" correctly times out. > > Running "truss -f timeout 2 sleep 10" prevents timeout from killing > sleep and the entire thing refuses to

Re: truss -f timeout 2 sleep 10 causes breakage

Mateusz Guzik writes: > Top of main, but I reproduced it on stable/14-e64d827d3 as well. Confirmed on 14.0-RELEASE-p5. > Mere "timeout 2 sleep 10" correctly times out. > > Running "truss -f timeout 2 sleep 10" prevents timeout from killing > sleep This is sort of expected as truss(1) uses

truss -f timeout 2 sleep 10 causes breakage

Top of main, but I reproduced it on stable/14-e64d827d3 as well. Mere "timeout 2 sleep 10" correctly times out. Running "truss -f timeout 2 sleep 10" prevents timeout from killing sleep and the entire thing refuses to exit, truss has to be killed off with SIGKILL. Here is the best part: after

Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

On Wed, Mar 27, 2024 at 12:38 PM Matthias Apitz wrote: > > > Hello, > > I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to > boot FreeBSD with boot verbose messages from an USB key and I'm able to > login. The /var/log/messages are here >

CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

Hello, I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to boot FreeBSD with boot verbose messages from an USB key and I'm able to login. The /var/log/messages are here http://www.unixarea.de/ASUS-VivoBook-Pro-14-messages.txt I can identify the harddisk as nda0 (correct),

Re: Only 1TB RAM out of 1.5TB on amd64

Same Problem with current: reeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: Thu Mar 14 02:58:39 UTC 2024 real memory = 1649265344512 (1572862 MB) avail memory = 1057118396416 (1008146 MB) On Fri, Mar 22, 2024 at 07:54:06PM +0100, Bernd Walter wrote: > .. > real memory = 1649265344512

Re: March 2024 stabilization week

Hi, On Mon, Mar 25, 2024 at 01:00:07AM -0700, Gleb Smirnoff wrote: T> This is an automated email to inform you that the March 2024 stabilization week T> started with FreeBSD/main at main-n268989-caccf6d3c008, which was tagged as T> main-stabweek-2024-Mar. A quick status update: * Netflix

Re: after trivial update, 15.0 ARM64 system no longer boots

On Mar 25, 2024, at 00:51, Lexi Winter wrote: > Lexi Winter: >> . . . > > . . . > > - even with the working keyboard, ctrl+alt+esc doesn't seem to work to > break into kdb when the problem occurs. i'm not sure if i'm doing > something wrong here or that key sequence doesn't work over USB,

CURRENT 220ee18f1964 memstick kernel panic, MacBookPro8,3

Originally posted to Photograph:

March 2024 stabilization week

Hi FreeBSD/main users & developers: This is an automated email to inform you that the March 2024 stabilization week started with FreeBSD/main at main-n268989-caccf6d3c008, which was tagged as main-stabweek-2024-Mar. The tag main-stabweek-2024-Mar has been published at

Re: after trivial update, 15.0 ARM64 system no longer boots

Lexi Winter: > i am not really an expert on either ARM64 in general or on the RPi > hardware in particular. could anyone suggest how i could debug this > problem, e.g. to get more information about why the system won't finish > booting? i dug into this a bit more, and to answer my own question:

FYI: main-n268827-75464941dc17 GENERIC-NODEBUG UFS-based poudriere bulk context got 4 "swap_pager: cannot allocate bio"

Context: I'm deliberately testing building example poudriere-devel configurations with only 2 GiBytes of RAM and RAM+SWAP == 8.5 GiBytes, SWAP on a partition of its own. # tail -3 /var/log/messages Mar 23 16:39:38 aarch64-main-pkgs kernel: pid 37137 (conftest), jid 11, uid 0: exited on signal 11

[LAST OFFICIAL REMINDER] Call for 2024Q1 status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2024 for work done since the last round of quarterly reports: January 2024 - March 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the

  1   2   3   4   5   6   7   8   9   10   >