ACPI BIOS Error (bug): [SOLVED]

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
User avatar
Catchpole
Level 4
Level 4
Posts: 266
Joined: Sat Dec 24, 2011 4:15 am
Location: Leeds UK

ACPI BIOS Error (bug): [SOLVED]

Post by Catchpole »

When I start up my Desktop with Linux Mint 20.1 I get these messages:

Is this just a bug which will go away after some future update?
What is it looking for?
dmesg gives:
[ 1.011765] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.011788] fbcon: Taking over console
[ 1.011792] No Local Variables are initialized for Method [_GTF]
[ 1.011792] No Arguments are initialized for method [_GTF]
[ 1.011794] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.011802] ata5.00: ATAPI: TSSTcorp CDDVDW SH-S223B, SB01, max UDMA/100
[ 1.011855] Console: switching to colour frame buffer device 128x48
[ 1.012200] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.012208] No Local Variables are initialized for Method [_GTF]
[ 1.012209] No Arguments are initialized for method [_GTF]
[ 1.012211] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.012424] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.012430] No Local Variables are initialized for Method [_GTF]
[ 1.012431] No Arguments are initialized for method [_GTF]
[ 1.012432] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.012441] ata2.00: ATA-8: ST500DM002-1BD142, KC45, max UDMA/133
[ 1.012443] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32)
[ 1.012533] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.012539] No Local Variables are initialized for Method [_GTF]
[ 1.012540] No Arguments are initialized for method [_GTF]
[ 1.012541] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.012549] ata5.00: configured for UDMA/100
[ 1.013829] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.013892] No Local Variables are initialized for Method [_GTF]
[ 1.013893] No Arguments are initialized for method [_GTF]
[ 1.013894] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.014219] ata2.00: configured for UDMA/133
[ 1.015831] ata1.00: ATA-10: CT480BX500SSD1, M6CR022, max UDMA/133
[ 1.015833] ata1.00: 937703088 sectors, multi 1: LBA48 NCQ (depth 32), AA
[ 1.021653] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.021695] No Local Variables are initialized for Method [_GTF]
[ 1.021696] No Arguments are initialized for method [_GTF]
[ 1.021698] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
Has this got anything to do with it?
Its a warning before the Error but not flagged up on the screen on startup;
[ 0.639660] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 0.641211] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20190816/utaddress-204)
[ 0.641217] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 0.641220] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/utaddress-204)
[ 0.641223] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 0.641224] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/utaddress-204)
[ 0.641228] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 0.641229] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000051F (\LED) (20190816/utaddress-204)
[ 0.641233] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/utaddress-204)
[ 0.641237] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 0.641237] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 0.642074] libphy: r8169: probed
[ 0.642085] i801_smbus 0000:00:1f.3: enabling device (0001 -> 0003)
[ 0.642219] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[ 0.642370] r8169 0000:04:00.0 eth0: RTL8168evl/8111evl, 94:de:80:57:80:e8, XID 2c9, IRQ 29
[ 0.642372] r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 0.659537] ahci 0000:00:1f.2: version 3.0
My system details:
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop" (64bit)
Memory = 12GB

What is it and what do I need to do?
Last edited by Catchpole on Wed Feb 24, 2021 7:43 am, edited 1 time in total.
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop" (64bit)
Memory = 12GB
SimpleLinuxUser
Level 1
Level 1
Posts: 16
Joined: Tue Feb 23, 2021 9:32 pm

Re: ACPI BIOS Error (bug):

Post by SimpleLinuxUser »

I have a few acpi errors too, less than yours, but the pc is working fine.
User avatar
Catchpole
Level 4
Level 4
Posts: 266
Joined: Sat Dec 24, 2011 4:15 am
Location: Leeds UK

Re: ACPI BIOS Error (bug):

Post by Catchpole »

Hi SimpleLinuxUser,

I forgot to mention that everything is working OK.

However the startup is delayed whilst it deals with the fault so I'd like a solution to speed things up.
Being an engineer I pay attention to details and this "bug" is bugging me. I like things to be neat and tidy.
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop" (64bit)
Memory = 12GB
t42
Level 5
Level 5
Posts: 605
Joined: Mon Jan 20, 2014 6:48 pm

Re: ACPI BIOS Error (bug):

Post by t42 »

Catchpole wrote:
Wed Feb 24, 2021 3:24 am
However the startup is delayed whilst it deals with the fault so I'd like a solution to speed things up.
Being an engineer I pay attention to details.
"However the startup is delayed" - how much?

Did you check a possibility of the motherboard BIOS update?
-=t42=-
User avatar
Catchpole
Level 4
Level 4
Posts: 266
Joined: Sat Dec 24, 2011 4:15 am
Location: Leeds UK

