[SOLVED] Bios Error

wayne1937 · 05-22-2021, 08:26 PM

This error does not seem to cause any problem with machine boot up or program operation. Just curious as to why it occurs !

Below is system information.

Code:

System:    Kernel: 5.8.0-53-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 4.8.6 
           wm: muffin dm: LightDM Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:   Type: Desktop System: Dell product: Inspiron 3471 v: N/A serial: <filter> Chassis: 
           type: 3 serial: <filter> 
           Mobo: Dell model: 02GDWG v: A00 serial: <filter> UEFI: Dell v: 1.0.2 date: 09/25/2019 
CPU:       Topology: Dual Core model: Intel Pentium Gold G5420 bits: 64 type: MT MCP 
           arch: Kaby Lake rev: A L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 30399 
           Speed: 3800 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 3800 2: 3800 3: 3800 
           4: 3800 
Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e90 
           Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 610 (CFL GT1) v: 4.6 Mesa 20.2.6 
           direct render: Yes 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a2f0 
           Sound Server: ALSA v: k5.8.0-53-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell 
           driver: r8169 v: kernel port: e000 bus ID: 01:00.0 chip ID: 10ec:8168 
           IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Dell 
           driver: ath9k v: kernel port: e000 bus ID: 02:00.0 chip ID: 168c:0036 
           IF: wlp2s0 state: down mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-14:6 chip ID: 0cf3:e005 
Drives:    Local Storage: total: 931.51 GiB used: 13.62 GiB (1.5%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
           speed: 6.0 Gb/s serial: <filter> 
RAID:      Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 bus ID: 00:17.0 
           chip ID: 8086.2822 
Partition: ID-1: / size: 449.63 GiB used: 13.61 GiB (3.0%) fs: ext4 dev: /dev/sda4 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 16 rev: 2.0 chip ID: 1d6b:0002 
           Device-1: 1-5:2 info: Dell Dell MS116 USB Optical Mouse type: Mouse 
           driver: hid-generic,usbhid rev: 2.0 chip ID: 413c:301a 
           Device-2: 1-6:3 info: Logitech Cordless Keyboard & Mouse type: Keyboard,Mouse 
           driver: hid-generic,usbhid rev: 1.1 chip ID: 046d:c509 
           Device-3: 1-8:4 info: Realtek RTS5129 Card Reader Controller type: <vendor specific> 
           driver: rtsx_usb,rtsx_usb_ms,rtsx_usb_sdmmc rev: 2.0 chip ID: 0bda:0129 
           Device-4: 1-14:6 info: Qualcomm Atheros type: Bluetooth driver: btusb rev: 1.1 
           chip ID: 0cf3:e005 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 rev: 3.0 chip ID: 1d6b:0003 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C 
           Fan Speeds (RPM): fan-1: 983 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http: //packages.linuxmint.com ulyssa main upstream import backport
           2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
           3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
           4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
           5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http: //archive.canonical.com/ubuntu/ focal partner
Info:      Processes: 209 Uptime: 20m Memory: 3.68 GiB used: 1.39 GiB (37.7%) Init: systemd v: 245 
           runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client inxi: 3.0.38

////////////////////////////////////////////////////////////////////////////

dmesg: Below is the error given during boot up.

Code:

[    1.251192] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200528/psargs-330)
[    1.251223] fbcon: Taking over console
[    1.251232] No Local Variables are initialized for Method [_GTF]
[    1.251235] No Arguments are initialized for method [_GTF]
[    1.251239] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[    1.251695] ata1.00: ATA-8: ST1000DM010-2EP102, 1001, max UDMA/133
[    1.251698] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.252645] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200528/psargs-330)
[    1.252662] No Local Variables are initialized for Method [_GTF]
[    1.252665] No Arguments are initialized for method [_GTF]
[    1.252668] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[    1.252827] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20200528/psargs-330)
[    1.252842] No Local Variables are initialized for Method [_GTF]
[    1.252844] No Arguments are initialized for method [_GTF]
[    1.252848] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[    1.252866] ata3.00: ATAPI: HL-DT-ST DVD+/-RW GU90N, A1C3, max UDMA/100
[    1.253106] ata1.00: configured for UDMA/133
[    1.253329] scsi 0:0:0:0: Direct-Access     ATA      ST1000DM010-2EP1 1001 PQ: 0 ANSI: 5
[    1.253675] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.253703] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    1.253707] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    1.253726] sd 0:0:0:0: [sda] Write Protect is off
[    1.253730] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.253752] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.254728] ata4: SATA link down (SStatus 4 SControl 300)
[    1.257419] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20200528/psargs-330)
[    1.257436] No Local Variables are initialized for Method [_GTF]
[    1.257438] No Arguments are initialized for method [_GTF]
[    1.257442] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[    1.257463] ata3.00: configured for UDMA/100

frankbell · 05-22-2021, 08:44 PM

A web search for ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP] turns up a number of forum posts at various sites. Perhaps one of them might help. Most of them seem to indicate that it has something to do with ACPI brightness control.

I get similar errors when booting this machine. As there seems to be no issue with functionality, I've chosen to ignore them.

wayne1937 · 05-22-2021, 09:45 PM

Quote:

Originally Posted by frankbell

A web search for ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP] turns up a number of forum posts at various sites. Perhaps one of them might help. Most of them seem to indicate that it has something to do with ACPI brightness control.

I get similar errors when booting this machine. As there seems to be no issue with functionality, I've chosen to ignore them.

Thank you frankbell. I too will ignore it.

frankbell · 05-22-2021, 10:09 PM

I must say, your reply gave me the best chuckle I've had in a long time.

On a more serious note, I have observed that, during boot, the kernel probes for a lot of things. Sometimes it doesn't find them because they are not there (and have no need to be there). That is not a cause for concern.

Sometimes, it may be a bug in a specific version of the kernel or of the firmware. But, if the system works otherwise, it's not necessarily worth loosing sleep over.

Just my two cents.