linux-kernel - Re: regression(?) 3.3-rc4 -> 3.3-rc5: drm intel hangs

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 1 Mar 2012 16:42:29 +0900
From:	Norbert Preining <preining@...ic.at>
To:	Paul Menzel <paulepanter@...rs.sourceforge.net>,
	Dave Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
	dri-devel@...ts.sourceforge.net
Subject: Re: regression(?) 3.3-rc4 -> 3.3-rc5: drm intel hangs

Hi everyone,

sorry for the late answer, I was sure that it does not happen again,
but alas, right then, it happened again.

On Di, 28 Feb 2012, Paul Menzel wrote:
> I do not know. But it would be interesting to know if you just see this
> in your log files or if you also see some effects like screen
> corruptions. You can increase the log level by adding `drm.debug=0x06`
> to the Linux kernel command line [1].

Yes: - gnome-screensaver dialog does not come up
- former case: fall back to gnome3 fallback mode, no 3d accel

I didn't have the drm.debug=0x06 running, but with the next reboot
I will activate it and hope it happens again.

On Di, 28 Feb 2012, Dave Airlie wrote:
> And you haven't changed userspace in any way?

On 25. Februar I got the new version of Debian's
	xserver-xorg-video-intel 2.18.0
	debian 2:2.18.0-1
updated from 2:2.17.0-1

Anything I can do to blame this on user space?

On Di, 28 Feb 2012, Daniel Vetter wrote:
> Wee need this i915_error_state file from debugfs (you might need to mount
> that first again) to diagnose gpu hangs. Also, it only contains
> information after a crash, so you need to rehang your machine if you've
> rebooted since then.

I didn't have debugfs mounted when it crashed, though ....
I mounted it *afterwards* and attach the i915_error_state file.
Mind, there is also a /debugfs/dri/64/ directory with a i915_error_state,
but they are absolutely the same.

If I have to have debugfs *monted* at the time of the crash, I have to
wait for the next instance.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@...ist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
GUERNSEY (adj.)
			--- Douglas Adams, The Meaning of Liff

View attachment "i915_error_state.gz" of type "text/plain" (195302 bytes)