Re: ACPI BIOS Error (bug):

Post by Catchpole »

Hi t42,

I'll have to time the delay. Timing it on the screen is easy enough but the total delay will be harder to measure.
Did you check a possibility of the motherboard BIOS update?
I don't know if I dare do a bios update but It's a thought. If anything goes wrong I can upgrade the board with a new one. :D

What problems would I have upgrading the motherboard (MB) with respect to the operating system? I wouldn't want to have to do another clean install when I've just done it recently!
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop" (64bit)
Memory = 12GB
t42
Level 5
Level 5
Posts: 605
Joined: Mon Jan 20, 2014 6:48 pm

Re: ACPI BIOS Error (bug):

Post by t42 »

Catchpole wrote:
Wed Feb 24, 2021 4:51 am
I'll have to time the delay. Timing it on the screen is easy enough but the total delay will be harder to measure.
These three commands may help

Code: Select all

systemd-analyze
systemd-analyze critical-chain
systemd-analyze blame
Catchpole wrote:
Wed Feb 24, 2021 4:51 am
What problems would I have upgrading the motherboard (MB) with respect to the operating system?
BIOS update can mess with computer on the far low level than OS. Usually motherboard is unbootable if something goes wrong and you need to prepare procedure to revert to the previews firmware.
-=t42=-
User avatar
AndyMH
Level 15
Level 15
Posts: 5939
Joined: Fri Mar 04, 2016 5:23 pm
Location: Wiltshire

Re: ACPI BIOS Error (bug):

Post by AndyMH »

Homebrew i5-8400+GTX1080 Cinnamon 19.0, 3 x Thinkpad T430 Cinnamon 19.0, i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate
User avatar
Catchpole
Level 4
Level 4
Posts: 266
Joined: Sat Dec 24, 2011 4:15 am
Location: Leeds UK

Re: ACPI BIOS Error (bug):

Post by Catchpole »

Hi t42,

The results of your commands are:

Code: Select all

user@computer:~$ systemd-analyze
Startup finished in 3.454s (kernel) + 3.083s (userspace) = 6.537s 
graphical.target reached after 3.049s in userspace
user@computer:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @3.049s
└─multi-user.target @3.049s
  └─networkd-dispatcher.service @2.310s +738ms
    └─basic.target @2.263s
      └─sockets.target @2.263s
        └─uuidd.socket @2.263s
          └─sysinit.target @2.260s
            └─apparmor.service @2.055s +97ms
              └─local-fs.target @2.054s
                └─boot-efi.mount @2.040s +13ms
                  └─systemd-fsck@dev-disk-by\x2duuid-9934\x2d6DD8.service @1.781s +258ms
                    └─dev-disk-by\x2duuid-9934\x2d6DD8.device @1.780s
user@computer:~$ systemd-analyze blame
1.811s apt-daily-upgrade.service                            
1.434s dev-sda2.device                                      
 738ms networkd-dispatcher.service                          
 563ms udisks2.service                                      
 374ms accounts-daemon.service                              
 306ms ubuntu-system-adjustments.service                    
 304ms systemd-journal-flush.service                        
 258ms systemd-fsck@dev-disk-by\x2duuid-9934\x2d6DD8.service
 248ms avahi-daemon.service                                 
 237ms NetworkManager.service                               
 230ms ufw.service                                          
 229ms systemd-logind.service                               
 225ms upower.service                                       
 223ms polkit.service                                       
 222ms ModemManager.service                                 
 205ms keyboard-setup.service                               
 190ms gpu-manager.service                                  
 183ms thermald.service                                     
 182ms e2scrub_reap.service                                 
 177ms systemd-journald.service                             
 175ms wpa_supplicant.service                               
 166ms systemd-udevd.service                                
 158ms systemd-modules-load.service                         
 152ms systemd-udev-trigger.service                         
 151ms systemd-resolved.service  
It seems to be just a matter of mili-seconds delay to the overall progress.
So after reading the link from AndyMH, I think I'll just leave it as it is and avoid making a mistake in the pursuit of a triviality that makes things worse.

The result of the inquiry is: leave it alone. I think that means [SOLVED]. (Or does it?)
I'll mark it as [SOLVED]
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop" (64bit)
Memory = 12GB
User avatar
Catchpole
Level 4
Level 4
Posts: 266
Joined: Sat Dec 24, 2011 4:15 am
Location: Leeds UK

Re: ACPI BIOS Error (bug): [SOLVED]

Post by Catchpole »

