[Solved] ACPI errors during boot

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
zenmaker
Level 1
Level 1
Posts: 3
Joined: Fri May 20, 2022 10:27 am

[Solved] ACPI errors during boot

Post by zenmaker »

During boot get these ACPI errors especially AE NOT found.

So I have 2 ssd and 2 hdd, one ssd is transcend and has windows install and 2 partitions.
The other ssd has linux mint and is crucial, uses ext4 and bios for grub.

The error seem to be related to the transcend ssd no error throws up for other disks in the journal. It feels like some grub or boot mbr issue though have tried reinstalling grub but still get the message.

is it a bad error to have.
during boot these errors show up

Code: Select all

ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)

ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)

ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)

ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)

ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)

ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)

ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
in journalctl found these warnings as well

Code: Select all

Run /init as init process
May 19 19:00:19 mintpc kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20190816/ut>
May 19 19:00:19 mintpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 19 19:00:19 mintpc kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/ut>
May 19 19:00:19 mintpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 19 19:00:19 mintpc kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/ut>
May 19 19:00:19 mintpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 19 19:00:19 mintpc kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/ut>
May 19 19:00:19 mintpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 19 19:00:19 mintpc kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
May 19 19:00:19 mintpc kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
May 19 19:00:19 mintpc kernel: r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
May 19 19:00:19 mintpc kernel: ahci 0000:00:1f.2: version 3.0
May 19 19:00:19 mintpc kernel: r8169 0000:03:00.0 eth0: RTL8106e, 00:e0:0d:00:17:3c, XID 449, IRQ 26

Code: Select all

[    1.204246] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.204273] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.204296] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.204321] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.204814] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.204829] fbcon: Taking over console
[    1.204833] No Local Variables are initialized for Method [_GTF]
[    1.204834] No Arguments are initialized for method [_GTF]
[    1.204835] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.204891] Console: switching to colour frame buffer device 80x30
[    1.205093] ata6.00: ATA-9: ST1000DM010-2DM162, CC46, max UDMA/133
[    1.205095] ata6.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.205146] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205152] No Local Variables are initialized for Method [_GTF]
[    1.205153] No Arguments are initialized for method [_GTF]
[    1.205155] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205216] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205222] No Local Variables are initialized for Method [_GTF]
[    1.205223] No Arguments are initialized for method [_GTF]
[    1.205224] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205309] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205315] No Local Variables are initialized for Method [_GTF]
[    1.205316] No Arguments are initialized for method [_GTF]
[    1.205317] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205327] ata1.00: ATA-9: TS256GSSD370S, O0919A, max UDMA/133
[    1.205328] ata1.00: 500118192 sectors, multi 2: LBA48 NCQ (depth 32), AA
[    1.205397] ata5.00: ATA-8: ST3500418AS, CC38, max UDMA/133
[    1.205398] ata5.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32)
[    1.205595] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205601] No Local Variables are initialized for Method [_GTF]
[    1.205603] No Arguments are initialized for method [_GTF]
[    1.205605] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205694] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205700] No Local Variables are initialized for Method [_GTF]
[    1.205701] No Arguments are initialized for method [_GTF]
[    1.205702] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205844] ata6.00: configured for UDMA/133
[    1.205938] ata1.00: configured for UDMA/133
[    1.206098] scsi 0:0:0:0: Direct-Access     ATA      TS256GSSD370S    9A   PQ: 0 ANSI: 5
[    1.206261] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.206353] sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
[    1.206366] sd 0:0:0:0: [sda] Write Protect is off
[    1.206367] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.206385] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.206425] ata2.00: ATA-10: CT240BX500SSD1, M6CR054, max UDMA/133
[    1.206426] ata2.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 32), AA
[    1.206553] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.206559] No Local Variables are initialized for Method [_GTF]
[    1.206560] No Arguments are initialized for method [_GTF]
[    1.206561] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.206733] ata5.00: configured for UDMA/133
[    1.210618] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.210624] No Local Variables are initialized for Method [_GTF]
[    1.210625] No Arguments are initialized for method [_GTF]
[    1.210627] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.213211] ata2.00: configured for UDMA/133
[    1.213336] scsi 1:0:0:0: Direct-Access     ATA      CT240BX500SSD1   054  PQ: 0 ANSI: 5
[    1.213560] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    1.213636] sd 1:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB)
[    1.213643] sd 1:0:0:0: [sdb] Write Protect is off
[    1.213644] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.213654] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.213707] scsi 4:0:0:0: Direct-Access     ATA      ST3500418AS      CC38 PQ: 0 ANSI: 5
[    1.213854] sd 4:0:0:0: Attached scsi generic sg2 type 0
[    1.213906] sd 4:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[    1.213930] sd 4:0:0:0: [sdc] Write Protect is off
[    1.213931] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    1.213962] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.214021] scsi 5:0:0:0: Direct-Access     ATA      ST1000DM010-2DM1 CC46 PQ: 0 ANSI: 5
[    1.214175] sd 5:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    1.214176] sd 5:0:0:0: [sdd] 4096-byte physical blocks
[    1.214179] sd 5:0:0:0: Attached scsi generic sg3 type 0
[    1.214182] sd 5:0:0:0: [sdd] Write Protect is off
[    1.214183] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[    1.214192] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.277092]  sda: sda1 sda2 sda3
[    1.277257]  sdb: sdb1 sdb2 < sdb5 >
[    1.296439]  sdd: sdd1 sdd2 sdd3
[    1.305000] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.308597] sd 1:0:0:0: [sdb] Attached SCSI disk
[    1.320612] sd 5:0:0:0: [sdd] Attached SCSI disk
[    1.376533] usb 1-1.4: new low-speed USB device number 3 using ehci-pci
[    1.386543]  sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 >
[    1.396518] usb 2-1.2: new full-speed USB device number 3 using ehci-pci
[    1.405008] sd 4:0:0:0: [sdc] Attached SCSI disk
[    1.425213] random: fast init done
Sudo parted -l

