Acpi error ae not found while resolving a named reference package element

I have an old computer with Ubuntu 20 that stops working suddenly. The computer doesn't open the ubuntu, I got this error: ACPI Error: AE_NOT_FOUND. While resolving a named reference package e...

The <device> it’s referring to is the device containing the filesystem. The error message you related indicates the device is /dev/sdb5 , not /dev/sdb. That’s why it tells you that it’s a partition table. Your cmd line should be more like «e2fsck -b 8193 /dev/sdb5». The problem doing that might be that this filesystem might be in use when you have booted into Ubuntu. You may have to boot with a live CD or live USB in order to try and repair your filesystem. But beware, in that case your filesystem may not be on sdb5, it might be on some other disk name. You can use the blkid command to tell you what is on a disk or disk partition. For example, you could run blkid /dev/sdb5 (or sudo blkid /dev/sda5) and it would tell you if there is a filesystem, what its UUID is, and any filesystem label it might have. If it DOES have a label, you can try e2fsck LABEL=yourFilesystemLabelHere (or even with its UUID, but those are long and complicated). If nothing else, you can use sudo blkid /dev/sd(something) (e.g. sda1, sda2, …, sdb1, sdb2, sdb3,… sdc1, sdc2, etc.) until you find your filesystem that’s now on sdb5.

Tough to diagnose remotely, but you’re right, you may have an issue deeper than just a corrupted filesystem. Not sure what to suggest for that, but at least maybe I have helped with how to use some more tools.

As «It’s me» suggests, you may want to add «acpi=off» along with «nomodeset» in /etc/default/grub , then run sudo update-grub, and perhaps reboot. That way your system will always boot with acpi=off. Something to try anyway.

Источник

Здравствуйте.

При каждой загрузке появляются сообщения.

kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210730/dspkginit-438)
kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210730/dspkginit-438)
Подскажите пожалуйста, что это значит?

Источник

Как правильно задавать вопросы

Правильно сформулированный вопрос и его грамотное оформление способствует высокой вероятности получения достаточно содержательного и по существу ответа. Общая рекомендация по составлению тем: 1. Для начала воспользуйтесь поиском форума. 2. Укажите версию ОС вместе с разрядностью. Пример: LM 19.3 x64, LM Sarah x32 3. DE. Если вопрос касается двух, то через запятую. (xfce, KDE, cinnamon, mate) 4. Какое железо. (достаточно вывод inxi -Fxz в спойлере (как пользоваться спойлером смотрим здесь)) или же дать ссылку на hw-probe 5. Суть. Желательно с выводом консоли, логами. 6. Скрин. Просьба указывать 2, 3 и 4 независимо от того, имеет ли это отношение к вопросу или нет. Так же не забываем об общих правилах Как пример вот

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

01 окт 2018, 13:23

Операционная система: Linux Mint 19 64-разрядная
Процессор: AMD Athlon(tm) II X4 645
Материнская плата: Gigabyte 970a ud3
Видеокарта: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730]

После выбора Linux Mint в GRUB появляется ошибка acpi error:ae_not_found,while resolving a named reference package element — lnkd(20180313/dspkginit-414) и монитор отключается. Сама система скорее всего стартует.

Что сделано?
1. Установил последний драйвер Mesa 18.3
2. Играл с параметрами запуска: noapic pci=nomsi,noaer acpi=strict/off.
Появляются разные другие ошибки, но результат тот же.
3. Обновил BIOS до последней версии.
4. Обновлял ядра с 4.15 до 4.18 и откатывал до 4.1

Нашёл баг ядра на чипе AMD

https://bugzilla.kernel.org/show_bug.cgi?id=198167

, но там указывается, что он присутствует, начиная с 4.14.3. У меня же не работает даже на 4.1. Чтобы проверить более старые ядра нужно уже удалять дополнительное ПО

Проблема прогрессировала. Изначально на Ubuntu 16.04 она возникала изредка и «решалась» перезагрузкой системы. Затем я купил SSD и поставил на него Linux Mint 19. На свежеустановленной системе было то же самое, но через 2 недели из периодической проблема стала регулярной. Теперь Linux Mint запускается только в режиме nomodeset, то есть с програмным рендерингом.

В каких-то рандомных редких случаях система стартует удачно и запускает видеодрайвер, но зависимость не выявлена. Это я заметил, когда экспериментировал с параметрами запуска. Думаешь, что заработало, но проверяешь повторно и снова видео не стартует.

Windows 10 из grub запускается без проблем. Всегда.

Буду благодарен за любую помощь. Прикладываю фото ошибок при разных параметрах запуска

https://yadi.sk/i/RL52ovcxLnRW5g

по-умолчанию

https://yadi.sk/i/KSLWKxQ0EBMmTQ

acpi=strict

https://yadi.sk/i/DqnveOVrtctVoA

pci=nomsi,noaer acpi=off

Аватара пользователя

Chocobo

Сообщения: 9953
Зарегистрирован: 27 авг 2016, 22:57
Решено: 214
Откуда: НН
Благодарил (а): 795 раз
Поблагодарили: 2979 раз
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#2

01 окт 2018, 14:50

karpo518, эта ошибка что спамит acpi — она вряд ли напрямую к видео.

Мне тоже думается что

karpo518 писал(а): ↑

01 окт 2018, 13:23


Сама система скорее всего стартует.

просто вывод либо куда-то в никуда, либо в неподдерживаемый режим.

Для начала попробуй на этом моменте, когда она стартует перейти в tty (ctrl-alt-f1) , залогиниться и вызвать DISPLAY=:0 xrandr

Ну и nomodeset — это тоже не свосем про программный рендеринг, или с ним корица ругается?

Изображение

   

Изображение

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#3

01 окт 2018, 16:08

Chocobo, спасибо за ответ.

Ну и nomodeset — это тоже не совсем про программный рендеринг, или с ним корица ругается?

Именно так. Выражение «Программный рендеринг» я взял из предупреждения от Cinamon. Оболочка в этом режиме предупреждает о возможном увеличении нагрузки на CPU, но добавляет, что для отладки этот режим — то что надо.

Для начала попробуй на этом моменте, когда она стартует перейти в tty (ctrl-alt-f1) , залогиниться и вызвать DISPLAY=:0 xrandr

Я пробовал перейти в этот режим, когда система уже выключила монитор. Вечером попробую сделать это на старте системы, если требуется.

Может быть сразу лог какой-нибудь глянуть?

Аватара пользователя

StarMAUGLI

Сообщения: 1609
Зарегистрирован: 10 сен 2016, 10:16
Решено: 18
Откуда: Москва
Благодарил (а): 686 раз
Поблагодарили: 187 раз
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#4

01 окт 2018, 16:52

karpo518 писал(а): ↑

01 окт 2018, 16:08


Может быть сразу лог какой-нибудь глянуть?

Что бы сразу глянуть все логи, можно загрузиться с той флешки с которой ставили минт и сделать hw-probe (как это сделать, см. ссылку в шапке над форумом). А сюда уже выложишь, только ссылку на эти логи.
ИМХО, если проблема прогрессирует, то это скорее к железу, нежели к ПО.

Аватара пользователя

rogoznik

Сообщения: 9443
Зарегистрирован: 27 июн 2017, 13:36
Решено: 119
Откуда: Нижний Тагил
Благодарил (а): 712 раз
Поблагодарили: 1814 раз
Контактная информация:

Birthday

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#5

01 окт 2018, 16:57

StarMAUGLI, в данном случае hw-probe соберет логи live-системы — они не помогут

Изображение

Изображение

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#6

01 окт 2018, 21:16

Господа, дома не сразу удалось неудачно запустить систему. Это помогло мне получить 2 лога: успешной загрузки и неудачной. Я отфильтровал файлы по слову failed. В неудачном варианте есть строка:
окт 01 20:41:57 karpo518-GA-970A-UD3 cinnamon-session[1207]: GLib-GIO-CRITICAL: t+969,02138s: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

Получается, что cinnamon не смог стартовать. Но почему это случилось, я так и не смог понять. Когда я переустанавливал систему, я монтировал непустую папку /home. Подозреваю, что я перенёс в новую систему какой-то старый кривой конфиг. С учетом того, что ранее папка принадлежала пользователю Ubuntu 16.04, на который дополнительно был установлен Cinnamon, проблема могла каким-то образом обостриться.

Прикладываю полные и отфильтрованные логи. Просьба подсказать, что с этим делать.

https://yadi.sk/d/MPEqMLZVZCQJDw

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#7

01 окт 2018, 21:22

P.S. сразу после выбора ОС в GRUB перейти в консоль через ctrl alt f1 не получилось. Система проигнорировала команду

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#8

02 окт 2018, 11:25

Снёс gnome-keyring. Долго боролся с этой софтиной, но она меня победила. Постоянно создаёт дубли связок ключей, которые я замучился удалять. Когда увидел в логе 2 000 строк ошибок от него, удалил без всяких сожалений. Вот сама ошибка:
gnome-keyring-daemon[1204]: GLib: g_hash_table_unref: assertion 'hash_table != NULL' failed

Несколько раз cinnamon запустился без проблем, но потом снова не получилось. Продолжил анализировать ошибки и нашёл:

udisksd[735]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory

Возможно эта ошибка и была причиной проблемы с gnome-keyring. Решилось установкой libblockdev-mdraid2. Пока cinnamon запускается без проблем. Вечером ещё перезапущу несколько раз проверю получше, ведь в логе всё ещё есть ошибки. Вообще странно, что свежая система не досчиталась пакета.

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#9

