All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <sclark46@earthlink.net>
To: sclark46@earthlink.net
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: I915 driver locks up
Date: Wed, 22 Dec 2010 14:40:32 -0500	[thread overview]
Message-ID: <4D125430.1020708@earthlink.net> (raw)
In-Reply-To: <4D10D2C3.8050508@earthlink.net>

On 12/21/2010 11:16 AM, Stephen Clark wrote:
> 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@earthlink.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
>
Hi Chris,

Just wanted to say I downloaded the latest drm_fixes from Dave Airlie 
and tried them
on 2.6.37rc7 and got the same gpu hang with the screen tearing 
horizontally. I have
the the intel gpu dump and a cat of the i915_error_state. Together they 
are over
2 megabytes. Should I send them to you directly since they seem to big 
for the mailing
list.

Regards,
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)




  reply	other threads:[~2010-12-22 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-18 20:09 I915 driver locks up Stephen Clark
2010-12-18 20:30 ` Stephen Clark
2010-12-18 21:40   ` Chris Wilson
2010-12-18 23:32     ` Stephen Clark
2010-12-19 11:02       ` Chris Wilson
2010-12-19 21:46         ` Stephen Clark
2010-12-21 16:16           ` Stephen Clark
2010-12-22 19:40             ` Stephen Clark [this message]
2010-12-22 19:49               ` Chris Wilson

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=4D125430.1020708@earthlink.net \
    --to=sclark46@earthlink.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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.