Hi t42,
Catchpole wrote: ↑
Wed Feb 24, 2021 9:51 am
I'll have to time the delay. Timing it on the screen is easy enough but the total delay will be harder to measure.
As I didn't time the startup when the system was working OK I can only make a guess as to the total delay.
However, when I switched the computer on I used to do a couple of things and by the time I had finished them it was jut the right time to sign in.
So from the time of switching on and after doing the same couple of things, the total time delay now is about 20 second later to get to the sign in screen.

As for the bios upgrade:
There is only one upgrade from the "F1" bios version to version "F3c" but its a "beta".
F3c
2‎.85 MB
2‎014/03/04
Download

Beta BIOS
Improve High-End Display card compatibility

==============================================

F2
2‎.82 MB
2‎013/03/19
Download

First Release

So unfortunately there is still a problem and I was a little hasty accepting the data from the error log and in adding the [SOLVED] marker!
You live and learn.

I've set "ACHI" and UEFI, turned off "Secure Boot" and made sure "CSM" is disabled.

If I've done all I can with the bios I guess I'll have to live with it or get a new motherboard. (unless there's another solution)
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop" (64bit)
Memory = 12GB
User avatar
Catchpole
Level 4
Level 4
Posts: 266
Joined: Sat Dec 24, 2011 4:15 am
Location: Leeds UK

Re: ACPI BIOS Error (bug): [SOLVED]

Post by Catchpole »

A re-run of the commands suggested by: t42

Code: Select all

systemd-analyze
systemd-analyze critical-chain
systemd-analyze blame
gives:

Code: Select all

28th Feb 2021 11:39hrs
user@computer:~$ systemd-analyze
Startup finished in 3.302s (kernel) + 35.977s (userspace) = 39.279s 
graphical.target reached after 28.153s in userspace
user@computer:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @28.153s
└─multi-user.target @28.153s
  └─postfix.service @28.146s +6ms
    └─postfix@-.service @24.114s +4.029s
      └─network-online.target @24.107s
        └─NetworkManager-wait-online.service @17.438s +6.668s
          └─NetworkManager.service @17.169s +266ms
            └─dbus.service @17.165s
              └─basic.target @17.147s
                └─sockets.target @17.147s
                  └─uuidd.socket @17.147s
                    └─sysinit.target @17.143s
                      └─apparmor.service @17.030s +112ms
                        └─local-fs.target @17.029s
                          └─run-user-1000-gvfs.mount @35.402s
                            └─run-user-1000.mount @32.935s
                              └─swap.target @524ms
                                └─swapfile.swap @391ms +133ms
                                  └─systemd-remount-fs.service @361ms +28ms
                                    └─systemd-journald.socket @343ms
user@computer:~$ systemd-analyze blame
18.731s fstrim.service                                       
16.606s dev-sda2.device                                      
 6.668s NetworkManager-wait-online.service                   
 4.029s postfix@-.service                                    
 1.056s man-db.service                                       
  925ms networkd-dispatcher.service                          
  757ms udisks2.service                                      
  538ms logrotate.service                                    
  511ms apt-daily-upgrade.service                            
  485ms ubuntu-system-adjustments.service                    
  482ms apt-daily.service                                    
  451ms systemd-logind.service                               
  449ms accounts-daemon.service                              
  349ms systemd-journal-flush.service                        
  323ms networking.service                                   
  290ms ModemManager.service                                 
  266ms NetworkManager.service                               
  260ms fwupd-refresh.service                                
  245ms avahi-daemon.service                                 
  238ms polkit.service                                       
  237ms systemd-resolved.service                             
  228ms ufw.service                                          
  214ms upower.service 
This gives much longer delay than when it was first run.
I can't understand why it didn't pick up the time delay in the first instance.

Does the fstrim.service take 18 seconds to complete?

I've done some reading around but can't find a solution.
Can anyone point me in the right direction?
Last edited by Catchpole on Mon Mar 01, 2021 3:23 am, edited 1 time in total.
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop" (64bit)
Memory = 12GB
User avatar
Catchpole
Level 4
Level 4
Posts: 266
Joined: Sat Dec 24, 2011 4:15 am
Location: Leeds UK

Re: ACPI BIOS Error (bug): [SOLVED]

Post by Catchpole »

I've found the cause of the problem at last!!

It was my graphics card - nvidia GEFORCE 210 That was causing the conflict.
Using the "Driver Manager" I changed the driver from the "recommended" proprietary driver to the Ubuntu one offered instead.
Now its back to its normal speed that I had before with the Mint 19.1 Operating System.
Perhaps Mint 20.1 will catch up with some future updates in the near future.

Thanks to everyone for your help.
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop" (64bit)
Memory = 12GB
Post Reply

Return to “Installation & Boot”