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
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: Question regarding an ACPI BIOS Error (bug)
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)
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)
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)
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)
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)
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)
-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: Re: ACPI BIOS ERROR
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
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: ACPI BIOS ERROR
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
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
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
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
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
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
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
steve wrote: > Should I open a ticket in the BTS? you have latest BIOS installed?
ACPI BIOS ERROR
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