02 окт 2018, 11:26

Всем спасибо за ответы. Тему не закрывайте, пожалуйста. Пока неясно, решилась ли проблема

Аватара пользователя

Chocobo

Сообщения: 9953
Зарегистрирован: 27 авг 2016, 22:57
Решено: 214
Откуда: НН
Благодарил (а): 795 раз
Поблагодарили: 2979 раз
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#10

02 окт 2018, 19:22

karpo518, Взаимосвяь между gnome-keyring и mdraid сложно придумать.

И опять же сам факт что gnome-kerying уже стартует, говорит о том, что за DM уже логин прошел и иксы не упали, т.к. дальше взлетают процессы от DE
Т.е сама система где-то там работает, а показывать тебе не хочет)

:wacko:

Изображение

   

Изображение

Аватара пользователя

StarMAUGLI

Сообщения: 1609
Зарегистрирован: 10 сен 2016, 10:16
Решено: 18
Откуда: Москва
Благодарил (а): 686 раз
Поблагодарили: 187 раз
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#11

02 окт 2018, 22:11

karpo518 писал(а): ↑

01 окт 2018, 21:16


Когда я переустанавливал систему, я монтировал непустую папку /home. Подозреваю, что я перенёс в новую систему какой-то старый кривой конфиг. С учетом того, что ранее папка принадлежала пользователю Ubuntu 16.04, на который дополнительно был установлен Cinnamon, проблема могла каким-то образом обостриться.

А создать нового «пустого» пользователя не пробовал для диагностики? Ну чтобы конфиги исключить… На нем же можно было бы обкатать какой-нибудь другой ДЕ.

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#12

09 мар 2019, 01:04

А создать нового «пустого» пользователя не пробовал для диагностики? Ну чтобы конфиги исключить… На нем же можно было бы обкатать какой-нибудь другой ДЕ.

Если моя система не стартует, то до выбора пользователя дело не доходит. Прошло достаточно много времени, но проблема никуда не делась. Сейчас, чтобы удачно стартовать систему с флагом radeon.dpm=0
Эта ситуация меня жутко раздражает:

1. Это не решает проблему полностью. Иногда при загрузки системы из ждущего режима я получаю зависание экрана и вынужден делать аппаратный ребут системы. Для кого-то это может показаться пустяком, но я использую ждущий режим, чтобы не запускать все необходимые для работы программы заново, а их достаточно много. И вот вместо 3-секундной загрузки я трачу несколько минут на полную загрузку системы и восстановление утерянных данных.

2. Система постоянно обновляется, и мой кастомный режим GRUB сползает вниз с дефолтной позиции., а значит не будет стартовать автоматически. Да и чтобы сразу после обновления использовать новое ядро приходится создавать новый кастомный режим с флагом radeon.dpm=0 на основе нового ядра. Это недолго, но угнетает мою нервную систему.

В целом достаточно досадно, что имея реальную проблему с системой, я весь такой готовый предоставить любую информацию так и не смог получить решения. Системы на базе Linux меня радуют тем, что можно посмотреть логи и увидеть причину ошибки, а затем исправить её. На деле выходит, что программист, который для работы и дома использует ОС Linux Mint и при этом не задался целью достичь дзена в познании данного дистрибутива, оказывается беспомощным перед проблемой. Эта ситуация меня огорчает.

Аватара пользователя

StarMAUGLI

Сообщения: 1609
Зарегистрирован: 10 сен 2016, 10:16
Решено: 18
Откуда: Москва
Благодарил (а): 686 раз
Поблагодарили: 187 раз
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#13

09 мар 2019, 02:07

karpo518 писал(а): ↑

09 мар 2019, 01:04


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

karpo518 писал(а): ↑

09 мар 2019, 01:04


Сейчас, чтобы удачно стартовать систему с флагом radeon.dpm=0

Чего-то вы нас путаете. У вас хоть при каком-то раскладе удаестя загрузиться?
Так сделайте второго пользователя. Выйдите из сеанса. И посмотрите сохраняется ли проблема у второго пользователя? Этим вы отсечете возможность перетаскивания некорректных конфигов… то, что вы писали

karpo518 писал(а): ↑

01 окт 2018, 21:16


Когда я переустанавливал систему, я монтировал непустую папку /home.

darkfenix писал(а): ↑

01 окт 2018, 16:57


в данном случае hw-probe соберет логи live-системы — они не помогут

если топик-стартеру все-таки удается загрузиться хоть в каком-нибудь состоянии, то давно уже можно было поделиться hw-probe…

а вот это все

karpo518 писал(а): ↑

09 мар 2019, 01:04


В целом достаточно досадно, что имея реальную проблему с системой, я весь такой готовый предоставить любую информацию так и не смог получить решения.

без реальных логов, больше похоже на троллинг

Аватара пользователя

Unborn

Сообщения: 1920
Зарегистрирован: 03 сен 2016, 13:36
Решено: 24
Благодарил (а): 5 раз
Поблагодарили: 264 раза
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#14

09 мар 2019, 12:11

StarMAUGLI писал(а): ↑

09 мар 2019, 02:07


без реальных логов, больше похоже на троллинг

Просто человек никак не может осознать, что вот на этом —

karpo518 писал(а): ↑

01 окт 2018, 13:23


Видеокарта: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730]

, которая даже кружки пива не стоит, ничего из современного нормально работать не будет. И что в —

karpo518 писал(а): ↑

01 окт 2018, 13:23


Материнская плата: Gigabyte 970a ud3

Hybrid EFI как минимум в первой ревизии. О чем его ОС Линукс, установленная в эмуляции БИОС ни ухом ни рылом. Ясен пень будет спамить еррорами по ацпи куда только можно, +большая вероятность, что присутствует разгон. Иначе Вин10 там будет просто, извините, усираться, а не работать, потому что

karpo518 писал(а): ↑

01 окт 2018, 13:23


AMD Athlon(tm) II X4 645

Core I5 то не догоняет, не говоря уж о Sandy.
Особенность железа. И никто это не будет фиксить.
Купить видяшку б/у получше, выше АМДшки 7000 серии и не нужно, установить LMDE2 + Каталист и сидеть на жопе ровно. Или ещё заменить Атлон на Феном, тогда уж что-то будет получаться и на amdgpu с новыми ядрами в современных дистрибутивах. И с ЦП без кэша 3-го уровня вообще не хрен делать х64 ОС, не работают они. Так, корячутся в однозадачном режиме.

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#15

05 май 2019, 01:06

Всем привет! Извините за долгое ожидание. Я не был подписан на тему, поэтому упустил её из виду. Подытожу информацию.

1. При запуске системы после выбора ядра монитор отключается (переходит в спящий режим). Системный блок продолжает работать.
2. Ранее, я анализировал приложенный лог неудачной загрузки и увидел ошибку, которая намекает на то, что cinnamon не смог стартовать. Сейчас уже не вспомню, что именно за ошибка.
3. Проблема не связана с выбором пользователя, потому что возникает до появления окна авторизации.
4. Система стартует успешно, если добавить в GRUB параметр запуска radeon.dpm=0

Прикладываю hw-probe, запрошенный вами ранее.

https://linux-hardware.org/?probe=9ebc8fd78b

Слепок сделан в режиме radeon.dpm=0

Очень рассчитываю на вашу помощь!

Купить видяшку б/у получше

Не играя ни в какие игры, совсем не рассчитывал, что мне в этом десятилетии потребуется новая видеокарта для запуска фильмов и редактора кода.

большая вероятность, что присутствует разгон

Никаким разгоном я не занимался. Процессор покупался из сегмента выше среднего для своего времени и он гораздо моложе видеокарты. Windows 10 работает прекрасно. С относительно тяжелыми программами компьютер справляется. Photoshop, Phpstorm работают без проблем. Тот же Kdenlive в Linux Mint в режиме radeon.dpm=0 работает без тормозов. Поэтому считаю, что говорить об устаревании процессора ещё рано. Его замена в ближайшие 5 лет ничем не оправдана. Ну если только, чтобы «починить» Linux Mint.

no avatar

karpo518

Сообщения: 20
Зарегистрирован: 01 окт 2018, 13:17
Контактная информация:

Linux Mint 19 не запускается с дефолтным драйвером видеокарты

#16

25 июл 2019, 22:20

Купил Radeon rx570. Хотел решить проблему на несколько лет с запасом. Поставил драйвера с оф. сайта. Теперь cinnamon вообще не стартует. Секс продолжается

 !  Сообщение из: Dja
просьба не выражаться грубо дабы не заработать предупреждение

Источник


0

1

…пожалуйста, как можно исправить следующее:

ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKH (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKG (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKF (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKG (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKH (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKE (20200430/dspkginit-605)
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKE (20200430/dspkginit-605)

код asl: https://pastebin.com/qciHQTTW
нетбук: samsung n150 plus

// Заранее благодарю.

Источник

Hi

Having recently upgraded from Cinnamon 19.3 to 20.1 I am getting a bunch of error messages flash up during boot.
I have a dual boot Windows 10/Linux Mint system with Windows on an SSD and Linux root on the SSD and Linux home on a separate HDD drive. I allowed the Mint installation to format the Linux root partition but not the home partition.
The errors I am getting are:

Code: Select all

russell@russell-GA-MA770T-UD3:~$ dmesg | grep -i error
[    0.160044] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160052] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160058] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160063] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160074] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160079] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160084] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160089] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160100] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160105] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160109] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160115] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160127] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160132] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160138] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160143] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160154] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160160] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160165] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160170] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160182] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160188] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160193] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160198] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160210] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160215] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160220] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160225] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160237] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160242] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160248] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160253] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160265] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160270] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160275] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160280] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160292] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    0.160298] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160303] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160308] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160320] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[    0.160325] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[    0.160331] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[    0.160336] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[    1.322389] RAS: Correctable Errors collector initialized.
[   14.144189] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[   14.144373] floppy: error 10 while reading block 0
[   28.127569] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[   28.127573] floppy: error 10 while reading block 0
[   28.919353] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
[   41.800231] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[   41.800243] floppy: error 10 while reading block 0
[   54.079629] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[   54.079634] floppy: error 10 while reading block 0
[   66.360159] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[   66.360171] floppy: error 10 while reading block 0

