On Thu, 12 Apr 2018, Anil Duggirala wrote:
> I am also getting missing firmware notices, namely,
> [9.269384] ath10k_pci :03:00.0: firmware: failed to load
> ath10k/pre-cal-pci-:03:00.0.bin (-2)
> [9.269386] ath10k_pci :03:00.0: Direct firmware load for
> ath10k/pre-cal-pci-00
to...@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
-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 mi
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 referr
> 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,
On Thu, 12 Apr 2018 11:40:15 -0500
Anil Duggirala wrote:
> On Thu, Apr 12, 2018, at 8:31 AM, to...@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 no
> 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,
> 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 :03:00.0: firmware: failed to load
ath10k/pre-cal-pci-:0
On Thu, Apr 12, 2018, at 8:31 AM, to...@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
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.
s
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/executi
-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]
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]
> (Nod
13 matches
Mail list logo
