Description of problem: Dell Precision 5530 ACPI errors With or w/o Dell WD19TB thunderbolt docking. Bios: # fwupdmgr get-updates No upgrades for Thunderbolt controller in Dell dock, current is 40.00: 40.00=same No upgrades for RTS5487 in Dell dock, current is 01.47: 01.47=same No upgrades for WD19TB, current is 01.00.00.00: 01.00.00.00=same No upgrades for Package level of Dell dock, current is 01.00.04.01: 01.00.04.01=same No upgrades for VMM5331 in Dell dock, current is 05.03.10: 05.03.10=same No upgrades for RTS5413 in Dell dock, current is 01.21: 01.21=same No upgrades for Precision 5530 System Firmware, current is 0.1.12.0: 0.1.11.2=older, 0.1.10.1=older, 0.1.8.1=older, 0.1.7.0=older, 0.1.6.0=older Version-Release number of selected component (if applicable): Linux localhost 5.2.14-200.fc30.x86_64 #1 SMP Tue Sep 10 12:17:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux How reproducible: When pushing LCD DIMM up or down buttons (F11 and F10). Steps to Reproduce: 1. Boot system and pushing DIMM up or down buttons 2. 3. Actual results: Pushing ALT+F12 for DIMM up [ 2201.346558] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20190509/psargs-330) [ 2201.346576] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2201.346933] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2201.347142] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2201.347398] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2201.347621] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2201.347755] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20190509/psparse-529) Pushing ALT-F11 for DIMM LCD down [ 2218.707807] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20190509/psargs-330) [ 2218.707824] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2218.708168] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2218.708489] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2218.708660] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2218.708936] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20190509/psparse-529) [ 2218.709101] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20190509/psparse-529) Expected results: No errors Additional info: Forked out these as it is clearly different to errors at boot seen bug # 1610727
Question, do the brightness up/down keys properly control the brightness? (despite the errors) Unfortunately ACPI errors like these are somewhat common and typically they are completely harmless. So unless you are seeing adverse side-effects you can safely ignore these errors.
(In reply to Hans de Goede from comment #1)> > Unfortunately ACPI errors like these are somewhat common and typically they > are completely harmless. So unless you are seeing adverse side-effects you > can safely ignore these errors. The problem is these errors pollute dmesg logs and spam root's tty. You're quite right these errors are firmware errors but maybe someone from Dell will actually address these bugs? The issue has been around in ALL Dell systems since xx10 series and is probably present in all 55x0, 75x0, and 77x0 precision mobile models. I had this issue in both 7510 and have it in 5540.
Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=204251
Hans, yes it adjusts the brightness of the internal display. Dell has Ubuntu 18.04LTS as an option for these laptops. I would expect that they would fix it and push it back to the community. I'm probably naive, but hopeful. https://bartongeorge.io/2019/05/29/ladies-and-gentlemen-introducing-the-dell-precision-5540-7540-and-7540-developer-editions/
Ubuntu is not fixing Dell's BIOS. They may create patches that tell the kernel to ease up on those specific kinds of messages, but I doubt it'll be allowed by the upstream as it's too hardware specific. The upstream bug even specifies what exactly in should be fixed in the ACPI code.
Dell Precision 7540 that was bought with Ubuntu on it and now has Arch stable with the newest stable kernel has the same errors when pushing the fn+ arrow up or arrow down. Operating System: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.7-arch1-2-ARCH OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM This is only from like two presses of the button. [36730.508093] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20190703/psargs-330) [36730.508118] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36730.508129] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36730.508139] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36730.508148] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36730.508157] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36730.508167] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36731.801310] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20190703/psargs-330) [36731.801335] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36731.801347] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36731.801356] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36731.801365] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36731.801374] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36731.801670] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36732.307266] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20190703/psargs-330) [36732.307272] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36732.307274] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36732.307276] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36732.307278] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36732.307280] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20190703/psparse-529) [36732.307282] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days