System information from inixi:

Code: Select all

russell@russell-GA-MA770T-UD3:~$ inxi -F
System:    Host: russell-GA-MA770T-UD3 Kernel: 5.4.0-73-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
           Distro: Linux Mint 20.1 Ulyssa 
Machine:   Type: Desktop System: Gigabyte product: GA-MA770T-UD3 v: N/A serial: <superuser/root required> 
           Mobo: Gigabyte model: GA-MA770T-UD3 v: x.x serial: <superuser/root required> BIOS: Award v: F7 
           date: 07/09/2010 
CPU:       Topology: Quad Core model: AMD Phenom II X4 945 bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 800 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
Graphics:  Device-1: NVIDIA GT218 [GeForce 210] driver: nvidia v: 340.108 
           Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce 210/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia driver: snd_hda_intel 
           Device-2: NVIDIA High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.4.0-73-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:e0:4c:70:45:01 
Drives:    Local Storage: total: 577.55 GiB used: 69.00 GiB (11.9%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
           ID-2: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB 
Partition: ID-1: / size: 23.40 GiB used: 9.80 GiB (41.9%) fs: ext4 dev: /dev/sda3 
           ID-2: /home size: 91.54 GiB used: 59.18 GiB (64.7%) fs: ext4 dev: /dev/sdb1 
           ID-3: /tmp size: 9.04 GiB used: 21.0 MiB (0.2%) fs: ext4 dev: /dev/sdb6 
           ID-4: swap-1 size: 3.72 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb5 
Sensors:   System Temperatures: cpu: 30.1 C mobo: N/A gpu: nvidia temp: 38 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 216 Uptime: 4m Memory: 3.84 GiB used: 1.11 GiB (28.9%) Shell: bash inxi: 3.0.38

Can anyone point me towards what is causing this problem and how I can fix it? Everything seems to be working despite the errors but it does slow down the boot.

Thanks

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.

Laptop: HP17bs086nf, Intel Core i5-7200U, Intel HD Graphics 620 . Mint Cinnamon 20.1
Desktop: Gigabyte GA-MA770T-UD3 motherboard, NVIDIA GeForce 210, AMD Phenom II Quad Core Processor 3GHz, 4GB ram, 120GB SSD, 500GB HDD. Mint Cinnamon 20.1

Источник

I’m getting these error messages every single time I reboot my desktop (and a couple of more I don’t know how to retain when it’s shutting down, but those are not relevant to this question so far):

[gorre@uplink ~]$ journalctl -p err..alert
...
-- Reboot --
May 11 21:47:03 uplink kernel: ACPI BIOS Error (bug): Failure looking up [_SB.PCI0.RP04.PXSX._SB.PCI0.RP05.PXSX], AE_NOT_FOUND (20180105/dswload2-194)
May 11 21:47:03 uplink kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180105/psobject-252)
May 11 21:47:03 uplink kernel: ACPI Error: Method parse/execution failed _SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20180105/psparse-550)
May 11 21:47:03 uplink kernel: ACPI BIOS Error (bug): Failure looking up [_SB.PCI0.RP08.PXSX._SB.PCI0.RP09.PXSX], AE_NOT_FOUND (20180105/dswload2-194)
May 11 21:47:03 uplink kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180105/psobject-252)
May 11 21:47:03 uplink kernel: ACPI Error: Method parse/execution failed _SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20180105/psparse-550)
May 12 07:09:30 uplink kernel: rtc_cmos 00:03: Alarms can be up to one month in the future
-- Reboot --
May 12 07:10:32 uplink kernel: ACPI BIOS Error (bug): Failure looking up [_SB.PCI0.RP04.PXSX._SB.PCI0.RP05.PXSX], AE_NOT_FOUND (20180105/dswload2-194)
May 12 07:10:32 uplink kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180105/psobject-252)
May 12 07:10:32 uplink kernel: ACPI Error: Method parse/execution failed _SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20180105/psparse-550)
May 12 07:10:32 uplink kernel: ACPI BIOS Error (bug): Failure looking up [_SB.PCI0.RP08.PXSX._SB.PCI0.RP09.PXSX], AE_NOT_FOUND (20180105/dswload2-194)
May 12 07:10:32 uplink kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180105/psobject-252)
May 12 07:10:32 uplink kernel: ACPI Error: Method parse/execution failed _SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20180105/psparse-550)

I found this article that states someone can add this line: echo "disable" > /sys/firmware/acpi/interrupts/gpe6F to /etc/rc.local, but I’m not sure if that’s the correct solution…moreover, if that’s only «patching» the error messages, but not fixing the underlying problem ‒ if any.

Or maybe should I wait for an upgrade?

I’m using:

[gorre@uplink ~]$ uname -a
Linux uplink 4.16.8-1-ARCH #1 SMP PREEMPT Wed May 9 11:25:02 UTC 2018 x86_64 GNU/Linux

…and this is my hardware:

  • Corsair RMX750 (750 Watt) 80+ Gold Fully Modular Power Supply
  • Intel Core i7-8700 (BX80684I78700) Processor
  • Asus Prime Z370-P
  • Corsair Force MP500 M.2 2280 240GB NVMe PCI-Express 3.0 x4 MLC SSD
  • Corsair Vengeance LPX 32GB (2 x 16GB) 288-Pin DDR4 SDRAM DDR4 2666 (PC4 21300)

UPDATE

New kernel 4.19.13-1-lts update:

$ uname -a
Linux uplink 4.19.13-1-lts #1 SMP Sun Dec 30 07:38:47 CET 2018 x86_64 GNU/Linux

…and the error/warning messages are finally gone!

-- Reboot --
Dec 28 09:40:42 uplink kernel: ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
Dec 28 09:40:42 uplink kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252)
Dec 28 09:40:42 uplink kernel: ACPI Error: Method parse/execution failed _SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170728/psparse-550)
Dec 28 09:40:42 uplink kernel: ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
Dec 28 09:40:42 uplink kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252)
Dec 28 09:40:42 uplink kernel: ACPI Error: Method parse/execution failed _SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170728/psparse-550)
Dec 28 09:41:08 uplink gnome-session-binary[712]: Unrecoverable failure in required component org.gnome.Shell.desktop
Dec 28 11:48:13 uplink flatpak[7192]: libostree HTTP error from remote flathub for <https://dl.flathub.org/repo/objects/3d/b5370c04103b9acd46bca2f315fb4855649926120b099a>
Dec 28 11:48:16 uplink flatpak[7192]: libostree HTTP error from remote flathub for <https://dl.flathub.org/repo/objects/e0/a43c4cbae106fc801d3c7bcc004b8222e9bf0528beef04>
Dec 29 12:19:37 uplink kernel: rtc_cmos 00:03: Alarms can be up to one month in the future
Dec 30 09:03:02 uplink kernel: rtc_cmos 00:03: Alarms can be up to one month in the future
Dec 30 19:07:11 uplink kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=952715 end=952716) time 142 us, min 1073, max 1079, scan>
Dec 31 08:11:28 uplink kernel: rtc_cmos 00:03: Alarms can be up to one month in the future
-- Reboot --
Jan 01 10:23:42 uplink gnome-session-binary[516]: Unrecoverable failure in required component org.gnome.Shell.desktop

Источник

#
11 месяцев, 3 недели назад

(отредактировано

11 месяцев, 3 недели назад)

fleef avatar

Темы:

2

Сообщения:

5

Участник с: 18 февраля 2022

Доброго времени суток!

Приспичило на днях посмотреть в journalctl и нашёл пару неприятных «надписей»:

Вывод journalctl -p 3:

kernel: x86/cpu: SGX disabled by BIOS.
~
ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
~
ACPI Error: Aborting method _SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
~
Error: Driver ‘pcspkr’ is already registered, aborting…

Вывод journalctl -p 2:

watchdog: watchdog0: watchdog did not stop!

Форумчане, дайте знать если это что-то важное и ядро бьётся в конвульсиях моля добить =)

P.S: Каждую строчку гуглил, где-то пишут что ничего страшного, другие бьют тревогу.
P.S2:
~ Kernel: 5.15.8-xanmod1-tt-1
~ CPU: i5-9400

я пони, у меня копыта, не могу и не хочУ

vs220

#
11 месяцев, 3 недели назад

Темы:

22

Сообщения:

8090

Участник с: 16 августа 2009

Ничего страшного нет, ACPI часто ошибки выдает .
А watchdog просто при выключении и перезагрузки не останавливается

alien175

#
11 месяцев, 3 недели назад

alien175 avatar

Темы:

20

Сообщения:

177

Участник с: 27 декабря 2010

acpi ругается на устаревшие таблицы. По факту, они не должны попадать в dmesg (ибо warning), но решили, что лучше отображать и сделать error.
у меня:

 $: sudo dmesg| grep -i acpi
