From: Tony Vroon <tony@linx.net>
To: Dave Airlie <airlied@linux.ie>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
linux-kernel@vger.kernel.org, Matt Turner <mattst88@gmail.com>
Subject: Re: [git pull] drm main pull for 3.4-rc1
Date: Tue, 27 Mar 2012 11:24:01 +0100 [thread overview]
Message-ID: <4F719541.1090001@linx.net> (raw)
In-Reply-To: <4F719262.7090008@linx.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 27/03/12 11:11, Tony Vroon wrote:
> No DMAR complaints in dmesg yet; it would have crashed by now if
> the fault was present.
To confirm, it is stable.
So ppgtt + VT-d is problematic on:
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd
Generation Core Processor Family Integrated Graphics Controller
[8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Fujitsu Limited. Device [10cf:15e9]
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at e0000000 (64-bit, non-prefetchable) [size=4M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 3000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
For the avoidance of doubt, it is a mobile Core i7 part:
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
stepping : 7
microcode : 0x25
Prior to the crash, I see:
DRHD: handling fault status reg 3
DMAR:[DMA Write] Request device [00:02.0] fault addr 12806b000
DMAR:[fault reason 05] PTE Write access is not set
DRHD: handling fault status reg 3
DMAR:[DMA Write] Request device [00:02.0] fault addr 128183000
DMAR:[fault reason 05] PTE Write access is not set
DRHD: handling fault status reg 3
DMAR:[DMA Write] Request device [00:02.0] fault addr 4147562000
DMAR:[fault reason 05] PTE Write access is not set
DRHD: handling fault status reg 3
DMAR:[DMA Write] Request device [00:02.0] fault addr 4147562000
DMAR:[fault reason 05] PTE Write access is not set
So I believe a bisection should point at commit
e21af88d39796c907c38648c824be3d646ffbe35, but I am willing to run one
if you really feel there is more to it?
Regards,
- --
Tony Vroon
UNIX systems administrator
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9xlUEACgkQp5vW4rUFj5q9mACgkyyW7PNZ4/vne++JXDrESaE8
D4AAn1hzqKHoMlwDCWxI+TbVkzrEZfGj
=SBBH
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-03-27 10:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 10:47 [git pull] drm main pull for 3.4-rc1 Dave Airlie
2012-03-21 10:47 ` Dave Airlie
2012-03-21 17:31 ` InKi Dae
2012-03-21 17:47 ` Dave Airlie
2012-03-21 17:47 ` Dave Airlie
2012-03-22 20:23 ` Linus Torvalds
2012-03-24 19:15 ` Linus Torvalds
2012-03-24 19:15 ` Linus Torvalds
2012-03-24 19:21 ` Daniel Vetter
2012-03-24 19:21 ` Daniel Vetter
2012-03-26 13:59 ` Tony Vroon
2012-03-26 14:32 ` Daniel Vetter
2012-03-26 14:36 ` Tony Vroon
2012-03-27 10:01 ` Daniel Vetter
2012-03-27 10:11 ` Tony Vroon
2012-03-27 10:24 ` Tony Vroon [this message]
2012-03-26 14:44 ` Tony Vroon
2012-03-27 19:31 ` Daniel Vetter
2012-03-27 20:39 ` Daniel Vetter
2012-03-27 20:39 ` Daniel Vetter
2012-03-28 8:55 ` Tony Vroon
2012-03-29 12:39 ` Daniel Vetter
2012-03-29 12:43 ` Tony Vroon
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=4F719541.1090001@linx.net \
--to=tony@linx.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.