public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Taillefumier <mathieu.taillefumier@free.fr>
To: Eric Anholt <eric@anholt.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] intel KMS bug on i915
Date: Wed, 18 Nov 2009 10:39:00 +0100	[thread overview]
Message-ID: <4B03C0B4.6080300@free.fr> (raw)
In-Reply-To: <1258433661.4882.5.camel@gaiman.anholt.net>

Hello,
> On Wed, 2009-11-11 at 12:44 +0100, Mathieu Taillefumier wrote:
>    
>> Hello,
>>
>> I recently switched to the last git kernel (the rc6) and have a serious
>> problem with KMS and xorg. I reported it to the xorg list but after some
>> research it seems that this problem is caused by some recent change in
>> the intel KMS stack. Some warnings and errors are reported by the
>> kernel. they are the following (only a small part of it):
>>
>> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
>> render error detected, EIR: 0x00000000
>> i915: Waking up sleeping processes
>> [drm:i915_wait_request] *ERROR* i915_wait_request returns -5 (awaiting 2
>> at 1)
>> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
>> render error detected, EIR: 0x00000000
>>
>> This problem is recurrent with all 2.6.32-rc versions and gives rise to
>> an unusable xorg (independent of the version), while the same xorg stack
>> works pretty well with the 2.6.31 kernel. The hardware is a sony laptop
>> with a intel 965 chipset and the bug can be reproduced at 100%
>>      
> Could you bisect the problem?  I don't think I've seen reports of this
> (fails at a time other than resume)
>    
Thanks for the reply.

I will try to bissect the problem (I have to start from the first rc1 
and go backward from that) but it might take some time since I am not an 
expert in git. What I can say is that the problem occur since the first 
rc of the kernel (and whatever recent version of libdrm). Moreover, I 
have this after a cold boot. Another person reported the same problem on 
the xorg list, so I am not alone :-).

regards

Mathieu


  reply	other threads:[~2009-11-18  9:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 11:44 [BUG] intel KMS bug on i915 Mathieu Taillefumier
2009-11-17  4:54 ` Eric Anholt
2009-11-18  9:39   ` Mathieu Taillefumier [this message]
2009-11-18 12:54   ` Mathieu Taillefumier
2009-11-19 16:38   ` Mathieu Taillefumier

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=4B03C0B4.6080300@free.fr \
    --to=mathieu.taillefumier@free.fr \
    --cc=eric@anholt.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox