On Tue, Nov 04, 2025 at 07:06:02AM -0800, Mike Larkin wrote: > On Tue, Nov 04, 2025 at 11:28:07AM +0100, Walter Alejandro Iglesias wrote: > > On Mon, Nov 03, 2025 at 09:38:55AM -0800, Mike Larkin wrote: > > > > After sending this message I tried hibernation in my old machine, an > > > > Intel Core 2 Duo with 4GB of RAM, where I have also OpenBSD installed. > > > > And it also takes a long time to hibernate there, with the added problem > > > > that when I turned it back on, I got a kernel panic. I'm not entirely > > > > > > what panic? > > > > > > > Let's start here, which is the data we already have. You can download > > from here the panic report (including screenshots): > > > > https://en.roquesor.com/Downloads/panic.tar.gz > > > > Corrupted mbuf list. Unsure how/why that happened. Does "ifconfig em0 down" > before hibernate help? Also, does it happen all the time?
No difference. > > > Besides: > > > > > 2. how long it takes to ZZZ immediately after a clean boot > > > > Right after booting I logged in and run from the console (without X): > > > > $ doas /usr/sbin/ZZZ > > > > I takse 34 seconds my new machine, 24 seconds my old one. I still think > > it's too much. > > > > > 3. the size of the image (printed on resume as it's being read) > > > > If at some point at booting this is printed, at least in my two machines > > it's imposible to catch (I can scroll back in my console). I can't find > > anything in the logs later either. > > > > > 4. results if setperf 100 improves things or not > > > > # sysctl hw.setperf=100 > > sysctl: hw.setperf: Operation not permitted > > > > > > -- > > Walter > -- Walter