Code: Select all

sudo parted -l
[sudo] password for rams:         
Model: ATA TS256GSSD370S (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  128GB  128GB  primary  ntfs         boot
 2      128GB   129GB  866MB  primary  ntfs         msftres
 3      129GB   256GB  127GB  primary  ntfs


Model: ATA CT240BX500SSD1 (scsi)
Disk /dev/sdb: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type      File system  Flags
 1      1049kB  538MB  537MB  primary   fat32        boot
 2      539MB   240GB  240GB  extended
 5      539MB   240GB  240GB  logical   ext4


Model: ATA ST3500418AS (scsi)
Disk /dev/sdc: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      32.3kB  12.6GB  12.6GB  primary   ntfs            boot
 2      12.6GB  500GB   488GB   extended                  lba
 5      12.6GB  24.0GB  11.4GB  logical   ntfs
 6      24.0GB  25.6GB  1620MB  logical   linux-swap(v1)
 7      25.6GB  86.0GB  60.4GB  logical   ntfs
 8      86.0GB  193GB   107GB   logical   ntfs
 9      193GB   301GB   107GB   logical   ntfs
10      301GB   408GB   107GB   logical   ntfs
11      409GB   437GB   28.9GB  logical   ntfs
12      437GB   500GB   62.7GB  logical   ntfs


Model: ATA ST1000DM010-2DM1 (scsi)
Disk /dev/sdd: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 1      1049kB  266GB   266GB  primary  ntfs
 2      266GB   581GB   315GB  primary  ntfs
 3      581GB   1000GB  419GB  primary  ntfs
Inxi

Code: Select all

nxi -Fzxxx
System:
  Kernel: 5.4.0-110-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
  Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: INTEL model: H61 serial: <filter> 
  BIOS: American Megatrends v: 4.6.5 date: 12/30/2020 
CPU:
  Topology: Quad Core model: Intel Xeon E31230 bits: 64 type: MT MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 8192 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 51085 
  Speed: 1596 MHz min/max: 1600/3600 MHz Core speeds (MHz): 1: 1596 2: 1596 
  3: 1594 4: 1596 5: 1596 6: 1596 7: 1596 8: 1596 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1060 6GB] driver: nvidia v: 510.73.05 
  bus ID: 01:00.0 chip ID: 10de:1b83 
  Display: x11 server: X.Org 1.20.13 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 
  v: 4.6.0 NVIDIA 510.73.05 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
  Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:10f0 
  Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 2-1.4:5 chip ID: 046d:0825 serial: <filter> 
  Sound Server: ALSA v: k5.4.0-110-generic 
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 
  v: kernel port: d000 bus ID: 03:00.0 chip ID: 10ec:8136 
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.82 TiB used: 21.96 GiB (1.2%) 
  ID-1: /dev/sda vendor: Transcend model: TS256GSSD370S size: 238.47 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: 9A temp: 33 C scheme: MBR 
  ID-2: /dev/sdb vendor: Crucial model: CT240BX500SSD1 size: 223.57 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: 054 temp: 42 C scheme: MBR 
  ID-3: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC38 temp: 47 C 
  scheme: MBR 
  ID-4: /dev/sdd vendor: Seagate model: ST1000DM010-2DM162 size: 931.51 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC46 temp: 45 C 
  scheme: MBR 
