Acpi error aborting method sb pci0

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

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

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

[    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

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

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 

Шо, опять? Ядро 5.6 и ACPI.

При переходе на 5.6 после выхода из саспенда dmesg спамит, и много чего перестаёт работать:

На 5.5 такого не было.

Куда деваться то со своим «старым» (P8Z68) железом?

Куда деваться то со своим «старым» (P8Z68) железом?

На свалку. У меня на лаптопе еще не такое происходить стало со временем, и всем пофиг на мои баг-репорты. Так что либо придумывай собственные костыли, либо меняй железку.

Как? i7-2600K на свалку?

Разбить? Пол-литру!? Вдребезги? Да я тебя!

не знаю про i7, но на i5 2400 даже сайты уже притормаживают, а на всяком дне типа i5 2410m не стесняясь тормозят в полную силу.

Зачем ты суспендишь десктоп?

ryzen 5 2600/b450 aorus elite

это появилось на 5 ядре, на 4.xx (точно не помню на каком именно), такого не было

У 2600K райзены первого поколения по синглкору посасывают, тащемт.

Я даже растерялся… А почему бы мне его не суспендить?

Каждый день пользуюсь. Наверное, чтоб просто клацнуть кнопкой и сразу начать пользоваться?

Если его не суспендить тоже можно просто сразу пользоваться, лол.

Предлагаешь не выключать?

Ну а сколько он там жрёт? В простое частота падает до 800мгц или сколько там.

Нет, конечно. Это пока «нытик-тред».

оставайся на 4.19

Могут сказать точно, что жрёт 80+ Ватт, так он ещё и не бесшумный.

а есть вообще разумный довод использовать максимально свежее ядро ?

А лучше обновится до Darwin Kernel Version 19.4.0

а есть вообще разумный довод использовать максимально свежее ядро ?

Вообще, конечно, нет.

_GTF — acpi функция переводящая (s)ata порт в состояние по умолчанию (или просто — инициализация).

DSSP — это какой-то флаг, на который ссылается эта функция, и который не установлен. Баг acpi/bios.

Скорее всего, в предыдущих версиях ядра из-за жалоб на эту ошибку, эта функция не вызывалась, а ядро само инициализировало sata-порты (сделали заглушку для конкретной материнки). После очередной чистки кода от старья эту заглушку выкинули и честно дергают acpi-функцию

Если нет проблем с дисками, то эту ошибку можно игнорировать.

Если нет проблем с дисками, то эту ошибку можно игнорировать.

Смотря что считать за проблему с дисками, точно есть проблемы с кедами, последний раз начали крашится ksshaskpass и system settings и может ещё что, обратил внимание только на это, ну и общая отзывчивость системы падает — в этом плане проблемы с дисками несомненно есть.

Ты привел только одну ошибку. И эта acpi-функция в основном простая заглушка, которая ничего не делает, максимум установит еще какой-нибудь флаг, ничего не значащий для работающей системы, чисто внутренняя для acpi, что типа порт инициализирован.

Думаю, у тебя скорее всего поломалось где-то в другом месте. Иначе у тебя при нормальном старте (не пробуждении из suspend) так же глючила система из-за дисков.

Думаю, у тебя скорее всего поломалось где-то в другом месте.

Всё может быть. Но мне кажется, что это всё-таки в ядре дело. На 5.5 не глючит так после выхода из сна.

Куда деваться то со своим «старым» (P8Z68) железом?

Ладно со старым, у меня с новым за последний год дважды спящий режим ломали.

глючит так после выхода из сна.

Это нормальное состояние вплоть до того, что при смене минорной версии (версиии патча) могут поломать засыпание. Потому что это неважная часть линукса, могут глобально перелопатить логику засыпания между патчами с соответствующими последствиями.

Конечно, всё бывает в первый раз. Но не припомню такие проблемы, системнику 8-10 лет.

Но не припомню такие проблемы, системнику 8-10 лет.

Купи себе модный (китайский) ноутбук/нетбук/планшет — будет что припомнить, что забывать не будешь успевать 🙂

Кто-то еще выключает компьютеры, кроме тех, кто собирает шумные ящики?

1. скорее не связанные вещи, вот у меня с 5.3

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

1. саспенды всегда работали, работают, будут работать с линуксами через одно место. Проще не использовать, тем более, еcли у тебя корабасный десктоп. Выключай на ночь и нормально.

Так было и так будет всегда: кривые, не соответствующие стандартам прошивки на платах Asus. Поэтому в ядре фиксить это никогда не будут.

Впрочем, они почти везде кривые в потребительском железе. Из того, что можно купить за разумные деньги «для дома, для семьи» – только с Supermicro не бывает проблем. Ну, или смотрите списки сертифицированного оборудования, например, redhat.

Как я понимаю ты позорище опенсорса имеешь ввиду сайты как браузер, а не как сервер?

Как сервер www, ppp, ftp, samba, dns, router, и ррочая и прочая даже первый пень до сих пор работоспособным будет.
(и особенно первый, второй и третий пни, так как у них биос в съёмном ПЗУ, а не на флеше, их сейчас как золото беззондовое хранить нужно)

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[Solved] ACPI errors during boot

[Solved] ACPI errors during boot

Post by zenmaker » Fri May 20, 2022 10:48 am

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

Re: ACPI errors during boot

Post by rene » Fri May 20, 2022 10:57 am

Re: ACPI errors during boot

Post by zenmaker » Sat May 21, 2022 6:43 am

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.

Re: ACPI errors during boot

Post by rene » Sat May 21, 2022 8:34 am

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.

Re: ACPI errors during boot

Post by zenmaker » Mon May 23, 2022 6:31 am

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

Again thanks for the help and your time much appreciate it.

Re: ACPI errors during boot

Post by Reddog1 » Mon May 23, 2022 8:21 pm

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]

