AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0015 address=0x0000000000001000 flags=0x0000]

[krot]

Many errors in /var/log/kern.log and /var/log/syslog like:
AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0015 address=0x0000000000001000 flags=0x0000]
These files grow constantly, taking more than 10 GB in 4-5 hours.

---
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: krot 2131 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=e26cb278-a987-418b-8a29-699a1c582847
InstallationDate: Installed on 2012-10-21 (439 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=d3f644cf-a581-4546-97ec-666292691b65 ro quiet splash
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-15-generic N/A
 linux-backports-modules-3.11.0-15-generic N/A
 linux-firmware 1.116
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: saucy
Uname: Linux 3.11.0-15-generic x86_64
UpgradeStatus: Upgraded to saucy on 2013-11-02 (62 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
dmi.bios.date: 12/27/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8e
dmi.board.name: GA-970A-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8e:bd12/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-970A-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1265940

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[krot (krot-mstu)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.13-rc7-trusty/

[Taralyn Darkchylde (hellion0)]

This bug was also affecting me and I was using the upstream kernel, but I found a workaround:

Open /etc/default/grub in your favored text editor (You'll need sudo, obviously)

Go to the line starting with 'GRUB_CMDLINE_LINUX_DEFAULT=' and add the following inside the quotes: iommu=soft

Save the file, then run 'sudo update-grub' in a terminal, then reboot. It should stop the spamming to logs and filling of your drives.

The source of the error seems to be broken AMD-Vi implementation on several motherboards.

[penalvch (penalvch)]

Taralyn Darkchylde, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

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