You are not logged in.
Pages: 1
i ran "journalctl -p 3 -xb" to check for system errors as a general maintenance and then i see this:
kernel: xhci_hcd ... AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xfffd7040 flags=0x0020
so ive discovered this happens every time my system hibernates. mmaybe on startup, too, but im not sure.
i believe i may have installed something about xhci last night from the AUR to resolve some "missing firmware" issues on boot that i was having. does anybody know what this error is, if its a big deal, and how to fix it? thank you.
Offline
https://bugzilla.kernel.org/show_bug.cgi?id=204843
suspend my computer to disk and reboot it into Windows, xhci_hcd reproducibly prints into dmesg
Do you have a parallel windows as well?
If so, don't do what the bug reporter does (cycle between hibernating systems) and also see the 3rd link in my signature on the topic.
Online
no im not dual booting at all, just arch linux is installed
Offline
should i disable my fast startup in the bios?
Offline
No, that's unrelated.
Rather post the complete system journal ("sudo journalctl -b", no "-x". Never. It's just pointless spam)
Online
i dont know what to do. nothing seems broken, should i just ignore this? did you mean for me to post my journal without -x or to not do that, it wasnt clear to me
Offline
Please do post the journal with -b without -x assuming the last boot had the issue.
Offline
ok here it is without the -x. it happens every time i hibernate. i spent a long time creating a swap file and telling it to hibernate to it, adding "resume" to the hooks for the initramfs, etc, as outlined in the wiki. maybe its related to all of that.
-- Journal begins at Mon 2021-04-05 02:19:49 CDT, ends at Wed 2021-04-07 15:50:02 CDT. --
Apr 06 22:15:01 colbylaptop kernel: i2c_hid i2c-ELAN0504:01: HID over i2c has not been provided an Int IRQ
Apr 06 23:18:08 colbylaptop kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x109780040 flags=0x0070]
Apr 06 23:18:08 colbylaptop kernel: amdgpu 0000:05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x1097c0000 flags=0x0070]
Apr 06 23:58:21 colbylaptop kernel: xhci_hcd 0000:05:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xfffd7040 flags=0x0020]
Apr 07 00:50:52 colbylaptop kernel: xhci_hcd 0000:05:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xfffd7040 flags=0x0020]
Apr 07 01:18:04 colbylaptop kernel: xhci_hcd 0000:05:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xfffd7040 flags=0x0020]
Apr 07 12:46:20 colbylaptop kernel: xhci_hcd 0000:05:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xfffd7040 flags=0x0020]
Apr 07 14:59:15 colbylaptop kernel: xhci_hcd 0000:05:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xfffd9040 flags=0x0020]
Apr 07 15:47:51 colbylaptop kernel: xhci_hcd 0000:05:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xfffd7040 flags=0x0020]
Last edited by caray (2021-04-07 20:53:40)
Offline
Really need the full journal to see what happens leading up to the issue.
If you just want to get rid of the message try booting with the kernel parameter iommu=soft
Offline
id really like to solve it though. how do i show the full journal?
Offline
https://wiki.archlinux.org/index.php/Li … in_clients drop the -p 3 use just -b
Offline
journalctl -b was insanely long, so i didnt wanna post it here. but i saw this:
Apr 08 23:43:03 colbylaptop kernel: usb usb1: root hub lost power or was reset
Apr 08 23:43:03 colbylaptop kernel: usb usb2: root hub lost power or was reset
Apr 08 23:43:03 colbylaptop kernel: usb usb3: root hub lost power or was reset
Apr 08 23:43:03 colbylaptop kernel: usb usb4: root hub lost power or was reset
Apr 08 23:43:03 colbylaptop kernel: xhci_hcd 0000:05:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000f address=0xfffd7040 flags=0x0020]
Offline
You can post it to ix.io.
Random excerpts are meaningless.
Online
If you read the link there are ways of uploading long outputs to a pastebin site these small bits an pieces can lack context, but this really sounds like the issue reported on the kernel bugzilla (... and hopefully the mailing list though I didn't explicitly check that)
Offline
Pages: 1