[    0.000000] BIOS-e820: [mem 0x000000007f5b0000-0x000000007f5bffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000007f5c0000-0x000000007f5c2fff] ACPI NVS
[    0.011826] ACPI: Early table checksum verification disabled
[    0.011837] ACPI: RSDP 0x00000000000F7DA0 000024 (v02 PTLTD )
[    0.011852] ACPI: XSDT 0x000000007F5B8DB7 00006C (v01 SECCSD LH43STAR 06040000  LTP 00000000)
[    0.011873] ACPI: FACP 0x000000007F5BFC92 0000F4 (v03 INTEL           06040000 PTL  00000002)
[    0.011895] ACPI: DSDT 0x000000007F5BA01F 005B7F (v01 INTEL  BEARG31A 06040000 MSFT 03000001)
[    0.011911] ACPI: FACS 0x000000007F5C2FC0 000040
[    0.011924] ACPI: FACS 0x000000007F5C2FC0 000040
[    0.011937] ACPI: MCFG 0x000000007F5BFD86 00003C (v01 PTLTD    MCFG   06040000  LTP 00000000)
[    0.011952] ACPI: HPET 0x000000007F5BFDC2 000038 (v01 PTLTD  HPETTBL  06040000  LTP 00000001)
[    0.011968] ACPI: APIC 0x000000007F5BFDFA 000068 (v01 PTLTD  ? APIC   06040000  LTP 00000000)
[    0.011983] ACPI: BOOT 0x000000007F5BFE62 000028 (v01 PTLTD  $SBFTBL$ 06040000  LTP 00000001)
[    0.011998] ACPI: SLIC 0x000000007F5BFE8A 000176 (v01 SECCSD LH43STAR 06040000  LTP 00000000)
[    0.012014] ACPI: SSDT 0x000000007F5B93BF 00025F (v01 PmRef  Cpu0Tst  00003000 INTL 20050624)
[    0.012029] ACPI: SSDT 0x000000007F5B9319 0000A6 (v01 PmRef  Cpu1Tst  00003000 INTL 20050624)
[    0.012045] ACPI: SSDT 0x000000007F5B8E23 0004F6 (v02 PmRef  CpuPm    00003000 INTL 20050624)
[    0.012058] ACPI: Reserving FACP table memory at [mem 0x7f5bfc92-0x7f5bfd85]
[    0.012064] ACPI: Reserving DSDT table memory at [mem 0x7f5ba01f-0x7f5bfb9d]
[    0.012069] ACPI: Reserving FACS table memory at [mem 0x7f5c2fc0-0x7f5c2fff]
[    0.012074] ACPI: Reserving FACS table memory at [mem 0x7f5c2fc0-0x7f5c2fff]
[    0.012079] ACPI: Reserving MCFG table memory at [mem 0x7f5bfd86-0x7f5bfdc1]
[    0.012084] ACPI: Reserving HPET table memory at [mem 0x7f5bfdc2-0x7f5bfdf9]
[    0.012089] ACPI: Reserving APIC table memory at [mem 0x7f5bfdfa-0x7f5bfe61]
[    0.012094] ACPI: Reserving BOOT table memory at [mem 0x7f5bfe62-0x7f5bfe89]
[    0.012099] ACPI: Reserving SLIC table memory at [mem 0x7f5bfe8a-0x7f5bffff]
[    0.012104] ACPI: Reserving SSDT table memory at [mem 0x7f5b93bf-0x7f5b961d]
[    0.012108] ACPI: Reserving SSDT table memory at [mem 0x7f5b9319-0x7f5b93be]
[    0.012114] ACPI: Reserving SSDT table memory at [mem 0x7f5b8e23-0x7f5b9318]
[    0.035171] ACPI: PM-Timer IO Port: 0x1008
[    0.035198] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.035206] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.035240] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[    0.035248] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.035261] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.035266] ACPI: HPET id: 0xffffffff base: 0xfed00000
[    0.154210] ACPI: Core revision 20210930
[    0.294759] ACPI: PM: Registering ACPI NVS region [mem 0x7f5c0000-0x7f5c2fff] (12288 bytes)
[    0.298835] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.309007] ACPI: Added _OSI(Module Device)
[    0.309015] ACPI: Added _OSI(Processor Device)
[    0.309019] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.309022] ACPI: Added _OSI(Processor Aggregator Device)
[    0.309027] ACPI: Added _OSI(Linux-Dell-Video)
[    0.309031] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.309035] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.325906] ACPI: 4 ACPI AML tables successfully acquired and loaded
[    0.326030] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210930/dspkginit-438)
[    0.326112] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKH (20210930/dspkginit-438)
[    0.326142] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210930/dspkginit-438)
[    0.326168] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210930/dspkginit-438)
[    0.326194] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210930/dspkginit-438)
[    0.326220] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKG (20210930/dspkginit-438)
[    0.326246] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210930/dspkginit-438)
[    0.326272] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210930/dspkginit-438)
[    0.326297] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210930/dspkginit-438)
[    0.326323] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210930/dspkginit-438)
[    0.326349] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210930/dspkginit-438)
[    0.326410] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210930/dspkginit-438)
[    0.326439] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210930/dspkginit-438)
[    0.326469] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210930/dspkginit-438)
[    0.326497] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210930/dspkginit-438)
[    0.326565] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210930/dspkginit-438)
[    0.326598] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210930/dspkginit-438)
[    0.326627] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210930/dspkginit-438)
[    0.326655] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210930/dspkginit-438)
[    0.326710] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210930/dspkginit-438)
[    0.326741] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210930/dspkginit-438)
[    0.326769] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210930/dspkginit-438)
[    0.326797] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210930/dspkginit-438)
[    0.326853] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20210930/dspkginit-438)
[    0.326883] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20210930/dspkginit-438)
[    0.326912] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20210930/dspkginit-438)
[    0.326941] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20210930/dspkginit-438)
[    0.326997] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKF (20210930/dspkginit-438)
[    0.327032] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKG (20210930/dspkginit-438)
[    0.327063] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKH (20210930/dspkginit-438)
[    0.327091] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKE (20210930/dspkginit-438)
[    0.327120] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKE (20210930/dspkginit-438)
[    0.334561] ACPI: Dynamic OEM Table Load:
[    0.334587] ACPI: SSDT 0xFFFF8E3E4124EC00 000203 (v02 PmRef  Cpu0Ist  00003000 INTL 20050624)
[    0.336686] ACPI: Dynamic OEM Table Load:
[    0.336711] ACPI: SSDT 0xFFFF8E3E419A2800 0006A5 (v02 PmRef  Cpu0Cst  00003001 INTL 20050624)
[    0.339971] ACPI: Dynamic OEM Table Load:
[    0.339991] ACPI: SSDT 0xFFFF8E3E411C8100 0000D4 (v02 PmRef  Cpu1Ist  00003000 INTL 20050624)
[    0.341442] ACPI: Dynamic OEM Table Load:
[    0.341460] ACPI: SSDT 0xFFFF8E3E41802540 000085 (v02 PmRef  Cpu1Cst  00003000 INTL 20050624)
[    0.343689] ACPI: EC: EC started
[    0.343695] ACPI: EC: interrupt blocked
[    0.346760] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.346772] ACPI: _SB_.PCI0.LPC0.H_EC: Boot DSDT EC used to handle transactions
[    0.346778] ACPI: Interpreter enabled
[    0.346850] ACPI: PM: (supports S0 S3 S4 S5)
[    0.346855] ACPI: Using IOAPIC for interrupt routing
[    0.346980] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.348056] ACPI: Enabled 10 GPEs in block 00 to 1F
[    0.376513] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
[    0.376555] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[    0.376898] ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0._OSC.CAPB], AE_ALREADY_EXISTS (20210930/dsfield-184)
[    0.376938] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20210930/dswload2-477)
[    0.376967] ACPI Error: Aborting method _SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (20210930/psparse-529)
[    0.377017] acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR DPC]
[    0.377030] acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR DPC]
[    0.377037] acpi PNP0A08:00: _OSC: platform retains control of PCIe features (AE_ALREADY_EXISTS)
[    0.377076] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-10] only partially covers this bridge
[    0.394575] ACPI: PCI: Interrupt link LNKA configured for IRQ 11
[    0.394902] ACPI: PCI: Interrupt link LNKB configured for IRQ 7
[    0.395233] ACPI: PCI: Interrupt link LNKC configured for IRQ 3
[    0.395582] ACPI: PCI: Interrupt link LNKD configured for IRQ 10
[    0.395924] ACPI: PCI: Interrupt link LNKE configured for IRQ 0
[    0.395931] ACPI: PCI: Interrupt link LNKE disabled
[    0.396272] ACPI: PCI: Interrupt link LNKF configured for IRQ 0
[    0.396279] ACPI: PCI: Interrupt link LNKF disabled
[    0.396629] ACPI: PCI: Interrupt link LNKG configured for IRQ 4
[    0.396967] ACPI: PCI: Interrupt link LNKH configured for IRQ 5
[    0.398613] ACPI: EC: interrupt unblocked
[    0.398621] ACPI: EC: event unblocked
[    0.398658] ACPI: EC: 0 stale EC events cleared
[    0.398658] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.398658] ACPI: EC: GPE=0x11
[    0.398658] ACPI: _SB_.PCI0.LPC0.H_EC: Boot DSDT EC initialization complete
[    0.398658] ACPI: _SB_.PCI0.LPC0.H_EC: EC: Used to handle transactions and events
[    0.399993] ACPI: bus type USB registered
[    0.401210] PCI: Using ACPI for IRQ routing
[    0.459569] pnp: PnP ACPI init
[    0.463491] pnp: PnP ACPI: found 4 devices
[    0.475255] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.529796] ACPI: AC: AC Adapter [ADP1] (on-line)
[    0.530248] ACPI: button: Lid Switch [LID0]
[    0.535508] ACPI: button: Power Button [PWRB]
[    0.535890] ACPI: button: Sleep Button [SLPB]
[    0.536341] ACPI: button: Power Button [PWRF]
[    0.549612] ACPI: thermal: Thermal Zone [TZ00] (57 C)
[    0.550505] ACPI: battery: Slot [BAT1] (battery absent)
[    0.573193] ACPI: bus type drm_connector registered
[    1.958381] ACPI: video: Video Device [IGD0] (multi-head: yes  rom: no  post: no)
[    1.964071] acpi device:03: registered as cooling_device2
[   19.977140] ACPI Warning: SystemIO range 0x0000000000001028-0x000000000000102F conflicts with OpRegion 0x0000000000001000-0x000000000000102F (_SB.PCI0.LPC0.PMIO) (20210930/utaddress-204)
[   19.977174] ACPI Warning: SystemIO range 0x0000000000001028-0x000000000000102F conflicts with OpRegion 0x0000000000001000-0x000000000000107F (PMIO) (20210930/utaddress-204)
[   19.977193] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[   19.977203] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00000000000011AF (_SB.PCI0.LPC0.GPOX) (20210930/utaddress-204)
[   19.977222] ACPI: OSL: Resource conflict; ACPI support missing from driver?

