All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Taillefumier <mathieu.taillefumier@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Dave Airlie <airlied@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
	Daniel Vetter <daniel@ffwll.ch>, Adam Jackson <ajax@redhat.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net,
	keithp@keithp.com, eric@anholt.net,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [BISECTED] drm: random hang since 620f378 "drm: prune modes when ..."
Date: Wed, 16 Dec 2009 13:19:30 +0100	[thread overview]
Message-ID: <4B28D052.4040303@gmail.com> (raw)
In-Reply-To: <20091214102015.2f43f5b4@jbarnes-piketon>

Hi,
> You can disable most of that code by loading i915 with 'powersave=0'.
> If that patch really is at fault the powersave=0 should work around the
> issue as well.
>
> It's been implicated in another issue (some display flicker and
> underruns) so I'm pretty sure there's something wrong with it in some
> configurations at least...
>    
Could it be also that the powersave feature produces gpu hangs when 
xserver is run the first time (after a cold boot). I have serious issues 
the intel drm starting at v2.6.32-rc2 (I can not use the v2.6.32 series 
on my laptop) while the same xorg stack works well with the v2.6.31 
series. I try to bisect this problem and obtained this (sorry it is a 
bit long):

  git bisect start 'drivers/gpu' 'arch/x86_64/'
# bad: [053fe57ac249a9531c396175778160d9e9509399] Merge 
git://git.kernel.org/pub
/scm/linux/kernel/git/davem/net-2.6
git bisect bad 053fe57ac249a9531c396175778160d9e9509399
# good: [74fca6a42863ffacaf7ba6f1936a9f228950f657] Linux 2.6.31
git bisect good 74fca6a42863ffacaf7ba6f1936a9f228950f657
# bad: [d8a2d0e00c0d5a0d55e14b884bff034205015e51] drm/i915: HDMI 
hardware workar
ound for Ironlake
git bisect bad d8a2d0e00c0d5a0d55e14b884bff034205015e51
# bad: [d50ba256b5f1478e15accfcfda9b72fd7a661364] drm/kms: start adding 
command
line interface using fb.
git bisect bad d50ba256b5f1478e15accfcfda9b72fd7a661364
# good: [551ebd837c75fc75df81811a18b7136c39cab487] drm/radeon/kms: add 
rn50/r100
/r200 CS tracker.
git bisect good 551ebd837c75fc75df81811a18b7136c39cab487
# good: [fdd5cace733370ab7a518a98ef084e02aa76fdea] drm/radeon/kms: Don't 
kzalloc
  memory which is immediately overwritten.
git bisect good fdd5cace733370ab7a518a98ef084e02aa76fdea
# good: [698443d9ec1a33eff65b27b9514e06998bf57eb3] drm/radeon/kms: 
disable VGA r
endering engine before taking over VRAM
git bisect good 698443d9ec1a33eff65b27b9514e06998bf57eb3
# good: [c214271563c00f2721c5111e27b53bf06dabc6e4] drm/radeon: 
consolidate famil
y flags used in pciids.
git bisect good c214271563c00f2721c5111e27b53bf06dabc6e4
# good: [93dc6c2b0d97a55508144073838e041140b206cd] drm/edid: Detailed 
standard t
iming blocks have six timings, not five.
git bisect good 93dc6c2b0d97a55508144073838e041140b206cd
# good: [4bbd4973703bf8a5f00f05eff30a99cd9814f37f] drm/radeon/kms: 
enable r600 t
v outputs.
git bisect good 4bbd4973703bf8a5f00f05eff30a99cd9814f37f
# good: [513bcb4655e68706594e45dfa1d4b181500110ba] drm/radeon/kms: don't 
require
  up to 64k allocations. (v2)
git bisect good 513bcb4655e68706594e45dfa1d4b181500110ba

Regards

Mathieu

      parent reply	other threads:[~2009-12-16 12:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 17:30 [BISECTED] drm: random hang since 620f378 "drm: prune modes when ..." Arnd Bergmann
2009-12-08 21:59 ` Arnd Bergmann
2009-12-08 22:13   ` Dave Airlie
2009-12-08 23:07     ` Arnd Bergmann
2009-12-09  5:38       ` Dave Airlie
2009-12-13 12:18         ` Arnd Bergmann
2009-12-13 12:30           ` Arnd Bergmann
2009-12-13 20:00             ` Daniel Vetter
2009-12-13 21:31               ` Arnd Bergmann
2009-12-13 21:54                 ` Dave Airlie
2009-12-14 18:20                   ` Jesse Barnes
2009-12-14 20:38                     ` Arnd Bergmann
2009-12-14 20:50                       ` Jesse Barnes
2009-12-15  9:51                         ` Arnd Bergmann
2009-12-16 13:53                           ` Arnd Bergmann
2009-12-16 20:18                             ` Jesse Barnes
2009-12-16 21:20                               ` Arnd Bergmann
2009-12-16 21:30                                 ` Jesse Barnes
2009-12-16 21:36                                   ` Arnd Bergmann
2009-12-16 22:41                                     ` Arnd Bergmann
2009-12-17 17:25                                       ` Jesse Barnes
2009-12-17 17:52                                         ` Arnd Bergmann
2009-12-17 19:13                                           ` Jesse Barnes
2009-12-19 13:16                                             ` Arnd Bergmann
2009-12-21 16:06                                             ` Arnd Bergmann
2009-12-21 17:57                                               ` Arnd Bergmann
2009-12-28 18:47                                                 ` Jesse Barnes
2009-12-30 22:00                                                   ` Arnd Bergmann
2009-12-16 12:19                     ` Mathieu Taillefumier [this message]

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=4B28D052.4040303@gmail.com \
    --to=mathieu.taillefumier@gmail.com \
    --cc=airlied@redhat.com \
    --cc=ajax@redhat.com \
    --cc=arnd@arndb.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=eric@anholt.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=keithp@keithp.com \
    --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.