You are not logged in.
i got this from "journalctl -b -p err"
kernel: ACPI Error: No handler for Region [RAM_] (0000000094cba733) [EmbeddedControl] (20180810/evregion-132)
kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20180810/exfldio-265)
kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC0._REG, AE_NOT_EXIST (20180810/psparse-516)
kernel: ACPI Error: No handler for Region [RAM_] (0000000094cba733) [EmbeddedControl] (20180810/evregion-132)
kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20180810/exfldio-265)
kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC0._REG, AE_NOT_EXIST (20180810/psparse-516)
kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
kernel: pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
kernel: pcieport 0000:00:1c.5: [ 0] RxErr (First)
kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
kernel: pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
kernel: pcieport 0000:00:1c.5: [ 0] RxErr (First)what is it trying to tell?
Last edited by iSeven7 (2020-04-28 22:51:24)
Offline
Welcome to the boards. Please use [ code ] for pasting output.
The ACPI errors can be normal and simply tell you that your ACPI implementation contains some values the kernel couldn't parse. They are usually harmless and only really "fixable" by updating your UEFI/BIOS firmware and hope that the vendor fixed whatever error there was, however unless you notice something actively not working, the best course of action is usually to just ignore these.
The other message shows some error on the PCI bus, we'd need more information and context here, especially what kind of device is on that PCI bus. They could however also be normal, some devices have "problems" switching from power states for example. However as these show severity=Corrected means that whatever error there was could be fixed without repercussions. Just two occurrences of these are likely to be harmless and pending on what exactly happened on your system at that time, expected.
Offline
iSeven7, I saw your report asking to have this thread deleted because the problem is fixed. We like to have people report how they fixed a problem; this may help others who have the same or similar problem. See this section of the Code of Conduct: https://wiki.archlinux.org/index.php/Co … way_street
Offline
For PCIe errors you might consider disabling ASPM either globally with pcie_aspm=off in your kernel command line or with an udev rule (see https://wiki.archlinux.org/index.php/Po … Management). This seems to be a recurrent problem on laptops.
Last edited by singeinfini (2020-04-29 07:49:19)
Offline