Re: panic On aarch64 main: "usbconfig -d ugen0.11 set_config 1" panicked (data abort) on Windows Dev Kit 2023; kgdb backtrace included

In reply to: Gleb Smirnoff : "Re: panic On aarch64 main: "usbconfig -d ugen0.11 set_config 1" panicked (data abort) on Windows Dev Kit 2023; kgdb backtrace included"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Mark Millard <marklmi_at_yahoo.com>
Date: Tue, 23 Dec 2025 19:42:21 UTC

On Dec 23, 2025, at 10:07, Gleb Smirnoff <glebius@freebsd.org> wrote:

> On Tue, Dec 23, 2025 at 09:49:13AM -0800, Mark Millard wrote:
> M> # uname -apKU
> M> FreeBSD aarch64-main-pbase 16.0-CURRENT FreeBSD 16.0-CURRENT main-n282662-117306dc606b GENERIC-NODEBUG arm64 aarch64 1600007 1600007
> 
> Very likely this is fixed by 77939d64f23da4b0b599fad6edd967ffd1d17217.
> And was broken by 0d469d23715d690b863787ebfa51529e1f6a9092.
> 
> Please update and re-check.

The more recent official pkgbase kernel is:

# uname -apKU
FreeBSD aarch64-main-pbase 16.0-CURRENT FreeBSD 16.0-CURRENT main-n282692-44f656641c23 GENERIC-NODEBUG arm64 aarch64 1600007 1600007

and is now installed.

It did not panic for:

usbconfig -d ugen0.11 set_config 0

(It has a quirk set that made 1 the default, unlike
the kernel the system was previously using.)

Note:
I did not update the world, just the kernels available.
I wanted to be able to potentially revert to using the
to the copies that I'd made of the older kernels.

===
Mark Millard
marklmi at yahoo.com