vasek

#
11 месяцев, 3 недели назад

(отредактировано

11 месяцев, 3 недели назад)

Темы:

47

Сообщения:

11417

Участник с: 17 февраля 2013

fleef
Вывод journalctl -p 3: …

Согласно DOC значение параметра —priority=3 означает вывод ошибок (error) … и логично предположить, что в идеале этот вывод должен быть пустым.
Но нужно различать случаи
1. Наличие ошибок в выводе непосрественно сразу после загрузки системы — этот вывод желательно иметь пустым

 journalctl -b -p3 --no-pager
-- No entries –

Если вывод не пустой, то следует понять, что это за ошибка, чем она обусловлена, как влияет на работу системы и как ее можно устронить. Желательно смотреть этот вывод после каждого серъезного обновления системы.
2. Появление ошибок в выводе в процессе работы системы — вывод не посредственно сразу после загрузки системы может быть пустым, но ошибки могут возникнуть непосредственно в процессе работы системы. Это совершенно разные случаи.

В части ошибки

fleef
Error: Driver ‘pcspkr’ is already registered, aborting…

В системе имеется модуль pcspkr
modinfo pcspkr -n
/lib/modules/5.16.8-arch1-1/kernel/drivers/input/misc/pcspkr.ko.zst
но по какой-то причине этот модуль загружается снова — система и пишет, что модуль уже загружен и отменяет его загрузку — нужно разбираться, если есть желание, что заставляет загружать этот модуль … на работу не сказывается.

В части ошибки

fleef
kernel: x86/cpu: SGX disabled by BIOS.

Можно предположить, что cpu имеет поддережку технологии SGX, но в BIOS она не активирована … вот об этом логи и говорят.
Эта поддержка в новых cpu вроде бы удалена — вызывает уязвимость.
Можно просто исключить загрузку этого встроенного модуля — прописать параметр ядра nosgx

В части ошибок ACPI — по идее этих ошибок в выводе journalctl -b -p3 —no-pager быть не должно, как правило, ошибки ACPI имеют приоритет warning и выскакивают с уровня p4.
Насколько могу судить, эти ошибки связаны с жестким диском — и не плохо бы понять причину их появления …

Хочешь понять суть плоблемы — больше гугли и читай …

EDIT — Дополнение в части ошибок ACPI — ошибки, насколько я понимаю, связаны с методом _GTF — это метод ACPI, который используется для повторной инициализации диска.
Как пишут умные дяди

 Ошибка связана с тем, что BOIS не имеет определенного метода _GTF. Это может быть обусловлено тем, что железо или не поддерживает команды ATA, которые инициализирует метод _GTF или разработчик BIOS не включил (не описал) их. … Если ваши диски SATA работают корректно без ошибок, скорее всего, это просто не требуется и не нужно беспокоиться об этом сообщении драйвера ядра.

Исключить эти ошибки помогает, но не всегда, загрузка с параметром ядра libata.noacpi=1

Ошибки не исчезают с опытом — они просто умнеют

Источник
View previous topic :: View next topic  
Author Message
figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Wed Jul 13, 2022 4:15 am    Post subject: Old Gigabyte motherboard, ACPI error, console screen Reply with quote
Re: my x86 server on Gigabyte GA-MA78GM-US2H with latest stable BIOS F8 10/08/2009 and an AMD Phenom 8650 x3 with 8 GB RAM, that boots to the console prompt (not X)

ADDING: The video is the built in Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200] with all the latest Radeon linux-firmware loaded built-in IAW Gentoo Radeon wiki.

A couple of days ago, on my x86 server I was happily running gentoo-sources-4.9.315 (then the LTS stable version in the 4.9 series), and I updated to 4.9.321 as part of a routine emerge world update. Everything is fine.

The 4.9 series kernel is expected EOL in January 2023, so I decided to update stepwise first to 4.14 and then 4.19 series to give me a couple of more years breathing room to December 2024.

The problem is that after the upgrade to gentoo-sources-4.14-286 I first noticed that the monitor never blanks. I first thought I would check the dpm status:

Code:
$ dmesg | grep dpm



returned nothing (should be something like «[Mon Jul 11 00:17:44 2022] [drm] radeon: dpm initialized» from my primary desktop PC).

Looking for other errors revealed the following ACPI errors:

Code:
$ dmesg | grep AE_NOT_FOUND

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[Tue Jul 12 23:05:57 2022] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

These errors are well documented (Internet searches) on various Gigabyte motherboards with no solutions other than «update BIOS» and «ignore, not important.»

I think they are important since there is a symptom (monitor doesn’t blank), but everything else seems to work (NFS server, NTP server, mailserver, webserver).

There are also a few of these memory reserved errors, but I don’t think these are part of the problem:

Code:
$ dmesg | grep could.not.be

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0x000f0000-0x000f7fff] could not be reserved

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0x000f8000-0x000fbfff] could not be reserved

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0x000fc000-0x000fffff] could not be reserved

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0xafde0000-0xafdfffff] could not be reserved

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0x00000000-0x0009ffff] could not be reserved

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0x00100000-0xafddffff] could not be reserved

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0xafef0000-0xcfeeffff] could not be reserved

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0xfec00000-0xfec00fff] could not be reserved

[Tue Jul 12 23:05:57 2022] system 00:08: [mem 0xfee00000-0xfee00fff] could not be reserved

I spent the next coupld of days upgrading in-turn to 4.19.250, 5.4.203, and finally 5.10.128. Nothing changed. Same ACPI errors and no console screen blanking (no radeon dpm).

I did try to force dpm on with a kernel boot commandline:

Code:
$ grep dpm /etc/default/grub

GRUB_CMDLINE_LINUX=»net.ifnames=0 ipv6.disable=1 radeon.dpm=1″



but this had no effect.

I also tried booting from a USB flash drive with MX-Linux 21 (Debian stable) running a Debian kernel in the 5.10 series:

Code:
$ uname -a

Linux mx1 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 GNU/Linux



which reveals exactly the same ACPI errors I pasted in above.

I’m hoping for a fellow Gigabyte motherboard user who might have actually solved this problem.

Note: If I start X (/etc/init.d/display-manager start), the monitor does blank into low power mode, but I really don’t want to run X by default.

Thanks for reading. I’m worn out rebooting.
_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

mike155
Advocate
Advocate

Joined: 17 Sep 2010
Posts: 4312
Location: Frankfurt, Germany
PostPosted: Wed Jul 13, 2022 3:31 pm    Post subject: Reply with quote
Do I understand correctly that you want screen blanking to be enabled on the TTY console?

Please run the commands below and post the output:

Code:
# cat /sys/module/kernel/parameters/consoleblank

# setterm -blank 1 -powerdown 1

# cat /sys/module/kernel/parameters/consoleblank



Does your screen blank now after a minute?
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Wed Jul 13, 2022 5:03 pm    Post subject: Reply with quote

mike155 wrote:
Do I understand correctly that you want screen blanking to be enabled on the TTY console?

Please run the commands below and post the output:

Code:
# cat /sys/module/kernel/parameters/consoleblank

# setterm -blank 1 -powerdown 1

# cat /sys/module/kernel/parameters/consoleblank



Does your screen blank now after a minute?



Excellent. That doesn’t diagnose the ACPI errors, but does solve the screen blanking problem (which happened automatically without intervention with kernels in the 4.9 and lower series). Here is what I get following your code:

Code:
# cat /sys/module/kernel/parameters/consoleblank

0

# setterm -blank 1 -powerdown 1

# cat /sys/module/kernel/parameters/consoleblank

60



and surely enough, the monitor blanks in a minute. I tried adding this line to /etc/local.d/baselayout1.start and it does not work. Does setterm only work when actually entering the command in the console? (sort of) I know for sure it doesn’t work within an ssh session when logging in remotely. (but see below)

Before pressing Submit on this message I did some searching and found the solution at: https://stackoverflow.com/questions/66537659/automating-setterm. The answer was to use the following string in the /etc/local.d/baselayout1.start script:

