AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x000f address=0x00000000bec09880 flags=0x0010]

Bug #1610622 reported by Boris A. Noskov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

 [ 19.880847] xhci_hcd 0000:02:00.0: can't setup: -110
 [ 19.880915] clocksource: Switched to clocksource tsc
 [ 19.880919] xhci_hcd 0000:02:00.0: USB bus 8 deregistered
 [ 19.880979] xhci_hcd 0000:02:00.0: init 0000:02:00.0 fail, -110
 [ 19.881033] xhci_hcd: probe of 0000:02:00.0 failed with error -110

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: hitkliv 1854 F.... pulseaudio
 /dev/snd/controlC2: hitkliv 1854 F.... pulseaudio
 /dev/snd/controlC0: hitkliv 1854 F.... pulseaudio
CurrentDesktop: X-Cinnamon
Date: Sun Aug 7 09:38:17 2016
HibernationDevice: RESUME=UUID=4c30b323-8466-484e-bca4-99052a00ff77
InstallationDate: Installed on 2016-08-06 (0 days ago)
InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
IwConfig:
 lo no wireless extensions.

 enp3s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=UUID=96a76e70-0ed0-478e-8558-7f0cffe4782d ro rootflags=subvol=@ quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic N/A
 linux-firmware 1.157.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-UD3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Boris A. Noskov (hitkliv) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Wellington Uemura (wellingtonuemura) wrote :

I also had a problem with a Gigabyte motherboard model GA-990FXA-UD5 R5, disabling the IOMMU solve the problem but it disables some USB ports.

I've solved this by adding "iommu=pt" at /etc/default/grub, find the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

and add:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iommu=pt"

Save it, run sudo update-grub and reboot. After that the event will be gone and you should see somethign like this

[ 1.536343] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
[ 1.536344] AMD-Vi: Interrupt remapping enabled
[ 1.536356] pci 0000:00:00.2: irq 72 for MSI/MSI-X
[ 1.536490] AMD-Vi: Initialized for Passthrough Mode

If you get something else, please check this post.
https://ubuntuforums.org/showthread.php?t=2254677

Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.