Hardware failing? if so, any help identify which part from the logs?

Framework Laptop 13 Linux
1

tl;dr framework13 flashing to off-like state, then back (in matter of seconds), and hoping for some preliminary help identifying the culprit.

I have a first-gen framework 13 and just tonight for the first time started seeing the laptop randomly flash to black (disconnect bluetooth, stopping audio, all LEDs go black), then flash back on picking up where it left off. So it’s clearly not a reboot (maybe it’s some partial suspend though?). The flash on/off lasts a maximum of 3-5 seconds. It happened three times tonight, about 10-15min apart.

leads…

Looking at logs below, the only “start” I can see clearly is PM: suspend entry (s2idle) which certainly looks suspiciously related to my nixos config, but I don’t want to jump into that thread just yet, without asking for general linux log-diving wisdom.

edits:

  • I’m actively using/typing on the laptop (in a terminal, programming), so I know for sure this isn’t just some silly-obvious sleep-setting (like “you didn’t boop the trackpad often enough so your machine went to sleep”).
  • this was happening while battery was in use (discharging, not charging). To guess: I think it started around 60%(?) and by the last time happened around 30%. I’m now plugged back in and recharging, to see if it keeps happening.

logs: dmesg output from journalctl

I always have the journalctl --follow --pager-end --catalog --system --full --all --dmesg runnng in a tmux pane, so everytime this happens I’ve gone and copy/save the latest logs I see there. I’ll share below, but first: is there something better I should do to debug? Somewhere else I should look for logs?

I don't think anything in these logs looks sensitive (just some chips mac addresses?) so here's what I'm seeing, if anyone can help identify what's up:

first time:

f:5a2e LEN=80 TC=0 HOPLIMIT=64 FLOWLBL=630400 PROTO=TCP SPT=22000 DPT=22000 WINDOW=65535 RES=0x00 SYN URGP=0
Dec 28 20:26:01 oankali kernel: wlp170s0: disconnect from AP c4:a8:16:6d:97:ca for new auth to c4:a8:16:6d:69:4a
Dec 28 20:26:01 oankali kernel: wlp170s0: authenticate with c4:a8:16:6d:69:4a
Dec 28 20:26:01 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:69:4a (try 1/3)
Dec 28 20:26:02 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:69:4a (try 2/3)
Dec 28 20:26:02 oankali kernel: wlp170s0: authenticated
Dec 28 20:26:02 oankali kernel: wlp170s0: associate with c4:a8:16:6d:69:4a (try 1/3)
Dec 28 20:26:02 oankali kernel: wlp170s0: RX ReassocResp from c4:a8:16:6d:69:4a (capab=0x1111 status=0 aid=3)
Dec 28 20:26:02 oankali kernel: wlp170s0: associated
Dec 28 20:26:02 oankali kernel: wlp170s0: Limiting TX power to 21 (24 - 3) dBm as advertised by c4:a8:16:6d:69:4a
Dec 28 20:30:45 oankali kernel: wlp170s0: deauthenticating from c4:a8:16:6d:69:4a by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 28 20:30:47 oankali kernel: PM: suspend entry (s2idle)
Dec 28 20:30:48 oankali kernel: Filesystems sync: 0.006 seconds
Dec 28 20:30:51 oankali kernel: Freezing user space processes
Dec 28 20:30:51 oankali kernel: Freezing user space processes completed (elapsed 0.003 seconds)
Dec 28 20:30:51 oankali kernel: OOM killer disabled.
Dec 28 20:30:51 oankali kernel: Freezing remaining freezable tasks
Dec 28 20:30:51 oankali kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Dec 28 20:30:51 oankali kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 28 20:30:51 oankali kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 28 20:30:51 oankali kernel: ACPI: EC: interrupt blocked
Dec 28 20:30:51 oankali kernel: ACPI: EC: interrupt unblocked
Dec 28 20:30:51 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Dec 28 20:30:51 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Dec 28 20:30:51 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_AUTH_KEY_0: 0x90
Dec 28 20:30:51 oankali kernel: iwlwifi 0000:aa:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Dec 28 20:30:51 oankali kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Dec 28 20:30:51 oankali kernel: OOM killer enabled.
Dec 28 20:30:51 oankali kernel: Restarting tasks ... done.
Dec 28 20:30:51 oankali kernel: random: crng reseeded on system resumption
Dec 28 20:30:51 oankali kernel: PM: suspend exit
Dec 28 20:30:53 oankali kernel: wlp170s0: authenticate with c4:a8:16:6d:97:ca
Dec 28 20:30:53 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:97:ca (try 1/3)
Dec 28 20:30:54 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:97:ca (try 2/3)
Dec 28 20:30:54 oankali kernel: wlp170s0: authenticated
Dec 28 20:30:54 oankali kernel: wlp170s0: associate with c4:a8:16:6d:97:ca (try 1/3)
Dec 28 20:30:54 oankali kernel: wlp170s0: RX AssocResp from c4:a8:16:6d:97:ca (capab=0x1111 status=0 aid=1)
Dec 28 20:30:54 oankali kernel: wlp170s0: associated
Dec 28 20:30:54 oankali kernel: wlp170s0: Limiting TX power to 21 (24 - 3) dBm as advertised by c4:a8:16:6d:97:ca
Dec 28 20:30:55 oankali kernel: input: Galaxy Buds Live (013B) (AVRCP) as /devices/virtual/input/input51
Dec 28 20:31:31 oankali kernel: wlp170s0: deauthenticating from c4:a8:16:6d:97:ca by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 28 20:31:33 oankali kernel: PM: suspend entry (s2idle)
Dec 28 20:31:33 oankali kernel: Filesystems sync: 0.009 seconds
Dec 28 20:31:34 oankali kernel: Freezing user space processes
Dec 28 20:31:34 oankali kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Dec 28 20:31:34 oankali kernel: OOM killer disabled.
Dec 28 20:31:34 oankali kernel: Freezing remaining freezable tasks
Dec 28 20:31:34 oankali kernel: Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
Dec 28 20:31:34 oankali kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 28 20:31:34 oankali kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 28 20:31:34 oankali kernel: ACPI: EC: interrupt blocked
Dec 28 20:31:34 oankali kernel: ACPI: EC: interrupt unblocked
Dec 28 20:31:34 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Dec 28 20:31:34 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Dec 28 20:31:34 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_AUTH_KEY_0: 0x90
Dec 28 20:31:34 oankali kernel: iwlwifi 0000:aa:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Dec 28 20:31:34 oankali kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Dec 28 20:31:34 oankali kernel: OOM killer enabled.
Dec 28 20:31:34 oankali kernel: Restarting tasks ... done.
Dec 28 20:31:34 oankali kernel: random: crng reseeded on system resumption
Dec 28 20:31:34 oankali kernel: PM: suspend exit
Dec 28 20:31:37 oankali kernel: wlp170s0: authenticate with c4:a8:16:6d:97:ca
Dec 28 20:31:37 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:97:ca (try 1/3)
Dec 28 20:31:37 oankali kernel: wlp170s0: authenticated
Dec 28 20:31:37 oankali kernel: wlp170s0: associate with c4:a8:16:6d:97:ca (try 1/3)
Dec 28 20:31:37 oankali kernel: wlp170s0: RX AssocResp from c4:a8:16:6d:97:ca (capab=0x1111 status=0 aid=1)
Dec 28 20:31:37 oankali kernel: wlp170s0: associated
Dec 28 20:31:37 oankali kernel: wlp170s0: Limiting TX power to 21 (24 - 3) dBm as advertised by c4:a8:16:6d:97:ca
Dec 28 20:31:38 oankali kernel: input: Galaxy Buds Live (013B) (AVRCP) as /devices/virtual/input/input52

second time:

Dec 28 20:34:47 oankali kernel: wlp170s0: deauthenticating from c4:a8:16:6d:97:ca by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 28 20:34:48 oankali kernel: PM: suspend entry (s2idle)
Dec 28 20:34:48 oankali kernel: Filesystems sync: 0.006 seconds
Dec 28 20:35:00 oankali kernel: Freezing user space processes
Dec 28 20:35:00 oankali kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Dec 28 20:35:00 oankali kernel: OOM killer disabled.
Dec 28 20:35:00 oankali kernel: Freezing remaining freezable tasks
Dec 28 20:35:00 oankali kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Dec 28 20:35:00 oankali kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 28 20:35:00 oankali kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 28 20:35:00 oankali kernel: ACPI: EC: interrupt blocked
Dec 28 20:35:00 oankali kernel: ACPI: EC: interrupt unblocked
Dec 28 20:35:00 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Dec 28 20:35:00 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Dec 28 20:35:00 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_AUTH_KEY_0: 0x90
Dec 28 20:35:00 oankali kernel: iwlwifi 0000:aa:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Dec 28 20:35:00 oankali kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Dec 28 20:35:00 oankali kernel: OOM killer enabled.
Dec 28 20:35:00 oankali kernel: Restarting tasks ... done.
Dec 28 20:35:00 oankali kernel: random: crng reseeded on system resumption
Dec 28 20:35:00 oankali kernel: PM: suspend exit
Dec 28 20:35:03 oankali kernel: wlp170s0: authenticate with c4:a8:16:6d:97:ca
Dec 28 20:35:03 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:97:ca (try 1/3)
Dec 28 20:35:04 oankali kernel: wlp170s0: authenticated
Dec 28 20:35:04 oankali kernel: wlp170s0: associate with c4:a8:16:6d:97:ca (try 1/3)
Dec 28 20:35:04 oankali kernel: wlp170s0: RX AssocResp from c4:a8:16:6d:97:ca (capab=0x1111 status=0 aid=1)
Dec 28 20:35:04 oankali kernel: wlp170s0: associated
Dec 28 20:35:04 oankali kernel: wlp170s0: Limiting TX power to 21 (24 - 3) dBm as advertised by c4:a8:16:6d:97:ca
Dec 28 20:35:04 oankali kernel: input: Galaxy Buds Live (013B) (AVRCP) as /devices/virtual/input/input53

third time:

Dec 28 20:58:05 oankali kernel: wlp170s0: deauthenticating from c4:a8:16:6d:97:ca by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 28 20:58:06 oankali kernel: PM: suspend entry (s2idle)
Dec 28 20:58:06 oankali kernel: Filesystems sync: 0.007 seconds
Dec 28 20:58:23 oankali kernel: Freezing user space processes
Dec 28 20:58:23 oankali kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Dec 28 20:58:23 oankali kernel: OOM killer disabled.
Dec 28 20:58:23 oankali kernel: Freezing remaining freezable tasks
Dec 28 20:58:23 oankali kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Dec 28 20:58:23 oankali kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 28 20:58:23 oankali kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 28 20:58:23 oankali kernel: ACPI: EC: interrupt blocked
Dec 28 20:58:23 oankali kernel: ACPI: EC: interrupt unblocked
Dec 28 20:58:23 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Dec 28 20:58:23 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Dec 28 20:58:23 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_AUTH_KEY_0: 0x90
Dec 28 20:58:23 oankali kernel: iwlwifi 0000:aa:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Dec 28 20:58:23 oankali kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Dec 28 20:58:23 oankali kernel: OOM killer enabled.
Dec 28 20:58:23 oankali kernel: Restarting tasks ... done.
Dec 28 20:58:23 oankali kernel: random: crng reseeded on system resumption
Dec 28 20:58:23 oankali kernel: PM: suspend exit
Dec 28 20:58:23 oankali kernel: usb 2-2: USB disconnect, device number 2
Dec 28 20:58:23 oankali kernel: device offline error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2
Dec 28 20:58:23 oankali kernel: EXT4-fs (sda1): shut down requested (2)
Dec 28 20:58:23 oankali kernel: Aborting journal on device sda1-8.
Dec 28 20:58:23 oankali kernel: device offline error, dev sda, sector 973406207 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
Dec 28 20:58:23 oankali kernel: device offline error, dev sda, sector 973406207 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
Dec 28 20:58:23 oankali kernel: Buffer I/O error on dev sda1, logical block 121667584, lost sync page write
Dec 28 20:58:23 oankali kernel: JBD2: I/O error when updating journal superblock for sda1-8.
Dec 28 20:58:23 oankali kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 28 20:58:23 oankali kernel: EXT4-fs (sda1): unmounting filesystem f7066521-3fbf-4010-aee8-f30532b6eb1e.
Dec 28 20:58:23 oankali kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 28 20:58:24 oankali kernel: usb 2-2: new SuperSpeed Plus Gen 2x1 USB device number 5 using xhci_hcd
Dec 28 20:58:24 oankali kernel: usb 2-2: New USB device found, idVendor=13fe, idProduct=6500, bcdDevice= 1.10
Dec 28 20:58:24 oankali kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 28 20:58:24 oankali kernel: usb 2-2: Product: USB DISK 3.2
Dec 28 20:58:24 oankali kernel: usb 2-2: Manufacturer:
Dec 28 20:58:24 oankali kernel: usb 2-2: SerialNumber: 070017CE39878809
Dec 28 20:58:24 oankali kernel: scsi host0: uas
Dec 28 20:58:24 oankali kernel: scsi 0:0:0:0: Direct-Access              USB DISK 3.2     PMAP PQ: 0 ANSI: 6
Dec 28 20:58:24 oankali kernel: sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Dec 28 20:58:24 oankali kernel: sd 0:0:0:0: [sda] Write Protect is off
Dec 28 20:58:24 oankali kernel: sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
Dec 28 20:58:24 oankali kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 28 20:58:24 oankali kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Dec 28 20:58:24 oankali kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Dec 28 20:58:24 oankali kernel:  sda: sda1
Dec 28 20:58:24 oankali kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Dec 28 20:58:26 oankali kernel: wlp170s0: authenticate with c4:a8:16:6d:97:ca
Dec 28 20:58:26 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:97:ca (try 1/3)
Dec 28 20:58:26 oankali kernel: wlp170s0: authenticated
Dec 28 20:58:26 oankali kernel: wlp170s0: associate with c4:a8:16:6d:97:ca (try 1/3)
Dec 28 20:58:26 oankali kernel: wlp170s0: RX AssocResp from c4:a8:16:6d:97:ca (capab=0x1111 status=0 aid=1)
Dec 28 20:58:26 oankali kernel: wlp170s0: associated
Dec 28 20:58:26 oankali kernel: wlp170s0: Limiting TX power to 21 (24 - 3) dBm as advertised by c4:a8:16:6d:97:ca
Dec 28 20:58:27 oankali kernel: input: Galaxy Buds Live (013B) (AVRCP) as /devices/virtual/input/input54
Dec 28 20:58:34 oankali kernel: EXT4-fs (sda1): recovery complete
Dec 28 20:58:34 oankali kernel: EXT4-fs (sda1): mounted filesystem f7066521-3fbf-4010-aee8-f30532b6eb1e r/w with ordered data mode. Quota mode: none.
Dec 28 20:58:59 oankali kernel: refused connection: IN=wlp170s0 OUT= MAC=54:14:f3:52:c1:23:d6:38:d3:ef:60:8f:08:00 SRC=192.168.4.21 DST=192.168.7.237 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=4051 DF PROTO=TCP SPT=42268 DPT=22000 WINDOW=65535 RES=0x00 SYN URGP=0
Dec 28 20:59:03 oankali kernel: refused connection: IN=wlp170s0 OUT= MAC=54:14:f3:52:c1:23:d6:38:d3:ef:60:8f:08:00 SRC=192.168.4.21 DST=192.168.7.237 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=25909 DF PROTO=TCP SPT=22000 DPT=22000 WINDOW=65535 RES=0x00 SYN URGP=0
Dec 28 20:59:11 oankali kernel: cros_ec_lpcs cros_ec_lpcs.0: packet too long (4 bytes, expected 0)

