Re: Testing 14-CURRENT-f44280bf5fb on aarch64

2022-05-10 Thread Hans Petter Selasky
On 5/10/22 09:37, Daniel Morante wrote: Updated to the latest (14.0-CURRENT #2 main-n255521-10f44229dcd: Tue May 10 02:52:27 EDT 2022) and removed the sysctl option (hw.usb.disable_enumeration=1). Still seeing the problem.  The below just endlessly prints out on the console: ```

Re: Testing 14-CURRENT-f44280bf5fb on aarch64

2022-05-10 Thread Daniel Morante
Updated to the latest (14.0-CURRENT #2 main-n255521-10f44229dcd: Tue May 10 02:52:27 EDT 2022) and removed the sysctl option (hw.usb.disable_enumeration=1). Still seeing the problem.  The below just endlessly prints out on the console: ``` FreeBSD/arm64 (mars.morante.com) (ttyu0) login:

Re: Testing 14-CURRENT-f44280bf5fb on aarch64

2022-05-04 Thread Hans Petter Selasky
On 5/4/22 09:49, Daniel Morante wrote: I'm still using the sysctl option "hw.usb.disable_enumeration=1" to prevent the USB devices from disconnecting/reconnecting every few seconds.  Other than that the improvement in stability with 14-CURRENT on aarach64 on this hardware is much better since

Testing 14-CURRENT-f44280bf5fb on aarch64

2022-05-04 Thread Daniel Morante
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