Code:
setterm -term linux -blank 1 -powerdown 1 > /dev/console



which redirects the output of the setterm commands to the console device.
_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

mike155
Advocate
Advocate

Joined: 17 Sep 2010
Posts: 4312
Location: Frankfurt, Germany
PostPosted: Wed Jul 13, 2022 5:25 pm    Post subject: Reply with quote
You could try to add the following parameter to the kernel command line parameters:

Code:
consoleblank=60



On some older mainboards, it helps to add the parameter below as well:

Code:
acpi_enforce_resources=lax



See /usr/src/linux/Documentation/admin-guide/kernel-parameters.txt:

Code:
consoleblank=   [KNL] The console blank (screen saver) timeout in

                 seconds. A value of 0 disables the blank timer.

                 Defaults to 0.

acpi_enforce_resources= [ACPI]

                 { strict | lax | no }

                 Check for resource conflicts between native drivers

                 and ACPI OperationRegions (SystemIO and SystemMemory

                 only). IO ports and memory declared in ACPI might be

                 used by the ACPI subsystem in arbitrary AML code and

                 can interfere with legacy drivers.

                 strict (default): access to resources claimed by ACPI

                 is denied; legacy drivers trying to access reserved

                 resources will fail to bind to device using them.

                 lax: access to resources claimed by ACPI is allowed;

                 legacy drivers trying to access reserved resources

                 will bind successfully but a warning message is logged.

                 no: ACPI OperationRegions are not marked as reserved,

                 no further checks are performed.

Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Wed Jul 13, 2022 6:51 pm    Post subject: Reply with quote
mike155 Thank you for the lead to acpi_enforce_resources=lax kernel command line parameters.

Unfortunately, it made no difference booting with it, leaving the same identical errors in dmesg output. On the plus side, console blanking still works vi the entry in /etc/local.d/baselayout1.start which I will continue to use.

For reference, there is a really long thread in kernel bugzilla about these errors, with frustrated users of older Gigabyte motherboards going back at least four years.

https://bugzilla.kernel.org/show_bug.cgi?id=198167

I’ve added myself to the Cc: list (now 24 users long). The errors are real, but not known to be harmful.

My plan is to just live with it and stick with gentoo-sources-5.10 series which gives me another 4 ½ years with that LTS kernel before EOL. In the meantime, maybe there will be a solution.
_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

mike155
Advocate
Advocate

Joined: 17 Sep 2010
Posts: 4312
Location: Frankfurt, Germany
PostPosted: Wed Jul 13, 2022 7:43 pm    Post subject: Reply with quote
The pleasure is on my side!

I didn’t know that I want TTY console screen blanking. After reading your post, I realized I want it. So i added ‘consoleblank=300’ to my kernel parameters. :D
Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area
PostPosted: Wed Jul 13, 2022 8:52 pm    Post subject: Reply with quote
What does zgrep ACPI /proc/config.gz return

