6.7 AMD-Vi: Event logged [IO_PAGE_FAULT


9 posts in this topic Last Reply

Recommended Posts

So all the dockers on my server kinda of just stopped working, however I was able to at least log into the thing.    I've attached my log file if anyone can tell me what is going on or how to fix it I would greatly appreciate it.  I'm not sure what other information to give you so if you need other information to assist with trouble shooting please let me know and I can provide it.

wopr-syslog-20190603-0405.zip

Link to post

You need to give more information. Go to Tools -> Diagnostics and attach the complete zip file to you next post. This will show what PCIe device you have at 05:00.0 and a load of other useful information. I'm guessing but is it an Nvidia graphics card? Are you passing it through to a VM? Have you tried Googling the error message? You'll find several hits and only one of them is this page.

Link to post

I'll take a look at your diagnostics when I get a bit more time but are you saying that even with VMs disabled (in Settings -> VM Manager) you are still getting the AMD-Vi error? You might want to look for a BIOS update but be aware of this thread

 

 

and the fact that you're using a first generation Ryzen and therefore don't immediately need support for the 3000 series. Maybe version 4023 or 4207 from here would be a good compromise.

 

Link to post

The errors begin as the array starts and the first disk mounts:

Jun  2 23:02:07 WOPR emhttpd: Mounting disks...
Jun  2 23:02:07 WOPR emhttpd: shcmd (46): /sbin/btrfs device scan
Jun  2 23:02:08 WOPR root: Scanning for Btrfs filesystems
Jun  2 23:02:08 WOPR emhttpd: shcmd (47): mkdir -p /mnt/disk1
Jun  2 23:02:08 WOPR emhttpd: shcmd (48): mount -t xfs -o noatime,nodiratime /dev/md1 /mnt/disk1
Jun  2 23:02:08 WOPR kernel: SGI XFS with ACLs, security attributes, no debug enabled
Jun  2 23:02:08 WOPR kernel: XFS (md1): Mounting V5 Filesystem
Jun  2 23:02:08 WOPR kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x00000000fd2b9000 flags=0x0000]
Jun  2 23:02:08 WOPR kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x00000000fd2b9080 flags=0x0000]

Looking at lspci for the problem device at 05:00.0 we see:

04:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 04)
05:01.0 RAID bus controller [0104]: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller [1095:3114] (rev 02)
	Subsystem: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller [1095:7114]
	Kernel driver in use: sata_sil
	Kernel modules: sata_sil
08:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller [1912:0014] (rev 03)

So nothing actually at 05:00.0 but a SiI SATA controller at 05:01.0. So maybe some virtual device at 05:00.0? I haven't come across anyone using that particular card before so I'm not sure how compatible it is. You might try Googling "unraid sii 3114". It seems like an old card and there's mention of SATARaid, which makes me a little dubious. Can you tell me more about it? A link to the product on Amazon or wherever would be useful. You might want to think about replacing it. So, it's actually nothing to do with the Nvidia card, which is at 09:00.0.

Link to post
11 hours ago, John_M said:

The errors begin as the array starts and the first disk mounts:


Jun  2 23:02:07 WOPR emhttpd: Mounting disks...
Jun  2 23:02:07 WOPR emhttpd: shcmd (46): /sbin/btrfs device scan
Jun  2 23:02:08 WOPR root: Scanning for Btrfs filesystems
Jun  2 23:02:08 WOPR emhttpd: shcmd (47): mkdir -p /mnt/disk1
Jun  2 23:02:08 WOPR emhttpd: shcmd (48): mount -t xfs -o noatime,nodiratime /dev/md1 /mnt/disk1
Jun  2 23:02:08 WOPR kernel: SGI XFS with ACLs, security attributes, no debug enabled
Jun  2 23:02:08 WOPR kernel: XFS (md1): Mounting V5 Filesystem
Jun  2 23:02:08 WOPR kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x00000000fd2b9000 flags=0x0000]
Jun  2 23:02:08 WOPR kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0000 address=0x00000000fd2b9080 flags=0x0000]

Looking at lspci for the problem device at 05:00.0 we see:


04:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 04)
05:01.0 RAID bus controller [0104]: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller [1095:3114] (rev 02)
	Subsystem: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller [1095:7114]
	Kernel driver in use: sata_sil
	Kernel modules: sata_sil
08:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller [1912:0014] (rev 03)

So nothing actually at 05:00.0 but a SiI SATA controller at 05:01.0. So maybe some virtual device at 05:00.0? I haven't come across anyone using that particular card before so I'm not sure how compatible it is. You might try Googling "unraid sii 3114". It seems like an old card and there's mention of SATARaid, which makes me a little dubious. Can you tell me more about it? A link to the product on Amazon or wherever would be useful. You might want to think about replacing it. So, it's actually nothing to do with the Nvidia card, which is at 09:00.0.

https://www.amazon.com/dp/B01N5LQ7Z3/ref=cm_sw_r_sms_c_api_i_kVX9CbCBYKCHZ

 

that’s the link for the card. It’s a simple cheap card, but it’s been in the server for nearly two years so this is a new problem. I may try to reseat the controller and possibly just get a new card ordered and assume that this one is just starting to go bad.

Link to post

Definitely not PCIe then and only SATA 1.5 Gb/s. You'll notice an improvement in parity check times if you replace it with the ones I mentioned and they are inexpensive too.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.