acpi

[Aleix Piulachs]

i repared acpi writing in /etc/default/grub at line

GRUB_CMDLINE_LINUX_DEFAULT=libata.noacpi=1
and then write
update-grub

acpi

[Aleix Piulachs]

i was able to repair the acpi drivers and i don’t get errors at startup

thermal acpi drivers

[Aleix Piulachs]

My laptop support pwm and starts the fans but when i start the system it
gives me acpi errors that i put below
[ 0.356880] ACPI Error: Needed type [Reference], found [Integer]
(ptrval) (20200925/exresop-66)

[ 0.356951] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands
for [OpcodeName unavailable] (20200925/dswexec-431)

[ 0.357018] ACPI Error: Aborting method \_PR.CPU0._PDC due to previous
error (AE_AML_OPERAND_TYPE) (20200925/psparse-529)
/dev/sda3: clean, 291329/1605184 files, 4074710/66406144 blocks

Fwd: acpi

[Aleix Piulachs]

-- Mensaje reenviado -
De: Aleix Piulachs 
Fecha: El jue, 25 may 2023 a las 21:26
Asunto: Re: acpi
Para: Alex 


these are the startup errors
[0.356880] ACPI Error:Needed type [Reference], found [Integer]
(___ptrval___) (20200925/exresop-66)
[0.356951] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands
for [OpcodeName unavailable] (20200925/dswexec-431)
[0.357018] ACPI Error: Aborting method \_PR.CPU0._PDC due to previous
error (AE_AML_OPERAND_TYPE) (20200925/psparse-529)
/dev/sda3: clean, 291329/16605184 files, 4074710/66406144 blocks

El El jue, 25 may 2023 a las 20:59, Alex  escribió:

> On Thu, 25 May 2023 20:55:02 +0200
> Aleix Piulachs  wrote:
>
> > When i start the computer it gives me acpi errors
>
> What error specifically?
>
> --
> Current PGP KeyID: 0AFB427F1800FD89751C4035292228735AE707FF
>
>
> https://blueselene.com/pgp-archive/0AFB427F1800FD89751C4035292228735AE707FF/key.pub
>

Re: acpi

[Alex]

On Thu, 25 May 2023 20:55:02 +0200
Aleix Piulachs  wrote:

> When i start the computer it gives me acpi errors

What error specifically?

-- 
Current PGP KeyID: 0AFB427F1800FD89751C4035292228735AE707FF

https://blueselene.com/pgp-archive/0AFB427F1800FD89751C4035292228735AE707FF/key.pub


pgpnv6jxyfGEd.pgp
Description: OpenPGP digital signature

acpi

[Aleix Piulachs]

When i start the computer it gives me acpi errors

Re: acpi bios error: could not resolve symbol in Tuxedo Aura 15

[Василий В]

Hello Rainer!
I assume bios just doesn't support some functions that kernel is
trying to query.  You could try to update bios, if possible. But as
you say you don't see any real problems, maybe it's better not to fix
something that is working already. I get similar messages on boot
(Debian Buster), but in fact everything works perfectly.

вс, 27 дек. 2020 г. в 04:48, Rainer Dorsch :
>
> Hi,
>
> I have a Tuxedo Aura 15 and after installing Debian bullseye, I see during
> boot a few
>
> acpi bios error: could not resolve symbol
>
> messages.
>
> See https://nc.d5x.de/s/3BYL8Fg88Xb5GRJ for a "screenshot".
>
> Does anybody understand what these messages want to tell me (so far I did not
> see anything not working).
>
> Any hint is welcome.
>
> Thanks
> Rainer
>
> Full machine data:
>
> rd@aura:~$ inxi -F
> System:Host: aura Kernel: 5.9.0-5-amd64 x86_64 bits: 64 Console: tty 3
> Distro: Debian GNU/Linux bullseye/sid
> Machine:   Type: Laptop System: TUXEDO product: TUXEDO Aura 15 Gen1 v: N/A
> serial: 
>   Mobo: TUXEDO s model: AURA1501 serial:  UEFI:
> INSYDE v: 1.07.03RTR2 date: 11/13/2020
> Battery:   ID-1: BAT0 charge: 20.4 Wh condition: 50.3/48.3 Wh (104%)
> CPU:   Info: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64
> type: MCP L2 cache: 4 MiB
>   Speed: 1398 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1398 2:
> 1396 3: 1397 4: 1397 5: 1401 6: 1399 7: 1397
>   8: 1396
> Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v:
> kernel
>   Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo
>   Display: server: X.org 1.20.10 driver: amdgpu,ati unloaded:
> fbdev,modesetting,vesa tty: 293x80
>   Message: Advanced graphics data unavailable in console. Try -G --
> display
> Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel
>   Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/
> Renoir Audio Processor driver: N/A
>   Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver:
> snd_hda_intel
>   Sound Server: ALSA v: k5.9.0-5-amd64
> Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
> driver: r8169
>   IF: enp2s0 state: down mac: 80:fa:5b:8a:20:da
>   Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi
>   IF: wlo1 state: up mac: 78:2b:46:2a:e2:48
> Drives:Local Storage: total: 465.76 GiB used: 6.07 GiB (1.3%)
>   ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
> size: 465.76 GiB
> Partition: ID-1: / size: 447.02 GiB used: 5.94 GiB (1.3%) fs: btrfs dev: /dev/
> dm-0
>   ID-2: /boot size: 473.5 MiB used: 124.1 MiB (26.2%) fs: ext2 dev: /
> dev/nvme0n1p2
>   ID-3: /boot/efi size: 511 MiB used: 8.4 MiB (1.7%) fs: vfat dev: /
> dev/nvme0n1p1
> Swap:  ID-1: swap-1 type: partition size: 17.73 GiB used: 0 KiB (0.0%)
> dev: /dev/dm-1
> Sensors:   System Temperatures: cpu: 24.1 C mobo: N/A gpu: amdgpu temp: 23.0 C
>   Fan Speeds (RPM): N/A
> Info:  Processes: 283 Uptime: 8h 24m Memory: 30.81 GiB used: 1.35 GiB
> (4.4%) Init: systemd runlevel: 5 Shell: Bash
>   inxi: 3.2.01
> rd@aura:~$
>
>
>
>
> --
> Rainer Dorsch
> http://bokomoko.de/
>
>

acpi bios error: could not resolve symbol in Tuxedo Aura 15

[Rainer Dorsch]

Hi,

I have a Tuxedo Aura 15 and after installing Debian bullseye, I see during 
boot a few

acpi bios error: could not resolve symbol

messages.

See https://nc.d5x.de/s/3BYL8Fg88Xb5GRJ for a "screenshot".

Does anybody understand what these messages want to tell me (so far I did not 
see anything not working).

Any hint is welcome.

Thanks
Rainer

Full machine data:

rd@aura:~$ inxi -F 
System:Host: aura Kernel: 5.9.0-5-amd64 x86_64 bits: 64 Console: tty 3 
Distro: Debian GNU/Linux bullseye/sid  
Machine:   Type: Laptop System: TUXEDO product: TUXEDO Aura 15 Gen1 v: N/A 
serial:   
  Mobo: TUXEDO s model: AURA1501 serial:  UEFI: 
INSYDE v: 1.07.03RTR2 date: 11/13/2020  
Battery:   ID-1: BAT0 charge: 20.4 Wh condition: 50.3/48.3 Wh (104%)  
CPU:   Info: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 
type: MCP L2 cache: 4 MiB  
  Speed: 1398 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1398 2: 
1396 3: 1397 4: 1397 5: 1401 6: 1399 7: 1397  
  8: 1396  
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: 
kernel  
  Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo  
  Display: server: X.org 1.20.10 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa tty: 293x80  
  Message: Advanced graphics data unavailable in console. Try -G --
display  
Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel  
  Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/
Renoir Audio Processor driver: N/A  
  Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: 
snd_hda_intel  
  Sound Server: ALSA v: k5.9.0-5-amd64  
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
driver: r8169  
  IF: enp2s0 state: down mac: 80:fa:5b:8a:20:da  
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi  
  IF: wlo1 state: up mac: 78:2b:46:2a:e2:48  
Drives:Local Storage: total: 465.76 GiB used: 6.07 GiB (1.3%)  
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB 
size: 465.76 GiB  
Partition: ID-1: / size: 447.02 GiB used: 5.94 GiB (1.3%) fs: btrfs dev: /dev/
dm-0  
  ID-2: /boot size: 473.5 MiB used: 124.1 MiB (26.2%) fs: ext2 dev: /
dev/nvme0n1p2  
  ID-3: /boot/efi size: 511 MiB used: 8.4 MiB (1.7%) fs: vfat dev: /
dev/nvme0n1p1  
Swap:  ID-1: swap-1 type: partition size: 17.73 GiB used: 0 KiB (0.0%) 
dev: /dev/dm-1  
Sensors:   System Temperatures: cpu: 24.1 C mobo: N/A gpu: amdgpu temp: 23.0 C  
  Fan Speeds (RPM): N/A  
Info:  Processes: 283 Uptime: 8h 24m Memory: 30.81 GiB used: 1.35 GiB 
(4.4%) Init: systemd runlevel: 5 Shell: Bash  
  inxi: 3.2.01  
rd@aura:~$ 




-- 
Rainer Dorsch
http://bokomoko.de/

Re: Obscure error messages from ACPI BERT in dmesg

[Thomas Schmitt]

Hi,

Semih Ozlem wrote:
> whenever I logon and have more than a few pages in
> firefox open, suddenly my memory usage (memory is 3.7 GiB as displayed by
> ubuntu system monitor) is around 70 and 80 percent. If I open a few more
> pages it jumps. If it reaches 100 % the computer freezes.

Well, yes, if your RAM is full and cannot be outsourced to swap storage
then undesirable things happen.


> I am wondering if
> the issues are at all related, and if you know ways of monitoring the system
> to decide whether it is just an issue of RAM being not powerful enough,

If you see in dmesg output
  [...] BERT: Error records from previous boot:
then maybe this is hardware related too.

But if firefox is just eating up your memory, then only more RAM or more
swap storage can help.
For a quick test, you could create a swap file on disk and try whether
your system gets more endurance.
See e.g.
  https://linuxize.com/post/create-a-linux-swap-file/

If not by some colorful system monitor i would watch the load on RAM
and swap by periodically executing command
  free -h
and ignoring all its columns except the first two: "total" and "used".


But as one can see from my recent posts, i am not an experienced sysadmin
who knows the most thorough hardware tests.


Have a nice day :)

Thomas

Obscure error messages from ACPI BERT in dmesg

[Thomas Schmitt]

Hi,

i don't get to cursing at vim and sshd of Debian 10 because i am still
stuck with hardware issues.

My newest problem is a message at boot time about some problem that was
recorded in the ACPI Boot Error Record Table during the previous uptime.
Google and uefi.org tell me that BERT is a facility where firmware can
store error messages which it deems at risk of being not delivered via
the normal error message channels of a running OS.

[0.006446] ACPI: BERT 0x89F05608 30 (v01 INTEL  EDK2 
0001 INTL 0001)
...
[0.893410] BERT: Error records from previous boot:
[0.893410] [Hardware Error]: event severity: fatal
[0.893411] [Hardware Error]:  Error 0, type: fatal
[0.893412] [Hardware Error]:   section type: unknown, 
81212a96-09ed-4996-9471-8d729c8e69ed
[0.893412] [Hardware Error]:   section length: 0xc20
[0.893413] [Hardware Error]:   : 0001   
  
[0.893414] [Hardware Error]:   0010:    
  
[0.893414] [Hardware Error]:   0020:    
  

... repeated in steps of 0x10 and all words being  until:

[0.893505] [Hardware Error]:   0c10:    
  

Google search of 81212a96-09ed-4996-9471-8d729c8e69ed gives the impression
that it is like plague and cholera united. (Computers freeze or reboot ...)

I do not see such dramatic effects, though.
Meanwhile i outruled that it is the knock-happy HDD (because unplugging it
does not prevent or change the message at next boot) or the missing i915
firmware (i installed it).

In the hope to learn more about that UUID or the format of BERT i even
downloaded
  https://uefi.org/sites/default/files/resources/ACPI_6_2_B_final_Jan30.pdf
But my hope to see UUID lists for error types was disappointed.


Does anybody have an idea how to identify the offending hardware part ?
(I cannot unplug CPU or SSD, of course ...)


Have a nice day :)

Thomas

Re: ACPI Errors

[Jonathan Oshita]

Well that's unfortunate, thanks for the information though.

Regards,
Jonathan

‐‐‐ Original Message ‐‐‐
On Monday, May 11, 2020 1:54 AM, Sven Hartge  wrote:

> Jonathan Oshita jkosh...@protonmail.com wrote:
>
> > I've been having the following error messages about 'ACPI' in my
> > 'kern.log' and haven't been able to figure out how to resolve them.
> > The system boots successfully after displaying the errors, but any
> > error message is usually a concern of mine.
>
> ACPI errors usually can only be solved by a BIOS/firmware update. But
> even then it is more than possible that nothing will change as BIOS
> vendors are notoriously bad at creating correct ACPI tables.
>
> > Is this something I should be worried about?
>
> No.
>
> > Is there any way I can eliminate these errors?
>
> Probably not.
>
> Grüße,
> Sven.
>
> --
>
> Sigmentation fault. Core dumped.

Re: ACPI Errors

[Sven Hartge]

Jonathan Oshita  wrote:


> I've been having the following error messages about 'ACPI' in my
> 'kern.log' and haven't been able to figure out how to resolve them.
> The system boots successfully after displaying the errors, but any
> error message is usually a concern of mine.

ACPI errors usually can only be solved by a BIOS/firmware update. But
even then it is more than possible that nothing will change as BIOS
vendors are notoriously bad at creating correct ACPI tables.

> Is this something I should be worried about? 

No.

> Is there any way I can eliminate these errors?

Probably not.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

ACPI Errors

[Jonathan Oshita]

Hello,

I've been having the following error messages about 'ACPI' in my 'kern.log' and 
haven't been able to figure out how to resolve them. The system boots 
successfully after displaying the errors, but any error message is usually a 
concern of mine.

Is this something I should be worried about? Is there any way I can eliminate 
these errors?

Regards,
Jonathan



System Information (inxi -SMCG):

System:Host: debian-3 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 
4.12.4
   Distro: Debian GNU/Linux 10 (buster)
Machine:   Type: Laptop System: Dell product: G7 7590 v: N/A serial: 
   Mobo: Dell model: 0WJH3G v: A00 serial:  UEFI: Dell 
v: 1.12.0
   date: 02/07/2020
CPU:   Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP
   L2 cache: 12.0 MiB
   Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800
   4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel
   Device-2: NVIDIA TU104M [GeForce RTX 2080 Mobile] driver: nvidia v: 
440.82
   Display: x11 server: X.Org 1.20.4 driver: modesetting,nvidia
   resolution: 1920x1080~144Hz
   OpenGL: renderer: GeForce RTX 2080 with Max-Q Design/PCIe/SSE2
   v: 4.6.0 NVIDIA 440.82


'kern.log' excerpt:

May 10 21:44:50 debian-3 kernel: [0.284974] ACPI: 13 ACPI AML tables 
successfully acquired and loaded
May 10 21:44:50 debian-3 kernel: [0.285835] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.286839] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.292528] ACPI: [Firmware Bug]: BIOS 
_OSI(Linux) query ignored
May 10 21:44:50 debian-3 kernel: [0.299865] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.299869] ACPI: SSDT 0x9A6BEBBBC900 
F4 (v02 PmRef  Cpu0Psd  3000 INTL 20160527)
May 10 21:44:50 debian-3 kernel: [0.300060] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.300140] ACPI: \_SB_.PR00: _OSC native 
thermal LVT Acked
May 10 21:44:50 debian-3 kernel: [0.300735] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.300739] ACPI: SSDT 0x9A6BEBD84800 
00046F (v02 PmRef  Cpu0Cst  3001 INTL 20160527)
May 10 21:44:50 debian-3 kernel: [0.300930] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.301076] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.301079] ACPI: SSDT 0x9A6BEBD86800 
000581 (v02 PmRef  Cpu0Ist  3000 INTL 20160527)
May 10 21:44:50 debian-3 kernel: [0.301312] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.301446] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.301449] ACPI: SSDT 0x9A6BEBBB9600 
00011B (v02 PmRef  Cpu0Hwp  3000 INTL 20160527)
May 10 21:44:50 debian-3 kernel: [0.301620] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.301717] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.301720] ACPI: SSDT 0x9A6BEBD81000 
000724 (v02 PmRef  HwpLvt   3000 INTL 20160527)
May 10 21:44:50 debian-3 kernel: [0.301883] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.302160] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.302163] ACPI: SSDT 0x9A6BEBD83800 
0005FC (v02 PmRef  ApIst3000 INTL 20160527)
May 10 21:44:50 debian-3 kernel: [0.302396] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.302527] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.302529] ACPI: SSDT 0x9A6BEBBC6000 
000317 (v02 PmRef  ApHwp3000 INTL 20160527)
May 10 21:44:50 debian-3 kernel: [0.302721] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.302903] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.302907] ACPI: SSDT 0x9A6BEBDD6000 
000AB0 (v02 PmRef  ApPsd3000 INTL 20160527)
May 10 21:44:50 debian-3 kernel: [0.303405] ACPI Error: No pointer back to 
namespace node in package ba9e0ff5 (20180810/dsargs-303)
May 10 21:44:50 debian-3 kernel: [0.303543] ACPI: Dynamic OEM Table Load:
May 10 21:44:50 debian-3 kernel: [0.303546] ACPI: SSDT 0x9A6BEBBC3000 
00030A (v02 PmRef  ApCst

Erreur ACPI avec une radeon sur un PC Intel

[Eric Heintzmann]

Bonjour à tous,


PC SOUS DEBIAN TESTING

Je possède un ordinateur portable HP Pavilion 17-e050sf sous Debian 
testing :

https://support.hp.com/fr-fr/document/c03817695
C'est un système à cartes graphiques hybrides Intel / AMD,
avec pilote "i915" pour la carte intégrée, et pilote "radeon" pour la 
carte additionnelle AMD (alternativement le pilote "amdgpu" peut-être 
utilisé pour la carte AMD)



$ lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM 
Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core 
processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family 
High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI 
Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 2 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 3 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC 
Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 
6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus 
Controller (rev 04)
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun 
XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile]
07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE 
Wireless Network Adapter (rev 01)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE 
PCI Express Fast Ethernet controller (rev 07)



LE PROBLEME

Le problème c'est que lorsque je démarre l'ordinateur, tout ce passe 
normalement jusqu'à l'invite GDM.
Mais lorsque je me connecte (via GDM) avec mon nom d'utilisateur et mon 
mot de passe, il y a presque une minute de latence avant que GNOME se 
lance. C'est cela le problème.(J'ai aussi testé xfce, enlightment, GNOME 
sous Xorg...sans plus de succès)
(Notez bien que le problème ne se produit qu'après un reboot ou 
démarrage à froid, mais pas après une fermeture de session)
Après de nombreux test j'ai constaté que blacklister le module "radeon" 
résolvait le problème ... au prix de la désactivation de la radeon.
(Alternativement booter avec le parametre kernel "radeon.modeset=0" 
résoud aussi le problème de la même manière)


Après lecture des logs il semble qu'il y ait des erreurs ACPI lors de du 
chargement ou du déchargement du driver de la carte graphique 
additionnelle AMD :


$ modprobe -r radeon
...
[  134.810044] ACPI Error: Aborting method \AMD3._ON due to previous 
error (AE_AML_LOOP_TIMEOUT) (20191018/psparse-529)

...
[  134.811473] acpi device:02: Failed to change power state to D0
...


$ modprobe radeon
...
[  382.899240] acpi device:02: Failed to change power state to D0
...
[  389.158051] acpi device:02: Cannot transition from (unknown) to D3hot
...

On pourrait penser que le problème est dû au driver radeon,
mais en fait j'ai exactement les mêmes messages d'erreur avec les 
drivers "amdgpu" (avec le support activé pour les cartes "si" et "cik" )


Tentative d'analyse

D'après :

$ ls -al /sys/bus/acpi/devices/device\:02/physical_node
lrwxrwxrwx 1 root root 0 avril 16 12:57 
/sys/bus/acpi/devices/device:02/physical_node -> 
../../../../pci:00/:00:01.0


et

$ lspci -s :00:01.0
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])

    Flags: bus master, fast devsel, latency 0, IRQ 24
    Bus: primary=00, secondary=01, subordinate=06, sec-latency=0
    I/O behind bridge: 5000-5fff [size=4K]
    Memory behind bridge: c200-c2ff [size=16M]
    Prefetchable memory behind bridge: 
a000-afff [size=256M]
    Capabilities: [88] Subsystem: Hewlett-Packard Company Xeon E3-1200 
v2/3rd Gen Core processor PCI Express Root Port

    Capabilities: [80] Power Management version 3
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [a0] Express Root Port (Slot+), MSI 00
    Capabilities: [100] Virtual Channel
    Capabilities: [140] Root Complex Link
    Capabilities: [d94] Secondary PCI Express
    Kernel driver in use: pcieport

Donc l'acpi dev

Re: Question regarding an ACPI BIOS Error (bug)

[didier gaumet]

fwupd is worth noting: https://en.wikipedia.org/wiki/Fwupd
and not only does it manage PC firmwares (UEFI) but peripheral cards
firmwares  too

but it is far from widely adopted :-(

Re: Question regarding an ACPI BIOS Error (bug)

[Andrei POPESCU]

On Sb, 28 mar 20, 14:40:54, G.W. Haywood wrote:
> 
> Perhaps you should read
> 
> https://www.debian.org/doc/manuals/debian-faq/choosing.en.html#s3.1
> 
> but do please note that this document is out of date - it refers to
> "Stretch" as the stable distribution, instead of "Buster", which has
> been the stable distribustion since July 6th 2019.

If it's just the name of the stable distribution it doesn't matter, the 
general principle is still the same.

Anyway, if you find anything outdated/wrong/missing you could report a 
bug against the 'debian-faq' package. Ideally with a patch ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Question regarding an ACPI BIOS Error (bug)

[G.W. Haywood]

Hi there,

On Sat, 28 Mar 2020, rba777 wrote:


...
[    0.457794] ACPI BIOS Error (bug): Failure creating named object 
[\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
[    0.457802] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190816/psobject-220)
...
Using apt and apt-file, I found numerous packages related to ACPI


Yes, that's to be expected. :)

It's also expected that, at startup, there will be messages logged
about workarounds for known bugs in computer firmware (e.g. BIOS).
Most of the time these messages are benign, and need no action to be
taken by you.  Apart from the existence of these error messages, do
you know that there is some sort of a problem related to the messages?


... I'm running a Debian testing ...


Under most circumstances I advise a stable version, since if you use
other versions then you can almost expect to run into problems, and
you are almost expected to be able to cope with them by yourself.

Perhaps you should read

https://www.debian.org/doc/manuals/debian-faq/choosing.en.html#s3.1

but do please note that this document is out of date - it refers to
"Stretch" as the stable distribution, instead of "Buster", which has
been the stable distribustion since July 6th 2019.


... I'm not sure of the package name I should use to report ...


I wonder if the issue is in the BIOS (firmware) in your computer, not
in a Debian package.  In that case you might not need to report it at
all, because it might already have been fixed, or your BIOS might be
obsolete.  UEFI has been relacing BIOS almost everywhere, for several
years, so if it is the latest version, I'd almost expect any BIOS to
be obsolete and therefore not fixable.  What is the computer?  Exactly
what model and version, and roughly how old, is the BIOS?

--

73,
Ged.

Re: Question regarding an ACPI BIOS Error (bug)

[Dan Ritter]

Jude DaShiell wrote: 
> 
> Does any Linux app exist to let systems know when bios updates become
> available for the bios running on those systems?

No. It would require a mechanism supported by each manufacturer,
and they tend not to even be consistent on their own websites.

Server manufacturers sometimes have mailing lists that you can
subscribe to for notifications. 

The best you can do otherwise is find the page for your
motherboard, figure out your current BIOS revision (dmidecode
will help), and then watch it periodically.

That said, once you have everything you care about working,
there's rarely a good reason to upgrade.

-dsr-

Re: Question regarding an ACPI BIOS Error (bug)

[Jude DaShiell]

On Sat, 28 Mar 2020, Darac Marjal wrote:

> Date: Sat, 28 Mar 2020 06:55:55
> From: Darac Marjal 
> To: debian-user@lists.debian.org
> Subject: Re: Question regarding an ACPI BIOS Error (bug)
>
>
> On 28/03/2020 09:35, rba...@protonmail.ch wrote:
> > Hi all, I've been redirected to this list while using reportbug. I
> > would gladly accept some help regarding the determination of the
> > Debian package responsible for those traces during boot:
>
> That would be the kernel itself. The number in square brackets at the
> start of the line is the time (in seconds) since the kernel started. At
> less than a second after startup, you're unlikely to have any user-space
> components loaded yet and, besides, the kernel is what is responsible
> for talking to ACPI.
>
>
> >
> > [??? 0.410073] ACPI: Added _OSI(Processor Device)
> > [??? 0.410073] ACPI: Added _OSI(3.0 _SCP Extensions)
> > [??? 0.410073] ACPI: Added _OSI(Processor Aggregator Device)
> > [??? 0.410073] ACPI: Added _OSI(Linux-Dell-Video)
> > [??? 0.410073] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
> > [??? 0.410073] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
>
> These aren't errors; these ones are just informative.
>
>
> > [??? 0.457794] ACPI BIOS Error (bug): Failure creating named object
> > [\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
> > [??? 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name
> > lookup/catalog (20190816/psobject-220)
> > [??? 0.457805] ACPI: Skipping parse of AML opcode: OpcodeName
> > unavailable (0x0014)
> > [??? 0.457807] ACPI BIOS Error (bug): Failure creating named object
> > [\_GPE._E47], AE_ALREADY_EXISTS (20190816/dswload2-323)
> > [??? 0.457811] ACPI Error: AE_ALREADY_EXISTS, During name
> > lookup/catalog (20190816/psobject-220)
> > [??? 0.457813] ACPI: Skipping parse of AML opcode: OpcodeName
> > unavailable (0x0014)
>
> These are errors. However, as the message says, these are BIOS errors.
> ACPI machine language (AML) is basically a program inside your BIOS
> which the OS can use to list and control devices. Sometimes these AML
> programs have bugs in them; sometimes they are a little too focussed on
> what Windows likes (rather than what is proper). The generally accepted
> solution to these is: if there is a noticeable issue with your computer
> (some device doesn't work or behaves improperly), then consider a BIOS
> upgrade. Otherwise, if there is no apparent effect, then you can ignore
> these errors.
>
>
> > [??? 0.458226] ACPI: 10 ACPI AML tables successfully acquired and loaded
> > [??? 0.459880] ACPI: EC: EC started
> > [??? 0.459881] ACPI: EC: interrupt blocked
> > [??? 0.461706] ACPI: \: Used as first EC
> > [??? 0.461708] ACPI: \: GPE=0x27, EC_CMD/EC_SC=0x66, EC_DATA=0x62
> > [??? 0.461708] ACPI: EC: Boot ECDT EC used to handle transactions
> >
> > Using apt and apt-file, I found numerous packages related to ACPI and
> > there are also a few kernel modules dedicated to ACPI (in the last
> > case I would say the package is linux-image-5.4.0-4-amd64 version
> > 5.4.19-1 since I'm running a Debian testing) so I'm not sure of the
> > package name I should use to report this issue.
> >
> > Regards,
> >
> > -- Rapha?l BAZAUD
> >
Does any Linux app exist to let systems know when bios updates become
available for the bios running on those systems?
>
>
>

--

Re: Question regarding an ACPI BIOS Error (bug)

[Darac Marjal]

On 28/03/2020 09:35, rba...@protonmail.ch wrote:
> Hi all, I've been redirected to this list while using reportbug. I
> would gladly accept some help regarding the determination of the
> Debian package responsible for those traces during boot:

That would be the kernel itself. The number in square brackets at the
start of the line is the time (in seconds) since the kernel started. At
less than a second after startup, you're unlikely to have any user-space
components loaded yet and, besides, the kernel is what is responsible
for talking to ACPI.


>
> [    0.410073] ACPI: Added _OSI(Processor Device)
> [    0.410073] ACPI: Added _OSI(3.0 _SCP Extensions)
> [    0.410073] ACPI: Added _OSI(Processor Aggregator Device)
> [    0.410073] ACPI: Added _OSI(Linux-Dell-Video)
> [    0.410073] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
> [    0.410073] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)

These aren't errors; these ones are just informative.


> [    0.457794] ACPI BIOS Error (bug): Failure creating named object
> [\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
> [    0.457802] ACPI Error: AE_ALREADY_EXISTS, During name
> lookup/catalog (20190816/psobject-220)
> [    0.457805] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [    0.457807] ACPI BIOS Error (bug): Failure creating named object
> [\_GPE._E47], AE_ALREADY_EXISTS (20190816/dswload2-323)
> [    0.457811] ACPI Error: AE_ALREADY_EXISTS, During name
> lookup/catalog (20190816/psobject-220)
> [    0.457813] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)

These are errors. However, as the message says, these are BIOS errors.
ACPI machine language (AML) is basically a program inside your BIOS
which the OS can use to list and control devices. Sometimes these AML
programs have bugs in them; sometimes they are a little too focussed on
what Windows likes (rather than what is proper). The generally accepted
solution to these is: if there is a noticeable issue with your computer
(some device doesn't work or behaves improperly), then consider a BIOS
upgrade. Otherwise, if there is no apparent effect, then you can ignore
these errors.


> [    0.458226] ACPI: 10 ACPI AML tables successfully acquired and loaded
> [    0.459880] ACPI: EC: EC started
> [    0.459881] ACPI: EC: interrupt blocked
> [    0.461706] ACPI: \: Used as first EC
> [    0.461708] ACPI: \: GPE=0x27, EC_CMD/EC_SC=0x66, EC_DATA=0x62
> [    0.461708] ACPI: EC: Boot ECDT EC used to handle transactions
>
> Using apt and apt-file, I found numerous packages related to ACPI and
> there are also a few kernel modules dedicated to ACPI (in the last
> case I would say the package is linux-image-5.4.0-4-amd64 version
> 5.4.19-1 since I'm running a Debian testing) so I'm not sure of the
> package name I should use to report this issue.
>
> Regards,
>
> -- Raphaël BAZAUD
>




signature.asc
Description: OpenPGP digital signature

Question regarding an ACPI BIOS Error (bug)

[rba777]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi all, I've been redirected to this list while using reportbug. I would gladly 
accept some help regarding the determination of the Debian package responsible 
for those traces during boot:

[    0.410073] ACPI: Added _OSI(Processor Device)
[    0.410073] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.410073] ACPI: Added _OSI(Processor Aggregator Device)
[    0.410073] ACPI: Added _OSI(Linux-Dell-Video)
[    0.410073] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.410073] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.457794] ACPI BIOS Error (bug): Failure creating named object 
[\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
[    0.457802] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190816/psobject-220)
[    0.457805] ACPI: Skipping parse of AML opcode: OpcodeName unavailable 
(0x0014)
[    0.457807] ACPI BIOS Error (bug): Failure creating named object 
[\_GPE._E47], AE_ALREADY_EXISTS (20190816/dswload2-323)
[    0.457811] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190816/psobject-220)
[    0.457813] ACPI: Skipping parse of AML opcode: OpcodeName unavailable 
(0x0014)
[    0.458226] ACPI: 10 ACPI AML tables successfully acquired and loaded
[    0.459880] ACPI: EC: EC started
[    0.459881] ACPI: EC: interrupt blocked
[    0.461706] ACPI: \: Used as first EC
[    0.461708] ACPI: \: GPE=0x27, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.461708] ACPI: EC: Boot ECDT EC used to handle transactions

Using apt and apt-file, I found numerous packages related to ACPI and there are 
also a few kernel modules dedicated to ACPI (in the last case I would say the 
package is linux-image-5.4.0-4-amd64 version 5.4.19-1 since I'm running a 
Debian testing) so I'm not sure of the package name I should use to report this 
issue.

Regards,

-- Raphaël BAZAUD
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsFcBAEBCAAGBQJefxpXAAoJEOzVCCaRTXlv8HgP/RCnoM8yhXI7QVnLbPVZ
fgLMose7xgTWVGPGyaktkzCtj6VQ9zb6wk2jQcd39ARgbIKHmjHmZ7k4usCh
7MLqRnn6+k4K6gJJzhT9IV4zBA50ttdvXdzAkFeHGh5sOSMXiNkMGfiZ9SDO
K94ZbYR5DZ0nW98Ql9/2O5nLZtEBvz2RPehaiKVak0F+ldms+5p5Ha82iemL
NlvTqpQ75UbYFi5PH+7e0b79G9LED394fEdzBTYbQWYvsnLu2odW8BW7FV+I
jo1rMg28tMyJeRKNtjcR8Kcjn3FlPPHq0VCj+YwLLkHlo0UYKVoktsRyBpSC
edyWZ8pa+/oIJw+foCKL6OrkODqw3kgFvq4t/TAZpW8VpN6mZ2wsa1TTOYbk
vg793H1LSTEwcHldI96OzS06fe/CDBmTlQUjF2eB44IhJ7hPhiDxvxkLfVyc
Lo2TzKzjbivPVBPyQ/hk7jX4f9CydB5Hcf+ox+48pjBqqqrkr3mewPwYzZJF
peLkuRrTLv/VnLUlA8UC/M6+4PoCXyfnykC1Hyh4wecxjEkpsW+GEji8g9Nx
e8yKbdtJOgHu8wCZ0YzxpKb4qc5NE/m+bA4vWmHeIthBbAHS3h2/R84djN08
kNlGcBbkKia1tHNExraAIFf18hpYw79jOutV8sX5m/Mxs9/s/L7FpWic09kN
aOxw
=Pksl
-END PGP SIGNATURE-

Re: Cant boot without ACPI=off after BIOS was updated

[Andrei POPESCU]

On Du, 08 mar 20, 09:02:30, Sebastián Carloza R wrote:
> Hi
> 
> My PC's (ASUS X571GD) BIOS was updated (to BIOS 306). I think Windows did
> it automatically in an update. I have a Dual Boot with Debian 10.3 and
> windows 10. From that moment I have to boot with ACPI = off, to load Debian.

What exactly happens without acpi=off?


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Cant boot without ACPI=off after BIOS was updated

[Alexander V. Makartsev]

On 08.03.2020 17:02, Sebastián Carloza R wrote:
> Hi
>
> My PC's (ASUS X571GD) BIOS was updated (to BIOS 306). I think Windows
> did it automatically in an update. I have a Dual Boot with Debian 10.3
> and windows 10. From that moment I have to boot with ACPI = off, to
> load Debian.
>
> I don't know what's the package I would have to report, if there is
> even one in this case.
>
> Greetings and thanks
Indeed, Windows 10 can update BIOS on it's volition. [1]
It's possible that if you reset BIOS to default settings it will solve
your issue. It is a good idea in general to reset BIOS settings after
update, restart PC and reconfigure BIOS settings.
Also, as an option you can rollback BIOS version to 302. [2]
Or ask ASUS support for an advice or possible fix. If a regression was
introduced in version 306, they probably will release a new BIOS version
with necessary fixes.

[1] https://www.asus.com/en/support/FAQ/1041263
[2] https://www.asus.com/ru/Laptops/ASUS-Laptop-X571GD/HelpDesk_BIOS/

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Cant boot without ACPI=off after BIOS was updated

[Sebastián Carloza R]

Hi

My PC's (ASUS X571GD) BIOS was updated (to BIOS 306). I think Windows did
it automatically in an update. I have a Dual Boot with Debian 10.3 and
windows 10. From that moment I have to boot with ACPI = off, to load Debian.

I don't know what's the package I would have to report, if there is even
one in this case.

Greetings and thanks

Re: noapi acpi=off

[zahid]

That was kinda easy. ...BUT

I found that .deb file at 
https://packages.debian.org/buster/all/firmware-misc-nonfree/download


I had the wifi pane up immediately with a list of networks.

I even rebooted. BUT

it says configuring interface but won't connect.

I am also having to connect using a usb 802.11n dongle to get the wifi  
with a list of wifi windows.


If I remove the  dongle the wifi  list disappears.

I bought the dongle to use for ubuntu 18-19 but don't need it for fedora 31.


could it be do with that error the bottom of of the error messages.

I had to install nividia package for windows 10 as well.


sudo dpkg -i firmware-misc-nonfree_20190114-2_all.deb
[sudo] password for zahid:
Selecting previously unselected package firmware-misc-nonfree.
(Reading database ... 183403 files and directories currently installed.)
Preparing to unpack firmware-misc-nonfree_20190114-2_all.deb ...
Unpacking firmware-misc-nonfree (20190114-2) ...
Setting up firmware-misc-nonfree (20190114-2) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
W: Possible missing firmware 
/lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau



On 21/01/2020 14:37, Greg Wooledge wrote:

On Tue, Jan 21, 2020 at 02:30:10PM +, zahid wrote:

So now I just want to

" to get this firmware package and install it  [ /lib/firmware/rt2870.bin
firmware-misc-nonfree
 ] "

what are the instructions I need to follow to do that.

I need to get use to install debian install package system anyway.

Download the package.  It will be a file whose name ends with ".deb".

Get this file onto the Debian computer, by any means.  Ethernet,
sneakernet, magical osmosis, typing the bytes out by hand, whatever it
takes.

Install the package using "dpkg -i filename", as root.

Reboot.


--
Backbutton.co.uk
¯\_(ツ)_/¯
♡۶Java♡۶RMI ♡۶
Make Use Method {MUM}
makeuse.org

Re: noapi acpi=off

[Greg Wooledge]

On Tue, Jan 21, 2020 at 02:30:10PM +, zahid wrote:
> So now I just want to
> 
> " to get this firmware package and install it  [ /lib/firmware/rt2870.bin
> firmware-misc-nonfree
>  ] "
> 
> what are the instructions I need to follow to do that.
> 
> I need to get use to install debian install package system anyway.

Download the package.  It will be a file whose name ends with ".deb".

Get this file onto the Debian computer, by any means.  Ethernet,
sneakernet, magical osmosis, typing the bytes out by hand, whatever it
takes.

Install the package using "dpkg -i filename", as root.

Reboot.

Re: noapi acpi=off

[zahid]

Thank for your response,

I want to avoid using  "netinst with non-free firmware" because that 
would mean a reinstall again.


and I would have to install other software al over again.


So now I just want to

" to get this firmware package and install it  [ 
/lib/firmware/rt2870.bin firmware-misc-nonfree 
 ] "


what are the instructions I need to follow to do that.

I need to get use to install debian install package system anyway.


while waiting for your response

I was trying to follow these instructions and I am getting these errors

https://wiki.debian.org/WiFi#Simple_guide

sudo make
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.19.0-6-amd64/build 
M=/home/zahid/rtl8192eu-linux-driver  modules
make[1]: *** /lib/modules/4.19.0-6-amd64/build: No such file or 
directory.  Stop.

make: *** [Makefile:1700: modules] Error 2
zahid@makeuse:~/rtl8192eu-linux-driver$ sudo make install
install -p -m 644 8192eu.ko 
/lib/modules/4.19.0-6-amd64/kernel/drivers/net/wireless/

install: cannot stat '8192eu.ko': No such file or directory
make: *** [Makefile:1706: install] Error 1

On 21/01/2020 13:27, Greg Wooledge wrote:

On Tue, Jan 21, 2020 at 11:15:34AM +, Zahid Rahman wrote:

During installation I got a prompt to install rtl_nic/rtl8168h-2.fw
rt2870.bin from media.
I was installing  using net install so I skipped it.

Awesome.  Knowing the exact filename of the firmware that you need
makes it *super* easy to identify the package that you need.

https://packages.debian.org/search?searchon=contents=rt2870.bin=exactfilename=stable=any

tells us that you need the package named "firmware-misc-nonfree".

As the name implies, this package is in the non-free section of Debian,
which means it's not included in the official installer images.

It *is* included in the unofficial "netinst with non-free firmware"
images.  If you use one of those, your problems will all go away.

If you aren't using one of the unofficial installers, then you'll need
to get this firmware package and install it.  That can be done over
ethernet, temporary or otherwise, or by sneakernetting it on a USB
stick, etc.


--
Backbutton.co.uk
¯\_(ツ)_/¯
♡۶Java♡۶RMI ♡۶
Make Use Method {MUM}
makeuse.org

Re: noapi acpi=off

[Greg Wooledge]

On Tue, Jan 21, 2020 at 11:15:34AM +, Zahid Rahman wrote:
> During installation I got a prompt to install rtl_nic/rtl8168h-2.fw
> rt2870.bin from media.
> I was installing  using net install so I skipped it.

Awesome.  Knowing the exact filename of the firmware that you need
makes it *super* easy to identify the package that you need.

https://packages.debian.org/search?searchon=contents=rt2870.bin=exactfilename=stable=any

tells us that you need the package named "firmware-misc-nonfree".

As the name implies, this package is in the non-free section of Debian,
which means it's not included in the official installer images.

It *is* included in the unofficial "netinst with non-free firmware"
images.  If you use one of those, your problems will all go away.

If you aren't using one of the unofficial installers, then you'll need
to get this firmware package and install it.  That can be done over
ethernet, temporary or otherwise, or by sneakernetting it on a USB
stick, etc.

Re: noapi acpi=off

[Zahid Rahman]

 125
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
Memory behind bridge: 8430-843f
Capabilities: 
Kernel driver in use: pcieport

00:1d.7 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port
(rev f0) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 126
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
Memory behind bridge: 8420-842f
Capabilities: 
Kernel driver in use: pcieport

00:1f.0 ISA bridge: Intel Corporation Device a30d (rev 10)
Subsystem: Hewlett-Packard Company Device 8575
Flags: bus master, medium devsel, latency 0

00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS
Flags: bus master, fast devsel, latency 32, IRQ 142
Memory at 84618000 (64-bit, non-prefetchable) [size=16K]
Memory at 8410 (64-bit, non-prefetchable) [size=1M]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH SMBus Controller
Flags: medium devsel, IRQ 16
Memory at 8462 (64-bit, non-prefetchable) [size=256]
I/O ports at efa0 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI
Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH SPI Controller
Flags: fast devsel
Memory at fe01 (32-bit, non-prefetchable) [size=4K]

01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f91 (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 8575
Flags: fast devsel, IRQ 16
Memory at 8300 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at 4000 [size=128]
Expansion ROM at 8400 [disabled] [size=512K]
Capabilities: 
Kernel modules: nouveau

01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
Subsystem: Hewlett-Packard Company Device 8574
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at 8408 (32-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD
Controller SM981/PM981 (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
Memory at 8450 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: nvme
Kernel modules: nvme

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16)
Subsystem: Hewlett-Packard Company RTL8111/8168/8411 PCI Express Gigabit
Ethernet Controller
Flags: bus master, fast devsel, latency 0, IRQ 17
I/O ports at 3000 [size=256]
Memory at 84404000 (64-bit, non-prefetchable) [size=4K]
Memory at 8440 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: r8169
Kernel modules: r8169

04:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)
Subsystem: Intel Corporation Device 0084
Flags: fast devsel, IRQ 11
Memory at 8430 (64-bit, non-prefetchable) [disabled] [size=16K]
Capabilities: 

05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A
PCI Express Card Reader (rev 01)
Subsystem: Hewlett-Packard Company RTS522A PCI Express Card Reader
Flags: bus master, fast devsel, latency 0, IRQ 127
Memory at 8420 (32-bit, non-prefetchable) [size=4K]
Capabilities: 
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci


Best Regards
zahid
Backbutton.co.uk
¯\_(ツ)_/¯
♡۶Java♡۶RMI ♡۶
Make Use Method {MUM}
makeuse.org
<http://www.backbutton.co.uk>


On Tue, 21 Jan 2020 at 06:08, Alexander V. Makartsev 
wrote:

> On 21.01.2020 10:21, Zahid Rahman wrote:
>
> So if you have  the latest version of debian and it is logging on and off
> ok ,  what are  the acpi setting,  kernel parameters.
>
> You can find this out by pressing 'e' when the grub screen is showing.
>
> I should have taken note when I had debian installed.
>
>
> I recommend to use default settings. By disabling ACPI you'll only cripple
> many internal hardware functions of your laptop.
> If there is some problem with default settings (only "quiet" as kernel
> parameter in grub), then disabling ACPI is not the solution.
> You need to look further, check logs to find out what exactly causing you
> trouble.
> We can advise more, if you can send useful snippets of logs or other
> information about your laptop here.
> Also describe in detail what problem do you trying to solve by disabling
> ACPI and changing kernel boot parameters?
>
> Debian has almost every driver and firmware currently supported by kernel,
> just like any oth

Re: noapi acpi=off

[Alexander V. Makartsev]

On 21.01.2020 10:21, Zahid Rahman wrote:
> So if you have  the latest version of debian and it is logging on and
> off ok ,  what are  the acpi setting,  kernel parameters.
>
> You can find this out by pressing 'e' when the grub screen is showing.
>
> I should have taken note when I had debian installed. 
>
>
I recommend to use default settings. By disabling ACPI you'll only
cripple many internal hardware functions of your laptop.
If there is some problem with default settings (only "quiet" as kernel
parameter in grub), then disabling ACPI is not the solution.
You need to look further, check logs to find out what exactly causing
you trouble.
We can advise more, if you can send useful snippets of logs or other
information about your laptop here.
Also describe in detail what problem do you trying to solve by disabling
ACPI and changing kernel boot parameters?

Debian has almost every driver and firmware currently supported by
kernel, just like any other distro. What model and make of network
adapter you trying to use?
You can find out this information using "lspci -v".
It is possible you simply have to install some additional package from
Debian repos with non-free firmware for your network adapter.


-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: noapi acpi=off

[Zahid Rahman]

So if you have  the latest version of debian and it is logging on and off
ok ,  what are  the acpi setting,  kernel parameters.

You can find this out by pressing 'e' when the grub screen is showing.

I should have taken note when I had debian installed.




On Tue, 21 Jan 2020, 05:13 Zahid Rahman,  wrote:

> Thank you.
>
> I have been getting same problem with ubuntu. I think these linux
> operating systems has corrupted some Table on my laptop.
>
> Although fedora has wifi driver , Debian does not.
>
> Ubuntu did not have a wifi driver,  but later wifi driver came with a
> software update.
> But then ubuntu would only work,
>  go to login screen in recovery mode due to this acpi issue.
>
> So now I am using open suse.
> That operating  system is compensating for the corrupted BIOS table and
> has wifi driver.  For some reason open opensuse.org  is extremely fast
> compare to all  linux operating system.
>
>
>
>
>
>
> On Mon, 20 Jan 2020, 22:11 Jonathan Dowland, 
> wrote:
>
>> On Mon, Jan 20, 2020 at 03:03:44PM +, Zahid Rahman wrote:
>> >I would appreciate if some one can tell me the precise kernel parameter
>> >values so the laptop
>> >will turm off and I promise to turn off  software updates after that.
>> >FEDORA 31.
>>
>> You've sent this to the Debian User list, for Debian users. You probably
>> want the Fedora Users list instead:
>> https://lists.fedoraproject.org/admin/lists/users.lists.fedoraproject.org/
>>
>>
>> --
>>
>> Jonathan Dowland
>>
>>

Re: noapi acpi=off

[Zahid Rahman]

Thank you.

I have been getting same problem with ubuntu. I think these linux operating
systems has corrupted some Table on my laptop.

Although fedora has wifi driver , Debian does not.

Ubuntu did not have a wifi driver,  but later wifi driver came with a
software update.
But then ubuntu would only work,
 go to login screen in recovery mode due to this acpi issue.

So now I am using open suse.
That operating  system is compensating for the corrupted BIOS table and has
wifi driver.  For some reason open opensuse.org  is extremely fast compare
to all  linux operating system.






On Mon, 20 Jan 2020, 22:11 Jonathan Dowland, 
wrote:

> On Mon, Jan 20, 2020 at 03:03:44PM +, Zahid Rahman wrote:
> >I would appreciate if some one can tell me the precise kernel parameter
> >values so the laptop
> >will turm off and I promise to turn off  software updates after that.
> >FEDORA 31.
>
> You've sent this to the Debian User list, for Debian users. You probably
> want the Fedora Users list instead:
> https://lists.fedoraproject.org/admin/lists/users.lists.fedoraproject.org/
>
>
> --
>
> Jonathan Dowland
>
>

Re: noapi acpi=off

[Jonathan Dowland]

On Mon, Jan 20, 2020 at 03:03:44PM +, Zahid Rahman wrote:

I would appreciate if some one can tell me the precise kernel parameter
values so the laptop
will turm off and I promise to turn off  software updates after that.
FEDORA 31.


You've sent this to the Debian User list, for Debian users. You probably 
want the Fedora Users list instead: 
https://lists.fedoraproject.org/admin/lists/users.lists.fedoraproject.org/



--

Jonathan Dowland

noapi acpi=off

[Zahid Rahman]

Hi,

The idea to introduce this acpi change  in the software updates across
linux platforms,
I  think was a very bad.

It has meant that   either I can't login or I am staring at a purple, or
black  blank screen depending on the linux flavour.
or the system is hanging  and won't  turn off.

Anyway I am currently able to login , but when I log off I have a black
screen but the laptop
doesn't actually power off.

I would appreciate if some one can tell me the precise kernel parameter
values so the laptop
will turm off and I promise to turn off  software updates after that.
FEDORA 31.

# grubby --info  /boot/vmlinuz-5.4.10-200.fc31.x86_64
index=0
kernel="/boot/vmlinuz-5.4.10-200.fc31.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet noapic acpi=off"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.4.10-200.fc31.x86_64.img"
title="Fedora (5.4.10-200.fc31.x86_64) 31 (Thirty One)"
id="0cf110914feb47d2b515ea01d0de0c99-5.4.10-200.fc31.x86_64"

Backbutton.co.uk
¯\_(ツ)_/¯
♡۶Java♡۶RMI ♡۶
Make Use Method {MUM}
<http://www.backbutton.co.uk>

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

[Andrea Borgia]

quick note, the bug report has been filed: 919227

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

[Andrea Borgia]

Il 09/01/19 00:07, Michael Lange ha scritto:




Just because it is old does not necessarily mean that no one bothers.


Sorry, that's not what I meant: I wanted to say the kernel is so old 
that it probably doesn't really matter if it is the debian or the 
upstream version I am using. That is, whatever patches Debian might have 
added back then have gone mainline for the most part.



Andrea.

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

[Michael Lange]

Hi,

On Tue, 8 Jan 2019 17:44:04 +0100
Andrea Borgia  wrote:

> Il 07/01/19 20:09, Michael Lange ha scritto:
> 
> 
> > Since the error message looks different from yours I guess that this
> > is probably a completely different issue, though.
> 
> Most likely you're right, however there was quite a big rewrite of ACPI 
> in 4.10 and I wouldn't rule it out completely.

I forgot to mention that the lid did not stop working here between 4.9 and
4.10. Actually here it works with a Siduction 4.16 kernel, but does not
with the Liquorix 4.19. Just for the fun of it I tried the Debian 4.19
kernel from Sid and the lid happens to work again. Maybe this is due to
some (possibly faulty) driver modules missing from the Debian kernel, but
that's of course just guesswork. 
I think for now I will just stick with 4.16 and see if in the course of
time the missing modules will be picked up by debian.

> > I believe reporting to debian is the best so long as you use a debian
> > kernel. If you want to report to kernel.org probably they'll expect
> > that you compile and try their kernel first.
> 
> That wouldn't be a problem: the thing is so old that it probably makes 
> no difference.

Just because it is old does not necessarily mean that no one bothers.
After I upgraded to Stretch I filed a bug report because my 20 year old
sound card suddenly had stopped working and after a couple of weeks they
had this fixed so now the card works as good as new. As far as Win 10 is
concerned that card is as dead as a doorknob :-)

Regards

Michael


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

It would seem that evil retreats when forcibly confronted.
-- Yarnek of Excalbia, "The Savage Curtain", stardate 5906.5

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

[Andrea Borgia]

Il 07/01/19 20:09, Michael Lange ha scritto:



Since the error message looks different from yours I guess that this is
probably a completely different issue, though.


Most likely you're right, however there was quite a big rewrite of ACPI 
in 4.10 and I wouldn't rule it out completely.




I believe reporting to debian is the best so long as you use a debian kernel.
If you want to report to kernel.org probably they'll expect that you
compile and try their kernel first.


That wouldn't be a problem: the thing is so old that it probably makes 
no difference. Anyhow, since my laptop is running the stock debian 
kernel I'll go along with your suggestion, once I'm done with another 
round of tests.


I've discovered a few bugreport that contain useful information:
https://bugzilla.kernel.org/show_bug.cgi?id=192231
https://bugzilla.kernel.org/show_bug.cgi?id=195455
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863257


See if you can find something useful to debug your issue and please let 
me know if you discover anything interesting.



Regards,
Andrea.

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

[Michael Lange]

Hi,

On Fri, 4 Jan 2019 20:11:53 +0100
Andrea Borgia  wrote:

(...)
> 
> dmesg has this interesting warning:
> ACPI: button: The lid device is not compliant to SW_LID.

oddly, here with my Lenovo Ideapad 100s the lid switch stopped working,
too. However, this is totally different hardware and I do not get the above
error message, but instead dmesg says after booting:

   ACPI Error: Method parse/execution failed \_SB.LID0._LID, AE_NOT_EXIST 
(20180810/psparse-516)

And when I close and re-open the lid dmesg|tail says:

 ACPI Error: No handler for Region [ECRE] (cad769b9) [GenericSerialBus] 
(20180810/evregion-132)
 ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20180810/exfldio-265)
 ACPI Error: Result stack is empty! State=5069dd47 
(20180810/dswstate-65)
 ACPI Error: Method parse/execution failed \_SB.LID0._LID, AE_NOT_EXIST 
(20180810/psparse-516)
 ACPI Error: No handler for Region [ECRE] (cad769b9) [GenericSerialBus] 
(20180810/evregion-132)
 ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20180810/exfldio-265)
 ACPI Error: Result stack is empty! State=fdc80083 
(20180810/dswstate-65)
 ACPI Error: Method parse/execution failed \_SB.LID0._LID, AE_NOT_EXIST 
(20180810/psparse-516)

Since the error message looks different from yours I guess that this is
probably a completely different issue, though. 


> What's the best way to handle this? IMHO it's quite likely a kernel 
> issue, most likely upstream.
> Should I file a bug on linux-image-amd64 or directly on
> bugzilla.kernel.org?

I believe reporting to debian is the best so long as you use a debian kernel.
If you want to report to kernel.org probably they'll expect that you
compile and try their kernel first.

Regards

Michael

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

Schshschshchsch.
-- The Gorn, "Arena", stardate 3046.2

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

[Andrea Borgia]

Il 04/01/19 20:11, Andrea Borgia ha scritto:


What's the best way to handle this? IMHO it's quite likely a kernel 
issue, most likely upstream.
Should I file a bug on linux-image-amd64 or directly on 
bugzilla.kernel.org?


No comments?


Meanwhile, I've been testing the kernels archived on snapshot.debian.org:
4.9.0-7: OK (last known working, see previous msg)
4.10.0-trunk: fails
4.11.0-2: fails
4.14.0-1: fails
4.19.0-1: fails (first failure detected, see previous msg)
(those versions which are failing all have the "SW_LID" warning)


In Documentation/acpi/acpi-lid.txt, I saw the newer kernels have added a 
button.lid_init_state and I have tried the possible values on 4.19.0-1:

method: fails
open: fails
ignore: fails


To recap, so far the last known working kernel for the lid switch was 
the one currently in "stable", that is 4.9.0-7, and I'm out of ideas :/



Andrea.

kernel regression from stable to testing (acpi lid / EEEpc 1215p)

[Andrea Borgia]

Hi.


On my EEEpc 1215p laptop, the upgrade from stable to testing broke the 
lid switch detection, since

* another OS detects it just fine and acts on it;
* the kernel from stable (4.9.0-7) does too
Therefore, HW is ok (not obvious on an old laptop...)


If I use the current kernel in testing (4.19.0-1), or really any 
"testing" kernel from december onwards (when I upgraded), this is the 
situation:

* the sleep keycombo Fn+F1 works
* pm-suspend works
* pm-hibernate works
If I observe the state of /proc/acpi/button/lid/LID/state from a remote 
shell and close the lid, it shows "open". Indeed, the fact that I can 
still use the system is a dead giveaway it's not suspended :P


/etc/default/acpi-support is fine: LID_SLEEP=true is active, both acpid 
and the system itself were restarted multiple times.


Closest bug I could find witha similar issue is not relevant, since it's 
way older than my working kernel: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820422



dmesg has this interesting warning:
ACPI: button: The lid device is not compliant to SW_LID.

Digging around, the common reply was along the lines of "meh, just a 
warning, ignore it if it works". Well, guess what, it doesn't :(



What's the best way to handle this? IMHO it's quite likely a kernel 
issue, most likely upstream.

Should I file a bug on linux-image-amd64 or directly on bugzilla.kernel.org?


Thanks,
Andrea.

Re: Re: ACPI BIOS ERROR

[steve]

Le 07-12-2018, à 17:34:20 -0500, Tyler McLean a écrit :


  Having this same exact series of error messages on boot and the first time
  i press a key after boot. fresh debian install, latest BIOS. super
  annoying. did you ever resolve this?


No, I guess it's a firmware bug, so only chance is that the manufacturer
corrects it.

Sorry

Re: Re: ACPI BIOS ERROR

[Tyler McLean]

Having this same exact series of error messages on boot and the first time
i press a key after boot. fresh debian install, latest BIOS. super
annoying. did you ever resolve this?

Re: How to Fix ACPI Error : Namespace lookup failure

[mick crane]

On 2018-11-10 19:31, finn wrote:

Greetings,
Whenever I boot up my PC I'm getting this error
`sudo dmesg`

[   12.432182] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV]
Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[   12.432241] ACPI Error: Method parse/execution failed
[\_SB.PCI0.B0D4._TMP] (Node 9de85a1f4410), AE_NOT_FOUND
(20160831/psparse-543)

It seems like something is missing (for ex. library, package etc).
I'm ignoring this error from 7-8 months because it has no bad effect
on PC my but I'm more interested in why am I getting this error? And
if possible, How can I fix this issue?


online search for error message appears to suggest it is a BIOS problem 
which you can ignore or perhaps update the BIOS



--
Key ID4BFEBB31

How to Fix ACPI Error : Namespace lookup failure

[finn]

Greetings,
Whenever I boot up my PC I'm getting this error
`sudo dmesg`

[   12.432182] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace 
lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[   12.432241] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.B0D4._TMP] (Node 9de85a1f4410), AE_NOT_FOUND 
(20160831/psparse-543)

It seems like something is missing (for ex. library, package etc).
I'm ignoring this error from 7-8 months because it has no bad effect on PC my 
but I'm more interested in why am I getting this error? And if possible, How 
can I fix this issue?

ACPI wrong battery information (kernel 4.18)

[debian]

Hi,

I've made a fresh installation of debian testing on my ASUS eeepc x101.
ACPI reports wrong battery informations. If I type acpi -V:

$ acpi -V
Battery 0: Discharging, 100%, 4200:00:00 remaining
Battery 0: design capacity 4300 mAh, last full capacity 4200 mAh = 97%
Adapter 0: off-line
Thermal 0: ok, 60.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 90.0
degrees C
Thermal 0: trip point 1 switches to mode passive at temperature 88.0
degrees C
Cooling 0: Processor 0 of 10
Cooling 1: LCD 8 of 10
Cooling 2: Processor 0 of 10

$ uname -a
Linux x101 4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 (2018-09-06) x86_64
GNU/Linux

$ cat /etc/debian_version 
buster/sid


But, if I use the 4.14 kernel acpi works fine:

$ acpi -V
Battery 0: Discharging, 30%, 01:32:16 remaining
Battery 0: design capacity 4400 mAh, last full capacity 4323 mAh = 98%
Adapter 0: off-line
Thermal 0: ok, 60.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 90.0
degrees C
Thermal 0: trip point 1 switches to mode passive at temperature 88.0
degrees C
Cooling 0: Processor 0 of 10
Cooling 1: LCD 8 of 10
Cooling 2: Processor 0 of 10

$ uname -a
Linux x101 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64
GNU/Linux


This may be a bug in acpi package? linux-image package...?

Greetings

Re: ACPI BIOS ERROR

[steve]

Le 24-09-2018, à 09:36:48 +0200, deloptes a écrit :


steve wrote:


I disable some ACPI settings in the BIOS and it reduced the waiting
time.


don't know someone has to debug it - might be something is reported on ACPI
that exists, but service can not be started. I would look forward to enable
more logging in this context - might be kernel driver, kernel or systemd or
something else that needs debugging. Then you'll know.
Also why do you not share what you exactly disabled?


Well, thank you for asking :)

Don't remember exactly. Will have to check when I have more time.

Thanks

Re: ACPI BIOS ERROR

[deloptes]

steve wrote:

> I disable some ACPI settings in the BIOS and it reduced the waiting
> time.

don't know someone has to debug it - might be something is reported on ACPI
that exists, but service can not be started. I would look forward to enable
more logging in this context - might be kernel driver, kernel or systemd or
something else that needs debugging. Then you'll know.
Also why do you not share what you exactly disabled?

regards

Re: ACPI BIOS ERROR

[steve]

Le 24-09-2018, à 08:12:37 +0200, deloptes a écrit :


steve wrote:


Machine stop 15 seconds during boot, then goes on.


This does not mean that it stops for that reason. 


I disable some ACPI settings in the BIOS and it reduced the waiting
time. 


Are you using systemd?


Yes.


I recall systemd waiting for something to start or complete.


Possible.


It might be this or something else. IMO those BIOS related messages are
harmless


That's also what I think. But I would like to have a clean boot without
errors.

Re: ACPI BIOS ERROR

[deloptes]

steve wrote:

> Machine stop 15 seconds during boot, then goes on.

This does not mean that it stops for that reason. Are you using systemd? I
recall systemd waiting for something to start or complete.
It might be this or something else. IMO those BIOS related messages are
harmless

regards

Re: ACPI BIOS ERROR

[steve]

Le 23-09-2018, à 15:20:40 +0200, deloptes a écrit :


steve wrote:


Yes I have.


in such a case you can try to track it via bug request, although some of
those are bois/firmware related and mostly not harmful.


Or the harm is very subtle and I don't see it.




do you have error description, because if it is a bug, it should be visible
some how.


All I have is what is posted here.

Machine stop 15 seconds during boot, then goes on.

Re: ACPI BIOS ERROR

[deloptes]

steve wrote:

> Yes I have.

in such a case you can try to track it via bug request, although some of
those are bois/firmware related and mostly not harmful.

do you have error description, because if it is a bug, it should be visible
some how.

Re: ACPI BIOS ERROR

[steve]

Le 22-09-2018, à 20:23:28 +0200, deloptes a écrit :


steve wrote:


Should I open a ticket in the BTS?


you have latest BIOS installed?


Yes I have.

Re: ACPI BIOS ERROR

[deloptes]

steve wrote:

> Should I open a ticket in the BTS?

you have latest BIOS installed?

ACPI BIOS ERROR

[steve]

Hi,

Almost sure nobody will have a solution, but for the sake of it, I'll
document it here.

dmesg | grep -i error
[0.004000] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all 
errors
[0.196456] ACPI BIOS Error (bug): Failure creating [\_SB.INTS], 
AE_ALREADY_EXISTS (20180531/dswload2-316)
[0.196461] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20180531/psobject-221)
[0.234643] ACPI BIOS Error (bug): Could not resolve [\SHAD._STA.SDS0], 
AE_NOT_FOUND (20180531/psargs-330)
[0.234647] ACPI Error: Method parse/execution failed \SHAD._STA, 
AE_NOT_FOUND (20180531/psparse-516)
[0.265882] ACPI BIOS Error (bug): Could not resolve [\SHAD._STA.SDS0], 
AE_NOT_FOUND (20180531/psargs-330)
[0.265887] ACPI Error: Method parse/execution failed \SHAD._STA, 
AE_NOT_FOUND (20180531/psparse-516)
[0.326959] ACPI BIOS Error (bug): Could not resolve [\SHAD._STA.SDS0], 
AE_NOT_FOUND (20180531/psargs-330)
[0.326959] ACPI Error: Method parse/execution failed \SHAD._STA, 
AE_NOT_FOUND (20180531/psparse-516)
[1.348312] ACPI BIOS Error (bug): Could not resolve [\SHAD._STA.SDS0], 
AE_NOT_FOUND (20180531/psargs-330)
[1.348392] ACPI Error: Method parse/execution failed \SHAD._STA, 
AE_NOT_FOUND (20180531/psparse-516)

(Not sure the first line is linked).

Should I open a ticket in the BTS?

Best

Steve

Re: Buster: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180313/dspkginit-414)

[local10]

Aug 27, 2018, 2:57 AM by b...@fineby.me.uk:

> On Mon, 27 Aug 2018 03:49:14 +0200 (CEST)
> local10 <> loca...@tutanota.com > > wrote:
>
> The two things are unrelated.  The error on boot is "annoying but
> harmless", according what I've read, after a *very* cursory search
> (translation: you could have done this yourself).
>
Sorry about that, kind of struggling right now, the current environment isn't 
very conductive to extensive searches.


> The failure to start SDDM/KDE is probably due to entropy issues, and has
> been discussed on this list recently.
>
Looks like there are bigger problems with X but I'll put it in a separate 
message.

Regards,

Re: Buster: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180313/dspkginit-414)

[Brad Rogers]

On Mon, 27 Aug 2018 03:49:14 +0200 (CEST)
local10  wrote:

Hello local10,

>Am getting the following errors on boot and, probably due to the
>errors, KDE cannot start (kde-plasma-desktop package was installed).

The two things are unrelated.  The error on boot is "annoying but
harmless", according what I've read, after a *very* cursory search
(translation: you could have done this yourself).

The failure to start SDDM/KDE is probably due to entropy issues, and has
been discussed on this list recently.
Options are:
Wait until SDDM starts (can be up to three minutes)
Mash on keyboard until SDDM starts (takes a few seconds)
Install 'haveged' to increase entropy during boot process

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Why do they try to hide our past pulling down houses and build car parks
Bricks & Mortar - The Jam


pgpZmeu4ToSlU.pgp
Description: OpenPGP digital signature

Buster: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180313/dspkginit-414)

[local10]

Hi,

Am getting the following errors on boot and, probably due to the errors, KDE 
cannot start (kde-plasma-desktop package was installed). The snapshot was from 
August 20, 2018 was used for buster installation.

Any ideas? Thanks


Aug 26 21:31:55 tstsrv kernel: [    0.032672] ACPI: Added _OSI(Module Device)
Aug 26 21:31:55 tstsrv kernel: [    0.032672] ACPI: Added _OSI(Processor Device)
Aug 26 21:31:55 tstsrv kernel: [    0.032672] ACPI: Added _OSI(3.0 _SCP 
Extensions)
Aug 26 21:31:55 tstsrv kernel: [    0.032672] ACPI: Added _OSI(Processor 
Aggregator Device)
Aug 26 21:31:55 tstsrv kernel: [    0.032672] ACPI: Added _OSI(Linux-Dell-Video)
Aug 26 21:31:55 tstsrv kernel: [    0.037417] ACPI: 2 ACPI AML tables 
successfully acquired and loaded
Aug 26 21:31:55 tstsrv kernel: [    0.037567] ACPI Error: AE_NOT_FOUND, While 
resolving a named reference package element - LNKC (20180313/dspkginit-414)
Aug 26 21:31:55 tstsrv kernel: [    0.037603] ACPI Error: AE_NOT_FOUND, While 
resolving a named reference package element - LNKD (20180313/dspkginit-414)
Aug 26 21:31:55 tstsrv kernel: [    0.037636] ACPI Error: AE_NOT_FOUND, While 
resolving a named reference package element - LNKA (20180313/dspkginit-414)
Aug 26 21:31:55 tstsrv kernel: [    0.037668] ACPI Error: AE_NOT_FOUND, While 
resolving a named reference package element - LNKB (20180313/dspkginit-414)
Aug 26 21:31:55 tstsrv kernel: [    0.037704] ACPI Error: AE_NOT_FOUND, While 
resolving a named reference package element - LNKD (20180313/dspkginit-414)
Aug 26 21:31:55 tstsrv kernel: [    0.037735] ACPI Error: AE_NOT_FOUND, While 
resolving a named reference package element - LNKA (20180313/dspkginit-414)
...
...
Aug 26 21:31:55 tstsrv kernel: [    0.038889] ACPI Error: AE_NOT_FOUND, While 
resolving a named reference package element - LNKC (20180313/dspkginit-414)
Aug 26 21:31:55 tstsrv kernel: [    0.038923] ACPI Error: AE_NOT_FOUND, While 
resolving a named reference package element - LNKD (20180313/dspkginit-414)
Aug 26 21:31:55 tstsrv kernel: [    0.040638] ACPI: Interpreter enabled
Aug 26 21:31:55 tstsrv kernel: [    0.040655] ACPI: (supports S0 S3 S4 S5)
Aug 26 21:31:55 tstsrv kernel: [    0.040656] ACPI: Using IOAPIC for interrupt 
routing
Aug 26 21:31:55 tstsrv kernel: [    0.040711] PCI: Using host bridge windows 
from ACPI; if necessary, use "pci=nocrs" and report a bug
Aug 26 21:31:55 tstsrv kernel: [    0.040824] ACPI: Enabled 5 GPEs in block 00 
to 1F
Aug 26 21:31:55 tstsrv kernel: [    0.045473] ACPI: PCI Root Bridge [PCI0] 
(domain  [bus 00-ff])
Aug 26 21:31:55 tstsrv kernel: [    0.045478] acpi PNP0A03:00: _OSC: OS 
supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 26 21:31:55 tstsrv kernel: [    0.045482] acpi PNP0A03:00: _OSC failed 
(AE_NOT_FOUND); disabling ASPM
Aug 26 21:31:55 tstsrv kernel: [    0.045701] PCI host bridge to bus :00

Re: how to change default locale [was Re: How to Fix ACPI Error : Namespace lookup failure]

[Dale Forsyth]

https://www.mycause.com.au/page/183259/a-smile-will-change-a-day-love-that-changed-my-world

From: davidson 
Sent: Saturday, 11 August 2018 8:02 PM
To: debian-user@lists.debian.org
Subject: how to change default locale [was Re: How to Fix ACPI Error : 
Namespace lookup failure]

On Sun, 5 Aug 2018, genius wrote:

> Q: how to change the Language option . my system default language is
> English , now I want to change it into Chinese..

If there is some connection between the original subject line of your
message ("Re: How to Fix ACPI Error : Namespace lookup failure") and
the question that you ask here, I am afraid I am not enough of a
wizard to figure it out.

Anyway, if I were you, this is how I would try to change the default
locale on my system:

As root I would do

  # dpkg-reconfigure locales

I would expect this to

  1. allow me to interactively select locales I want generated, and then

  2. let me select one of the generated locales to be the default locale.

I hope this is helpful.

--
  The day will come  |  Last words, August Spies (1855--1887).
  When our silence will be   |  Hanged, by the state of Illinois,
  More powerful than |  alongside fellow journalists
  The voices you strangle today  |  Adolf Fischer and Albert Parsons.

Re: how to change default locale [was Re: How to Fix ACPI Error : Namespace lookup failure]

[Dale Forsyth]

https://www.mycause.com.au/page/183259/a-smile-will-change-a-day-love-that-changed-my-world

From: davidson 
Sent: Saturday, 11 August 2018 8:02 PM
To: debian-user@lists.debian.org
Subject: how to change default locale [was Re: How to Fix ACPI Error : 
Namespace lookup failure]

On Sun, 5 Aug 2018, genius wrote:

> Q: how to change the Language option . my system default language is
> English , now I want to change it into Chinese..

If there is some connection between the original subject line of your
message ("Re: How to Fix ACPI Error : Namespace lookup failure") and
the question that you ask here, I am afraid I am not enough of a
wizard to figure it out.

Anyway, if I were you, this is how I would try to change the default
locale on my system:

As root I would do

  # dpkg-reconfigure locales

I would expect this to

  1. allow me to interactively select locales I want generated, and then

  2. let me select one of the generated locales to be the default locale.

I hope this is helpful.

--
  The day will come  |  Last words, August Spies (1855--1887).
  When our silence will be   |  Hanged, by the state of Illinois,
  More powerful than |  alongside fellow journalists
  The voices you strangle today  |  Adolf Fischer and Albert Parsons.

how to change default locale [was Re: How to Fix ACPI Error : Namespace lookup failure]

[davidson]

On Sun, 5 Aug 2018, genius wrote:


Q: how to change the Language option . my system default language is
English , now I want to change it into Chinese..


If there is some connection between the original subject line of your
message ("Re: How to Fix ACPI Error : Namespace lookup failure") and
the question that you ask here, I am afraid I am not enough of a
wizard to figure it out.

Anyway, if I were you, this is how I would try to change the default
locale on my system:

As root I would do

 # dpkg-reconfigure locales

I would expect this to

 1. allow me to interactively select locales I want generated, and then

 2. let me select one of the generated locales to be the default locale.

I hope this is helpful.

--
 The day will come  |  Last words, August Spies (1855--1887).
 When our silence will be   |  Hanged, by the state of Illinois,
 More powerful than |  alongside fellow journalists
 The voices you strangle today  |  Adolf Fischer and Albert Parsons.

Re: How to Fix ACPI Error : Namespace lookup failure

[genius]

Q: how to change the Language option . my system default language is English , 
now I want to change it into Chinese..

Re: ACPI Error on boot

[Henrique de Moraes Holschuh]

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-:03:00.0.bin failed with error -2
> [9.269403] ath10k_pci :03:00.0: firmware: failed to load 
> ath10k/cal-pci-:03:00.0.bin (-2)
> [9.269404] ath10k_pci :03:00.0: Direct firmware load for 
> ath10k/cal-pci-:03:00.0.bin failed with error -2
> [9.311104] ath10k_pci :03:00.0: firmware: failed to load 
> ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
> [9.311107] ath10k_pci :03:00.0: Direct firmware load for 
> ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
> [9.33] ath10k_pci :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

Re: ACPI Error on boot

[Felix Miata]

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 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/

Re: ACPI Error on boot

[tomas]