(or grep ACPI on .config — wherever it is, if config is not in kernel.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland

copy of my local repo
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Wed Jul 13, 2022 9:03 pm    Post subject: Reply with quote

Code:
$ zgrep ACPI /proc/config.gz

gzip: /proc/config.gz: No such file or directory

But,

Code:
$ grep ACPI /usr/src/linux/.config

# Power management and ACPI options

CONFIG_ARCH_SUPPORTS_ACPI=y

CONFIG_ACPI=y

CONFIG_ACPI_LEGACY_TABLES_LOOKUP=y

CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=y

CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y

# CONFIG_ACPI_DEBUGGER is not set

CONFIG_ACPI_SPCR_TABLE=y

CONFIG_ACPI_SLEEP=y

CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y

# CONFIG_ACPI_EC_DEBUGFS is not set

# CONFIG_ACPI_AC is not set

# CONFIG_ACPI_BATTERY is not set

CONFIG_ACPI_BUTTON=y

CONFIG_ACPI_VIDEO=y

CONFIG_ACPI_FAN=y

# CONFIG_ACPI_TAD is not set

CONFIG_ACPI_DOCK=y

CONFIG_ACPI_CPU_FREQ_PSS=y

CONFIG_ACPI_PROCESSOR_CSTATE=y

CONFIG_ACPI_PROCESSOR_IDLE=y

CONFIG_ACPI_PROCESSOR=y

CONFIG_ACPI_HOTPLUG_CPU=y

# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set

CONFIG_ACPI_THERMAL=y

CONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=y

CONFIG_ACPI_TABLE_UPGRADE=y

# CONFIG_ACPI_DEBUG is not set

# CONFIG_ACPI_PCI_SLOT is not set

CONFIG_ACPI_CONTAINER=y

CONFIG_ACPI_HOTPLUG_IOAPIC=y

# CONFIG_ACPI_SBS is not set

# CONFIG_ACPI_HED is not set

# CONFIG_ACPI_CUSTOM_METHOD is not set

CONFIG_HAVE_ACPI_APEI=y

CONFIG_HAVE_ACPI_APEI_NMI=y

# CONFIG_ACPI_APEI is not set

# CONFIG_ACPI_DPTF is not set

# CONFIG_ACPI_CONFIGFS is not set

CONFIG_X86_ACPI_CPUFREQ=y

CONFIG_X86_ACPI_CPUFREQ_CPB=y

# end of Power management and ACPI options

CONFIG_PNPACPI=y

CONFIG_ATA_ACPI=y

# CONFIG_PATA_ACPI is not set

CONFIG_ACPI_I2C_OPREGION=y

# ACPI drivers

# ACPI drivers

# CONFIG_SENSORS_ACPI_POWER is not set

# ACPI INT340X thermal drivers

# end of ACPI INT340X thermal drivers

# CONFIG_MFD_INTEL_LPSS_ACPI is not set

# CONFIG_MMC_SDHCI_ACPI is not set

CONFIG_ACPI_WMI=y

# CONFIG_ACPI_CMPC is not set

# CONFIG_SYSTEM76_ACPI is not set



Thank you for asking.
_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area
PostPosted: Wed Jul 13, 2022 10:01 pm    Post subject: Reply with quote
If it were me, I’d play with ACPI settings

CONFIG_ACPI_SPCR_TABLE=y — serial console (are you using it)

some HOTPLUG stuff, TABLE_UPGRADES, some other misc stuff in the ACPI selection area.

Turn off anything that you don’t need, if nothing else, it should drop the number of «complaints» :lol:
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland

copy of my local repo
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Thu Jul 14, 2022 3:36 am    Post subject: Reply with quote
I turned off:

CONFIG_ACPI_REV_OVERRIDE_POSSIBLE

CONFIG_ACPI_SPCR_TABLE

CONFIG_ACPI_DOCK

I think those are safe to turn off, but it didn’t make any difference. Best I can tell, the rest are important.
_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

pjp
Administrator
Administrator

Joined: 16 Apr 2002
Posts: 19605
PostPosted: Thu Jul 14, 2022 4:30 am    Post subject: Reply with quote
I was curious as these stood out to me:

CONFIG_HOTPLUG_CPU enables logical online/offline

CONFIG_ACPI_HOTPLUG_CPU enables ACPI support for physical add/remove

https://lwn.net/Articles/537570/

CONFIG_ACPI_DOCK

This driver supports ACPI-controlled docking stations and removable drive bays such as the IBM Ultrabay and the Dell Module Bay.

/usr/src/linux/drivers/acpi/Kconfig

Interesting that ACPI_HOTPLUG defaults to on. I can’t imagine any consumer hardware supporting physical hot swap of most anything connecting to a motherboard.

I’ve only ever perceived docking stations for laptops, and mine is now old enough that I’m not going to buy one for it, so it would seem I can disable those on my next update.
_________________
Quis separabit? Quo animo?
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Thu Jul 14, 2022 5:08 am    Post subject: Reply with quote
I can’t wait to find and disable those HOTPLUG items. Will report tomorrow — well, after sleeping anyway.
_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area
PostPosted: Thu Jul 14, 2022 9:30 am    Post subject: Reply with quote
CONFIG_ACPI_I2C_OPREGION=y — not sure it’s needed on your mb unless you have i2c devices (smart batteries, etc) and you probably don’t

CONFIG_ACPI_CONTAINER=y — used by hotplug cpu/mem (all 3 can be turned off)

and of course things like DOCK (if you don’t have one), AC (if not a laptop), etc can be turned off.

And if nothing else, you might turn on ACPI debugging (long enough to fully understand what’s going on)

Edit to add: looking at old bug reports, it might be firmware related.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland

copy of my local repo
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Thu Jul 14, 2022 5:05 pm    Post subject: Reply with quote
Some of these HOTPLUG items cannot be reasonably turned off by normal methods. I did manage to turn off CONFIG_ACPI_I2C_OPREGION and a couple of other settings.

In the meantime, I also managed for force loading the k10temp module. I ran into that issue just coincidentally while researching some of these kernel configuration options.

ADDED:

Code:
$ cat /etc/modprobe.d/99-local.conf

#modprobe k10temp force=1

options k10temp force=1



I do get an error for that, but I can still see it working in sensors:

Code:
[Thu Jul 14 12:52:01 2022] k10temp 0000:00:18.3: unreliable CPU thermal sensor; check erratum 319



https://www.kernel.org/doc/html/latest/hwmon/k10temp.html

After reboot, no new errors, no fewer errors, and I believe I still have full functionality. Thank you for participating.
_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

pjp
Administrator
Administrator

Joined: 16 Apr 2002
Posts: 19605
PostPosted: Thu Jul 14, 2022 6:09 pm    Post subject: Reply with quote

figueroa wrote:
Some of these HOTPLUG items cannot be reasonably turned off by normal methods. I did manage to turn off CONFIG_ACPI_I2C_OPREGION and a couple of other settings.

Interesting. I’ll try today or maybe this week/weekend. I couldn’t figure out the purpose of ACPI_HOTPLUG_IOAPIC, so at least for now, I’ll leave that one alone.

Also, in case it wasn’t obvious in my previous post, CONFIG_HOTPLUG_CPU seems fine as it is «logical» not physical.
_________________
Quis separabit? Quo animo?
Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area
PostPosted: Thu Jul 14, 2022 6:20 pm    Post subject: Reply with quote
I have this as a cmd line option, acpi_enforce_resources=no

It allows me to load the sensor driver, «lax» instead of «no» would work for driver loading, but lax still prints messages from acpi, «no» turns those messages off.

I have a feeling that as old as that mb is, it’s got an incomplete acpi implementation in the bios, that will never be fixed by gigabyte.

But I’m sure they’d be real happy to sell you a new mb :lol:

Edit to add: what does «ls /sys/firmware/acpi/*» return
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland

copy of my local repo
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Fri Jul 15, 2022 3:45 am    Post subject: Reply with quote
I definitely don’t expect Gigabyte to update the BIOS on my old motherboard. In fact I’m running on version F8, and I havea beta of their version F9 (MA78GUS2.F9d) but I think I won’t apply it. After all, I can’t actually find anything that doesn’t work.

BTW, I like the motherboard a lot. One of the best I’ve ever owned. However, back when it was new, I had to hack a ribbon cable to the parallel port to correct the pinout on the motherboard. Shame on them.

Regarding acpi firmware:

Code:
$ ls /lib/firmware/acpi*

ls: cannot access ‘/lib/firmware/acpi*’: No such file or directory

$ ls /lib/firmware | grep -i acpi

$


_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area
PostPosted: Fri Jul 15, 2022 9:19 am    Post subject: Reply with quote
firmware would be related to either amd, amd-ucode and/or radeon, depending on which hardware you have.

What does «grep ACPI /var/log/dmesg» show (or if no /var/log/dmesg «dmesg|grep ACPI»)

On my system, all the acpi setup, etc happens early on and thus is in /var/log/dmesg.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland

copy of my local repo
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Fri Jul 15, 2022 3:56 pm    Post subject: Reply with quote

Anon-E-moose wrote:
firmware would be related to either amd, amd-ucode and/or radeon, depending on which hardware you have.

What does «grep ACPI /var/log/dmesg» show (or if no /var/log/dmesg «dmesg|grep ACPI»)

On my system, all the acpi setup, etc happens early on and thus is in /var/log/dmesg.



I think this is the best way to capture all the acpi & ACPI messages:

Code:
$ dmesg -H | grep -i acpi

[  +0.000000] BIOS-e820: [mem 0x00000000afde0000-0x00000000afde2fff] ACPI NVS

[  +0.000000] BIOS-e820: [mem 0x00000000afde3000-0x00000000afdeffff] ACPI data

[  +0.000073] ACPI: Early table checksum verification disabled

[  +0.000009] ACPI: RSDP 0x00000000000F7120 000014 (v00 GBT   )

[  +0.000005] ACPI: RSDT 0x00000000AFDE3000 00003C (v01 GBT    GBTUACPI 42302E31 GBTU 01010101)

[  +0.000008] ACPI: FACP 0x00000000AFDE3040 000074 (v01 GBT    GBTUACPI 42302E31 GBTU 01010101)

[  +0.000007] ACPI: DSDT 0x00000000AFDE30C0 00691F (v01 GBT    GBTUACPI 00001000 MSFT 03000000)

[  +0.000004] ACPI: FACS 0x00000000AFDE0000 000040

[  +0.000004] ACPI: SSDT 0x00000000AFDE9AC0 00067F (v01 PTLTD  POWERNOW 00000001  LTP 00000001)

[  +0.000004] ACPI: HPET 0x00000000AFDEA140 000038 (v01 GBT    GBTUACPI 42302E31 GBTU 00000098)

[  +0.000004] ACPI: MCFG 0x00000000AFDEA180 00003C (v01 GBT    GBTUACPI 42302E31 GBTU 01010101)

[  +0.000004] ACPI: TAMG 0x00000000AFDEA1C0 00029A (v01 GBT    GBT   B0 5455312E BG?? 53450101)

[  +0.000004] ACPI: APIC 0x00000000AFDE9A00 000084 (v01 GBT    GBTUACPI 42302E31 GBTU 01010101)

[  +0.000005] ACPI: Reserving FACP table memory at [mem 0xafde3040-0xafde30b3]

[  +0.000002] ACPI: Reserving DSDT table memory at [mem 0xafde30c0-0xafde99de]

[  +0.000002] ACPI: Reserving FACS table memory at [mem 0xafde0000-0xafde003f]

[  +0.000002] ACPI: Reserving SSDT table memory at [mem 0xafde9ac0-0xafdea13e]

[  +0.000001] ACPI: Reserving HPET table memory at [mem 0xafdea140-0xafdea177]

[  +0.000002] ACPI: Reserving MCFG table memory at [mem 0xafdea180-0xafdea1bb]

[  +0.000002] ACPI: Reserving TAMG table memory at [mem 0xafdea1c0-0xafdea459]

[  +0.000001] ACPI: Reserving APIC table memory at [mem 0xafde9a00-0xafde9a83]

[  +0.000015] ACPI: Local APIC address 0xfee00000

[  +0.000143] ACPI: PM-Timer IO Port: 0x4008

[  +0.000002] ACPI: Local APIC address 0xfee00000

[  +0.000006] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])

[  +0.000003] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])

[  +0.000001] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])

[  +0.000002] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])

[  +0.000003] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)

[  +0.000002] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)

[  +0.000002] ACPI: IRQ0 used by override.

[  +0.000002] ACPI: IRQ9 used by override.

[  +0.000002] Using ACPI (MADT) for SMP configuration information

[  +0.000002] ACPI: HPET id: 0x10b9a201 base: 0xfed00000

[  +0.000003] Kernel command line: BOOT_IMAGE=/boot/kernel-5.10.128-gentoo root=/dev/sda1 ro net.ifnames=0 ipv6.disable=1 acpi_enforce_resources=lax

[  +0.000037] ACPI: Core revision 20200925

[  +0.001010] PM: Registering ACPI NVS region [mem 0xafde0000-0xafde2fff] (12288 bytes)

[  +0.000017] ACPI: bus type PCI registered

[  +0.001848] ACPI: Added _OSI(Module Device)

[  +0.000033] ACPI: Added _OSI(Processor Device)

[  +0.000033] ACPI: Added _OSI(3.0 _SCP Extensions)

[  +0.000032] ACPI: Added _OSI(Processor Aggregator Device)

[  +0.000033] ACPI: Added _OSI(Linux-Dell-Video)

[  +0.000033] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)

[  +0.000000] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)

[  +0.003611] ACPI: 2 ACPI AML tables successfully acquired and loaded

[  +0.000230] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000043] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000043] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000045] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000048] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000042] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000554] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000046] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000042] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000046] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000045] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000045] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000046] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000127] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000045] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKA (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKB (20200925/dspkginit-438)

[  +0.000040] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKC (20200925/dspkginit-438)

[  +0.000041] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element — LNKD (20200925/dspkginit-438)

[  +0.001943] ACPI: Interpreter enabled

[  +0.000056] ACPI: (supports S0 S3 S5)

[  +0.000033] ACPI: Using IOAPIC for interrupt routing

[  +0.000104] PCI: Using host bridge windows from ACPI; if necessary, use «pci=nocrs» and report a bug

[  +0.000201] ACPI: Enabled 5 GPEs in block 00 to 1F

[  +0.005327] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])

[  +0.000046] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]

[  +0.000253] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[  +0.000098] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[  +0.000098] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[  +0.000104] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[  +0.000096] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[  +0.000096] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[  +0.000099] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[  +0.000098] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[  +0.000000] ACPI: bus type USB registered

[  +0.000151] PCI: Using ACPI for IRQ routing

[  +0.000086] pnp: PnP ACPI init

[  +0.000000] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)

[  +0.000046] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)

[  +0.000182] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)

[  +0.000027] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active)

[  +0.000239] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)

[  +0.000241] pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)

[  +0.000123] pnp 00:06: Plug and Play ACPI device, IDs PNP0303 (active)

[  +0.000038] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)

[  +0.000037] system 00:08: Plug and Play ACPI device, IDs PNP0c01 (active)

[  +0.000022] pnp: PnP ACPI: found 9 devices

[  +0.036118] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns

[  +0.000061] ACPI: Power Button [PWRB]

[  +0.000853] ACPI: Power Button [PWRF]

[  +0.000132] parport_pc 00:05: reported by Plug and Play ACPI

[  +0.000017] acpi_cpufreq: overriding BIOS provided _PSD data



and here are the firmware messages:

Code:
$ dmesg -H | grep -i firmw

[  +0.000044] pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can’t size)

[  +0.000005] Loading firmware: radeon/RS780_pfp.bin

[  +0.000003] Loading firmware: radeon/RS780_me.bin

[  +0.000004] Loading firmware: radeon/R600_rlc.bin

[  +0.000004] Loading firmware: radeon/RS780_uvd.bin



Searching the Internet on the pci Firmware Bug gets a lot of hits. Thanks again for asking.

ADDING:

Code:
$ dmesg -H | grep -i microcod

[  +0.000010] [drm] Loading RS780 Microcode

[  +0.002861] microcode: CPU0: patch_level=0x01000095

[  +0.002634] microcode: CPU1: patch_level=0x01000095

[  +0.002432] microcode: CPU2: patch_level=0x01000095

[  +0.000032] microcode: Microcode Update Driver: v2.2.


_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area
PostPosted: Fri Jul 15, 2022 6:54 pm    Post subject: Reply with quote
Looks like someone else had a similar question/problem with acpi

https://forums.gentoo.org/viewtopic-t-976240-start-0.html

Interestingly enough, when he swapped to efi csm then the messages went away.

Sounds like acpi doesn’t have all the info on pci devices/interrupts and thus the complaints disabled,

but if I understand it right anything on those interrupts can’t be used by the kernel.

You might do a «dmesg |grep -i irq and see if any of these are in use => 3 4 5 6 7 10 11

You can also look under /sys/kernel/irq/<irq #>/<files>

the files are read only there won’t be much info if they aren’t being used by a device, otherwise it might give you an idea which device(s) it’s complaining about.

On my system, irq 2 isn’t used

Code:
/sys/kernel/irq $ ls 2

actions  chip_name  hwirq  name  per_cpu_count  type  wakeup

don@don64 /sys/kernel/irq $ cat 2/*

XT-PIC

0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

edge

disabled

irq 8 is

Code:
/sys/kernel/irq $ ls 8

actions  chip_name  hwirq  name  per_cpu_count  type  wakeup

don@don64 /sys/kernel/irq $ cat 8/*

rtc0

IR-IO-APIC

8

edge

0,0,0,0,0,0,0,0,0,19,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

edge

disabled

Not all entries will return a value. but I can see that irq 8 has something to do with time (rtc)

As far as whether the AE error messages are harmless or not, I don’t know.

To me it says something is not being understood, at least at the time the kernel was booting
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland

copy of my local repo
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Fri Jul 15, 2022 7:36 pm    Post subject: Reply with quote
Interesting for sure. For what it’s worth, I boot with BIOS/GRUB. I have UEFI disabled.

Code:
$ dmesg | grep -i irq

[Thu Jul 14 20:15:31 2022] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)

[Thu Jul 14 20:15:31 2022] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)

[Thu Jul 14 20:15:31 2022] ACPI: IRQ0 used by override.

[Thu Jul 14 20:15:31 2022] ACPI: IRQ9 used by override.

[Thu Jul 14 20:15:31 2022] NR_IRQS: 2304, nr_irqs: 448, preallocated irqs: 16

[Thu Jul 14 20:15:31 2022] spurious 8259A interrupt: IRQ7.

[Thu Jul 14 20:15:31 2022] __common_interrupt: 1.55 No irq handler for vector

[Thu Jul 14 20:15:31 2022] __common_interrupt: 2.55 No irq handler for vector

[Thu Jul 14 20:15:31 2022] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[Thu Jul 14 20:15:31 2022] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[Thu Jul 14 20:15:31 2022] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[Thu Jul 14 20:15:31 2022] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[Thu Jul 14 20:15:31 2022] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[Thu Jul 14 20:15:31 2022] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[Thu Jul 14 20:15:31 2022] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[Thu Jul 14 20:15:31 2022] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.

[Thu Jul 14 20:15:31 2022] PCI: Using ACPI for IRQ routing

[Thu Jul 14 20:15:31 2022] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0

[Thu Jul 14 20:15:31 2022] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled

[Thu Jul 14 20:15:31 2022] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A

[Thu Jul 14 20:15:31 2022] [drm] radeon: irq initialized.

[Thu Jul 14 20:15:32 2022] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]

[Thu Jul 14 20:15:32 2022] ata1: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 22

[Thu Jul 14 20:15:32 2022] ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 22

[Thu Jul 14 20:15:32 2022] ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 22

[Thu Jul 14 20:15:32 2022] ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 22

[Thu Jul 14 20:15:32 2022] ata5: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f300 irq 22

[Thu Jul 14 20:15:32 2022] ata6: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f380 irq 22

[Thu Jul 14 20:15:32 2022] ata7: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14

[Thu Jul 14 20:15:32 2022] ata8: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15

[Thu Jul 14 20:15:32 2022] ehci-pci 0000:00:12.2: irq 17, io mem 0xfe02c000

[Thu Jul 14 20:15:32 2022] ehci-pci 0000:00:13.2: irq 19, io mem 0xfe029000

[Thu Jul 14 20:15:32 2022] ohci-pci 0000:00:12.0: irq 16, io mem 0xfe02e000

[Thu Jul 14 20:15:32 2022] ohci-pci 0000:00:12.1: irq 16, io mem 0xfe02d000

[Thu Jul 14 20:15:32 2022] ohci-pci 0000:00:13.0: irq 18, io mem 0xfe02b000

[Thu Jul 14 20:15:32 2022] ohci-pci 0000:00:13.1: irq 18, io mem 0xfe02a000

[Thu Jul 14 20:15:33 2022] ohci-pci 0000:00:14.5: irq 18, io mem 0xfe028000

[Thu Jul 14 20:15:33 2022] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1

[Thu Jul 14 20:15:33 2022] serio: i8042 KBD port at 0x60,0x64 irq 1

[Thu Jul 14 20:15:33 2022] rtc_cmos 00:02: alarms up to one month, 242 bytes nvram, hpet irqs

[Thu Jul 14 20:15:33 2022]   #1: HDA ATI HDMI at 0xfdffc000 irq 19

[Thu Jul 14 20:15:41 2022] r8169 0000:02:00.0 eth0: RTL8168c/8111c, 00:24:1d:2a:5b:3b, XID 3c4, IRQ 25

[Thu Jul 14 20:15:52 2022] RTL8211B Gigabit Ethernet r8169-0-200:00: attached PHY driver [RTL8211B Gigabit Ethernet] (mii_bus:phy_addr=r8169-0-200:00, irq=IGNORE)



and,

Code:
$ cat /sys/kernel/irq/2/*

XT-PIC

0,0,0

edge

disabled

$ cat /sys/kernel/irq/8/*

rtc0

IO-APIC

8

edge

0,1,0

edge

disabled


_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area
PostPosted: Fri Jul 15, 2022 8:10 pm    Post subject: Reply with quote
I see

parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]

and irq 7 is one of those that LNK? doesn’t think anything is using it.

Wonder why acpi doesn’t think anything is there, that’s the parallel port ( I believe )

00:04: ttyS0 at I/O 0x3f8 (irq = 4,

serial port.

If you’re not using those you might shut them off in the bios.

On my systems in the past with those ports, if I had no devices on them I disabled them in the bios.

Nothing else shows in your list, but there may be things there which might show under /sys/kernel/irq/<whatever>

Edit to add: Now that I think about it, all those IRQs mentioned are the old standard pc interrupts 1-7 and 8-15 with cascade on irq 2.

Those would be considered legacy devices, not sure what all options you have in your bios for controlling IRQs and things like serial/parallel ports

but you might just tool around in the corners to see if there is something that needs setting OR unsetting.

Code:
IRQ 3 – serial port controller for serial port 2 (shared with serial port 4, if present)

IRQ 4 – serial port controller for serial port 1 (shared with serial port 3, if present)

IRQ 5 – parallel port 3 or sound card

IRQ 6 – floppy disk controller

IRQ 7 – parallel port 1

10 and 11 are left open for things like scsi or nic.

So unless you have devices on those IRQs then the messages are harmless, though they should be warnings not errors, and thus could be shut off, as far as logging.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland

copy of my local repo
Back to top

View user's profile Send private message

figueroa
Advocate
Advocate

Joined: 14 Aug 2005
Posts: 2724
Location: Edge of the Marsh USA
PostPosted: Fri Jul 15, 2022 8:41 pm    Post subject: Reply with quote
I really should disable those devices. 12-13 years ago I would have the parallel port and two serial ports in active use. Now everything is network and USB. That will be my next trick. Thanks for mentioning those.
_________________
Andy Figueroa

hp pavilion hpe h8-1260t/2AB5; spinning rust x3

i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570

amd64/17.1/desktop (stable), OpenRC, -systemd -pulseaudio
Back to top

View user's profile Send private message

Display posts from previous:   

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Источник

Bug 202655
— AE_NOT_FOUND, While resolving a named reference package element GA-MA790XT-UD4P — AMD Phenom™ II X6

Summary:

AE_NOT_FOUND, While resolving a named reference package element GA-MA790XT-UD…

Status: NEW

Alias:

 None

Product:

 ACPI

Classification:

 Unclassified

Component:

 ACPICA-Core

(show other bugs)

Hardware:

 x86-64
Linux

Importance:

P1
normal

Assignee:

 acpi_acpica-core@kernel-bugs.osdl.org

URL:

Keywords:

Depends on:

Blocks:

Reported: 2019-02-23 16:47 UTC by sunwebrw
Modified: 2019-09-07 09:44 UTC
(History)

CC List:

 3
users

(show)

See Also:

Kernel Version:

 4.19.23

Tree:

 Mainline

Regression:

 No

Attachments

acpidump


(148.52 KB,
text/plain)

2019-02-23 16:47 UTC,

sunwebrw

 Details


Add an attachment
(proposed patch, testcase, etc.)

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Acpi bios error при установке windows 10
  • Acpi bios error при установке linux
  • Acpi bios error windows 10 при загрузке ноутбука
  • Acpi bios error supermicro
  • Acpi bios error failure creating named object ubuntu

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии