[Bug 270489] Laptop doesn't wake from suspend anymore with 13.2-RC5

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 27 Mar 2023 21:20:20 UTC

            Bug ID: 270489
           Summary: Laptop doesn't wake from suspend anymore with 13.2-RC5
           Product: Base System
           Version: 13.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: henrix@camandro.org

I've upgraded from 13.2-RC3 to 13.2-RC5 (RC4 was too fast for me to try it!)
and my laptop stopped waking up from suspend -- when I open the lid nothing
happens and I need to hard reboot it.  Fortunately, I still have a
booenvironment with -RC3.

Looking at the kernel logs since RC3, I suspect this is related with commit:

commit 7622d3671cbef860d5dede0e4beace8fd152cd87
Author: Konstantin Belousov <kib@FreeBSD.org>
Date:   Fri Mar 17 15:02:03 2023 +0200

    amd64: properly recalculate mitigations knobs after resume

But this is only a guess, of course.  Here's what what's on dmesg about my T490
laptop CPU:

CPU: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (1800.00-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x806ec  Family=0x6  Model=0x8e  Stepping=12
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended
  Structured Extended
  TSC: P-state invariant, performance statistics

(Not sure if this is useful or where to get more useful information.)

Now, maybe this is a different issue, or maybe it is the same... but when I
tried to compile a kernel with the above commit reverted in the 'releng/13.2'
branch (and running -RC5), I had an hard-reboot (!).  As I said, I'm not sure
if that's a different issue, because I had the 4 CPUs at 100%, so maybe it was
an overheating issue.  When I booted back into RC3 kern.msgbuf had the

Fatal trap 9: general protection fault while in kernel mode
cpuid = 3; apic id = 06
instruction pointer     = 0x20:0xffffffff810a253a
stack pointer           = 0x28:0xfffffe012cdcbc20
frame pointer           = 0x28:0xfffffe012cdcbd60
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 15190 (cc)
trap number             = 9
panic: general protection fault
cpuid = 3
time = 1679950971
KDB: stack backtrace:
#0 0xffffffff80c53dc5 at kdb_backtrace+0x65
#1 0xffffffff80c06741 at vpanic+0x151
#2 0xffffffff80c065e3 at panic+0x43
#3 0xffffffff810b1fa7 at trap_fatal+0x387
#4 0xffffffff81088e78 at calltrap+0x8
#5 0xffffffff80f5645f at vmspace_exit+0x7f
#6 0xffffffff80bbc841 at exit1+0x591
#7 0xffffffff80bbc2ad at sys_sys_exit+0xd
#8 0xffffffff810b289c at amd64_syscall+0x10c
#9 0xffffffff8108978b at fast_syscall_common+0xf8
Uptime: 11m17s
Dumping 1470 out of 24183 MB: (CTRL-C to abort) ..2% (CTRL-C to abort)
..11%..21% (CTRL-C to abort) ..31% (CTRL-C to abort) ..41%..51% (CTRL-C to
abort)  (CTRL-C to abort) ..61%..71%..81%..91% (CTRL-C to abort)  (CTRL-C to
abort) ---<<BOOT>>---

You are receiving this mail because:
You are the assignee for the bug.