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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 Mar 2012 14:59:43 +0100
From:	Tony Vroon <tony@...x.net>
To:	Dave Airlie <airlied@...ux.ie>
CC:	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org, Matt Turner <mattst88@...il.com>,
	daniel@...ll.ch
Subject: Re: [git pull] drm main pull for 3.4-rc1

On 21/03/12 10:47, Dave Airlie wrote:
> i915: re-enabling GMBUS, finish gpu patch (might help hibernation who 
> knows), missed irq fixes, stencil tiling fixes, interlaced support, 
> aliasesd PPGTT support for SNB/IVB, swizzling for SNB/IVB, semaphore fixes

This causes an eventual (after barely a minute of use) lockup that I can
not recover from on my Lifebook S761. It does not switch to a text
console for me, but by stopping my graphical login manager (slim) early
I got this:
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

(The full dmesg is attached so you can see it in context)
In the interest of full disclosure, this is a dual-screen setup:
Screen 0: minimum 320 x 200, current 1680 x 1818, maximum 8192 x 8192
LVDS1 connected 1366x768+0+1050 (normal left inverted right x axis y
axis) 293mm x 165mm
HDMI2 connected 1680x1050+0+0 (normal left inverted right x axis y axis)
459mm x 296mm

To confirm, that is the i915 graphics:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09) (prog-if 00
[VGA controller])
	Subsystem: Fujitsu Limited. Device 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

Please let me know if you want a full lspci, and what your favourite
options are. I am back on a Thursday git snapshot now, which runs fine:
Linux adrastea 3.3.0-04074-g5375871 #1 SMP PREEMPT Thu Mar 22 09:27:24
GMT 2012 x86_64 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-Mail: tony@...x.net

View attachment ".config" of type "text/plain" (70368 bytes)

View attachment "dmesg.txt" of type "text/plain" (48668 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (263 bytes)