Partition:
  ID-1: / size: 218.57 GiB used: 21.96 GiB (10.0%) fs: ext4 dev: /dev/sdb5 
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: nvidia temp: 42 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 33% 
Info:
  Processes: 276 Uptime: 23m Memory: 7.73 GiB used: 1.89 GiB (24.4%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
rene
Level 20
Level 20
Posts: 12212
Joined: Sun Mar 27, 2016 6:58 pm

Re: ACPI errors during boot

Post by rene »

zenmaker wrote: Fri May 20, 2022 10:48 am is it a bad error to have.
It is a type of error you'd hope was fixed with a BIOS update at some point but otherwise, if all works then no; please see viewtopic.php?f=42&t=371358&p=2160587#p2160587
zenmaker
Level 1
Level 1
Posts: 3
Joined: Fri May 20, 2022 10:27 am

Re: ACPI errors during boot

Post by zenmaker »

The thing was i didnt have this error before, when i was using ubuntu 21.10, hated 22.04 due to snap and stuff and was distro hopping, from debian to fedora to pop but settled on mint.

Its just annoying to see that, im sure its some issue with boot managers on how they are reading the windows disk.
rene
Level 20
Level 20
Posts: 12212
Joined: Sun Mar 27, 2016 6:58 pm

Re: ACPI errors during boot

Post by rene »

zenmaker wrote: Sat May 21, 2022 6:43 am Its just annoying to see that, im sure its some issue with boot managers on how they are reading the windows disk.
It's definitely not -- but Mint 20.x is on a Ubuntu 20.04 base, i.e., significantly older than 21.10 and.or 22.04, and you are explicitly using the standard 5.4 kernel series.

If you're sure that 21.10 and/or 22.04 did not show you the ACPI messages you may try upgrading to the 5.13 series: Upgrade Manager -> View -> Linux kernels; pick the newest 5.13 series kernel and reboot into it. Although it doesn't tend to happen, as a matter of the in the linked tutorial post described BIOS <-> kernel interaction a kernel-sides update may have also fixed (or more likely, simply silenced) this on your system after all.

If not you'd "need" to follow the advise given there as to replacing quiet with loglevel=3 -- which for all I know might in fact be something newer Ubuntu releases do OOTB at the moment, although I doubt it.
zenmaker
Level 1
Level 1
Posts: 3
Joined: Fri May 20, 2022 10:27 am

Re: ACPI errors during boot

Post by zenmaker »

Hi thanks for the help, so i tested out ubuntu 21.10 impish and jammy on live usb to make sure, funnily impish is the only version it doesnt appear i think its cause of their splash logo probably has the fix you mentioned, while in jammy the errors throw up before logo shows up.

So ended up using loglevel=3 on mint and is now nice and quiet boot, and i can show off to my windows friends how superior linux is without all those errors throwing up on boot :lol:

Again thanks for the help and your time much appreciate it.
Reddog1
Level 7
Level 7
Posts: 1939
Joined: Wed Jun 01, 2011 2:12 pm

Re: ACPI errors during boot

Post by Reddog1 »

The kernel developers, in their great wisdom, decided to print lower log-level errors on the boot screen, and this has led to a heap of questions about why the acpi errors are occurring. Some other distributions have set the log level=3 out-of-the-box in order to avoid this nuisance.

Please set the topic as [solved]
rene
Level 20
Level 20
Posts: 12212
Joined: Sun Mar 27, 2016 6:58 pm

Re: ACPI errors during boot

Post by rene »

Reddog1 wrote: Mon May 23, 2022 8:21 pm The kernel developers, in their great wisdom, decided [ ... ]
As detailed last time as well, this has less to do with kernel developers than with distributions, and with users of said distributions who for some or other strange reason -- I mean that; think about it -- feel that the booting kernel should by default not produce messages: viewtopic.php?f=61&t=373212&hilit=kernel
Reddog1
Level 7
Level 7
Posts: 1939
Joined: Wed Jun 01, 2011 2:12 pm

Re: [Solved] ACPI errors during boot

Post by Reddog1 »

Yes, you are right, it is a decision made by the distribution (and those with the distribution that make determinations about the kernel). Anytime errors are shown at boot, it is definitely going to cause consternation, especially among new users. As I mentioned, some distributions have specifically set the /etc/default/grub to not print that log-level of messages.

Here is the stock grub line from an arch-based distro:

GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 nowatchdog nvme_load=YES"
rene
Level 20
Level 20
Posts: 12212
Joined: Sun Mar 27, 2016 6:58 pm

Re: [Solved] ACPI errors during boot

Post by rene »

Interesting that it's then even becoming standard to do that; wouldn't have assumed that. And yes, I will admit that those ACPI KERN_ERR messages are annoying; have them even on an old, bog-standard Intel C2D with integrated graphics system.
Locked

Return to “Installation & Boot”