From those log lines above, much of the content that was bolded was roughly from the line:

  • sd 0:0:0:0: [sda] Synchronizing SCSI cache
  • sd 0:0:0:0: [sda] Attached SCSI disk

(I’m guessing all the I/O disk errors are due to the fact that the machine suddenly had this issue, in the middle of some disk-operation… so just guessing that disk messages are red herrings).

edits: added a couple bullets to “leads” to answer power/suspend thoughts I left out.

2

Any magnets near the machine? Galaxy buds case, for example?

3

Huh they were actually nearby in my pocket (though some inches away, not touching directly). Let me see if I can repro the issue again (and I’ll be careful to leave those somewhere else).

4

Okay confirmed not related to nearby magnets. But maybe related to bluetooth somehow crashing something critical?

reproduced, maybe related to bluetooth bug?

the below log line that’s highlighted red is Bluetooth: hci0: SCO packet for unknown connection handle 257

this happened moments after listening to audio via new earbuds (and again: definitely the case, and no other magnets, were near my laptop):

Dec 29 18:02:58 oankali kernel: input: Galaxy Buds FE (AVRCP) as /devices/virtual/input/input20
Dec 29 18:04:25 oankali kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257
Dec 29 18:04:25 oankali kernel: wlp170s0: deauthenticating from c4:a8:16:6d:97:ca by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 29 18:04:26 oankali kernel: PM: suspend entry (s2idle)
Dec 29 18:04:26 oankali kernel: Filesystems sync: 0.010 seconds
Dec 29 18:04:35 oankali kernel: Freezing user space processes
Dec 29 18:04:35 oankali kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Dec 29 18:04:35 oankali kernel: OOM killer disabled.
Dec 29 18:04:35 oankali kernel: Freezing remaining freezable tasks
Dec 29 18:04:35 oankali kernel: Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
Dec 29 18:04:35 oankali kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 29 18:04:35 oankali kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 29 18:04:35 oankali kernel: ACPI: EC: interrupt blocked
Dec 29 18:04:35 oankali kernel: ACPI: EC: interrupt unblocked
Dec 29 18:04:35 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Dec 29 18:04:35 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Dec 29 18:04:35 oankali kernel: iwlwifi 0000:aa:00.0: WFPM_AUTH_KEY_0: 0x90
Dec 29 18:04:35 oankali kernel: iwlwifi 0000:aa:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Dec 29 18:04:35 oankali kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Dec 29 18:04:35 oankali kernel: OOM killer enabled.
Dec 29 18:04:35 oankali kernel: Restarting tasks ... done.
Dec 29 18:04:35 oankali kernel: random: crng reseeded on system resumption
Dec 29 18:04:35 oankali kernel: PM: suspend exit
Dec 29 18:04:38 oankali kernel: input: Galaxy Buds FE (AVRCP) as /devices/virtual/input/input21
Dec 29 18:04:38 oankali kernel: wlp170s0: authenticate with c4:a8:16:6d:97:ca
Dec 29 18:04:38 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:97:ca (try 1/3)
Dec 29 18:04:38 oankali kernel: wlp170s0: authenticated
Dec 29 18:04:38 oankali kernel: wlp170s0: associate with c4:a8:16:6d:97:ca (try 1/3)
Dec 29 18:04:38 oankali kernel: wlp170s0: RX AssocResp from c4:a8:16:6d:97:ca (capab=0x1111 status=0 aid=4)
Dec 29 18:04:38 oankali kernel: wlp170s0: associated
Dec 29 18:04:39 oankali kernel: wlp170s0: Limiting TX power to 21 (24 - 3) dBm as advertised by c4:a8:16:6d:97:ca
Dec 29 18:04:43 oankali kernel: wlp170s0: disconnect from AP c4:a8:16:6d:97:ca for new auth to c4:a8:16:6d:69:4a
Dec 29 18:04:43 oankali kernel: wlp170s0: authenticate with c4:a8:16:6d:69:4a
Dec 29 18:04:43 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:69:4a (try 1/3)
Dec 29 18:04:43 oankali kernel: wlp170s0: authenticated
Dec 29 18:04:43 oankali kernel: wlp170s0: associate with c4:a8:16:6d:69:4a (try 1/3)
Dec 29 18:04:43 oankali kernel: wlp170s0: RX ReassocResp from c4:a8:16:6d:69:4a (capab=0x1111 status=0 aid=1)
Dec 29 18:04:43 oankali kernel: wlp170s0: associated
Dec 29 18:04:43 oankali kernel: wlp170s0: Limiting TX power to 21 (24 - 3) dBm as advertised by c4:a8:16:6d:69:4a
Dec 29 18:04:52 oankali kernel: wlp170s0: disconnect from AP c4:a8:16:6d:69:4a for new auth to c4:a8:16:6d:97:ca
Dec 29 18:04:52 oankali kernel: wlp170s0: authenticate with c4:a8:16:6d:97:ca
Dec 29 18:04:52 oankali kernel: wlp170s0: send auth to c4:a8:16:6d:97:ca (try 1/3)
Dec 29 18:04:52 oankali kernel: wlp170s0: authenticated
Dec 29 18:04:52 oankali kernel: wlp170s0: associate with c4:a8:16:6d:97:ca (try 1/3)
Dec 29 18:04:52 oankali kernel: wlp170s0: RX ReassocResp from c4:a8:16:6d:97:ca (capab=0x1111 status=0 aid=4)
Dec 29 18:04:52 oankali kernel: wlp170s0: associated
Dec 29 18:04:52 oankali kernel: wlp170s0: Limiting TX power to 21 (24 - 3) dBm as advertised by c4:a8:16:6d:97:ca

