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
|
# (отредактировано 5 лет, 7 месяцев назад) |
|
|
Темы: 3 Сообщения: 14 Участник с: 26 июня 2017 |
Доброе время суток, господа! Как говорится: «поможите кто чем может». После нескольких лет на Debian решил перебраться на Arch linux, но возникли некоторые трудности: ТТХ: MSI GE70 2OE ms-1757, HDD 1T GPT UEFI, Nvidia GF750 2G (WIFI, bluetooth — realtec, Ethernet — Ateros). Установил базовую систему (512mb efi, 8G swap, 100G ext4 /, 200G ext4 /home, 1G ext2 /boot) и вроде бы даже, после перезагрузки, завелась и работает, но… на начальном загрузочном экране появляются надписи об ошибках: Объясните пожалуйста, что это и если возможно, как это можно вылечить. |
|
vasek |
# (отредактировано 5 лет, 7 месяцев назад) |
|
Темы: 47 Сообщения: 11417 Участник с: 17 февраля 2013 |
Эти сообщения обусловлены таблицей DSDT. Если все работает нормально, забей. Ошибки не исчезают с опытом — они просто умнеют |
|
indeviral |
# (отредактировано 5 лет, 7 месяцев назад) |
|
Темы: 39 Сообщения: 3170 Участник с: 10 августа 2013 |
попробуйте отключить, дискретную видеокарту в биос.
Ошибки в тексте-неповторимый стиль автора© |
|
vasek |
# (отредактировано 5 лет, 7 месяцев назад) |
|
Темы: 47 Сообщения: 11417 Участник с: 17 февраля 2013 |
Там где указаны методы _SB.PCIO….. , это однозначно ошибки/варнинги таблицы DSDT, а вот где указано EmbeddedControl возможно связаны как то еще и с ядром, нужно смотреть и гуглить. В начале года похожие сообщения обсуждались вроде бы на BBS, но точно не помню.
Ошибки не исчезают с опытом — они просто умнеют |
|
hathory |
# (отредактировано 5 лет, 7 месяцев назад) |
|
Темы: 3 Сообщения: 14 Участник с: 26 июня 2017 |
Спасибо, видюху сегодня попробую отключить. Если меня память не подводит, то таблицы DSDT это весь перечень оборудования передаваемый BIOS в ОС. vasek, спасибо, натолкнули на мысль — EmbeddedControl — подозреваю это контроллер RAID массива, на ноуте есть две шины для организации RAIDа на ssd интерфейса М2. Да может быть именно с ними проблема и возникает. А вот с «таблицы DSDT» совсем непонятно, мне технических знаний не хватает, биолог я по образованию. |
|
vasek |
# (отредактировано 5 лет, 7 месяцев назад) |
|
Темы: 47 Сообщения: 11417 Участник с: 17 февраля 2013 |
Повторюсь, если все работает, то и забей на эти таблицы. Как то уже описывал, как можно проверить и узнать все ошибки и варнинги таблицы DSDT и, главное, они практически есть у всех. Ошибки не исчезают с опытом — они просто умнеют |
|
vasek |
# |
|
Темы: 47 Сообщения: 11417 Участник с: 17 февраля 2013 |
У меня как то выскочила ошибка MCE, пришлось установить mcelog для контроля и в загрузочных логах стали выскакивать сообщения
Но на работу это не влияет и вообщем то сообщения, как пишут, безобидные. Ошибки не исчезают с опытом — они просто умнеют |
|
vasek |
# (отредактировано 5 лет, 7 месяцев назад) |
|
Темы: 47 Сообщения: 11417 Участник с: 17 февраля 2013 |
Посмотрел внимательнее твои сообщения. Первые три относятся к Embeded Controller, подключенному к LPC bus (Low Pin Count bus) — что это за контроллер, нужно разбираться конкретно.
Следующие два относятся к видеокартам (интегрированной и дискретной)
Что конкретно это означает — нужно смотреть саму таблицу, но смысла в этом не вижу, если все работает. PS … забыл подметить — _BCL — Brightness Control Levels — связано с подсветкой Ошибки не исчезают с опытом — они просто умнеют |
|
hathory |
# (отредактировано 5 лет, 7 месяцев назад) |
|
Темы: 3 Сообщения: 14 Участник с: 26 июня 2017 |
vasek, спасибо большое, да с видеокартами проблема решилась, поставил Bumblebee и ошибки пропали (правда Bluetooth отвалился, но это решабельно, и подозреваю что из-за tlp). Из LPC bus — на ноуте только встроенная камера — bison, подозреваю дело именно в ней. BCL — Brightness Control Levels — нет такой, у старших моделей моей линейки ноутов есть, у моего нет, но видимо BIOS имеет упоминание о подсветке =) vasek, еще раз спасибо большое, прям жить стало приятно. |
I have problem with BIOS on my laptop. It looks like a bug with error code, some method(s) is not implemented.
ACPI BIOS error (bug): Could not resolve [SB.PCI0.LPCB.HEC.ECAV], AE_NOT_FOUND (20181213/psargs-330)
ACPI Error: Method parse/execution failed TZ.FNCL, AE_NOT_FOUND (20181213/pspargs-531)
ACPI Error: Method parse/execution failed TZ.FN01._ON, AE_NOT_FOUND (20181213/pspargs-531) ….
You can find more information on the screenshots
I’ve tryed to use option nouveau.setmode=0 after — in grub (edit mode) Also nomodeset option, it doesn’t help with installation.
nouveau.setmode=0 option
Once by some miracle ubuntu distr have done the setup, without any errors, but after reloading I haven’t seen anything in boot options (UEFI)
I followed the instruction by ubuntu server instalation https://www.pugetsystems.com/labs/hpc/The-Best-Way-To-Install-Ubuntu-16-04-with-NVIDIA-Drivers-and-C… and faced with the same problems
Only one way to drop this error — add option acpi=off but in this case I have no a lot of features on my laptop
I tried to connect with HP support assistants but they told me — we don’t support any linux distrs, only windows, sorry. Maybe later we’ll update BIOS, and your problem will be solved.
Could anybody help me to fix this issue?
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
danny_h69
- Level 1
- Posts: 4
- Joined: Thu Jul 20, 2017 8:03 am
- Location: Australia
[SOLVED] ACPI errors on boot
Hi everyone. I am still very «green» when it comes to Linux (pun sort of intended) so please be patient.
I have previously run Linux Mint 18.1 Serena 64bit Cinnamon on this new SSD on the same machine without (these) issues. I have a separate SSD that has Win10 installed. The system boots and I can select the linux drive without any problems. The home folder is encrypted. I recently changed to Sonya and now that on boot the Mint logo comes up with the section to enter the password to setup the crypt (un-encrypt). Of note is that the logo and field appears large (using on-board graphics?) I am unable to enter anything into the field. I then have to re-start the machine and select the linux drive (via boot menu) and then the first option.
I then get the ACPI errors (listed below) before a command line that then lets me enter the encryption password. The disk d-encrypts happily and then onto welcome screen etc. The system then seems to work well.
Result of: inxi -F && dmesg | grep -i error (I found the query on another site with a similar problem but with no solution…)
Code: Select all
daniel@Minty ~ $ inxi -F && dmesg | grep -i error
System: Host: Minty Kernel: 4.10.0-30-generic x86_64 (64 bit)
Desktop: Cinnamon 3.4.6 Distro: Linux Mint 18.2 Sonya
Machine: System: Gigabyte product: N/A
Mobo: Gigabyte model: Z77X-UD5H
Bios: American Megatrends v: F16h date: 07/11/2016
CPU: Quad core Intel Core i7-3770K (-HT-MCP-) cache: 8192 KB
clock speeds: max: 3900 MHz 1: 1599 MHz 2: 1671 MHz 3: 1607 MHz
4: 1621 MHz 5: 1624 MHz 6: 1623 MHz 7: 1837 MHz 8: 1616 MHz
Graphics: Card: NVIDIA GK107 [GeForce GTX 650]
Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
Resolution: 1920x1080@60.00hz
GLX Renderer: GeForce GTX 650/PCIe/SSE2
GLX Version: 4.5.0 NVIDIA 384.59
Audio: Card-1 Intel 7 Series/C210 Series Family High Definition Audio Controller
driver: snd_hda_intel
Card-2 NVIDIA GK107 HDMI Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.10.0-30-generic
Network: Card-1: Intel 82579V Gigabit Network Connection driver: e1000e
IF: eno1 state: down mac: 94:de:80:61:78:7b
Card-2: Qualcomm Atheros AR8161 Gigabit Ethernet driver: alx
IF: enp7s0 state: up speed: 1000 Mbps duplex: full
mac: 94:de:80:61:78:6b
Drives: HDD Total Size: 2525.5GB (9.2% used)
ID-1: /dev/sda model: CT250BX100SSD1 size: 250.1GB
ID-2: /dev/sdb model: Crucial_CT275MX3 size: 275.1GB
ID-3: /dev/sdc model: ST2000DM001 size: 2000.4GB
Partition: ID-1: / size: 221G used: 13G (6%) fs: ext4 dev: /dev/dm-1
ID-2: /boot size: 472M used: 388M (87%) fs: ext2 dev: /dev/sdb1
ID-3: swap-1 size: 34.31GB used: 0.00GB (0%) fs: swap dev: /dev/dm-3
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 36C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 277 Uptime: 40 min Memory: 1763.0/32130.1MB
Client: Shell (bash) inxi: 2.2.35
[ 1.166429] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 1.166513] ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT1._GTF] (Node ffff935d7e0dc1e0), AE_NOT_FOUND (20160930/psparse-543)
[ 1.166632] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 1.166724] ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff935d7e0dcd48), AE_NOT_FOUND (20160930/psparse-543)
[ 1.166830] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 1.166902] ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT2._GTF] (Node ffff935d7e0dcc58), AE_NOT_FOUND (20160930/psparse-543)
[ 1.167007] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 1.167076] ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT0._GTF] (Node ffff935d7e0dc2f8), AE_NOT_FOUND (20160930/psparse-543)
[ 1.167667] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 1.167741] ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT0._GTF] (Node ffff935d7e0dc2f8), AE_NOT_FOUND (20160930/psparse-543)
[ 1.167841] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 1.167911] ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT2._GTF] (Node ffff935d7e0dcc58), AE_NOT_FOUND (20160930/psparse-543)
[ 1.168779] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 1.168873] ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT1._GTF] (Node ffff935d7e0dc1e0), AE_NOT_FOUND (20160930/psparse-543)
[ 1.188180] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[ 1.188286] ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff935d7e0dcd48), AE_NOT_FOUND (20160930/psparse-543)
[ 17.804662] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
daniel@Minty ~ $I was going to just re-install Serena, but I thought I’d give the forum a try first. 
Ideally I just want to be able to select the linux drive and have the mint logo and logon screen come up and work from there. Any thoughts?
Regards,
Dan.
Last edited by danny_h69 on Sat Aug 19, 2017 4:49 am, edited 2 times in total.
-
danny_h69
- Level 1
- Posts: 4
- Joined: Thu Jul 20, 2017 8:03 am
- Location: Australia
Re: ACPI errors on boot
Post
by danny_h69 » Thu Aug 17, 2017 9:37 pm
Thanks Catweazel. I’ll try that today…
Ahh, that’s a show that brings back memories… and probably gives our ages away.
Cheers
Dan
-
danny_h69
- Level 1
- Posts: 4
- Joined: Thu Jul 20, 2017 8:03 am
- Location: Australia
Re: ACPI errors on boot
Post
by danny_h69 » Sat Aug 19, 2017 4:48 am
Ok. Tried changing kernels, but didn’t work. I had some suspicion that there was some sort of error or conflict with the graphics card drivers. When I chose the Linux distro/drive the Linux Mint logo and encryption password field looked like it was using very basic graphics and wouldn’t allow me to enter anything into the field. The other ACPI errors came up after a couple of attempts to login.
I was running the current nVidia drivers, so I reverted back to the xserver-xorg-video-nouveau driver and rebooted. Lo and behold, correct graphics resolution and a usable password field. Entered passwords and hey presto logged in no problems.
I could have left it there, but I wanted to be able to use the nVidia drivers.
Here’s the solution I found that worked. https://community.linuxmint.com/tutorial/view/176
Basically I opened the /etc/default/grub file using Nemo to gain elevated privileges.
Added «nouveau.blacklist=1» to the line «GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash»
Should look something like this: «GRUB_CMDLINE_LINUX_DEFAULT=»nouveau.blacklist=1 quiet splash» acpi=force apm=power_off»
Saved the grub file then rebooted. Then reverted back to nVidia drivers and rebooted again. Now it works! Excellent… one step closer to giving Microgreed the flick once and for all.
Hope this helps someone else out there.
Cheers
Dan
-
[vanicci]
Re: [SOLVED] ACPI errors on boot
Post
by [vanicci] » Tue Mar 20, 2018 1:26 pm
Hi Dan, glad that you fix the problem.
I’m currently experiencing the same problem and I am not a programmer so it’s rather challenging for me to understand the steps that you had to go through.
I have a question about this:
«Basically I opened the /etc/default/grub file using Nemo to gain elevated privileges.
Added «nouveau.blacklist=1» to the line «GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash»
Should look something like this: «GRUB_CMDLINE_LINUX_DEFAULT=»nouveau.blacklist=1 quiet splash» acpi=force apm=power_off»
Saved the grub file then rebooted. Then reverted back to nVidia drivers and rebooted again. Now it works! Excellent… one step closer to giving Microgreed the flick once and for all.»
Where do you «open» the /etc/default/grub file? Do I need to go to Boot Manager?
I am trying to explore Linux Mint dual booting my old laptop (bought Nov 2015) as I heard many great things about Linux. Since I am just starting to learn Python I would like to play around with Linux Mint for the first time.
My machine is: https://goo.gl/XKkn9u
ACER Aspire F5-571 15.6″ Laptop — Intel® Core™ i3-5005U (5th Generation) — 4GB Ram — 1TB HDD — DVD/RW — Windows 10
So I installed Linux Mint 18.3 Sylvia into my USB using Rufus (followed a tutorial online).
At first, I used [UEFI] as the «Boot Mode» but when I ran it, it was just black screen and nothing else.
I read somewhere to change it to [Legacy], so I did.
When I started booting the USB, I just see all these «ACPI errors.»
See screenshot here:
https://ibb.co/ky3jxx
I also tried changing the USB ports — it didn’t work.
I even bought a new USB and installed «fresh» — didn’t work neither.
If you can just direct me where to «open» the /etc/default/grub file and the rest of the steps, that would be much appreciated.
Regards,
[vanicci]
-
Moem
- Level 22
- Posts: 15163
- Joined: Tue Nov 17, 2015 9:14 am
- Location: The Netherlands
- Contact:
Re: [SOLVED] ACPI errors on boot
Post
by Moem » Tue Mar 20, 2018 1:41 pm
[vanicci] wrote: ↑
Tue Mar 20, 2018 1:26 pm
Hi Dan, glad that you fix the problem.I’m currently experiencing the same problem and I am not a programmer so it’s rather challenging for me to understand the steps that you had to go through.
The poster hasn’t been back here since their problem was solved, so you might be better off posting a new thread. Threads that are marked as solved don’t always attract as much attention.
If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!
-
jak_jak221
Re: [SOLVED] ACPI errors on boot
Post
by jak_jak221 » Sat Aug 31, 2019 4:39 pm
I had a similar problem like this. After entering emergency mode and running journalctl -xb I received ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364). This happened after I had cloned my disk using dd. After running the system in recovery mode I discovered an error stating that the previous UUID assigned to the disk that contains the clone could no longer be found. I commented out the line in the fstab file and restarted the computer. The system ran as normal. While dd did clone the data from the original disk to the new disk, it also carried over the UUID and since the fstab file contained the old UUID the computer couldn’t find it and launched into emergency mode. Watch out for this if you are new to dd.
I know you are new, and we all started out new ,you can learn a lot by learning to just copy/paste the error messages into a search engine. In this case you will see it is a common error message, also maybe there is no solution. on that I don’t know for sure, since it is not my problem I have no reason to read all the results and seem , but any way:
by hack3rcon »How can I solve it?
You start by searching for information, based on the error messages, that is what they are for, below is a example:
I copy /paste the error message into a search engine:
Code: Select all
ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT5._GET, AE_NOT_FOUND (20180810/psparse-516)First hit, of many : https://forum.manjaro.org/t/acpi-error- … 1/15474/13
Looks like this is a Bug across all of Linux. Although I have very limited knowledge of how these things work. Still trying to find a kernel parameter that will disable the spewing of this text. If anything you could go post your logs on the bug report for further evidence.
========== back to :
by hack3rcon »How can I solve it?
So, after reading the first result, you should also read the others, then if you find any that offer solutions, start trying them , if you do find one that works, of course tell us here as well.
You ask «How can I slove it ?» , but if you can not or do not want to make some effort your self, or just do not find a solution, feel free to ask: «Can some one hold my hand and help me solve this ? » and someone will.
There is no reason you can not solve this yourself, if you put some effort into it, me, I ignore many of the error messages when booting, and as long as everything is working ok, they are irrelevant.
Hint, also sometimes the out put of ‘dmesg’ is usefull,…you run ‘dmesg’, and review the errors , if any. SOMETIMES, but not all ways, ‘dmesg’ reveals the cause of the problem.
Please Read What we expect you have already Done
Search Engines know a lot, and
«If God had wanted computers to work all the time, He wouldn’t have invented RESET buttons»
and
Just say NO to help vampires!
- Печать
Страницы: [1] Вниз
Тема: ACPI Error (dmesg log) Ubuntu 13.04 (Прочитано 6584 раз)
0 Пользователей и 1 Гость просматривают эту тему.
dr-kart
dmesg ругаеццо
[ 0.806004] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
[ 0.806007] ACPI Error: Method parse/execution failed [_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff8802120679b0), AE_NOT_FOUND (20121018/psparse-537)
[ 0.807402] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
[ 0.807406] ACPI Error: Method parse/execution failed [_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff8802120679b0), AE_NOT_FOUND (20121018/psparse-537)
[ 0.807490] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
[ 0.807493] ACPI Error: Method parse/execution failed [_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880212067a28), AE_NOT_FOUND (20121018/psparse-537)
[ 0.808346] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
[ 0.808350] ACPI Error: Method parse/execution failed [_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880212067a28), AE_NOT_FOUND (20121018/psparse-537)
По ссылкам гугла ходил и так ничего и не понял. Что делать?
« Последнее редактирование: 01 Июня 2013, 14:02:44 от dr-kart »
dr-kart
всё что я понял это: после обновления биос, сделать disable acpi.
Биос обновил (v.12 от 18.04.2013). В логе те же ошибки.
Народ всё-таки (гугление) рапортует о баге в линухе, afaik.
Разъясните мне, ибо (я тупой) 
Пользователь решил продолжить мысль 01 Июня 2013, 15:12:30:
Не пойму что делать. Первая ссылка гугления по первой Error строке моего dmesq log:
Kernel 3.8.0: USB devices don’t work at all (regression from 3.7.0)
http://www.spinics.net/lists/linux-usb/msg80021.html
« Последнее редактирование: 01 Июня 2013, 15:17:27 от dr-kart »
Den78
« Последнее редактирование: 01 Июня 2013, 15:32:16 от Den78 »
dr-kart
btw, у меня не ноут, и нет bumblbee.
У меня «ровная» intel B75 материнка + Nvidia дискретно.
dr-kart
попробовал загрузку liveCD ubuntu 12.04.02.
По «F6» выбирал:
[1] noapic — не помогает, те же ошибки в логе
[2] acpi off — лог без ошибок. Но система даже разрешение экрана не определила корректно
[3] ничего не выбирал (загрузка по умолчанию) — те же ошибки в логе
На десерт, puppy 5.5 с ядром 3.4.17. Ошибки те же.
dmesg | grep Error
[ 1.041986] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
[ 1.041993] ACPI Error: Method parse/execution failed [_SB_.PCI0.SAT0.SPT5._GTF] (Node f3060770), AE_NOT_FOUND (20120320/psparse-536)
[ 1.042177] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
[ 1.042182] ACPI Error: Method parse/execution failed [_SB_.PCI0.SAT0.SPT4._GTF] (Node f30607b8), AE_NOT_FOUND (20120320/psparse-536)
[ 1.042817] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
[ 1.042822] ACPI Error: Method parse/execution failed [_SB_.PCI0.SAT0.SPT5._GTF] (Node f3060770), AE_NOT_FOUND (20120320/psparse-536)
[ 1.043069] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
[ 1.043074] ACPI Error: Method parse/execution failed [_SB_.PCI0.SAT0.SPT4._GTF] (Node f30607b8), AE_NOT_FOUND (20120320/psparse-536)
# uname -a
Linux puppypc23937 3.4.17-PAE #1 SMP Fri Nov 2 19:12:33 EST 2012 i686 Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz GenuineIntel GNU/Linux Что делать? Надоел секс с линуксом.
uneex@ya.ru
Надоел Линух?
Переходи на BSD.
Беркли дал миру две вещи
LSD и BSD,
я не думаю,
что это — случайность.
Аноним (с)
А ошибки эти, из-за криворукости интеловских прожектёров, которые написали свой безумный ACPI крайне убого, а те кто должен, так сказать реализовывать его — ещё тупее, вообще не вникают что за код там должен быть. У меня, на BSD — та же ошибка, но вообще (у нас) есть утилита acpidump, которая позволяет вытащить байт-код из бивиса и поправить, а затем подменять своим при загрузке. Меня на это — не хватает. ACPI — вообще большая помойка, кажись потому и запутаная, что создана в интересах NSA.
- Печать
Страницы: [1] Вверх
-
#1
Hello everyone,
I have problem with my Proxmox and need to reboot machine, sometimes I need to hard reset. Computer works for 2 or 3 days and then the same problem occurs.
Here is part of log
ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[ 0.048483] No Local Variables are initialized for Method [PXSX]
[ 0.048484] No Arguments are initialized for method [PXSX]
[ 0.048485] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[ 0.048489] ACPI Error: Method parse/execution failed _SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[ 0.049662] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[ 0.049668] No Local Variables are initialized for Method [PXSX]
[ 0.049668] No Arguments are initialized for method [PXSX]
[ 0.049669] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[ 0.049672] ACPI Error: Method parse/execution failed _SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[ 0.050656] ACPI Error: [_SB_.PCI0.RP13.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[ 0.050661] No Local Variables are initialized for Method [PXSX]
[ 0.050662] No Arguments are initialized for method [PXSX]
[ 0.050663] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[ 0.050666] ACPI Error: Method parse/execution failed _SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[ 0.057410] ACPI Error: [_SB_.PCI0.RP05.PXSX.WIST] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
[ 0.057410] No Local Variables are initialized for Method [CNDP]
[ 0.057410] No Arguments are initialized for method [CNDP]
[ 0.057410] ACPI Error: Method parse/execution failed CNDP, AE_NOT_FOUND (20170831/psparse-550)
[ 0.057410] ACPI Error: Method parse/execution failed , AE_NOT_FOUND (20170831/psparse-550)
there were an error for I/O
I’ve run test with smartctl -t long -a /dev/sda and no errors
Also I’ve upgraded kernel to the latest version.
I’m using ordinary computer:
Intel core I5-8400
ASUS Prime B360-Plus
4x8GB DDR4 Kingston 2666Mhz
SSD Kingston A400 480GB
Proxmox 5.3-8
I have more computers like this one and never had similar problem.
Also, there are 12 VMs that are running CentOS 6.
Could this be motherboard fault? This machine is assembled in March this year, so basically it’s new
Can someone help with this? Sorry for my poor english
Chris
Proxmox Staff Member
-
#3
Thanks for response. I thought about update BIOS but not sure will it help.
I will try with BIOS update.
I have also found this logs
[98846.565550] sd 3:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98846.565552] sd 3:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 35 14 6f d8 00 00 08 00
[98846.565553] print_req_error: I/O error, dev sda, sector 890531800
[98846.565803] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.617729] sd 3:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.617732] sd 3:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.617733] print_req_error: I/O error, dev sda, sector 890531464
[98848.618017] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.618493] sd 3:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.618494] sd 3:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.618495] print_req_error: I/O error, dev sda, sector 890531464
[98848.618784] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.688347] sd 3:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.688350] sd 3:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.688351] print_req_error: I/O error, dev sda, sector 890531464
[98848.688668] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.689149] sd 3:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.689151] sd 3:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.689152] print_req_error: I/O error, dev sda, sector 890531464
[98848.689481] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.748574] sd 3:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.748576] sd 3:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.748577] print_req_error: I/O error, dev sda, sector 890531464
[98848.748959] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.750243] sd 3:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.750245] sd 3:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 35 13 b8 68 00 00 08 00
[98848.750246] print_req_error: I/O error, dev sda, sector 890484840
[98848.750637] device-mapper: thin: process_cell: dm_thin_find_block() failed: e
-
#4
Thanks for response. I thought about update BIOS but not sure will it help.
I will try with BIOS update.I have also found this logs
[98846.565550] sd 3:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98846.565552] sd 3:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 35 14 6f d8 00 00 08 00
[98846.565553] print_req_error: I/O error, dev sda, sector 890531800
[98846.565803] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.617729] sd 3:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.617732] sd 3:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.617733] print_req_error: I/O error, dev sda, sector 890531464
[98848.618017] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.618493] sd 3:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.618494] sd 3:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.618495] print_req_error: I/O error, dev sda, sector 890531464
[98848.618784] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.688347] sd 3:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.688350] sd 3:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.688351] print_req_error: I/O error, dev sda, sector 890531464
[98848.688668] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.689149] sd 3:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.689151] sd 3:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.689152] print_req_error: I/O error, dev sda, sector 890531464
[98848.689481] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.748574] sd 3:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.748576] sd 3:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.748577] print_req_error: I/O error, dev sda, sector 890531464
[98848.748959] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.750243] sd 3:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.750245] sd 3:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 35 13 b8 68 00 00 08 00
[98848.750246] print_req_error: I/O error, dev sda, sector 890484840
[98848.750637] device-mapper: thin: process_cell: dm_thin_find_block() failed: e
That looks like a faulty disk.
-
#5
Yes, it does look, but still not sure if that’s the problem. Machine is working for about 3 days and then this happens.
I’m still new to linux so it’s a bit difficult for me to explain in more details.
When machine «freezes» this log for I/O occurs, I can’t type anything because it is writing constantly, so the only way to stop it is to hard reset machine.
I will try with BIOS update but I don’t think it will help. I think that the problem is ssd or in motherboard itself, and only way to find out is to replace ssd and see what will happen.
Or maybe is problem in power supply, maybe power supply is week and in one moment can’t deliver enough of power.
This problem is very complicated, never saw anything like it.
-
#6
Hello again.
So, 10 days ago I updated bios to the newest version and from then I didn’t encountered any problem.
For now this is working.
Still, I don’t know what truly caused the problem with ACPI since the motherboard is new and working since march.
So, if any of you encounter the same problem just update bios to the newest version, it should solve the porblem.
Thanks everyone for help.
Chris
Proxmox Staff Member
-
#7
Glad you are up and running without issues now. Please mark the thread as solved for others to ease the search.
-
#8
Hey guys, I have new info about this problem.
So, it wasn’t the problem in BIOS, it was in the SSD.
I found out that the writing speed of ssd is not as the vendor says (480GB to 500MB/s Read and 450MB/s Write)
I’ve tested it with crystal disk info and the writing speed was about 250MB/s writing. I did a little research on the internet and found out that vendor says that this is some bug in there firmware. In order to upgrade it, need to install their software which is written only for windows and also it will destroy your data.
So, I did that, but didn’t test it again, no time for that.
Just wanna to say, if someone having this issues like me, don’t use Kingstons cheap ssd’s if you have a lot of writing on the drive, use Samsung Evo 860 or other (I’m using Evo 860 on 7 different machines, 24h writing a lot of data, never had the problem with any of it).