[SOLVED] Issues with speed after spontaneous power blip

[TJ1]

OS: Linux
Framework 13 11th gen

Not sure if this has happened to anyone else, but today the laptop “blipped”.

At first I thought, I had run the battery to 0, which happens from time to time as the power was not connected. However, the power light was still on, which was unusual.

The machine was unresponsive, so I rebooted. There was a green light on boot that I didn’t notice before. Ever since then, the speed has been very slow. Booting has taken 5-10 minutes. Emacs has taken 86 seconds to load. Not normal.

I’m not sure where to start debugging this. Did something happen to the disk? Did something happen to the motherboard? I’m considering buying another disk tomorrow.

I have a SK Hynix Gold 1TB and here are the current hdparm results. Does anyone have any hdparm results for comparison?

$ sudo hdparm -tT  /dev/nvme0n1
/dev/nvme0n1:
 Timing cached reads:   1824 MB in  2.00 seconds = 913.57 MB/sec
 Timing buffered disk reads: 914 MB in  3.00 seconds = 304.41 MB/sec

$ sudo hdparm -tT --direct /dev/nvme0n1
/dev/nvme0n1:
 Timing O_DIRECT cached reads:   1980 MB in  2.00 seconds = 991.83 MB/sec
 Timing O_DIRECT disk reads: 3192 MB in  3.00 seconds = 1064.00 MB/sec

$ sudo nvme list
Node                  Generic               SN                   Model                                    Namespace Usage                      Format           FW Rev  
--------------------- --------------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1          /dev/ng0n1            AS12T000710102J18    SHGP31-1000GM-2                          1           1.00  TB /   1.00  TB    512   B +  0 B   41061C20

$ sudo nvme smart-log /dev/nvme0n1
Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning                        : 0
temperature                             : 48°C (321 Kelvin)
available_spare                         : 100%
available_spare_threshold               : 10%
percentage_used                         : 0%
endurance group critical warning summary: 0
Data Units Read                         : 2,840,256 (1.45 TB)
Data Units Written                      : 7,748,319 (3.97 TB)
host_read_commands                      : 34,864,625
host_write_commands                     : 191,313,748
controller_busy_time                    : 191
power_cycles                            : 187
power_on_hours                          : 14,089
unsafe_shutdowns                        : 100
media_errors                            : 0
num_err_log_entries                     : 0
Warning Temperature Time                : 0
Critical Composite Temperature Time     : 0
Temperature Sensor 1           : 41°C (314 Kelvin)
Temperature Sensor 2           : 46°C (319 Kelvin)
Thermal Management T1 Trans Count       : 0
Thermal Management T2 Trans Count       : 0
Thermal Management T1 Total Time        : 0
Thermal Management T2 Total Time        : 0

$ sudo nvme self-test /dev/nvme0n1 --self-test-code 1h
$ sudo nvme self-test /dev/nvme0n1
Device Self Test Log for NVME device:nvme0n1
Current operation  : 0
Current Completion : 0%
Self Test Result[0]:
  Operation Result             : 0
  Self Test Code               : 1
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0x3709
  Vendor Specific              : 0 0
Self Test Result[1]:
  Operation Result             : 0xf
Self Test Result[2]:
  Operation Result             : 0xf
Self Test Result[3]:
  Operation Result             : 0xf
Self Test Result[4]:
  Operation Result             : 0xf
Self Test Result[5]:
  Operation Result             : 0xf
Self Test Result[6]:
 

[dimitris]

Couple of threads/known issues come to mind, with possible mitigations there too:

[RESPONDED] CPU gets stuck at 0.2 GHz

Hi all, Wondering if anyone else is having an issue (I run Linux, and haven’t tested this on Windows) where when playing video games (both natively and via Proton), it will suddenly start lagging after an indeterminate amount of time (sometimes hours, sometimes five minutes). I had had an issue with my charger and had it replaced around January/February, and have updated my drivers. I had installed Void and Ubuntu dual-boot, and for the last month or so, running games on Ubuntu worked fine (ex…

and the last point in:

Known issues on early Framework Laptops

We build and thoroughly test on the order of a couple hundred laptops during design, development, and manufacturing bring-up before we start shipping out to customers, but it’s inevitable as we ramp up production that we find new issues after systems land in your hands. There is a standard process in consumer electronics for this called “Early Field Failure Analysis” or EFFA. With this, we take back every system or module we can that has an issue or failure early-on to determine both why it ha…

edit: one thing to try is to fully reset the mainboard: Fully Resetting the Mainboard State - Framework Guides

[TJ1]

OK, this is unbelievable, but resetting the mainboard worked. Thank you for the suggestion. I had already bought a new disk and ram…guess I got to return them now.

$ sudo hdparm -tT /dev/nvme0n1 
/dev/nvme0n1:
 Timing cached reads:   35536 MB in  2.00 seconds = 17808.56 MB/sec
 Timing buffered disk reads: 6778 MB in  3.00 seconds = 2259.21 MB/sec

$ sudo hdparm --direct -tT /dev/nvme0n1

/dev/nvme0n1:
 Timing O_DIRECT cached reads:   4650 MB in  2.00 seconds = 2325.50 MB/sec
 Timing O_DIRECT disk reads: 5978 MB in  3.00 seconds = 1992.43 MB/sec

[Be_Far]

Fascinating. Bookmarking this topic in case I ever experience a ‘blip’.

[TJ1]

So, in hindsight, I believe that this was caused by overheating which is odd because I have been using the laptop in 45 degree weather at times. The fans were on, fairly loud, but also partially blocked. In theory, I guess the cpu must have throttled and then never reset.

I have updated the bios to 3.17, so hopefully, that should prevent any future issues like this one.

[Matt_Hartley]

@TJ1

I have updated the bios to 3.17, so hopefully, that should prevent any future issues like this one.

Thanks for the update. I’ll mark this as resolved. If it crops up again, please update this thread and we may need to look into a CPU repaste.