All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43655] Latest radeon dri driver on HD6950 with kernel 3.2 flickers
Date: Mon, 12 Dec 2011 09:03:23 +0000	[thread overview]
Message-ID: <bug-43655-502-PbsCeLxDY1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-43655-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=43655

--- Comment #3 from Alexandre Demers <alexandre.f.demers@gmail.com> 2011-12-12 01:03:23 PST ---
OK, so after testing first all RCs, I narrowed the problem between RC3 and RC4.
So, bisecting gave me the following culprit:

commit 9b5a4d4f65e260a109eaeea8bbc8062a7c58b55e
Merge: cb35999 67589c7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Nov 28 13:49:43 2011 -0800

    Merge branch 'for-3.2-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/gi

    * 'for-3.2-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu
      percpu: explain why per_cpu_ptr_to_phys() is more complicated than
necessa
      percpu: fix chunk range calculation
      percpu: rename pcpu_mem_alloc to pcpu_mem_zalloc

It has nothing to do with drm in itself. But it must be related at some
point... I'll reset my tree tomorrow and retest to be sure by compiling just
before this commit.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-12-12  9:03 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09  6:06 [Bug 43655] New: Latest radeon dri driver on HD6950 with kernel 3.2 flickers bugzilla-daemon
2011-12-09 14:00 ` [Bug 43655] " bugzilla-daemon
2011-12-11  9:00 ` bugzilla-daemon
2011-12-12  9:03 ` bugzilla-daemon [this message]
2011-12-14  1:48 ` bugzilla-daemon
2011-12-15 10:18 ` bugzilla-daemon
2011-12-15 22:03 ` bugzilla-daemon
2011-12-16  0:31 ` bugzilla-daemon
2011-12-16  1:50 ` bugzilla-daemon
2011-12-16  9:38 ` bugzilla-daemon
2011-12-16 14:51 ` bugzilla-daemon
2011-12-17 18:06 ` [Bug 43655] Latest radeon dri driver on HD6950 with GRUB set gfxpayload=$linux_gfx_mode put the display in a flickering state bugzilla-daemon
2011-12-17 18:23 ` bugzilla-daemon
2012-04-29 19:45 ` bugzilla-daemon
2012-07-21 10:49 ` bugzilla-daemon
2012-07-26 12:33 ` bugzilla-daemon
2012-07-30 14:59 ` bugzilla-daemon
2012-07-30 15:12 ` bugzilla-daemon
2012-08-04  4:58 ` bugzilla-daemon
2012-08-04 13:26 ` bugzilla-daemon
2012-08-20  3:00 ` bugzilla-daemon
2012-10-18 13:51 ` bugzilla-daemon
2013-03-29  3:07 ` bugzilla-daemon
2013-03-29 22:23 ` bugzilla-daemon
2013-03-29 22:24 ` [Bug 43655] Latest radeon dri driver on HD6950 with GRUB set "GRUB_GFXPAYLOAD_LINUX=keep" " bugzilla-daemon
2013-03-30  0:38 ` bugzilla-daemon
2013-03-30  2:44 ` bugzilla-daemon
2013-03-30 23:32 ` bugzilla-daemon
2013-04-02 17:29 ` bugzilla-daemon
2013-04-02 23:50 ` bugzilla-daemon
2013-04-02 23:54 ` bugzilla-daemon
2013-04-03  0:08 ` bugzilla-daemon
2013-04-03  1:56 ` bugzilla-daemon
2013-04-03 13:39 ` bugzilla-daemon
2013-04-04 19:31 ` bugzilla-daemon
2013-04-05  2:38 ` bugzilla-daemon
2013-08-09 18:25 ` bugzilla-daemon

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=bug-43655-502-PbsCeLxDY1@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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.