You are not logged in.

Pages: 1

#1 2020-05-02 22:12:15

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

[SOLVED] ACPI errors during BIOS boot time

I've been using my HP Probook 430 G4 for 2 years now with seemingly no errors whatsoever. There were a few ACPI errors during startup but they were relatively harmless and after doing some research I found that I could do nothing about them, so I just stopped paying attention:

ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000b29e9ba8 (20200110/exresop-557)
ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20200110/dswexec-431)
ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20200110/psparse-529)
ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20200110/psparse-529)
ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000009b0ec886 (20200110/exresop-557)
ACPI Error: AE_RML_OPERAND_TYPE, While resolving operands for [Index] (20200110/dswexec-431)
ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20200110/psparse-529)
ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (RE_AML_OPERAND_TYPE) (20200110/psparse-529)
ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000ff93e3d (20200110/exresop-557)
ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20200110/dswexec-431)
ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20200110/psparse-529)
ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20200110/psparse-529)
ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000eb4168ac (20200110/exresop-557)
ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20200110/dswexec-431)
ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20200110/psparse-529)
ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20200110/psparse-529)

However after one of the recent updates (now I'm running kernel version 5.6.8) I've stumbled upon something more serious. Sometimes my laptop freezes during BIOS boot up time and if it does get to actual system boot it briefly displays the following ACPI errors which I've never seen before:

x86/cpu: VMX (outside TXT) disabled by BIOS
ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT. FIeld [CAP1] at bit offset/length 64/32 exceeds size of target Buffer (64 bits) (20200110/dsopcode-198)
ACPI Error: Aborting method \_SB._OSC due to previous error (AE_AML_BUFFER_LIMIT) (20200110/psparse-529)
ata1.00: exception Emask 0x10 SAct 0x2000000 SErr 0xc50001 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error
ata1: SError: { RecovData PHYRdyChg CommWake Handshk LinkSeq }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:c8:08:00:00/00:00:00:00:00/40 tag 25 ncq dma 4096 in res 50/00:08:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: failed to set xfermode (err_mask=0x100)
ata1.00: failed to enable AA (error_mask=0x100)
ata1.00: revalidation failed (errno=-5)

My BIOS version is "P85 Ver. 01.06 06/18/2017". This HP forum post shows that other users have experienced the same issue as me, but it should have been fixed in kernel version 5.4. However my errors are new and it bothers me. What are my next steps? If you need any additional information about my Arch Linux install, please ask away.

Last edited by dr3amyxen0 (2020-05-07 00:07:26)

Offline

#2 2020-05-03 05:35:40

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: [SOLVED] ACPI errors during BIOS boot time

Have you run a smartctl test on whatever is connected to "ata1.00" to check if it's a hardware issue? https://wiki.archlinux.org/index.php/S.M.A.R.T.

If "ata1.00" is for instance /dev/sda...

smartctl -t short /dev/sda

wait for the test to finish, and then...

smartctl -a /dev/sda

and look for errors in the lower sections of the output.

What is connected to "ata1.00"? Spinning HDD/SSD?

Edit: also there is a bios update - https://support.hp.com/gb-en/drivers/se … c/10477243
which shows you are using a really old bios version.
See https://bbs.archlinux.org/viewtopic.php … 8#p1870408 which should help get the file from the .exe download

Last edited by paulkerry (2020-05-03 05:41:49)

Offline

#3 2020-05-03 08:01:00

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

Re: [SOLVED] ACPI errors during BIOS boot time

paulkerry wrote:

Have you run a smartctl test on whatever is connected to "ata1.00" to check if it's a hardware issue? What is connected to "ata1.00"? Spinning HDD/SSD?

I'm almost completely sure it's an HDD that I've been getting a lot of problems with recently. File system check errors all over the place so I had to manually run fsck every so often. Here is the log from smartctl:

ATA Error Count: 1054 (device log contains only the most recent five errors)

Error 1054 occurred at disk power-on lifetime: 8639 hours (359 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 10 c8 e6 68 0c  Error: ICRC, ABRT at LBA = 0x0c68e6c8 = 208201416

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 40 b0 a0 12 04 40 00      09:48:19.361  WRITE FPDMA QUEUED
  61 40 a8 98 7d 51 40 00      09:48:19.361  WRITE FPDMA QUEUED
  61 40 a0 70 a2 c3 40 00      09:48:19.361  WRITE FPDMA QUEUED
  61 40 98 00 68 4e 40 00      09:48:19.361  WRITE FPDMA QUEUED
  61 40 90 00 a8 42 40 00      09:48:19.360  WRITE FPDMA QUEUED

Error 1053 occurred at disk power-on lifetime: 8639 hours (359 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 3f 96 6d 0c  Error: ICRC, ABRT at LBA = 0x0c6d963f = 208508479

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 40 d0 00 96 6d 40 00      09:30:45.369  WRITE FPDMA QUEUED
  61 40 c8 a0 12 04 40 00      09:30:45.369  WRITE FPDMA QUEUED
  60 08 c0 c0 9d 13 40 00      09:30:45.369  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      09:30:45.368  FLUSH CACHE EXT
  60 08 98 40 9d 13 40 00      09:30:45.368  READ FPDMA QUEUED

Error 1052 occurred at disk power-on lifetime: 8639 hours (359 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 ff 25 45 00  Error: ICRC, ABRT at LBA = 0x004525ff = 4531711

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 18 d0 2a 45 40 00      09:13:09.259  WRITE FPDMA QUEUED
  61 08 10 b8 2a 45 40 00      09:13:09.259  WRITE FPDMA QUEUED
  61 08 08 48 2a 45 40 00      09:13:09.259  WRITE FPDMA QUEUED
  61 08 00 f8 25 45 40 00      09:13:09.259  WRITE FPDMA QUEUED
  61 08 f0 e8 24 45 40 00      09:13:09.259  WRITE FPDMA QUEUED

Error 1051 occurred at disk power-on lifetime: 8639 hours (359 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 77 3c 40 0e  Error: ICRC, ABRT at LBA = 0x0e403c77 = 239090807

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 a8 c0 29 41 40 00      09:04:02.418  WRITE FPDMA QUEUED
  61 10 a0 68 3c 40 40 00      09:04:02.418  WRITE FPDMA QUEUED
  61 08 98 28 2a 40 40 00      09:04:02.418  WRITE FPDMA QUEUED
  61 08 90 68 29 40 40 00      09:04:02.418  WRITE FPDMA QUEUED
  61 08 88 80 28 40 40 00      09:04:02.418  WRITE FPDMA QUEUED

Error 1050 occurred at disk power-on lifetime: 8638 hours (359 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 0f 28 40 0e  Error: ICRC, ABRT at LBA = 0x0e40280f = 239085583

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 70 b0 33 42 40 00      08:19:25.301  WRITE FPDMA QUEUED
  61 08 68 08 19 41 40 00      08:19:25.301  WRITE FPDMA QUEUED
  61 08 60 08 33 00 40 00      08:19:25.301  WRITE FPDMA QUEUED
  61 08 40 18 33 41 40 00      08:19:25.301  WRITE FPDMA QUEUED
  61 08 38 70 3c 40 40 00      08:19:25.301  WRITE FPDMA QUEUED

Still not entirely sure what I'm looking at. I've never run into these kinds of hardware problems before so I just assumed my hard disk was dying.

paulkerry wrote:

See which should help get the file from the .exe download

My BIOS indeed is really old. The thread you've linked suggests I extract .bin files from the official .exe file however it cannot be opened as an archive. I will try to research the subject more as I've been advised against updating BIOS on Linux machines.

Offline

#4 2020-05-03 10:19:00

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,104

Re: [SOLVED] ACPI errors during BIOS boot time

Please post the entire smartctl -a . But yes that doesn't look good, sometimes these issues are just due to SATA powermanagement not working properly, but you'd have noticed bugs with that much sooner. Just from this without the full picture I'd say you shouldn't trust the drive anymore.

Offline

#5 2020-05-03 13:08:45

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

Re: [SOLVED] ACPI errors during BIOS boot time

V1del wrote:

Please post the entire smartctl -a

$ sudo smartctl -a /dev/sda           
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.6.8-arch1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi/HGST Travelstar Z5K500
Device Model:     HGST HTS545050A7E680
Serial Number:    
LU WWN Device Id: 5 000cca 899f6ef36
Firmware Version: GR2OA230
User Capacity:    500107862016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Sun May  3 16:01:54 2020 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(   45) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 108) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   222   222   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0012   087   087   000    Old_age   Always       -       21431
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   081   081   000    Old_age   Always       -       8645
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       2297
191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       21
193 Load_Cycle_Count        0x0012   073   073   000    Old_age   Always       -       275482
194 Temperature_Celsius     0x0002   162   162   000    Old_age   Always       -       37 (Min/Max 13/47)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       1070
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1070 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1070 occurred at disk power-on lifetime: 8645 hours (360 days + 5 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 4f e9 14 0d  Error: ICRC, ABRT at LBA = 0x0d14e94f = 219474255

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 10 d8 50 e9 14 40 00      15:25:31.840  WRITE FPDMA QUEUED
  61 10 c0 40 e9 14 40 00      15:25:31.840  WRITE FPDMA QUEUED
  61 40 50 70 a2 c3 40 00      15:25:31.839  WRITE FPDMA QUEUED
  61 40 48 00 96 6d 40 00      15:25:31.839  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      15:25:31.839  FLUSH CACHE EXT

Error 1069 occurred at disk power-on lifetime: 8645 hours (360 days + 5 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 c0 40 b0 10 00  Error: ICRC, ABRT at LBA = 0x0010b040 = 1093696

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 b0 70 09 ac 40 00      15:04:27.338  WRITE FPDMA QUEUED
  61 00 a8 00 b0 10 40 00      15:04:27.338  WRITE FPDMA QUEUED
  61 08 a0 b0 33 42 40 00      15:04:27.337  WRITE FPDMA QUEUED
  61 08 40 08 19 41 40 00      15:04:27.337  WRITE FPDMA QUEUED
  61 08 38 b8 2c 40 40 00      15:04:27.337  WRITE FPDMA QUEUED

Error 1068 occurred at disk power-on lifetime: 8644 hours (360 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 98 e8 dc 79 05  Error: ICRC, ABRT at LBA = 0x0579dce8 = 91872488

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 58 88 28 dc 79 40 00      14:44:31.213  WRITE FPDMA QUEUED
  61 40 80 e8 d6 79 40 00      14:44:31.213  WRITE FPDMA QUEUED
  61 80 78 68 d5 79 40 00      14:44:31.213  WRITE FPDMA QUEUED
  61 c0 70 58 cf 79 40 00      14:44:31.213  WRITE FPDMA QUEUED
  61 40 68 18 ca 79 40 00      14:44:31.213  WRITE FPDMA QUEUED

Error 1067 occurred at disk power-on lifetime: 8644 hours (360 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 a0 10 58 0c 05  Error: ICRC, ABRT at LBA = 0x050c5810 = 84695056

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 f8 68 00 b0 10 40 00      14:31:28.935  WRITE FPDMA QUEUED
  61 08 60 70 09 ac 40 00      14:31:28.931  WRITE FPDMA QUEUED
  61 00 58 00 70 0c 40 00      14:31:28.909  WRITE FPDMA QUEUED
  61 38 50 00 78 0c 40 00      14:31:28.905  WRITE FPDMA QUEUED
  61 50 48 b0 5a 0c 40 00      14:31:28.901  WRITE FPDMA QUEUED

Error 1066 occurred at disk power-on lifetime: 8644 hours (360 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 58 f0 6a 0c 05  Error: ICRC, ABRT at LBA = 0x050c6af0 = 84699888

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 c0 08 40 65 0c 40 00      14:25:19.067  WRITE FPDMA QUEUED
  61 40 00 00 60 0c 40 00      14:25:19.067  WRITE FPDMA QUEUED
  61 48 f8 00 68 0c 40 00      14:25:19.067  WRITE FPDMA QUEUED
  61 00 b8 00 5c 0c 40 00      14:25:19.067  WRITE FPDMA QUEUED
  61 00 b0 00 58 0c 40 00      14:25:19.063  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      8639         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

As for the drive I've already started copying away my files while it still works.

Offline

#6 2020-05-03 13:22:13

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

Re: [SOLVED] ACPI errors during BIOS boot time

V1del wrote:

SATA powermanagement not working properly

If that makes any difference I'm using TLP for better battery life alongside with KDE power management tools, but the configs are pretty much default with all the settings commented out:

# ------------------------------------------------------------------------------
# /etc/tlp.conf - TLP user configuration
# See full explanation: https://linrunner.de/en/tlp/docs/tlp-configuration.html
#
# New configuration scheme (TLP 1.3). Settings are read in the following order:

# 1. Intrinsic defaults
# 2. /etc/tlp.d/*.conf - Drop-in customization snippets
# 3. /etc/tlp.conf     - User configuration (this file)
#
# Notes:
# - In case of identical parameters, the last occurence has precedence
# - This also means, parameters enabled here will override anything else
# - IMPORTANT: all parameters here are disabled, remove the leading '#'
#   to enable them; shown values may be suggestions rather than defaults
# - Default *: intrinsic default that is effective when the parameter is missing
#     or disabled by a leading '#'; use PARAM="" to disable an intrinsic default
# - Default <none>: do nothing or use kernel/hardware defaults

# ------------------------------------------------------------------------------
# tlp - Parameters for power saving

# Set to 0 to disable, 1 to enable TLP.
# Default: 1

#TLP_ENABLE=1

# Operation mode when no power supply can be detected: AC, BAT.
# Concerns some desktop and embedded hardware only.
# Default: <none>

#TLP_DEFAULT_MODE=AC

# Operation mode select: 0=depend on power source, 1=always use TLP_DEFAULT_MODE
# Note: use in conjunction with TLP_DEFAULT_MODE=BAT for BAT settings on AC.
# Default: 0

#TLP_PERSISTENT_DEFAULT=0

# Power supply class to ignore when determining operation mode: AC, BAT.
# Note: try on laptops where operation mode AC/BAT is incorrectly detected.
# Default: <none>

#TLP_PS_IGNORE=BAT

# Seconds laptop mode has to wait after the disk goes idle before doing a sync.
# Non-zero value enables, zero disables laptop mode.
# Default: 0 (AC), 2 (BAT)

#DISK_IDLE_SECS_ON_AC=0
#DISK_IDLE_SECS_ON_BAT=2

# Dirty page values (timeouts in secs).
# Default: 15 (AC), 60 (BAT)

#MAX_LOST_WORK_SECS_ON_AC=15
#MAX_LOST_WORK_SECS_ON_BAT=60

# Note: CPU parameters below are disabled by default, remove the leading #
# to enable them, otherwise kernel defaults will be used.
#
# Select a CPU frequency scaling governor.
# Intel Core i processor with intel_pstate driver:
#   powersave(*), performance.
# Other hardware with acpi-cpufreq driver:
#   ondemand(*), powersave, performance, conservative, schedutil.
# (*) is recommended.
# Use tlp-stat -p to show the active driver and available governors.
# Important:
#   powersave for intel_pstate and ondemand for acpi-cpufreq are power
#   efficient for *almost all* workloads and therefore kernel and most
#   distributions have chosen them as defaults. If you still want to change,
#   you should know what you're doing!
# Default: <none>

#CPU_SCALING_GOVERNOR_ON_AC=powersave
#CPU_SCALING_GOVERNOR_ON_BAT=powersave

# Set the min/max frequency available for the scaling governor.
# Possible values depend on your CPU. For available frequencies see
# the output of tlp-stat -p.
# Default: <none>

#CPU_SCALING_MIN_FREQ_ON_AC=0
#CPU_SCALING_MAX_FREQ_ON_AC=0
#CPU_SCALING_MIN_FREQ_ON_BAT=0
#CPU_SCALING_MAX_FREQ_ON_BAT=0

# Set Intel CPU energy/performance policies HWP.EPP and EPB:
#   performance, balance_performance, default, balance_power, power
# Values are given in order of increasing power saving.
# Notes:
# - Requires an Intel Core i processor
# - HWP.EPP requires kernel 4.10 and intel_pstate driver
# - EPB requires kernel 5.2 or module msr and x86_energy_perf_policy
#   from linux-tools
# - When HWP.EPP is available, EPB is not set
# Default: balance_performance (AC), balance_power (BAT)

#CPU_ENERGY_PERF_POLICY_ON_AC=balance_performance
#CPU_ENERGY_PERF_POLICY_ON_BAT=balance_power

# Set Intel CPU P-state performance: 0..100 (%).
# Limit the max/min P-state to control the power dissipation of the CPU.
# Values are stated as a percentage of the available performance.
# Requires an Intel Core i processor with intel_pstate driver.
# Default: <none>

#CPU_MIN_PERF_ON_AC=0
#CPU_MAX_PERF_ON_AC=100
#CPU_MIN_PERF_ON_BAT=0
#CPU_MAX_PERF_ON_BAT=30

# Set the CPU "turbo boost" feature: 0=disable, 1=allow
# Requires an Intel Core i processor.
# Important:
# - This may conflict with your distribution's governor settings
# - A value of 1 does *not* activate boosting, it just allows it
# Default: <none>

#CPU_BOOST_ON_AC=1
#CPU_BOOST_ON_BAT=0

# Minimize number of used CPU cores/hyper-threads under light load conditions:
#   0=disable, 1=enable.
# Default: 0 (AC), 1 (BAT)

#SCHED_POWERSAVE_ON_AC=0
#SCHED_POWERSAVE_ON_BAT=1

# Kernel NMI Watchdog:
#   0=disable (default, saves power), 1=enable (for kernel debugging only).
# Default: 0

#NMI_WATCHDOG=0

# Change CPU voltages aka "undervolting" - Kernel with PHC patch required.
# Frequency voltage pairs are written to:
#   /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
# CAUTION: only use this, if you thoroughly understand what you are doing!
# Default: <none>.

#PHC_CONTROLS="F:V F:V F:V F:V"

# Disk devices; separate multiple devices with spaces.
# Devices can be specified by disk ID also (lookup with: tlp diskid).
# Note: DISK parameters below are effective only when this option is configured.
# Default: "nvme0n1 sda"

#DISK_DEVICES="nvme0n1 sda"

# Disk advanced power management level: 1..254, 255 (max saving, min, off).
# Levels 1..127 may spin down the disk; 255 allowable on most drives.
# Separate values for multiple disks with spaces. Use the special value 'keep'
# to keep the hardware default for the particular disk.
# Default: 254 (AC), 128 (BAT)

#DISK_APM_LEVEL_ON_AC="254 254"
#DISK_APM_LEVEL_ON_BAT="128 128"

# Hard disk spin down timeout:
#   0:        spin down disabled
#   1..240:   timeouts from 5s to 20min (in units of 5s)
#   241..251: timeouts from 30min to 5.5 hours (in units of 30min)
# See 'man hdparm' for details.
# Separate values for multiple disks with spaces. Use the special value 'keep'
# to keep the hardware default for the particular disk.
# Default: <none>

#DISK_SPINDOWN_TIMEOUT_ON_AC="0 0"
#DISK_SPINDOWN_TIMEOUT_ON_BAT="0 0"

# Select I/O scheduler for the disk devices.
# Multi queue (blk-mq) schedulers:
#   mq-deadline(*), none, kyber, bfq
# Single queue schedulers:
#   deadline(*), cfq, bfq, noop
# (*) recommended.
# Separate values for multiple disks with spaces. Use the special value 'keep'
# to keep the kernel default scheduler for the particular disk.
# Notes:
# - Multi queue (blk-mq) may need kernel boot option 'scsi_mod.use_blk_mq=1'
#   and 'modprobe mq-deadline-iosched|kyber|bfq' on kernels < 5.0
# - Single queue schedulers are legacy now and were removed together with
#   the old block layer in kernel 5.0
# Default: keep

#DISK_IOSCHED="mq-deadline mq-deadline"

# AHCI link power management (ALPM) for disk devices:
#   min_power, med_power_with_dipm(*), medium_power, max_performance.
# (*) Kernel >= 4.15 required, then recommended.
# Multiple values separated with spaces are tried sequentially until success.
# Default:
#  - "med_power_with_dipm max_performance" (AC)
#  - "med_power_with_dipm min_power" (BAT)

#SATA_LINKPWR_ON_AC="med_power_with_dipm max_performance"
#SATA_LINKPWR_ON_BAT="med_power_with_dipm min_power"

# Exclude host devices from AHCI link power management.
# Separate multiple hosts with spaces.
# Default: <none>

#SATA_LINKPWR_BLACKLIST="host1"

# Runtime Power Management for AHCI host and disks devices:
#   on=disable, auto=enable.
# EXPERIMENTAL ** WARNING: auto may cause system lockups/data loss.
# Default: <none>

#AHCI_RUNTIME_PM_ON_AC=on
#AHCI_RUNTIME_PM_ON_BAT=on

# Seconds of inactivity before disk is suspended.
# Note: effective only when AHCI_RUNTIME_PM_ON_AC/BAT is activated.
# Default: 15

#AHCI_RUNTIME_PM_TIMEOUT=15

# PCI Express Active State Power Management (PCIe ASPM):
#   default(*), performance, powersave, powersupersave.
# (*) keeps BIOS ASPM defaults (recommended)
# Default: <none>

#PCIE_ASPM_ON_AC=default
#PCIE_ASPM_ON_BAT=default

# Set the min/max/turbo frequency for the Intel GPU.
# Possible values depend on your hardware. For available frequencies see
# the output of tlp-stat -g.
# Default: <none>

#INTEL_GPU_MIN_FREQ_ON_AC=0
#INTEL_GPU_MIN_FREQ_ON_BAT=0
#INTEL_GPU_MAX_FREQ_ON_AC=0
#INTEL_GPU_MAX_FREQ_ON_BAT=0
#INTEL_GPU_BOOST_FREQ_ON_AC=0
#INTEL_GPU_BOOST_FREQ_ON_BAT=0

# Radeon graphics clock speed (profile method): low, mid, high, auto, default;
# auto = mid on BAT, high on AC.
# Default: default

#RADEON_POWER_PROFILE_ON_AC=default
#RADEON_POWER_PROFILE_ON_BAT=default

# Radeon dynamic power management method (DPM): battery, performance.
# Default: <none>

#RADEON_DPM_STATE_ON_AC=performance
#RADEON_DPM_STATE_ON_BAT=battery

# Radeon DPM performance level: auto, low, high; auto is recommended.
# Note: effective only when RADEON_DPM_STATE_ON_AC/BAT is activated.
# Default: auto

#RADEON_DPM_PERF_LEVEL_ON_AC=auto
#RADEON_DPM_PERF_LEVEL_ON_BAT=auto

# WiFi power saving mode: on=enable, off=disable; not supported by all adapters.
# Default: off (AC), on (BAT)

#WIFI_PWR_ON_AC=off
#WIFI_PWR_ON_BAT=on

# Disable wake on LAN: Y/N.
# Default: Y

#WOL_DISABLE=Y

# Enable audio power saving for Intel HDA, AC97 devices (timeout in secs).
# A value of 0 disables, >=1 enables power saving (recommended: 1).
# Default: 0 (AC), 1 (BAT)

#SOUND_POWER_SAVE_ON_AC=0
#SOUND_POWER_SAVE_ON_BAT=1

# Disable controller too (HDA only): Y/N.
# Note: effective only when SOUND_POWER_SAVE_ON_AC/BAT is activated.
# Default: Y

#SOUND_POWER_SAVE_CONTROLLER=Y

# Power off optical drive in UltraBay/MediaBay: 0=disable, 1=enable.
# Drive can be powered on again by releasing (and reinserting) the eject lever
# or by pressing the disc eject button on newer models.
# Note: an UltraBay/MediaBay hard disk is never powered off.
# Default: 0

#BAY_POWEROFF_ON_AC=0
#BAY_POWEROFF_ON_BAT=0

# Optical drive device to power off
# Default: sr0

#BAY_DEVICE="sr0"

# Runtime Power Management for PCI(e) bus devices: on=disable, auto=enable.
# Default: on (AC), auto (BAT)

#RUNTIME_PM_ON_AC=on
#RUNTIME_PM_ON_BAT=auto

# Exclude PCI(e) device adresses the following list from Runtime PM
# (separate with spaces). Use lspci to get the adresses (1st column).
# Default: <none>

#RUNTIME_PM_BLACKLIST="bb:dd.f 11:22.3 44:55.6"

# Exclude PCI(e) devices assigned to the listed drivers from Runtime PM.
# Default when unconfigured is "amdgpu nouveau nvidia radeon" which
# prevents accidential power-on of dGPU in hybrid graphics setups.
# Separate multiple drivers with spaces.
# Default: "amdgpu mei_me nouveau nvidia pcieport radeon", use "" to disable
# completely.

#RUNTIME_PM_DRIVER_BLACKLIST="amdgpu mei_me nouveau nvidia pcieport radeon"

# Set to 0 to disable, 1 to enable USB autosuspend feature.
# Default: 1

#USB_AUTOSUSPEND=1

# Exclude listed devices from USB autosuspend (separate with spaces).
# Use lsusb to get the ids.
# Note: input devices (usbhid) are excluded automatically
# Default: <none>

#USB_BLACKLIST="1111:2222 3333:4444"

# Bluetooth devices are excluded from USB autosuspend:
#   0=do not exclude, 1=exclude.
# Default: 0

#USB_BLACKLIST_BTUSB=0

# Phone devices are excluded from USB autosuspend:
#   0=do not exclude, 1=exclude (enable charging).
# Default: 0

#USB_BLACKLIST_PHONE=0

# Printers are excluded from USB autosuspend:
#   0=do not exclude, 1=exclude.
# Default: 1

#USB_BLACKLIST_PRINTER=1

# WWAN devices are excluded from USB autosuspend:
#   0=do not exclude, 1=exclude.
# Default: 0

#USB_BLACKLIST_WWAN=0

# Include listed devices into USB autosuspend even if already excluded
# by the blacklists above (separate with spaces). Use lsusb to get the ids.
# Default: <none>

#USB_WHITELIST="1111:2222 3333:4444"

# Set to 1 to disable autosuspend before shutdown, 0 to do nothing
# Note: use as a workaround for USB devices that cause shutdown problems.
# Default: 0

#USB_AUTOSUSPEND_DISABLE_ON_SHUTDOWN=0

# Restore radio device state (Bluetooth, WiFi, WWAN) from previous shutdown
# on system startup: 0=disable, 1=enable.
# Note: the parameters DEVICES_TO_DISABLE/ENABLE_ON_STARTUP/SHUTDOWN below
#   are ignored when this is enabled.
# Default: 0

#RESTORE_DEVICE_STATE_ON_STARTUP=0

# Radio devices to disable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
# Default: <none>

#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"

# Radio devices to enable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
# Default: <none>

#DEVICES_TO_ENABLE_ON_STARTUP="wifi"

# Radio devices to disable on shutdown: bluetooth, wifi, wwan.
# Note: use as a workaround for devices that are blocking shutdown.
# Default: <none>

#DEVICES_TO_DISABLE_ON_SHUTDOWN="bluetooth wifi wwan"

# Radio devices to enable on shutdown: bluetooth, wifi, wwan.
# (to prevent other operating systems from missing radios).
# Default: <none>

#DEVICES_TO_ENABLE_ON_SHUTDOWN="wwan"

# Radio devices to enable on AC: bluetooth, wifi, wwan.
# Default: <none>

#DEVICES_TO_ENABLE_ON_AC="bluetooth wifi wwan"

# Radio devices to disable on battery: bluetooth, wifi, wwan.
# Default: <none>

#DEVICES_TO_DISABLE_ON_BAT="bluetooth wifi wwan"

# Radio devices to disable on battery when not in use (not connected):
#   bluetooth, wifi, wwan.
# Default: <none>

#DEVICES_TO_DISABLE_ON_BAT_NOT_IN_USE="bluetooth wifi wwan"

# Battery charge thresholds (ThinkPad only).
# May require external kernel module(s), refer to the output of tlp-stat -b.
# Charging starts when the remaining capacity falls below the
# START_CHARGE_THRESH value and stops when exceeding the STOP_CHARGE_THRESH
# value.

# Main / Internal battery (values in %)
# Default: <none>

#START_CHARGE_THRESH_BAT0=75
#STOP_CHARGE_THRESH_BAT0=80

# Ultrabay / Slice / Replaceable battery (values in %)
# Default: <none>

#START_CHARGE_THRESH_BAT1=75
#STOP_CHARGE_THRESH_BAT1=80

# Restore charge thresholds when AC is unplugged: 0=disable, 1=enable.
# Default: 0

#RESTORE_THRESHOLDS_ON_BAT=1

# Battery feature drivers: 0=disable, 1=enable
# Default: 1 (all)

#NATACPI_ENABLE=1
#TPACPI_ENABLE=1
#TPSMAPI_ENABLE=1

# ------------------------------------------------------------------------------
# tlp-rdw - Parameters for the radio device wizard

# Possible devices: bluetooth, wifi, wwan.
# Separate multiple radio devices with spaces.
# Default: <none> (for all parameters below)

# Radio devices to disable on connect.

#DEVICES_TO_DISABLE_ON_LAN_CONNECT="wifi wwan"
#DEVICES_TO_DISABLE_ON_WIFI_CONNECT="wwan"
#DEVICES_TO_DISABLE_ON_WWAN_CONNECT="wifi"

# Radio devices to enable on disconnect.

#DEVICES_TO_ENABLE_ON_LAN_DISCONNECT="wifi wwan"
#DEVICES_TO_ENABLE_ON_WIFI_DISCONNECT=""
#DEVICES_TO_ENABLE_ON_WWAN_DISCONNECT=""

# Radio devices to enable/disable when docked.

#DEVICES_TO_ENABLE_ON_DOCK=""
#DEVICES_TO_DISABLE_ON_DOCK=""

# Radio devices to enable/disable when undocked.

#DEVICES_TO_ENABLE_ON_UNDOCK="wifi"
#DEVICES_TO_DISABLE_ON_UNDOCK=""

Offline

#7 2020-05-03 14:26:21

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,104

Re: [SOLVED] ACPI errors during BIOS boot time

No relocated sectors or general errors so from that aspect it doesn't look too bad, to test the SATA theory uncomment the SATA_LINKPWR_ON_{AC,BAT} options and have them only read "max_performance"

Offline

#8 2020-05-03 14:36:23

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: [SOLVED] ACPI errors during BIOS boot time

OP wrote:

Sometimes my laptop freezes during BIOS boot up time

If the system indeed freezes during the BIOS phase, there might be a problem with the power supply or seating (no cables :-( ) of the drive.
Does this happen on battery *and* AC?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2020-05-03 15:54:00

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

Re: [SOLVED] ACPI errors during BIOS boot time

V1del wrote:

No relocated sectors or general errors

It has been about three times already when my drive stopped responding during work and I couldn't access or write any files so the only option was to reboot. After rebooting the default file system check failed so I had to enter emergency root mode and run fsck manually answering 'yes' to every prompt. Having done that I was finally able to boot into my home directory. However the last time two days ago the fsck output was completely enormous filled with the same two or three messages. I couldn't grasp what was happening as the text on the screen was moving so quickly and fsck eventually failed. I had to run it several times to make it work. What I'm trying to say is that it's possible that relocated sectors and other errors could have been present in the past but I fixed them with fsck. Of course, if I get the idea how this works right. As I've said, I'm not an experienced user when it comes to hardware and usually just stick to the wiki.

V1del wrote:

to test the SATA theory uncomment the SATA_LINKPWR_ON_{AC,BAT} options and have them only read "max_performance"

Thanks for the suggestion. I will try it as soon as my files finish copying to an external drive. I presume I will get your idea worked if the ata1 startup messages are gone?

Offline

#10 2020-05-03 15:57:02

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

Re: [SOLVED] ACPI errors during BIOS boot time

seth wrote:
OP wrote:

Sometimes my laptop freezes during BIOS boot up time

If the system indeed freezes during the BIOS phase, there might be a problem with the power supply or seating (no cables :-( ) of the drive.
Does this happen on battery *and* AC?

It only happened when I was at home so the laptop was on power supply. I will check if the errors persist on battery. Thanks for the idea.

Offline

#11 2020-05-03 16:02:08

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: [SOLVED] ACPI errors during BIOS boot time

dr3amyxen0 wrote:

My BIOS indeed is really old. The thread you've linked suggests I extract .bin files from the official .exe file however it cannot be opened as an archive. I will try to research the subject more as I've been advised against updating BIOS on Linux machines.

You won't be updating the bios under a running linux o/s if that's what you mean - you will do so using hp's own internal bios upgrade mechanism that is built into the bios itself by going into bios and selecting "upgrade bios from local media": this method is o/s independent. It's this method that is explained on the link I posted.

Did you try file-roller on the exe file? 7z might also be able to extract the exe file if file-roller doesn't work.

Edit: re your smart output: a good drive wouldn't usually have all of those error blocks that start with the line...

Error 1070 occurred at disk power-on lifetime: 8645 hours (360 days + 5 hours)

Which appears to be related to this value in the smart output (which I wouldn't like to see if it was my drive)...
"199 UDMA_CRC_Error_Count" = 1070

Last edited by paulkerry (2020-05-03 16:15:21)

Offline

#12 2020-05-03 16:31:01

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOLVED] ACPI errors during BIOS boot time

About that line from the smartctl output:

199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       1070

That "1070" at the end of the line is the amount of times that this "UDMA_CRC_Error_Count" event happened over the life of the drive. Perhaps start saving the output of "smartctl -A /dev/sda" in a file regularly so that you can in the future compare how that number develops over time.

When I had that particular UDMA_CRC_Error_Count event happening on a desktop PC in the past, the reason was a bad SATA data cable. The count stopped increasing after changing the cable. You can't swap cables in a laptop, but maybe something simple like removing the drive once and putting it back could help? I'd try cleaning the contacts on the SATA connector of the driver carefully, like spray it with an electrical contact cleaner product or something.

Last edited by Ropid (2020-05-03 16:32:09)

Offline

#13 2020-05-03 16:47:58

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

Re: [SOLVED] ACPI errors during BIOS boot time

Ropid wrote:

When I had that particular UDMA_CRC_Error_Count event happening on a desktop PC in the past, the reason was a bad SATA data cable. The count stopped increasing after changing the cable. You can't swap cables in a laptop, but maybe something simple like removing the drive once and putting it back could help? I'd try cleaning the contacts on the SATA connector of the driver carefully, like spray it with an electrical contact cleaner product or something.

My laptop HDD bay doesn't have a caddy inside so it's a little bit loose there. SATA connector indeed could be the case. Thanks for the tip.

Offline

#14 2020-05-03 16:52:44

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

Re: [SOLVED] ACPI errors during BIOS boot time

paulkerry wrote:

You won't be updating the bios under a running linux o/s if that's what you mean - you will do so using hp's own internal bios upgrade mechanism that is built into the bios itself by going into bios and selecting "upgrade bios from local media": this method is o/s independent. It's this method that is explained on the link I posted.

Did you try file-roller on the exe file? 7z might also be able to extract the exe file if file-roller doesn't work.

Yeah, I got it right from the link you had posted, I just couldn't extract the .exe file using 7z so I decided to put it off. File-roller did the trick, so thanks for that.

Offline

#15 2020-05-03 18:57:11

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: [SOLVED] ACPI errors during BIOS boot time

dr3amyxen0 wrote:

My laptop HDD bay doesn't have a caddy inside so it's a little bit loose there. SATA connector indeed could be the case.

seth previsously wrote:

seating (no cables :-( ) of the drive

"It's always the cables" smile
So really check there.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2020-05-07 00:07:08

dr3amyxen0
Member
Registered: 2018-02-21
Posts: 21

Re: [SOLVED] ACPI errors during BIOS boot time

I will mark the thread solved. I will post an update if something changes in case someone will search for this thread in the future. Thanks everyone who helped me figure this out.

Offline

Pages: 1

Board footer

Powered by FluxBB