Re: ACPI errors during boot

Post by rene » Tue May 24, 2022 7:07 am

Re: [Solved] ACPI errors during boot

Post by Reddog1 » Tue May 24, 2022 10:23 pm

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»

Re: [Solved] ACPI errors during boot

Post by rene » Wed May 25, 2022 6:14 am

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] ACPI errors and graphics card drivers issues

[SOLVED] ACPI errors and graphics card drivers issues

Post by Lock3 » Sat Aug 15, 2020 5:50 pm

It’s my first post here, so hello everyone.
I’ve just installed for the first time Linux Mint 64 bits in dual-boot with Windows 10 both in legacy mode.

The dual-boot works fine and so does Mint except that I have these ACPI errors on boot :

Moreover, it is impossible to install the Nvidia drivers which are recommended in the driver manager. When I try to do it, the system doesn’t recognize my graphics card anymore and the image is only managed by the CPU. I specify that I have an RTX 2070.

Secure boot is disabled as well as fast boot on windows 10.

I browsed the forum and tried to modify GRUB without success. Is this a kernel problem?

Thank you in advance for your answers

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sat Aug 15, 2020 6:05 pm

(if you type: the letter F is a capital letter, and don’t omit the space after inxi!)

Copy/paste the output in your next message.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 3:23 am

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 4:22 am

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 5:20 am

I chose a 2015 firmware version because the version of 2018 was still in beta status.

It still doesn’t work.

When I installed Mint I chose «Something Else» in the installer option and I have created a partition in ext4 an / for mount. Do I have to create a swap partition like older version of ubuntu ? Or this is irrelevant for this subject ?

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 5:59 am

I chose a 2015 firmware version because the version of 2018 was still in beta status.

That’s indeed irrelevant.

You might try a kernel update from the Canonical Kernel Team PPA:
https://easylinuxtipsproject.blogspot.c . t.html#ID8
(item 8 )

That should give you the latest kernel from the 5.4 series, which hopefully contains improvements that are relevant for your problem.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 8:36 am

I did as you said and switched to the 5.4.0-44 and unfortunately it doesn’t change anything.

I experience some weird crashes too : I tried to open Rhythmbox or the firewall and it’s stop the current session and send me back to the login screen. (It happens before the kernel update)

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 12:46 pm

