Date: Sun, 09 Aug 2020 14:05:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 210132] hang on boot with locked SSD / regression towards 10.1 Message-ID: <bug-210132-227-e9dXQZa3v6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210132-227@https.bugs.freebsd.org/bugzilla/> References: <bug-210132-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210132 Hannes Hauswedell <h2+fbsdports@fsfe.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Only Me |Affects Some People --- Comment #2 from Hannes Hauswedell <h2+fbsdports@fsfe.org> --- Four years later, and the problem persists. FreeBSD-12.1 and a snapshot of FreeBSD-13 hang at the same location. Possibly related debug output of FreeBSD13 when booting: uma_zalloc_debug: zone "kenv" with the following non-sleepable locks held: exclusive sleep mutex CAM device lock (CAM device lock) r = 0(....) locked @ /usr/src/sys/cam/scsi/scsi_pass.c:674 stack backtrace: ... While ZFS native encryption will allow using unencrypted SLOGs on SSDs in the future, FreeBSD should still be able to boot a computer that contains a locked self-encrypted device (SED). This is definitely a bug and a regression. My system is currently in a state where it is barely maintainable with no upgrade path. Please let me know if there is anything I can do to help fix this. Please also tell whether this issue will be acted upon in the near future or whether I should look for different solutions (e.g. Linux with ZFS). Thank you! -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210132-227-e9dXQZa3v6>