-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 :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-:03:00.0.bin failed with error -2
> [9.269403] ath10k_pci :03:00.0: firmware: failed to load 
> ath10k/cal-pci-:03:00.0.bin (-2)
> [9.269404] ath10k_pci :03:00.0: Direct firmware load for 
> ath10k/cal-pci-:03:00.0.bin failed with error -2
> [9.311104] ath10k_pci :03:00.0: firmware: failed to load 
> ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
> [9.311107] ath10k_pci :03:00.0: Direct firmware load for 
> ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
> [9.33] ath10k_pci :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-

Re: ACPI Error on boot

[deloptes]

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

Re: ACPI Error on boot

[Anil Duggirala]

> 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,

Re: ACPI Error on boot

[Michael Lange]

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 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

Re: ACPI Error on boot

[Anil Duggirala]

>   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,

Re: ACPI Error on boot

[Anil Duggirala]

> 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-:03:00.0.bin (-2)
[9.269386] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:03:00.0.bin failed with error -2
[9.269403] ath10k_pci :03:00.0: firmware: failed to load 
ath10k/cal-pci-:03:00.0.bin (-2)
[9.269404] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/cal-pci-:03:00.0.bin failed with error -2
[9.311104] ath10k_pci :03:00.0: firmware: failed to load 
ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
[9.311107] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[9.33] ath10k_pci :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,

Re: ACPI Error on boot

[Anil Duggirala]

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 message.

thanks Tomas

Re: ACPI Error on boot

[songbird]

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

Re: ACPI Error on boot

[Henrique de Moraes Holschuh]

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 9346529f5960), 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

Re: ACPI Error on boot

[tomas]

-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 9346529f5960), 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-

Re: ACPI Error on boot

[Anil Duggirala]

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 9346529f5960), 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,

ACPI Error on boot

[Anil Duggirala]

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 
9346529f5960), AE_AML_MUTEX_NOT_ACQUIRED (20160831/psparse-543)
Could someone tell me what this error means,
thanks a lot,

Anil

ACPI Error at boot time

[Anil Duggirala]

I am getting two errors almost always at boot time:
ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/exmutex-393)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node 
8cf9129f5898), AE_AML_MUTEX_NOT_ACQUIRED (20160831/psparse-543)
I am dual booting Win 10 and am also getting errors about missing firmware 
(Atheros) which I believe is not related to this.
thanks for your help !

stable-backports kernel 4.14.3 ACPI errors with new Gigabyte EFI motherboard

[Geoffrey Brimhall]

Hi -

Am using debian9, just upgraded my system to a gigabyte Z370 + intel
core-i7-8700k, bootup is EFI.

System works fine, but bootup is really slowed down because of the
following ACPI errors.

In digging around, looks like the issue is gigabyte needs to fix their
bios, have put in a support request for this.

In the meantime, is there some kernel boot option I could use that might
have the bootup ignore the errors ( and hopefully speed up the boot ) ?

I originally was using the 4.9.x kernel in debian stable, but upgraded to
the 4.14.x in backports.

-geoff Brimhall

Bootup error messages ( seem to be warning that really slow the bootup ):

[0.080726] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure,
AE_NOT_FOUND (20170728/dswload2-191)
[0.080732] ACPI Error: Method parse/execution failed
\_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170728/psparse-550)
[0.080909] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure,
AE_NOT_FOUND (20170728/dswload2-191)
[0.080912] ACPI Error: Method parse/execution failed
\_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170728/psparse-550)
[4.209055] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20170728/psargs-364)
[4.209078] ACPI Error: Method parse/execution failed
\_SB.PCI0.SAT0.PRT1._GTF, AE_NOT_FOUND (20170728/psparse-550)
[4.209141] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20170728/psargs-364)
[4.209163] ACPI Error: Method parse/execution failed
\_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170728/psparse-550)
[4.211342] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20170728/psargs-364)
[4.211364] ACPI Error: Method parse/execution failed
\_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170728/psparse-550)
[4.251184] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20170728/psargs-364)
[4.251232] ACPI Error: Method parse/execution failed
\_SB.PCI0.SAT0.PRT1._GTF, AE_NOT_FOUND (20170728/psparse-550)

Re: Sense APM, problemes amb ACPI

[Pep]

Hola.

A mí me dona el mateix error a la arrencada (ACPI error, method 
parse/execution failed), pero si arrenco amb el kernel 4.8.0.1 no me 
dona cap error.


Ho has provat?.

Salut,

Pep



El 20/10/17 a les 11:38, Narcis Garcia ha escrit:

Un ordinador amb Debian 9 em dóna aquestes alertes:

ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid
Address but zero Length: 0x0050/0x0 (20160831/tbfadt-658)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 0,
using default 8 (20160831/tbfadt-708)
pmd_set_huge: Cannot satisfy [mem 0xf400-0xf420] with a
huge-page mapping due to MTRR override.
acpi LNXCPU:00: Invalid PBLK length [7]
acpi LNXCPU:01: Invalid PBLK length [7]
ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared
5, ACPI requires 4 (20160831/nsarguments-189)
ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS
(20160831/dsfield-211)
ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] (Node
8a0f930aeaa0), AE_ALREADY_EXISTS (20160831/psparse-543)

Primer he buscat la manera de deshabilitar ACPI a la BIOS, però no hi ha
opció. He provat, una a una, a afegir aquestes opcions d'arrencada:

acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off
noapic
nolapic
acpi=off

I la única que em permet arrencar sense queixa sobre ACPI és "acpi=off".
El problema és que aleshores l'ordinador no apaga en aturar el sistema.

He provat d'afegir "apm=power-off", però no funciona i ja he llegit que
el mòdul APM no s'inclou al nucli des de Debian 5.

Algú sap una alternativa per a què l'ordinador efectivament apagui sense
ACPI?

Per cert, què perdo deshabilitant ACPI?

Re: Sense APM, problemes amb ACPI

[Narcis Garcia]

Si, ja vaig actualitzar la BIOS abans de fer la instal·lació.
De moment, assumeixo els les alertes per a tenir una apagada fàcil a
l'ordinador.



__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 20/10/17 a les 12:55, Josep Lladonosa ha escrit:
> On 20 October 2017 at 11:38, Narcis Garcia <debianli...@actiu.net> wrote:
>> Un ordinador amb Debian 9 em dóna aquestes alertes:
>>
>> ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid
>> Address but zero Length: 0x0050/0x0 (20160831/tbfadt-658)
>> ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 0,
>> using default 8 (20160831/tbfadt-708)
>> pmd_set_huge: Cannot satisfy [mem 0xf400-0xf420] with a
>> huge-page mapping due to MTRR override.
>> acpi LNXCPU:00: Invalid PBLK length [7]
>> acpi LNXCPU:01: Invalid PBLK length [7]
>> ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared
>> 5, ACPI requires 4 (20160831/nsarguments-189)
>> ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS
>> (20160831/dsfield-211)
>> ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] (Node
>> 8a0f930aeaa0), AE_ALREADY_EXISTS (20160831/psparse-543)
> 
> Hi ha bios amb "bugs". Abans de provar coses recomanen actualitzar la
> bios a la darrera versió (m'ha resolt situacions similars en màquines
> antigues). Val a dir que de vegades apareixen avisos de coses que no
> resten funcionalitat al sistema, és a dir, que els avisos es poden
> obviar (si funciona, és clar).
> 
> 
>>
>> Primer he buscat la manera de deshabilitar ACPI a la BIOS, però no hi ha
>> opció. He provat, una a una, a afegir aquestes opcions d'arrencada:
>>
>> acpi=ht
>> pci=noacpi
>> acpi=noirq
>> pnpacpi=off
>> noapic
>> nolapic
>> acpi=off
>>
>> I la única que em permet arrencar sense queixa sobre ACPI és "acpi=off".
>> El problema és que aleshores l'ordinador no apaga en aturar el sistema.
>>
>> He provat d'afegir "apm=power-off", però no funciona i ja he llegit que
>> el mòdul APM no s'inclou al nucli des de Debian 5.
>>
>> Algú sap una alternativa per a què l'ordinador efectivament apagui sense
>> ACPI?
>>
>> Per cert, què perdo deshabilitant ACPI?
>>
>> --
>>
>>
>> __
>> I'm using this express-made address because personal addresses aren't masked 
>> enough at this mail public archive. Public archive administrator should fix 
>> this against automated addresses collectors.
>>
> 
> 
> 

Re: Sense APM, problemes amb ACPI

[Narcis Garcia]

$ apt search linux-image-4.8
No em troba res. I prefereixo utilitzar paquets mantinguts al repositori
de Debian, per si sorgeixen altres coses a resoldre.



__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.

El 20/10/17 a les 12:51, Pep ha escrit:
> Hola.
> 
> A mí me dona el mateix error a la arrencada (ACPI error, method
> parse/execution failed), pero si arrenco amb el kernel 4.8.0.1 no me
> dona cap error.
> 
> Ho has provat?.
> 
> Salut,
> 
> Pep
> 
> 
> 
> El 20/10/17 a les 11:38, Narcis Garcia ha escrit:
>> Un ordinador amb Debian 9 em dóna aquestes alertes:
>>
>> ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid
>> Address but zero Length: 0x0050/0x0 (20160831/tbfadt-658)
>> ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 0,
>> using default 8 (20160831/tbfadt-708)
>> pmd_set_huge: Cannot satisfy [mem 0xf400-0xf420] with a
>> huge-page mapping due to MTRR override.
>> acpi LNXCPU:00: Invalid PBLK length [7]
>> acpi LNXCPU:01: Invalid PBLK length [7]
>> ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared
>> 5, ACPI requires 4 (20160831/nsarguments-189)
>> ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS
>> (20160831/dsfield-211)
>> ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] (Node
>> 8a0f930aeaa0), AE_ALREADY_EXISTS (20160831/psparse-543)
>>
>> Primer he buscat la manera de deshabilitar ACPI a la BIOS, però no hi ha
>> opció. He provat, una a una, a afegir aquestes opcions d'arrencada:
>>
>> acpi=ht
>> pci=noacpi
>> acpi=noirq
>> pnpacpi=off
>> noapic
>> nolapic
>> acpi=off
>>
>> I la única que em permet arrencar sense queixa sobre ACPI és "acpi=off".
>> El problema és que aleshores l'ordinador no apaga en aturar el sistema.
>>
>> He provat d'afegir "apm=power-off", però no funciona i ja he llegit que
>> el mòdul APM no s'inclou al nucli des de Debian 5.
>>
>> Algú sap una alternativa per a què l'ordinador efectivament apagui sense
>> ACPI?
>>
>> Per cert, què perdo deshabilitant ACPI?
>>
> 

Sense APM, problemes amb ACPI

[Narcis Garcia]

Un ordinador amb Debian 9 em dóna aquestes alertes:

ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid
Address but zero Length: 0x0050/0x0 (20160831/tbfadt-658)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 0,
using default 8 (20160831/tbfadt-708)
pmd_set_huge: Cannot satisfy [mem 0xf400-0xf420] with a
huge-page mapping due to MTRR override.
acpi LNXCPU:00: Invalid PBLK length [7]
acpi LNXCPU:01: Invalid PBLK length [7]
ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared
5, ACPI requires 4 (20160831/nsarguments-189)
ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS
(20160831/dsfield-211)
ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] (Node
8a0f930aeaa0), AE_ALREADY_EXISTS (20160831/psparse-543)

Primer he buscat la manera de deshabilitar ACPI a la BIOS, però no hi ha
opció. He provat, una a una, a afegir aquestes opcions d'arrencada:

acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off
noapic
nolapic
acpi=off

I la única que em permet arrencar sense queixa sobre ACPI és "acpi=off".
El problema és que aleshores l'ordinador no apaga en aturar el sistema.

He provat d'afegir "apm=power-off", però no funciona i ja he llegit que
el mòdul APM no s'inclou al nucli des de Debian 5.

Algú sap una alternativa per a què l'ordinador efectivament apagui sense
ACPI?

Per cert, què perdo deshabilitant ACPI?

-- 


__
I'm using this express-made address because personal addresses aren't masked 
enough at this mail public archive. Public archive administrator should fix 
this against automated addresses collectors.

Re: Problemas con ACPI

[Quijote Libre]

Muchísimas gracias Rafael, ha quedado resulto con tus indicaciones.

Un saludo


El 09/10/17 a las 09:47, Rafael Ruiz Gonzalez escribió:




El 18/09/17 a las 20:43, Quijote Libre escribió:


Buenas trades

Estoy con Debian statble con escritorio mate, sólo con los 
repositorios main y al arrancar el equipo recibo errores de ACPI, os 
pego la salida de consola:



$ sudo dmesg | grep ACPI | grep -i error
[sudo] password for asim:
[    1.745663] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[    1.745942] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT1._GTF] (Node 9dd6160c0848), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.746370] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[    1.746644] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.747865] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[    1.748137] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT0._GTF] (Node 9dd6160c03c0), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.748550] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[    1.748823] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.750535] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[    1.750807] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT0._GTF] (Node 9dd6160c03c0), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.780632] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[    1.780906] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT1._GTF] (Node 9dd6160c0848), AE_NOT_FOUND 
(20160831/psparse-543)
[ 1800.226267] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[ 1800.226279] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[ 1800.227574] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[ 1800.227582] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[15760.568857] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[15760.568866] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[15760.570968] ACPI Error: [DSSP] Namespace lookup failure, 
AE_NOT_FOUND (20160831/psargs-359)
[15760.570977] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)


Tras bucear en la Web sólo he encontrado una solución que funciona 
que es incluir en la carga del kernel la opción acpi=off


Mi problema es que al hacerlo el apagado del equipo empieza a no 
funcionar correctamente y ya no sé cómo resolverlo.


¿Alguna sugerencia?

Gracias


--
Quijote Libre

Usuario GNU/Linux: #609825
GNUsocial: quitter.se/quijotelibre
Diáspora: quijoteli...@joindiaspora.com
Web: http://quijotelibre.com/




parece ser que con el parámetro libata.noacpi=1, al arrancar el 
kernel, deja de emitir errores de ACPI, pero lo que no se realmente es 
si, como dicen, es un fallo del firmware de la placa base o si 
realmente es un problema de kernel para ACPI, o quizás la comunicación 
entre ambos, pero a mi me ha dejado de emitir errores en ACPI y 
arranca y cierra con normalidad el sistema.


un saludo.

Re: Problemas con ACPI

[Rafael Ruiz Gonzalez]

El 18/09/17 a las 20:43, Quijote Libre escribió:

Buenas trades

Estoy con Debian statble con escritorio mate, sólo con los repositorios main y 
al arrancar el equipo recibo errores de ACPI, os pego la salida de consola:


$ sudo dmesg | grep ACPI | grep -i error
[sudo] password for asim:
[1.745663] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[1.745942] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT1._GTF] (Node 9dd6160c0848), AE_NOT_FOUND 
(20160831/psparse-543)
[1.746370] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[1.746644] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[1.747865] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[1.748137] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT0._GTF] (Node 9dd6160c03c0), AE_NOT_FOUND 
(20160831/psparse-543)
[1.748550] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[1.748823] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[1.750535] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[1.750807] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT0._GTF] (Node 9dd6160c03c0), AE_NOT_FOUND 
(20160831/psparse-543)
[1.780632] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[1.780906] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT1._GTF] (Node 9dd6160c0848), AE_NOT_FOUND 
(20160831/psparse-543)
[ 1800.226267] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[ 1800.226279] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[ 1800.227574] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[ 1800.227582] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[15760.568857] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[15760.568866] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[15760.570968] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[15760.570977] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)


Tras bucear en la Web sólo he encontrado una solución que funciona que es 
incluir en la carga del kernel la opción acpi=off

Mi problema es que al hacerlo el apagado del equipo empieza a no funcionar 
correctamente y ya no sé cómo resolverlo.

¿Alguna sugerencia?

Gracias


--
Quijote Libre

Usuario GNU/Linux: #609825
GNUsocial: quitter.se/quijotelibre
Diáspora: quijoteli...@joindiaspora.com<mailto:quijoteli...@joindiaspora.com>
Web: http://quijotelibre.com/


parece ser que con el parámetro libata.noacpi=1, al arrancar el kernel, deja de 
emitir errores de ACPI, pero lo que no se realmente es si, como dicen, es un 
fallo del firmware de la placa base o si realmente es un problema de kernel 
para ACPI, o quizás la comunicación entre ambos, pero a mi me ha dejado de 
emitir errores en ACPI y arranca y cierra con normalidad el sistema.

un saludo.

Problemas con ACPI

[Quijote Libre]

Buenas trades

Estoy con Debian statble con escritorio mate, sólo con los repositorios 
main y al arrancar el equipo recibo errores de ACPI, os pego la salida 
de consola:



$ sudo dmesg | grep ACPI | grep -i error
[sudo] password for asim:
[    1.745663] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[    1.745942] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT1._GTF] (Node 9dd6160c0848), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.746370] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[    1.746644] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.747865] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[    1.748137] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT0._GTF] (Node 9dd6160c03c0), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.748550] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[    1.748823] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.750535] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[    1.750807] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT0._GTF] (Node 9dd6160c03c0), AE_NOT_FOUND 
(20160831/psparse-543)
[    1.780632] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[    1.780906] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT1._GTF] (Node 9dd6160c0848), AE_NOT_FOUND 
(20160831/psparse-543)
[ 1800.226267] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[ 1800.226279] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[ 1800.227574] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[ 1800.227582] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[15760.568857] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[15760.568866] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)
[15760.570968] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND 
(20160831/psargs-359)
[15760.570977] ACPI Error: Method parse/execution failed 
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9dd6160c09b0), AE_NOT_FOUND 
(20160831/psparse-543)


Tras bucear en la Web sólo he encontrado una solución que funciona que 
es incluir en la carga del kernel la opción acpi=off


Mi problema es que al hacerlo el apagado del equipo empieza a no 
funcionar correctamente y ya no sé cómo resolverlo.


¿Alguna sugerencia?

Gracias


--
Quijote Libre

Usuario GNU/Linux: #609825
GNUsocial: quitter.se/quijotelibre
Diáspora: quijoteli...@joindiaspora.com
Web: http://quijotelibre.com/

Re: "ACPI error" depuis passage à Stretch

[Stephane Ascoet]

Le 12/07/2017 à 21:23, antoine.sobocinski a écrit :

Bonsoir à tous.

Mon rapport de bogue a été clôturé. Voici la réponse du mainteneur (en
anglais bien sûr) :


Bonjour, contrairement a une pratique generale, "cloturer" ne peut pas 
etre utilise dans ce type de 
cas(<http://www.academie-francaise.fr/cloturer-la-seance>) et 
visiblement tu as depose le bug au mauvais endroit: aupres d'un paquet 
permettant d'effectuer des actions en se basant sur ACPI plutot qu'au 
niveau de la gestion ACPI en elle meme, qui se trouve dans le noyau.

--
Bien cordialement, Stephane Ascoet

Re: "ACPI error" depuis passage à Stretch

[antoine.sobocinski]

Bonsoir à tous.

Mon rapport de bogue a été clôturé. Voici la réponse du mainteneur (en
anglais bien sûr) :

>This may be a kernel problem, or a hardware one (which to me looks most
>likely), but certainly not related to the tool acpi you reported it
>against. Therefore I close the report.



Le 06/07/2017 à 21:46, Gaëtan PERRIER a écrit :
> Le Thu, 6 Jul 2017 10:35:44 +0200
> Alain Rpnpif <rpn...@free.fr> a écrit:
> 
>> Le  5 juillet 2017, Benoit B a écrit :
>>
>>> Idem pour moi,
>>>
>>> ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond
>>> end of object (length 0x5) (20160831/exoparg2-427)
>>> [   14.235257] ACPI Error: Method parse/execution failed
>>> [\_SB.PCI0.GFX0._DOD] (Node 9317bb0ab500), AE_AML_PACKAGE_LIMIT
>>> (20160831/psparse-543)
>>> [   14.235269] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _DOD
>>> (20160831/video-1254)
>>
>> Pour moi aussi sur une carte MSI avec microprocesseur AMD A4-5300 APU,
>> récente.
>>
>> Je n'ai pas remarqué d'autres dysfonctionnements liés à cette erreur. Je
>> suis sous Jessie-backports avec pratiquement le même noyau que Sketch
>> (4.9).
>>
>> -- 
>> Alain Rpnpif
> 
> De même de mon côté sur une ASUS P8P67-LE
> 
> 
> [1.505990] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20170119/psargs-363) [1.506092] ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT1._GTF] (Node 9fb48e0c5780), AE_NOT_FOUND
> (20170119/psparse-543) [1.506282] ACPI Error: [DSSP] Namespace lookup
> failure, AE_NOT_FOUND (20170119/psargs-363) [1.506382] ACPI Error: Method
> parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node 9fb48e0c5aa0),
> AE_NOT_FOUND (20170119/psparse-543) [1.506530] ata5.00: ATAPI: PLEXTOR
> DVDR   PX-880SA, 1.10, max UDMA/100 [1.506552] ata7: SATA link down
> (SStatus 0 SControl 300) [1.506577] ata6: SATA link up 3.0 Gbps (SStatus
> 123 SControl 300) [1.506593] ata8: SATA link down (SStatus 0 SControl 300)
> [1.506603] ata4.00: ATA-9: C300-CTFDDAC064MAG, 0007, max UDMA/100
> [1.506605] ata4.00: 125045424 sectors, multi 16: LBA48 NCQ (depth 31/32),
> AA [1.506967] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20170119/psargs-363) [1.507067] ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT1._GTF] (Node 9fb48e0c5780), AE_NOT_FOUND
> (20170119/psparse-543) [1.507340] ata4.00: configured for UDMA/100
> [1.507487] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20170119/psargs-363) [1.507597] ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT2._GTF] (Node 9fb48e0c5aa0), AE_NOT_FOUND
> (20170119/psparse-543) [1.507748] ata5.00: configured for UDMA/100
> [1.507797] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20170119/psargs-363) [1.507896] ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT3._GTF] (Node 9fb48e0c5b68), AE_NOT_FOUND
> (20170119/psparse-543) [1.508331] ata6.00: ATA-8: TOSHIBA DT01ACA200,
> MX4OABB0, max UDMA/133 [1.508333] ata6.00: 3907029168 sectors, multi 16:
> LBA48 NCQ (depth 31/32), AA [1.509518] ACPI Error: [DSSP] Namespace lookup
> failure, AE_NOT_FOUND (20170119/psargs-363) [1.509617] ACPI Error: Method
> parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node 9fb48e0c5b68),
> AE_NOT_FOUND (20170119/psparse-543) [1.510159] ata6.00: configured for
> UDMA/133 [1.510770] ata10: SATA link down (SStatus 0 SControl 330)
> [1.514582] ata9: SATA link down (SStatus 0 SControl 330) [1.515881]
> ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [1.516251] ACPI
> Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
> [1.516350] ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT0._GTF] (Node 9fb48e0c55f0), AE_NOT_FOUND
> (20170119/psparse-543) [1.516498] ata3.00: supports DRM functions and may
> not be fully accessible [1.517477] ata3.00: ATA-10:
> Crucial_CT250MX200SSD1, MU04, max UDMA/133 [1.517479] ata3.00: 488397168
> sectors, multi 16: LBA48 NCQ (depth 31/32), AA [1.518769] ACPI Error:
> [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
> [1.518869] ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT0._GTF] (Node 9fb48e0c55f0), AE_NOT_FOUND
> (20170119/psparse-543)
> 
> A+
> 
> Gaëtan
> 

Re: "ACPI error" depuis passage à Stretch

[Gaëtan PERRIER]

Le Thu, 6 Jul 2017 10:35:44 +0200
Alain Rpnpif <rpn...@free.fr> a écrit:

> Le  5 juillet 2017, Benoit B a écrit :
> 
> > Idem pour moi,
> > 
> > ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond
> > end of object (length 0x5) (20160831/exoparg2-427)
> > [   14.235257] ACPI Error: Method parse/execution failed
> > [\_SB.PCI0.GFX0._DOD] (Node 9317bb0ab500), AE_AML_PACKAGE_LIMIT
> > (20160831/psparse-543)
> > [   14.235269] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _DOD
> > (20160831/video-1254)
> 
> Pour moi aussi sur une carte MSI avec microprocesseur AMD A4-5300 APU,
> récente.
> 
> Je n'ai pas remarqué d'autres dysfonctionnements liés à cette erreur. Je
> suis sous Jessie-backports avec pratiquement le même noyau que Sketch
> (4.9).
> 
> -- 
> Alain Rpnpif

De même de mon côté sur une ASUS P8P67-LE


[1.505990] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20170119/psargs-363) [1.506092] ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT1._GTF] (Node 9fb48e0c5780), AE_NOT_FOUND
(20170119/psparse-543) [1.506282] ACPI Error: [DSSP] Namespace lookup
failure, AE_NOT_FOUND (20170119/psargs-363) [1.506382] ACPI Error: Method
parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node 9fb48e0c5aa0),
AE_NOT_FOUND (20170119/psparse-543) [1.506530] ata5.00: ATAPI: PLEXTOR
DVDR   PX-880SA, 1.10, max UDMA/100 [1.506552] ata7: SATA link down
(SStatus 0 SControl 300) [1.506577] ata6: SATA link up 3.0 Gbps (SStatus
123 SControl 300) [1.506593] ata8: SATA link down (SStatus 0 SControl 300)
[1.506603] ata4.00: ATA-9: C300-CTFDDAC064MAG, 0007, max UDMA/100
[    1.506605] ata4.00: 125045424 sectors, multi 16: LBA48 NCQ (depth 31/32),
AA [1.506967] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20170119/psargs-363) [1.507067] ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT1._GTF] (Node 9fb48e0c5780), AE_NOT_FOUND
(20170119/psparse-543) [1.507340] ata4.00: configured for UDMA/100
[1.507487] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20170119/psargs-363) [1.507597] ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT2._GTF] (Node 9fb48e0c5aa0), AE_NOT_FOUND
(20170119/psparse-543) [1.507748] ata5.00: configured for UDMA/100
[1.507797] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20170119/psargs-363) [1.507896] ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT3._GTF] (Node 9fb48e0c5b68), AE_NOT_FOUND
(20170119/psparse-543) [1.508331] ata6.00: ATA-8: TOSHIBA DT01ACA200,
MX4OABB0, max UDMA/133 [1.508333] ata6.00: 3907029168 sectors, multi 16:
LBA48 NCQ (depth 31/32), AA [1.509518] ACPI Error: [DSSP] Namespace lookup
failure, AE_NOT_FOUND (20170119/psargs-363) [1.509617] ACPI Error: Method
parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node 9fb48e0c5b68),
AE_NOT_FOUND (20170119/psparse-543) [1.510159] ata6.00: configured for
UDMA/133 [1.510770] ata10: SATA link down (SStatus 0 SControl 330)
[1.514582] ata9: SATA link down (SStatus 0 SControl 330) [1.515881]
ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [1.516251] ACPI
Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[1.516350] ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT0._GTF] (Node 9fb48e0c55f0), AE_NOT_FOUND
(20170119/psparse-543) [1.516498] ata3.00: supports DRM functions and may
not be fully accessible [1.517477] ata3.00: ATA-10:
Crucial_CT250MX200SSD1, MU04, max UDMA/133 [    1.517479] ata3.00: 488397168
sectors, multi 16: LBA48 NCQ (depth 31/32), AA [1.518769] ACPI Error:
[DSSP] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[1.518869] ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT0._GTF] (Node 9fb48e0c55f0), AE_NOT_FOUND
(20170119/psparse-543)

A+

Gaëtan


pgpDpQSRc5nXT.pgp
Description: PGP signature

Re: "ACPI error" depuis passage à Stretch

[Alain Rpnpif]

Le  5 juillet 2017, Benoit B a écrit :

> Idem pour moi,
> 
> ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond
> end of object (length 0x5) (20160831/exoparg2-427)
> [   14.235257] ACPI Error: Method parse/execution failed
> [\_SB.PCI0.GFX0._DOD] (Node 9317bb0ab500), AE_AML_PACKAGE_LIMIT
> (20160831/psparse-543)
> [   14.235269] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _DOD
> (20160831/video-1254)

Pour moi aussi sur une carte MSI avec microprocesseur AMD A4-5300 APU,
récente.

Je n'ai pas remarqué d'autres dysfonctionnements liés à cette erreur. Je
suis sous Jessie-backports avec pratiquement le même noyau que Sketch
(4.9).

-- 
Alain Rpnpif

Re: "ACPI error" depuis passage à Stretch

[Benoit B]

Idem pour moi,

ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond
end of object (length 0x5) (20160831/exoparg2-427)
[   14.235257] ACPI Error: Method parse/execution failed
[\_SB.PCI0.GFX0._DOD] (Node 9317bb0ab500), AE_AML_PACKAGE_LIMIT
(20160831/psparse-543)
[   14.235269] ACPI Exception: AE_AML_PACKAGE_LIMIT, Evaluating _DOD
(20160831/video-1254)

--
Benoit


Le 2 juillet 2017 à 17:40, antoine.sobocinski
<antoine.sobocin...@laposte.net> a écrit :
> Bonjour à tous.
>
> Depuis la mise à niveau vers Stretch (en tout cas, je ne me souviens pas
> de les avoir vu auparavant),  j'ai une série de messages qui
> apparaissent systématiquement à l'allumage de mon ordinateur, et plus
> précisément après avoir sélectionné Debian (je suis en dual-boot avec
> windows 7).
>
> Voici les messages extraits du journal :
>
> ACPI Error: Evaluating _BCM failed (20160831/video-354)
> ACPI Error: Method parse/execution failed [\_SB.PCI0.VGA.LCDD._BCM]
> (Node 8eb9fb0af668), AE_AML_BUFFER_LIMIT (20160831/psparse-543)
> ACPI Error: Method parse/execution failed [\_SB.PCI0.SBRG.EC0.STBR]
> (Node 8eb9fb0b70a0), AE_AML_BUFFER_LIMIT (20160831/psparse-543)
> ACPI Exception: AE_AML_BUFFER_LIMIT, Index (0x0005D) is beyond end
>
>
> Quelqu'un pourrait-il me dire s'il s'agit d'un problème important et
> s'il me faudrait envoyer un rapport de bogue (au mainteneur du paquet
> ACPI ou un autre ?)
>
> Pour information, voici ma configuration (extraction du rapport établi
> avec debian-bug de emacs) :
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
> LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages acpi depends on:
> ii  libc6  2.24-11+deb9u1
>
> acpi recommends no packages.
>
> acpi suggests no packages.of object (length 0x10) (20160831/exoparg2-427)
>
> Merci d'avance pour votre aide.
>