I’m gonna keep testing and see how to reproduce more reliably. But I’m open to any more ideas!

5

So I guess the question is what is triggering the suspends and why?

In particular, is a user-space process triggering the suspends? My guess would be: “yes”, but how to prove it / find the culprit? Maybe there’s some setting in /sys/power/ that can be tweaked to increase the verbosity level, including the information about the trigger? Or is there perhaps some way to intercept access to /sys/power/state system-wide and find the culprit that way?

One theory (not based on anything in particular in your logs) is that maybe the battery occasionally misreports a very low charge level (0?), prompting suspend? Does your problem only happen on battery power or also when plugged in? Do you have upowerd running? If so, maybe try running with upower --monitor-detail in a terminal window to see if it prints anything of interest during these suspend events?

1 Like
6

Thanks! it indeed only happens when discharging (so far). Good to know you also don’t see anything obvious in the logs that I’m missing.

Good idea on upower, I’m running --monitor-detail now as I discharge (with journalctl side-by-side). Hopefully I can catch something interesting happening.

I’ll report back next time this happens.

7

I also recall someone running into an issue with the sensor failing. I believe that it is part of the audio board. I will link the thread if I can dig it up.

Found it: [SOLVED] Laptop randomly hibernating (unexpected lid switch event) - #4 by Richard_Tango-Lowy

1 Like
8

Glad to be of service ;- )

It took me a month to diagnose the problem, and about 3 minutes to fix it!

1 Like
9

Happy New Year! I hope that you are well!

10

I am! Just finished a very busy season at the chocolate shop and am taking a break in Costa Rica before preparing for the Valentine’s Day rush. I decided to bring my new Thinkpad X1 Carbon Gen 11 along instead of the FW13, as the battery life is really excellent. You know, I’ve decided I really prefer the Framework, so maybe it’s time for that new bigger battery…

Happy New Year to you!

11

Thanks all! This hasn’t happened again since my last update, but your issue with your audiocard is interesting. I did recently upgrade a bunch of components myself (screen, hinge, webcam), so it’s possible I messed something up when I was in there…