So I tried the tip with

I still have the ACPI errors and the graphic card still doesn’t work.

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 1:03 pm

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 1:42 pm

This beta bios was made only for spectre vulnerability on CPU wich I am already protected.

Many users had issues with this Bios and I will not take my chance with it I think.

It’s a shame beacause Mint works flawlessly on my laptop and it seems to have many issues with a dual boot on legacy mode. Perhaps should I try to convert all the os on EFI mode ? Is it possible anyway without reinstalling the two OS ?

Re: ACPI errors and graphics card drivers issues

Post by SMG » Sun Aug 16, 2020 1:43 pm

When the Nvidia driver loads properly, you will see nvidia in both the device driver and the display driver.

Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2070 Rev. A] vendor: Micro-Star MSI
driver: nvidia v: 450.57 bus ID: 01:00.0

Display: x11 server: X.Org 1.20.8 driver: fbdev,modesetting,nouveau
unloaded: vesa resolution: 640×480

I don’t see it loaded or unloaded in the display drivers, so I’m going to suggest the driver did not install properly. I don’t what method you used to install it, but Pjotr’s website has a section on NVIDIA: how to install the latest video card drivers and roblm has tips for installing on LM20 in this post (scroll to the section in big blue letters — Mint 20 Nvidia Driver Installation Update).

Hopefully information in one of those two places (or both) can help you.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 2:21 pm

I tried the first step already without success unfortunately.

I will try the second one with driver directly downloaded from nvidia website.

Thanks for answering guys.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 6:32 pm

The second one was better than the others

Driver nvidia-450 has worked flawlessly with the roblm installation technique (with the driver downloaded on nvidia website) after

, every program on Mint worked fine, no crashes. UNTIL I have rebooted the system and now the driver is gone, with the GPU. Mint is on hardware only with 640*480 resolution.

ACPI errors still there but it seems to be not the real problem here.

The boot sequence don’t recognize the nvidia driver I think.

Boot issue ? kernel issue ? I don’t know

Re: ACPI errors and graphics card drivers issues

Post by SMG » Sun Aug 16, 2020 8:26 pm

UNTIL I have rebooted the system and now the driver is gone, with the GPU. Mint is on hardware only with 640*480 resolution.

ACPI errors still there but it seems to be not the real problem here.

The boot sequence don’t recognize the nvidia driver I think.

Boot issue ? kernel issue ? I don’t know

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Mon Aug 17, 2020 4:59 am

Yes I removed the nomodeset.

I tried a fresh install again this morning, but again it’s like Mint can’t find the GPU nivdia-driver after or during the boot sequence.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Mon Aug 17, 2020 5:30 am

OK I’ve got something new here.

As I said, I did a fresh install and installed the recommanded nvidia-driver-440 an rebooted. Nothing new for this part, the driver didn’t launch.

But I have just disconnected (close session) and login again (without reboot) and then everything works fine.

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don’t know what.

Re: ACPI errors and graphics card drivers issues

Post by SMG » Mon Aug 17, 2020 12:09 pm

OK I’ve got something new here.

As I said, I did a fresh install and installed the recommanded nvidia-driver-440 an rebooted. Nothing new for this part, the driver didn’t launch.

But I have just disconnected (close session) and login again (without reboot) and then everything works fine.

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don’t know what.

That sounds similar to what was happening to several people in this thread. Maybe reading through the thread will help. As I understand it, it is not that something is preventing the driver from starting, but rather something is not telling the driver to start at the correct time in the start-up sequence. I know there is a way to fix this (since several people in the thread were able to do it), but I don’t currently have the knowledge level to be able to guide something through the correct steps for doing it.

Perhaps someone with more knowledge than I currently have will be able to help

Источник

My Ubuntu 18.04 system has been working fine for quite some time (a few years). It suddenly threw up this error. Causes the system to auto-reboot several time. Sometimes it is able to boot into the login but even after login, it is behaving in a cranky manner. What gives?

linux kernel 5.4.0-42-generic

Update:

