From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39202] FPS - KDE desktop effects with 3.0 rc6 kernel
Date: Tue, 16 Aug 2011 01:49:02 -0700 (PDT) [thread overview]
Message-ID: <20110816084902.E3D1F13005E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39202-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=39202
--- Comment #19 from Siganderson <dj_def@webmail.it> 2011-08-16 01:49:02 PDT ---
(In reply to comment #18)
> If vblank_mode=0 doesn't make a difference either, I'm afraid you'll really
> need to bisect.
I did a rough bisect (tagging as bad even all the uncompilable commits and
tagging as good every 2.6.38-rc commit without testing it) and got a result.
Is it better to label an uncompilable commit as bad or to skip it?
dcdf3a293522e6ef09d8b3650ac1ceec56438e5d is the first bad commit
commit dcdf3a293522e6ef09d8b3650ac1ceec56438e5d
Author: Roman Zippel <zippel@linux-m68k.org>
Date: Tue Nov 18 21:25:17 2008 +0100
m68k: Add helper function handle_kernel_fault()
Add helper function handle_kernel_fault() in signal.c, so frame_extra_sizes
can become static, and to avoid future code duplication.
Signed-off-by: Roman Zippel <zippel@linux-m68k.org>
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
:040000 040000 dd4a90c01a056ed7ac20f83518bf6c041c6190ad
1cd025a7a61a8e0c872bdc34ce039bc18e6e91d0 M arch
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-08-16 8:49 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 19:11 [Bug 39202] New: KDE desktop effects with 3.0 rc6 kernel bugzilla-daemon
2011-07-13 19:25 ` [Bug 39202] " bugzilla-daemon
2011-07-13 20:22 ` bugzilla-daemon
2011-07-13 22:26 ` bugzilla-daemon
2011-07-13 22:26 ` bugzilla-daemon
2011-07-13 22:27 ` bugzilla-daemon
2011-07-14 8:09 ` [Bug 39202] FPS - " bugzilla-daemon
2011-08-09 11:12 ` bugzilla-daemon
2011-08-09 11:15 ` bugzilla-daemon
2011-08-09 21:29 ` bugzilla-daemon
2011-08-09 21:30 ` bugzilla-daemon
2011-08-09 21:31 ` bugzilla-daemon
2011-08-10 7:49 ` bugzilla-daemon
2011-08-10 13:31 ` bugzilla-daemon
2011-08-10 15:59 ` bugzilla-daemon
2011-08-12 9:09 ` bugzilla-daemon
2011-08-12 13:17 ` bugzilla-daemon
2011-08-15 9:49 ` bugzilla-daemon
2011-08-15 17:59 ` bugzilla-daemon
2011-08-15 18:04 ` bugzilla-daemon
2011-08-16 7:41 ` bugzilla-daemon
2011-08-16 8:49 ` bugzilla-daemon [this message]
2011-08-16 8:54 ` bugzilla-daemon
2011-08-16 9:14 ` bugzilla-daemon
2011-08-16 9:34 ` bugzilla-daemon
2011-08-16 11:07 ` bugzilla-daemon
2011-08-16 17:24 ` bugzilla-daemon
2011-08-18 9:39 ` bugzilla-daemon
2011-08-18 9:45 ` bugzilla-daemon
2011-08-18 10:00 ` bugzilla-daemon
2011-08-18 11:09 ` bugzilla-daemon
2011-08-18 12:04 ` bugzilla-daemon
2011-08-18 12:06 ` bugzilla-daemon
2011-08-18 13:20 ` bugzilla-daemon
2011-08-18 14:19 ` bugzilla-daemon
2011-08-18 15:50 ` bugzilla-daemon
2011-08-18 16:52 ` bugzilla-daemon
2011-08-18 17:02 ` bugzilla-daemon
2011-08-18 17:32 ` bugzilla-daemon
2011-08-18 17:37 ` bugzilla-daemon
2011-08-18 17:47 ` bugzilla-daemon
2011-08-18 17:50 ` bugzilla-daemon
2011-08-18 18:23 ` bugzilla-daemon
2011-08-18 18:43 ` bugzilla-daemon
2011-08-19 16:45 ` bugzilla-daemon
2011-09-07 16:55 ` bugzilla-daemon
2011-10-26 23:57 ` bugzilla-daemon
2011-10-27 20:36 ` bugzilla-daemon
2011-10-27 22:05 ` bugzilla-daemon
2011-10-27 22:27 ` bugzilla-daemon
2011-10-27 22:31 ` bugzilla-daemon
2011-10-27 22:33 ` bugzilla-daemon
2011-10-28 12:39 ` bugzilla-daemon
2011-10-28 12:42 ` bugzilla-daemon
2011-10-28 13: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=20110816084902.E3D1F13005E@annarchy.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.