(disconnected)
uhub4: detached
ugen0.2: at usbus0
uhub4 numa-domain 0 on uhub0
uhub4: on usbus0
uhub4: 4 ports with 4 removable, self powered
```
On 5/4/2022 4:10 AM, Hans Petter Selasky wrote:
On 5/4/22 09:49, Daniel Morante wrote:
I'm still using the sysctl option "hw.usb.disable_enumerat
I have been testing 14-CURRENT-f44280bf5fb for the last few days and so
far it's been okay on my hardware (Cavium ThunderX2). Most of the
details of the system are saved in
http://venus.morante.net/downloads/unibia/screenshots/freebsd/R281-T91/14-CURRENT-f44280bf5fb.
I've only had one kernel
I've seen it on an arm64 system:
KDB: stack backtrace:
db_trace_self() at db_trace_self
db_trace_self_wrapper() at db_trace_self_wrapper+0x30
vpanic() at vpanic+0x174
panic() at panic+0x44
do_el1h_sync() at do_el1h_sync+0x184
handle_el1h_sync() at handle_el1h_sync+0x78
--- exception, esr
Will history/completion continue to work the same way? (for example
typing part of the command, pressing UP and having it complete based on
history)
On 9/22/2021 4:36 AM, Baptiste Daroussin wrote:
Hello,
TL;DR: this is not a proposal to deorbit csh from base!!!
For years now, csh is the
Yes my fstab entry is:
/dev/gpt/swap none swap sw 0 0
It looks though that this issue might only happen on arm64? I tried to
reproduce on amd64 without any luck.
On 8/8/2021 3:03 AM, Gary Jennejohn wrote:
On Sat, 7 Aug 2021 20:10:50 -0400
Daniel Morante via
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
Also, this release seems to have gotten a lot more attention than
usual. So probably more people are testing.
On 3/31/21 1:24 PM, Rainer Duffner wrote:
Am 31.03.2021 um 17:58 schrieb Glen Barber :
A small set of updates that we consider blocking the 13.0 release have
been brought to our