1. The BIOS was updated and that resolved the crazy auto-reboot issue and made the system usable.

2. I found that this Error appears in the dmesg log of both 18.04 and 16.04. Below is a more detailed list of the ACPI error msg (I found some related ACPI msgs was issued but without the ACPI syntax). It seems the issue pertains to the method _GTF. What is that and what does it do? Also, what is a DSSP?

More details from dmesg on the error:

[    1.201570] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.201575] No Local Variables are initialized for Method [_GTF]
[    1.201576] No Arguments are initialized for method [_GTF]
[    1.201577] ACPI Error: Aborting method _SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.205307] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205311] No Local Variables are initialized for Method [_GTF]
[    1.205312] No Arguments are initialized for method [_GTF]
[    1.205313] ACPI Error: Aborting method _SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.249944] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.249949] No Local Variables are initialized for Method [_GTF]
[    1.249950] No Arguments are initialized for method [_GTF]
[    1.249951] ACPI Error: Aborting method _SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.333524] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.333529] No Local Variables are initialized for Method [_GTF]
[    1.333530] No Arguments are initialized for method [_GTF]
[    1.333531] ACPI Error: Aborting method _SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)

Try rotating through the kernel options.

Worst case scenario run it with acpi=off or noacpi but if you’re not experiencing issues I would just leave it as it it.

acpi=off OR noacpi
This parameter disables the whole ACPI system. This may prove very useful, for example, if your computer does not support ACPI or if you think the ACPI implementation might cause some problems (for instance random reboots or system lockups).

acpi=force
Activates the ACPI system even if your computer BIOS date is older than 2000. This parameter overrides acpi=off and can also be used with current hardware if the ACPI support is not activated despite apm=off.

pci=noacpi OR acpi=noirq
These parameters disable the PCI IRQ routing

pci=acpi
This parameter activates the PCI IRQ routing

acpi_irq_balance
ACPI is allowed to use PIC interrupts to minimize the common use of IRQs.

acpi_irq_nobalance
ACPI is not allowed to use PIC interrupts.

acpi=oldboot
Deactivates the ACPI system almost completely; only the components required for the boot process will be used.

acpi=ht
Deactivates the ACPI system almost completely; only the components required for hyper threading will be used.

noapic
Disable the «Advanced Programmable Interrupt Controller (APIC)».

nolapic
Disable the «local APIC».

apm=off OR noapm
Disable the Advanced Power Management.

irqpoll
Changes the way the kernel handles interrupt calls (set it to polling). Can be useful in case of hardware interrupt issues.

acpi.power_nocheck=1 OR acpi_osi=Linux
Disable the check of power state. Option two modifies the list of supported OS interface strings (changes the OS compatibility reported to the BIOS). Necessary on some broken BIOSes to make temperature/fan control work.

Full info found in https://help.ubuntu.com/community/BootOptions

So this is just another workaround for the «Dell logo» issue mentioned earlier (Early Dell logo display in BIOS).
Unfortunately it doesn’t help with the problem I’m experiencing.

Yes, I did because I don’t really care about the s2idle sleep. It drains my battery and fans spin when my laptop is in my backpack.

I couldn’t reproduce the problem without mem_sleep_default=deep

If I knew that there will be this many issues with this laptop I would have gotten the non 2-in-1 variant which is apparently a lot better on Linux, but I got this one for half price new, so I thought it will be worth it. I mean, it’s not that bad, many issues were solved already by the community, but the issue I’m experiencing is apparently new, because I didn’t find anyone else experiencing it. Anyway, thanks for the help I received so far.

Also, since I posted here, the issue seems a lot harder to reproduce. The freezes still happen, but less often, I guess it’s just unpredictable. Weird, because I haven’t really changed anything since in the configuration.

@EDIT
The only thing changing is the battery charge level. Maybe it influences the probability of a freeze on sleep/wake?

@EDIT

Yeah, so the issue is back at its full intensity. If anyone has any more ideas what I can try to solve this, please let me know.

Last edited by krystiancha (2020-10-18 20:11:54)