Re: Thinkpad R40e can't boot Debian 9.0.0 netinst image without acpi=off

[deloptes]

Olivier F. R. Dierick wrote:

> acpi=off

I don't know about the kernel

http://www.thinkwiki.org/wiki/Category:R40e

but you better check if your ATI will be supported with the recent X
server ;)



regards

Thinkpad R40e can't boot Debian 9.0.0 netinst image without acpi=off

[Olivier F. R. Dierick]

Hi,

I wanted to file a bug report, but I don't know which package the issue
belongs to.

The computer is a IBM Thinkpad R40e.

Currently Debian 8 is installed. Ever since Debian 8 was installed on
the harddrive I had to add acpi=off to the kernel options, otherwise the
computer does not boot. No other acpi/clock/irq option mentioned on
Internet works. Blacklisting the acpi_cpufreq or any other acpi* module
does not fix the issue.

The Debian 8 live CD image used to install the system does not have the
issue. The previous OS was Debian 7 Wheezy and it did not have the
issue.

Now I'm trying to upgrade to Debian 9 by reinstalling the system from
scratch. I've downloaded the debian 9.0.0 netinst install.

The netinst image is copied with command dd to an USB key.
The computer boots on the key and the first menu appears.
I select "Graphical Install".
The light on the USB key blinks a few minutes.
After a while, the screen goes black with a static(=not blinking) text
cursor in the corner. No disk, USB or other activity visible. No
reaction to Ctrl+Alt+DEL or any keypress. The computer is stuck in that
state and only a poweroff (hold powerbutton 4 sec) does work.

Pressing TAB in the menu when "Graphical Install" is highlighted and
adding acpi=off to the kernel options does prevent the lock and allows
the graphical installer to start.

I repeated the same steps with the Debian 8.6.0 netinst image and the
issue is not present (at least not until Debian is installed on the hard
drive).

I guess there was some change in kernel config after the Debian 8 live
cd/netinst images were built. This change prevents the default kernel
from booting on the Thinkpad R40e. This change is now part of the Debian
9.0.0 netinst image.
-- 
Olivier F. R. Dierick
o.dier...@piezo-forte.be

"ACPI error" depuis passage à Stretch

[antoine.sobocinski]

Bonjour à tous.

Depuis la mise à niveau vers Stretch (en tout cas, je ne me souviens pas
de les avoir vu auparavant),  j'ai une série de messages qui
apparaissent systématiquement à l'allumage de mon ordinateur, et plus
précisément après avoir sélectionné Debian (je suis en dual-boot avec
windows 7).

Voici les messages extraits du journal :

ACPI Error: Evaluating _BCM failed (20160831/video-354)
ACPI Error: Method parse/execution failed [\_SB.PCI0.VGA.LCDD._BCM]
(Node 8eb9fb0af668), AE_AML_BUFFER_LIMIT (20160831/psparse-543)
ACPI Error: Method parse/execution failed [\_SB.PCI0.SBRG.EC0.STBR]
(Node 8eb9fb0b70a0), AE_AML_BUFFER_LIMIT (20160831/psparse-543)
ACPI Exception: AE_AML_BUFFER_LIMIT, Index (0x0005D) is beyond end


Quelqu'un pourrait-il me dire s'il s'agit d'un problème important et
s'il me faudrait envoyer un rapport de bogue (au mainteneur du paquet
ACPI ou un autre ?)

Pour information, voici ma configuration (extraction du rapport établi
avec debian-bug de emacs) :

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages acpi depends on:
ii  libc6  2.24-11+deb9u1

acpi recommends no packages.

acpi suggests no packages.of object (length 0x10) (20160831/exoparg2-427)

Merci d'avance pour votre aide.



signature.asc
Description: OpenPGP digital signature

Re: How to Fix ACPI Error : Namespace lookup failure

[Darac Marjal]

On Thu, Apr 20, 2017 at 02:57:20AM +, 慕 冬亮 wrote:

  Dear all,

  After I reverted BIOS back to default setting, I found some following
  error messages related to ACPI:

  [    0.847234] ACPI: Thermal Zone [THM] (25 C)
  [    0.847347] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace
  lookup failure, AE_NOT_FOUND (20160831/psargs-359)
  [    0.847605] ACPI Error: Method parse/execution failed
  [\_TZ.TZ00._TMP] (Node 987b7d51dac8), AE_NOT_FOUND
  (20160831/psparse-543)
  [    0.848038] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace
  lookup failure, AE_NOT_FOUND (20160831/psargs-359)
  [    0.848240] ACPI Error: Method parse/execution failed
  [\_TZ.TZ00._TMP] (Node 987b7d51dac8), AE_NOT_FOUND
  (20160831/psparse-543)
  [    0.848524] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace
  lookup failure, AE_NOT_FOUND (20160831/psargs-359)
  [    0.848725] ACPI Error: Method parse/execution failed
  [\_TZ.TZ01._TMP] (Node 987b7d51de38), AE_NOT_FOUND
  (20160831/psparse-543)
  [    0.848998] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace
  lookup failure, AE_NOT_FOUND (20160831/psargs-359)
  [    0.849198] ACPI Error: Method parse/execution failed
  [\_TZ.TZ01._TMP] (Node 987b7d51de38), AE_NOT_FOUND
  (20160831/psparse-543)
  How to fix this problem?


My understanding is that ACPI implementations are often a bit patchy. I
suspect that, in this instance, your ACPI is either declaring that some
functions are available and not implementing them, or it's simply not
implementing standard functions.

Many OEMs don't implement ACPI as fully as, perhaps, they should. There
are stories of certain functions being unavailable unless the operating
system declares itself to be "Windows" (I believe that Linux detects
these situations and tells a white lie). Similarly, if a function is not
used in Windows (or perhaps is replaced by a driver that the OEM
provides for Windows), then the OEM may see no need to implement that
function in ACPI.

Your options as I see them are:
1. See if there is a newer BIOS revision available (or, if the OEM
ships it separately, an update to the EC [Embedded Controller]).
2. Complain to the OEM. You may get fobbed off with a "Not Supported"
excuse.
3. Report the errors to the kernel ACPI maintainer(s) in case there is
a work around.
4. Ignore the errors. (Of course, if the missing function is important,
then this may not be an option).

--
For more information, please reread.


signature.asc
Description: PGP signature

How to Fix ACPI Error : Namespace lookup failure

[慕 冬亮]

Dear all,

After I reverted BIOS back to default setting, I found some following error 
messages related to ACPI:

[0.847234] ACPI: Thermal Zone [THM] (25 C)
[0.847347] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup 
failure, AE_NOT_FOUND (20160831/psargs-359)
[0.847605] ACPI Error: Method parse/execution failed [\_TZ.TZ00._TMP] (Node 
987b7d51dac8), AE_NOT_FOUND (20160831/psparse-543)
[0.848038] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup 
failure, AE_NOT_FOUND (20160831/psargs-359)
[0.848240] ACPI Error: Method parse/execution failed [\_TZ.TZ00._TMP] (Node 
987b7d51dac8), AE_NOT_FOUND (20160831/psparse-543)
[0.848524] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup 
failure, AE_NOT_FOUND (20160831/psargs-359)
[0.848725] ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node 
987b7d51de38), AE_NOT_FOUND (20160831/psparse-543)
[0.848998] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup 
failure, AE_NOT_FOUND (20160831/psargs-359)
[0.849198] ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node 
987b7d51de38), AE_NOT_FOUND (20160831/psparse-543)

How to fix this problem?

Question on /proc/acpi/wakeup

[solitone]

Wakeup capable devices are listed in /proc/acpi/wakeup. For example, in my 
sytem I've got:

~
solitone@alan:~$ cat /proc/acpi/wakeup 
Device  S-state   Status   Sysfs node
PEG0  S3*disabled
ECS4*disabled  platform:PNP0C09:00
HDEF  S3*disabled  pci::00:1b.0
RP01  S3*disabled  pci::00:1c.0
RP02  S3*disabled  pci::00:1c.1
RP03  S3*disabled  pci::00:1c.2
ARPT  S4*enabled   pci::03:00.0
RP05  S3*disabled  pci::00:1c.4
RP06  S3*disabled  pci::00:1c.5
SPIT  S3*disabled
XHC1  S3*enabled  pci::00:14.0
ADP1  S4*disabled  platform:ACPI0003:00
LID0  S4*enabled  platform:PNP0C0D:00
~

It is possible to disable devices with e.g. 
solitone@alan:~$ sudo echo XHC1 > /proc/acpi/wakeup

However, when system reboots such settings are lost, and  /proc/acpi/wakeup is 
reset to its original content.

How does this work? What is the thing that resets /proc/acpi/wakeup to its 
standard content? What does this content depend on? What is that determines 
whether a device is enabled or disabled in the first place?

Re: intel_pstate vs acpi-cpufreq freq scale

[Julian Brooks]

After some discussion with Liquorix people (who are still not convinced by
intel_pstate)
http://techpatterns.com/forums/viewtopic.php?p=12509#12509
I'm going to try out the new 'schedutils' option with acpi-cpufreq

See how it goes eh.

Regards,

Julian

On 16 January 2017 at 23:49, Julian Brooks <jbee...@gmail.com> wrote:

> Dear Luis,
>
> Many thanks for your input and guidance here.
>
> 'Have you tried to see if this happens with debian's official kernel?'
> Doh! Of course.
> Yes I have now, and intel_pstate is active - yay.
>
> Complete newb with any kind of kernel config/tweaking/rebuilding - need to
> do some reading-up.
>
> Thanks again,
>
> Julian
>
> On 16 January 2017 at 15:03, Luis Felipe Tabera Alonso <lui...@lftabera.es
> > wrote:
>
>> On lunes, 16 de enero de 2017 1:13:09 (CET) Julian Brooks wrote:
>> > Hi all,
>>
>> Hi Julian,
>>
>> > Fresh install of Sid, with
>> > liquorix 4.9-3 (2017-01-07) x86_64 kernel (for RT audio work).
>> > Have also installed linrunner's TLP.
>>
>> Have you tried to see if this happens with debian's official kernel?
>>
>> > My understanding is that the x230's Ivy Bridge processor should make
>> use of
>> > intel_pstate for frequency scaling but I can't seem to load the kernel
>> > module at boot.
>>
>> Is it a module? At least on debian kernels, intel_pstate is inside the
>> kernel,
>> not as a separate module.
>>
>> $ grep -i pstate config-4.8.0-2-amd64
>> CONFIG_X86_INTEL_PSTATE=y
>>
>> however, on liquorix
>>
>> $ grep -i pstate config-4.9.0-3.2-liquorix-amd64
>> # CONFIG_X86_INTEL_PSTATE is not set
>>
>> So it seems that liquorix kernel has not compiled intel_pstate. So could
>> try
>> to recompile it as a module for your running kernel of rebuild liquorix
>> kernel
>> with intel_pstate support.
>>
>> Luis
>>
>
>

Re: intel_pstate vs acpi-cpufreq freq scale

[Julian Brooks]

Dear Luis,

Many thanks for your input and guidance here.

'Have you tried to see if this happens with debian's official kernel?'
Doh! Of course.
Yes I have now, and intel_pstate is active - yay.

Complete newb with any kind of kernel config/tweaking/rebuilding - need to
do some reading-up.

Thanks again,

Julian

On 16 January 2017 at 15:03, Luis Felipe Tabera Alonso 
wrote:

> On lunes, 16 de enero de 2017 1:13:09 (CET) Julian Brooks wrote:
> > Hi all,
>
> Hi Julian,
>
> > Fresh install of Sid, with
> > liquorix 4.9-3 (2017-01-07) x86_64 kernel (for RT audio work).
> > Have also installed linrunner's TLP.
>
> Have you tried to see if this happens with debian's official kernel?
>
> > My understanding is that the x230's Ivy Bridge processor should make use
> of
> > intel_pstate for frequency scaling but I can't seem to load the kernel
> > module at boot.
>
> Is it a module? At least on debian kernels, intel_pstate is inside the
> kernel,
> not as a separate module.
>
> $ grep -i pstate config-4.8.0-2-amd64
> CONFIG_X86_INTEL_PSTATE=y
>
> however, on liquorix
>
> $ grep -i pstate config-4.9.0-3.2-liquorix-amd64
> # CONFIG_X86_INTEL_PSTATE is not set
>
> So it seems that liquorix kernel has not compiled intel_pstate. So could
> try
> to recompile it as a module for your running kernel of rebuild liquorix
> kernel
> with intel_pstate support.
>
> Luis
>

Re: intel_pstate vs acpi-cpufreq freq scale

[Luis Felipe Tabera Alonso]

On lunes, 16 de enero de 2017 1:13:09 (CET) Julian Brooks wrote:
> Hi all,

Hi Julian,

> Fresh install of Sid, with
> liquorix 4.9-3 (2017-01-07) x86_64 kernel (for RT audio work).
> Have also installed linrunner's TLP.

Have you tried to see if this happens with debian's official kernel?

> My understanding is that the x230's Ivy Bridge processor should make use of
> intel_pstate for frequency scaling but I can't seem to load the kernel
> module at boot.

Is it a module? At least on debian kernels, intel_pstate is inside the kernel, 
not as a separate module.

$ grep -i pstate config-4.8.0-2-amd64
CONFIG_X86_INTEL_PSTATE=y

however, on liquorix

$ grep -i pstate config-4.9.0-3.2-liquorix-amd64
# CONFIG_X86_INTEL_PSTATE is not set

So it seems that liquorix kernel has not compiled intel_pstate. So could try 
to recompile it as a module for your running kernel of rebuild liquorix kernel 
with intel_pstate support.

Luis

intel_pstate vs acpi-cpufreq freq scale

[Julian Brooks]

Hi all,

I've got a new machine:
LENOVO ThinkPad X230 i5 23252GG
To replace my ol' trusty x61s.

Fresh install of Sid, with
liquorix 4.9-3 (2017-01-07) x86_64 kernel (for RT audio work).
Have also installed linrunner's TLP.

My understanding is that the x230's Ivy Bridge processor should make use of
intel_pstate for frequency scaling but I can't seem to load the kernel
module at boot.

TLP (and other sources) are telling me the system has acpi-cpufreq running
the frequency scaling.

Have tried adding 'intel_pstate=enable' to grub (+ update-grub), no change
(liquorix should load intel_pstate by defualt anyway, according to the
docs).
Have blacklisted the acpi-cpufreq module (which leaves me without any
scaling - unsurprisingly:).
Installed & uninstalled cpufreqtools & sysfsutils - no change either way.

And am now going round in (ever frustrating) circles with this.

Any advice gratefully received, and hope I've provided enough info - please
let me know if not.

Regards to all,

Julian