Re: [git pull] drm main pull for 3.4-rc1

. Regards, - -- Tony Vroon UNIX systems administrator London Internet Exchange Ltd, Trinity Court, Trinity Street, Peterborough, PE1 1DA Registered in England number 3137929 E-Mail: t...@linx.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http

Re: [git pull] drm main pull for 3.4-rc1

x86_64 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz GenuineIntel GNU/Linux Obviously I would like to have x2apic and my IOMMU back... Regards, - -- Tony Vroon UNIX systems administrator London Internet Exchange Ltd, Trinity Court, Trinity Street, Peterborough, PE1 1DA Registered in England number

Re: [git pull] drm main pull for 3.4-rc1

No DMAR complaints in dmesg yet; it would have crashed by now if the fault was present. Regards, - -- Tony Vroon UNIX systems administrator London Internet Exchange Ltd, Trinity Court, Trinity Street, Peterborough, PE1 1DA Registered in England number 3137929 E-Mail: t...@linx.net -BEGIN PGP

Re: [git pull] drm main pull for 3.4-rc1

-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

Re: [git pull] drm main pull for 3.4-rc1

on both mainline and your for-chainsaw branch with additional SNB patching. With ppgtt and the iommu fully enabled, your SNB patches remove the DMAR warnings but do not address the stability problem, in that it still crashes in the same way. Regards, - -- Tony Vroon UNIX systems administrator

Re: [git pull] drm main pull for 3.4-rc1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/03/12 13:39, Daniel Vetter wrote: Is the for-chainsaw branch plus intel_iommu=igfx_off now stable for you? It appears to crash when I shut my machine down, but has otherwise behaved quite well. Regards, - -- Tony Vroon UNIX systems

[8086:0416] i915 Inability to drive internal (eDP) panel since 4.7 final

On 25/08/16 12:19, Jani Nikula wrote: > Please attach drm.debug=14 module parameter, > and attach dmesg all the way from boot. Added to bug 97060, which is the same problem. One good run, one bad run. Thank you. Regards, -- Tony Vroon Systems Infrastructure Manager London Internet Exchan

[8086:0416] i915 Inability to drive internal (eDP) panel since 4.7 final

Good morning, Could you please CC me on any replies as I am not subscribed to this mailing list. Recent i915 development appears to have stopped my eDP panel from being driven correctly. The last working release was 4.6.7; any 4.7 kernel will not drive the screen and 4.8-RC3 does not drive the

[REVERT] drm/radeon: consolidate vga and dvi get_modes functions (v2)

and only truth in kernel troubleshooting and I followed it to the letter. > Have you verified that reverting it actually helps ? I just tried it on a clean tree and indeed, it did not help as you expected. So, Alex, sorry to waste your time. Ben, other ideas? Regards, -- Tony Vroon Server sys

[REVERT] drm/radeon: consolidate vga and dvi get_modes functions (v2)

Please consider reverting commit 3e22920fbd0005927bc41f71daeb056a0f4def82 by title of: drm/radeon: consolidate vga and dvi get_modes functions (v2) I have bisected this as the culprit for my PowerMac 7,3 crashing back into OpenFirmware very early at boot with an invalid memory access. The

[git pull] drm main pull for 3.4-rc1

4 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz GenuineIntel GNU/Linux I only subscribe to LKML, please CC me to be sure. Regards, -- Tony Vroon UNIX systems administrator London Internet Exchange Ltd, Trinity Court, Trinity Street, Peterborough, PE1 1DA Registered in England number 3137929 E-M

[git pull] drm main pull for 3.4-rc1

t bisect arguments. 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 at linx.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using

[git pull] drm main pull for 3.4-rc1

21 BST 2012 x86_64 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz GenuineIntel GNU/Linux Obviously I would like to have x2apic and my IOMMU back... Regards, - -- Tony Vroon UNIX systems administrator London Internet Exchange Ltd, Trinity Court, Trinity Street, Peterborough, PE1 1DA Registered in England

[git pull] drm main pull for 3.4-rc1

0 No DMAR complaints in dmesg yet; it would have crashed by now if the fault was present. 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 at linx.net -BEG

[git pull] drm main pull for 3.4-rc1

-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 Corpo

[git pull] drm main pull for 3.4-rc1

=igfx_off is stable on both mainline and your "for-chainsaw" branch with additional SNB patching. With ppgtt and the iommu fully enabled, your SNB patches remove the DMAR warnings but do not address the stability problem, in that it still crashes in the same way. Regards, - -- Tony

[git pull] drm main pull for 3.4-rc1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/03/12 13:39, Daniel Vetter wrote: > Is the for-chainsaw branch plus intel_iommu=igfx_off now stable for > you? It appears to crash when I shut my machine down, but has otherwise behaved quite well. Regards, - -- Tony Vroon UNIX s