Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #194640 > unrolled thread

ACPI Error on boot

Back to article view | Back to linux.debian.user

Contents

  ACPI Error on boot Anil Duggirala <anilduggirala@fastmail.fm> - 2018-04-09 19:00 +0200
    Re: ACPI Error on boot Anil Duggirala <anilduggirala@fastmail.fm> - 2018-04-12 15:20 +0200
      Re: ACPI Error on boot <tomas@tuxteam.de> - 2018-04-12 15:40 +0200
        Re: ACPI Error on boot Anil Duggirala <anilduggirala@fastmail.fm> - 2018-04-12 18:50 +0200
          Re: ACPI Error on boot Michael Lange <klappnase@freenet.de> - 2018-04-12 19:00 +0200
            Re: ACPI Error on boot Anil Duggirala <anilduggirala@fastmail.fm> - 2018-04-12 20:00 +0200
      Re: ACPI Error on boot Henrique de Moraes Holschuh <hmh@debian.org> - 2018-04-12 16:00 +0200
        Re: ACPI Error on boot Anil Duggirala <anilduggirala@fastmail.fm> - 2018-04-12 18:50 +0200
          Re: ACPI Error on boot <tomas@tuxteam.de> - 2018-04-12 23:50 +0200
            Re: ACPI Error on boot Felix Miata <mrmazda@earthlink.net> - 2018-04-13 00:20 +0200
          Re: ACPI Error on boot Henrique de Moraes Holschuh <hmh@debian.org> - 2018-04-13 02:40 +0200
      Re: ACPI Error on boot songbird <songbird@anthive.com> - 2018-04-12 17:00 +0200
        Re: ACPI Error on boot Anil Duggirala <anilduggirala@fastmail.fm> - 2018-04-12 18:50 +0200
          Re: ACPI Error on boot deloptes <deloptes@gmail.com> - 2018-04-12 20:50 +0200

#194640 — ACPI Error on boot

hello, 
I am getting an error on boot in my dual boot Win 10-Debian 9 system, 
ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/exmutex-393)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff9346529f5960), AE_AML_MUTEX_NOT_ACQUIRED (20160831/psparse-543)
Could someone tell me what this error means,
thanks a lot,

Anil

[toc] | [next] | [standalone]

#194721

On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote:
> hello, 
> I am getting an error on boot in my dual boot Win 10-Debian 9 system, 
> ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/
> exmutex-393)
> ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] 
> (Node ffff9346529f5960), AE_AML_MUTEX_NOT_ACQUIRED (20160831/
> psparse-543)
> Could someone tell me what this error means,
> thanks a lot,
> 
> Anil
> 

Can someone please help me out, or let me know why Im not getting any help with this,
thanks,

[toc] | [prev] | [next] | [standalone]

#194722

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Apr 12, 2018 at 08:09:08AM -0500, Anil Duggirala wrote:
> On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote:
> > hello, 
> > I am getting an error on boot in my dual boot Win 10-Debian 9 system, 
> > ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/
> > exmutex-393)
> > ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] 
> > (Node ffff9346529f5960), AE_AML_MUTEX_NOT_ACQUIRED (20160831/
> > psparse-543)
> > Could someone tell me what this error means,
> > thanks a lot,
> > 
> > Anil
> > 
> 
> Can someone please help me out, or let me know why Im not getting any help with this,
> thanks,

I did some search engine gymnastics, and it doesn't seem clear
what that message means at all.

Is there any negative effect on your boot you link to this
message?

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlrPX8cACgkQBcgs9XrR2kZfrwCfYuSroCOQFUTFoL0za7ZVH9rU
ezAAn3oHXZF8FxuqgHGh998zEbw6Ic19
=ruXl
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#194729

On Thu, Apr 12, 2018, at 8:31 AM, tomas@tuxteam.de wrote:
 
> Is there any negative effect on your boot you link to this
> message?
> 

I do not understand the wording of this question, could you please rephrase it?
I did not link anything to my O post. The only negative effect I see is the error message.

thanks Tomas

[toc] | [prev] | [next] | [standalone]

#194732

On Thu, 12 Apr 2018 11:40:15 -0500
Anil Duggirala <anilduggirala@fastmail.fm> wrote:

> On Thu, Apr 12, 2018, at 8:31 AM, tomas@tuxteam.de wrote:
>  
> > Is there any negative effect on your boot you link to this
> > message?
> > 
> 
> I do not understand the wording of this question, could you please
> rephrase it? I did not link anything to my O post. The only negative
> effect I see is the error message.

I think what he means could be said in other words for example like "Is
there any negative effect when the machine boots that you believe is
related to this error message?"

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Pain is a thing of the mind.  The mind can be controlled.
		-- Spock, "Operation -- Annihilate!" stardate 3287.2

[toc] | [prev] | [next] | [standalone]

#194733

> I think what he means could be said in other words for example like "Is
> there any negative effect when the machine boots that you believe is
> related to this error message?"
> 

I am also getting notices of missing firmware,
that is the only other thing I have noticed,
thanks,

[toc] | [prev] | [next] | [standalone]

#194723

On Thu, 12 Apr 2018, Anil Duggirala wrote:
> On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote:
> > I am getting an error on boot in my dual boot Win 10-Debian 9 system, 

> > ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/
> > exmutex-393)
> > ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] 
> > (Node ffff9346529f5960), AE_AML_MUTEX_NOT_ACQUIRED (20160831/
> > psparse-543)
> > Could someone tell me what this error means,

Assuming the kernel is not broken, it means that the firmware writers
screwed it up, and are trying to release a lock (mutex) that was not
taken.

I.e. it is reporting a "BIOS bug".

You could try to report to the system vendor, and ask them for a fix.

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#194730

> Assuming the kernel is not broken, it means that the firmware writers
> screwed it up, and are trying to release a lock (mutex) that was not
> taken.
> 

I am also getting missing firmware notices, namely,
[    9.269384] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:03:00.0.bin (-2)
[    9.269386] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2
[    9.269403] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/cal-pci-0000:03:00.0.bin (-2)
[    9.269404] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[    9.311104] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
[    9.311107] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[    9.311113] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2

Could the other ACPI Errors be related to this missing firmware?
Do you also recommend updating my BIOS?

thanks,

[toc] | [prev] | [next] | [standalone]

#194738

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Apr 12, 2018 at 11:43:09AM -0500, Anil Duggirala wrote:
> > Assuming the kernel is not broken, it means that the firmware writers
> > screwed it up, and are trying to release a lock (mutex) that was not
> > taken.
> > 
> 
> I am also getting missing firmware notices, namely,
> [    9.269384] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:03:00.0.bin (-2)
> [    9.269386] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2
> [    9.269403] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/cal-pci-0000:03:00.0.bin (-2)
> [    9.269404] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [    9.311104] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
> [    9.311107] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
> [    9.311113] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
> 
> Could the other ACPI Errors be related to this missing firmware?

As deloptes said, this is not related: the "missing firmware" notice
means that the operating system has detected a hardware (ath10k, that's
the WiFi) which could use some firmware (but perhaps works fine without).

The firmware itself is non-free, that's why it is in a separate package.
I think deloptes already said how to find/install it.

> Do you also recommend updating my BIOS?

I don't know. There are others around here with more experience in
that than me.

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlrP0vcACgkQBcgs9XrR2kbVMQCfXL9z/BcTMSjVbq+q2AFj66FS
BMEAn0FvqWxeNVJvykvJ0f7zudq9/h2Q
=XRoa
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#194739

tomas@tuxteam.de composed on 2018-04-12 23:43 (UTC+0200):

> On Thu, Apr 12, 2018 at 11:43:09AM -0500, Anil Duggirala wrote:

>> Do you also recommend updating my BIOS?

> I don't know. There are others around here with more experience in
> that than me.

IME, a BIOS update is usually the only way to make ACPI "errors" go away,
although it often seems to be the case that the errors reported are themselves
erroneous, log noise rather than real trouble.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#194741

On Thu, 12 Apr 2018, Anil Duggirala wrote:
> I am also getting missing firmware notices, namely,
> [    9.269384] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:03:00.0.bin (-2)
> [    9.269386] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2
> [    9.269403] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/cal-pci-0000:03:00.0.bin (-2)
> [    9.269404] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [    9.311104] ath10k_pci 0000:03:00.0: firmware: failed to load ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
> [    9.311107] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
> [    9.311113] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
> 
> Could the other ACPI Errors be related to this missing firmware?

No.  And in the specific case of ath10k, which actually searches for
firmware in descending preference order, it is sort of normal to get
these annoying logs even if you have the correct firmware package
installed.  It is being addressed on a future kernel so that such
searches can be made silent.

> Do you also recommend updating my BIOS?

Keep that thing up-to-date, maybe with an one-month delay to let the
vendor recall bad updates (they are rare, but it has happened to some),
or looking around at forums to see if anyone is complaining of issues
before you apply the update.

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#194727

Anil Duggirala wrote:
...
> Can someone please help me out, or let me know why Im not getting any help with this,

  lack of details about machine, debian versions, 
things tried, etc, and for me being busy with 
other things for a while to even begin to look 
at this message to begin with.

  so, um, hey, sometimes takes time for people to see
and digest and think about and maybe won't ever get an
answer.  just the way it can go at times.  :)

  have you updated BIOS to latest version from machine
vendor?


  songbird

[toc] | [prev] | [next] | [standalone]

#194731

>   have you updated BIOS to latest version from machine
> vendor?
> 

I have not, I will see if there is a newer version. I am running Debian Stretch on a Dell 3580 Latitude machine. I have not tried anything so far to fix this error,
thanks a lot,

[toc] | [prev] | [next] | [standalone]

#194735

Anil Duggirala wrote:

>>   have you updated BIOS to latest version from machine
>> vendor?
>> 
> 
> I have not, I will see if there is a newer version. I am running Debian
> Stretch on a Dell 3580 Latitude machine. I have not tried anything so far
> to fix this error, thanks a lot,

what is referred here as firmware is the bios of the computer - upgrade.

the missing atheros firmware is not related to the ACPI error - you can
install the missing firmware either via debian package or from the vendor.
install:

$ apt-cache search firmware-atheros
firmware-atheros - Binary firmware for Atheros wireless cards

regards

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web