Re: CURRENT: panic init() on acpi_shutdown
- Reply: obiwac : "Re: CURRENT: panic init() on acpi_shutdown"
- In reply to: Guido Falsi : "Re: CURRENT: panic init() on acpi_shutdown"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 17 Sep 2025 22:29:28 UTC
On Thu, 18 Sep 2025, Guido Falsi wrote: Cc: obiwac ; please see freebsd-current > On 9/17/25 23:48, Bjoern A. Zeeb wrote: >> On Wed, 17 Sep 2025, Oleg Nauman wrote: >> >>> On Wed, Sep 17, 2025 at 10:44 PM A FreeBSD User <freebsd@walstatt- de.de> >>> wrote: >>>> >>>> Hello, >>>> >>>> Maybe some minor issue, but since two days I can not shutdown recent >>>> CURRENT (at the moment >>>> FreeBSD 16.0-CURRENT #0 master-n280445-2d85bc89294b: Wed Sep 17 20:11:48 >>>> CEST 2025 amd64). >>>> >>>> System stops with a db> carret, a backtrace is shown. No core saved >>>> (although configured), USB >>>> keyboards unresponsive, filesystems (system on UFS, data graveyard on >>>> ZFS) unharmed and >>>> already cleanly unmounted as it seems, tried to save the backtrace, but >>>> keyboards are >>>> nonworking at that stage (picture taken from screen only). >>>> >>>> The crash seems to occur quite after everything is ready to reboot and or >>>> switch the box off. >> >> Yes, and USB is all detached; same problem here. Started after I >> rebased my branch to main yesterday. >> >> >>> I am experiencing the same issue with panic on shutdown >>> >>> Backtrace looks like >> >> Seems you are blessed in that your keyboard still worked? I could not >> get a dump either; only a photo of the panic so far. The end of the >> backtrace looks the same. >> > > Reverting [1] and [2] seems to "fix" it. > > [1] > https://cgit.freebsd.org/src/commit/?id=ce5e22b28ef6caff3ffd228ac188114b08c0da02 > > [2] > https://cgit.freebsd.org/src/commit/?id=e779891327b1d9b9ab10ba482e59f498790505a7 > > -- Bjoern A. Zeeb r15:7