You are not logged in.

#1 2019-04-02 10:58:07

Soptik
Member
Registered: 2019-03-11
Posts: 64

Playing Skyrim on battery causes ACPI Error and reboots computer

Hi,

yesterday, I downloaded Skyrim and played it (laptop was plugged in). I played it for like 40 minutes without issues.

Today, I started it, but laptop was not plugged in - it was running on battery. Like 5 seconds after loading the game, I encountered sudden FPS drop for about half a second and than my computer rebooted.

Here is suspicious journalctl I found (colored red):

# journalctl -b

Apr 02 12:43:41 arstotzka kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Apr 02 12:43:41 arstotzka kernel: ACPI: Power Button [PWRF]
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN00._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:00: Failed to change power state to D0
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN00._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:00: Failed to set initial power state
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:00: Cannot transition from (unknown) to D3hot
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN01._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:01: Failed to change power state to D0
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN01._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:01: Failed to set initial power state
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:01: Cannot transition from (unknown) to D3hot
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN02._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:02: Failed to change power state to D0
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN02._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:02: Failed to set initial power state
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:02: Cannot transition from (unknown) to D3hot
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN03._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:03: Failed to change power state to D0
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN03._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:03: Failed to set initial power state
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:03: Cannot transition from (unknown) to D3hot
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN04._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:04: Failed to change power state to D0
Apr 02 12:43:41 arstotzka kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPCB.HEC.ECMD], AE_NOT_FOUND (20181213/psargs-330)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: ACPI Error: Method parse/execution failed \_TZ.FN04._ON, AE_NOT_FOUND (20181213/psparse-531)
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:04: Failed to set initial power state
Apr 02 12:43:41 arstotzka kernel: acpi PNP0C0B:04: Cannot transition from (unknown) to D3hot

Here is full journalctl -b log: https://pastebin.com/DxzgGiRL


$ dmesg -l err
https://pastebin.com/MLm3ps9D

I'll try changing kernel parameter libata.noacpi to 1 and edit if it helped. Edit: it didn't.

Last edited by Soptik (2019-04-02 11:25:21)

Offline

#2 2019-04-02 13:00:17

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,568

Re: Playing Skyrim on battery causes ACPI Error and reboots computer

How old is your battery? Are you using TLP?

Last edited by d_fajardo (2019-04-02 13:03:48)

Offline

#3 2019-04-02 16:06:55

Soptik
Member
Registered: 2019-03-11
Posts: 64

Re: Playing Skyrim on battery causes ACPI Error and reboots computer

I have new laptop, it isn't even a month old. I can get several hours of moderate usage on the battery without problems.

I don't use TLP, but I played with powertop a bit (I just let it run for a while and then let it do all the optimalizations it suggested). I don't know if the powertop configuration broke it, I never played Skyrim before the optimalizations.

Offline

#4 2019-04-02 20:15:59

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,568

Re: Playing Skyrim on battery causes ACPI Error and reboots computer

You have a lot of errors on power state change, setting power state, etc. I would definitely have a look if the problem comes from powertop. Anyway, are you able to recreate the problem or symptom?

Offline

#5 2019-04-03 08:52:24

Soptik
Member
Registered: 2019-03-11
Posts: 64

Re: Playing Skyrim on battery causes ACPI Error and reboots computer

Yes, I recreated the problem like three times, every time I play skyrim on battery my computer reboots.

Would you have a suggestion where to start investigating the problem?

Offline

#6 2019-04-03 08:57:42

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,723

Re: Playing Skyrim on battery causes ACPI Error and reboots computer

As already mentioned, if there are currently any powertop options enabled, disable them.

If that doesn't fix it, it is quite likely that the relevant hardware threshholds are lowered directly from firmware, and running Skyrim causes your system to trigger these. If you think that this should be possible, you might want to look into firmware/UEFI/BIOS updates provided by your vendor.

What exact laptop model is this. Also FWIW since any potential logs during the actual problem will not be included in the journalctl -b output, what do you get for

journalctl -b-1

on the boot after reproduction of a crash?

Last edited by V1del (2019-04-03 09:00:58)

Offline

Board footer

Powered by FluxBB