linux-kernel - Re: I915 driver locks up

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:	Tue, 21 Dec 2010 11:16:03 -0500
From:	Stephen Clark <sclark46@...thlink.net>
To:	sclark46@...thlink.net
CC:	Chris Wilson <chris@...is-wilson.co.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: I915 driver locks up

On 12/19/2010 04:46 PM, Stephen Clark wrote:
> On 12/19/2010 06:02 AM, Chris Wilson wrote:
>> On Sat, 18 Dec 2010 18:32:49 -0500, Stephen 
>> Clark<sclark46@...thlink.net>  wrote:
>>> I had been using mesa-7.9.
>>> I loaded mesa-7.10 similar results. There is no
>>>
>>> /sys/kernel/debug/dri/0/i915_error_state
>>>
>>> In fact there is nothing in the /sys/kernel/debug directory. Do I have
>>> to enable
>>> something.
>> You need to "mount -tdebugfs debug /sys/kernel/debug".
>>
>>> With the later kernel - things are worse X becomes totally useless 
>>> it looks
>>> like my lcd panel lost horizontal sync. With the 2.6.25 kernel X is
>>> still usable
>>> this makes me think at least some of the problem is kernel related.
>> 2.6.25 to present marks the transition between UMS and KMS, i.e. moving
>> of the userspace modesetting code into the kernel. And that should not
>> have regressed. Can you please, grab an intel_reg_dumper of the working
>> setup and the lost-sync setup, and include a drm.debug=0xe dmesg 
>> (i.e. add
>> drm.debug=0xe to your boot commandline)?
>>
>>> With 2.6.37-rc6 and mesa 7.10 with hardware acceleration turned off 
>>> in wine-
>>>
>>> Dec 18 18:01:50 joker4 yum[5244]: Updated: 
>>> mesa-libGL-7.10-0.17.fc15.x86_64
>>> Dec 18 18:01:52 joker4 yum[5244]: Updated: 
>>> mesa-libGL-7.10-0.17.fc15.i686
>>> Dec 18 18:01:54 joker4 yum[5244]: Updated: 
>>> mesa-libGLU-7.10-0.17.fc15.x86_64
>>> Dec 18 18:02:02 joker4 yum[5244]: Updated: 
>>> mesa-dri-drivers-7.10-0.17.fc15.x86_6
>>> 4
>>> Dec 18 18:02:03 joker4 yum[5244]: Updated: 
>>> mesa-libGLU-7.10-0.17.fc15.i686
>>> Dec 18 18:02:11 joker4 yum[5244]: Updated: 
>>> mesa-dri-drivers-7.10-0.17.fc15.i686
>> Good, those drivers are recent enough that I should be able to use the
>> error state to find the broken code.
>> -Chris
>>
> Hi Chris,
>
> I emailed the information you requested, it was quite large, and 
> haven't seen it show up on
> LKML yet. Don't know if it is being blocked by the ML or not.
>
> Regards,
> Steve
>
Hi Chris,

Just wondering if you received what you needed from me. I still have the 
info
for the 2.6.37rc6 kernel that I haven't sent awaiting some kind of 
acknowledgment that
you received the initial info I send for the 2.6.35 kernel.

Steve

-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/