From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42782] IO_PAGE_FAULT while starting xorg
Date: Wed, 29 Aug 2012 14:54:38 +0000 (UTC) [thread overview]
Message-ID: <20120829145438.DF15711FB49@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42782-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42782
Tango <tango@thetangos.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tango@thetangos.com
--- Comment #12 from Tango <tango@thetangos.com> 2012-08-29 14:54:38 ---
I have this problem as well. In my case it seems to be a regression. My
2.6.37-r4 kernel boots properly and X starts without error.
Been trying sense March to get any stable 3.x.x kernel to boot and start X
properly. I have had no problems getting them to boot but none would allow me
to start X.
Attempting to start X produces these errors in demsg.
[ 8.368285] nvidia: module license 'NVIDIA' taints kernel.
[ 8.368289] Disabling lock debugging due to kernel taint
[ 8.382108] vgaarb: device changed decodes:
PCI:0000:08:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 8.382524] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 295.71 Thu Aug
2 19:22:08 PDT 2012
[ 9.329795] AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x0016
address=0x000000041a386200 flags=0x0010]
[ 9.329812] AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x0016
address=0x00000004147d0000 flags=0x0010]
[ 9.329823] AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x0016
address=0x00000004147d0040 flags=0x0010]
[ 9.329834] AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x0016
address=0x0000000000006000 flags=0x0000]
[ 9.329843] AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x0016
address=0x0000000000006040 flags=0x0000]
[ 9.329853] AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x0016
address=0x0000000000006080 flags=0x0000]
[ 9.329862] AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x0016
address=0x00000000000060c0 flags=0x0000]
[ 17.341563] NVRM: RmInitAdapter failed! (0x27:0x38:1190)
[ 17.341573] NVRM: rm_init_adapter(0) failed
Early in the kernel boot process all my kernels were reporting,
Please enable the IOMMU option in the BIOS setup
This costs you 64 MB of RAM
I verified that IOMMU was in fact enabled in my BIOS. So I am not sure if that
is just a suggestion or that the kernel isn't detecting the IOMMU settings.
After much research I narrowed the problem down to AMD_IOMMU. I can boot my
3.4.9-kernel, (configured and striped to absolute essentials for testing) and
start X properly only if I boot it with amd_iommu=off.
Kernel command line: root=/dev/sda3 amd_iommu=off
video=uvesafb:mtrr:3,ywrap,1280x1024-32@75 splash=verbose,theme:livecd-2007.0
console=tty1
My Linux Distro is Gentoo
Portage 2.1.11.9 (default/linux/amd64/10.0, gcc-4.5.4, glibc-2.15-r2,
3.4.9-gentoo x86_64)
System uname:
Linux-3.4.9-gentoo-x86_64-AMD_Phenom-tm-_II_X6_1100T_Processor-with-gentoo-2.1
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-08-29 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 12:13 [Bug 42782] New: IO_PAGE_FAULT while starting xorg bugzilla-daemon
2012-02-16 12:14 ` [Bug 42782] " bugzilla-daemon
2012-02-16 12:17 ` bugzilla-daemon
2012-02-16 12:17 ` bugzilla-daemon
2012-02-16 14:02 ` bugzilla-daemon
2012-06-25 13:36 ` bugzilla-daemon
2012-06-25 13:50 ` bugzilla-daemon
2012-06-25 13:50 ` bugzilla-daemon
2012-06-25 13:52 ` bugzilla-daemon
2012-06-25 14:06 ` bugzilla-daemon
2012-06-25 14:21 ` bugzilla-daemon
2012-06-26 15:11 ` bugzilla-daemon
2012-08-29 14:54 ` bugzilla-daemon [this message]
2012-08-30 14:39 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120829145438.DF15711FB49@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).