From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33912] [RV515] Kernel .35 onwards, Random X freezes while scrolling
Date: Fri, 10 Jun 2011 15:10:40 GMT [thread overview]
Message-ID: <201106101510.p5AFAeaZ006190@demeter1.kernel.org> (raw)
In-Reply-To: <bug-33912-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=33912
--- Comment #11 from Alex Deucher <alexdeucher@gmail.com> 2011-06-10 15:10:39 ---
(In reply to comment #10)
> (In reply to comment #9)
> > Can you bisect?
>
> I have never bisected a kernel, but I can try. Just have a few doubts.
>
> 1 * Can I do with the Ubuntu kernel as per Ubuntu instructions[0] as:
> $ git bisect start Ubuntu-2.6.35-1.1 Ubuntu-2.6.34-5.14
>
> Which seems a saner incremental interval of Jun5 -> Jun 4.
That should be fine. The closest two kernels that where which have and don't
have the problem are your best bet.
> 2 * Are there any pointers to narrow down the kernel commit from the backtraces
> I have posted?
> Or is just looking for "drivers/gpu/drm/radeon/" the closest?
You can narrow the bisection to just radeon, but if the problem is something
non-radeon you'll get inconclusive results.
>
> 3 * Is there any specific command I need to run if I hit the bug?
> Or is gdb of X sufficient?
> Do I need to set any variables to get better logs of the freeze?
It's really hard to narrow down what causes the GPU to hang. It could be a bug
in the kernel, it could also be a certain combination of command buffers or
userspace acceleration drivers that happen to make the GPU angry. Just getting
the commit id should be enough. You might also try a newer ddx and/or mesa 3D
driver to see if that helps.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2011-06-10 15:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 9:31 [Bug 33912] New: [RV515] Kernel .35 onwards, Random X freezes while scrolling bugzilla-daemon
2011-04-25 9:33 ` [Bug 33912] " bugzilla-daemon
2011-04-25 9:35 ` bugzilla-daemon
2011-04-25 9:37 ` bugzilla-daemon
2011-04-27 20:21 ` bugzilla-daemon
2011-04-27 20:24 ` bugzilla-daemon
2011-04-27 20:25 ` bugzilla-daemon
2011-04-29 9:25 ` bugzilla-daemon
2011-04-29 9:31 ` bugzilla-daemon
2011-04-29 9:31 ` bugzilla-daemon
2011-04-29 9:32 ` bugzilla-daemon
2011-04-29 9:33 ` bugzilla-daemon
2011-04-29 9:33 ` bugzilla-daemon
2011-06-10 3:23 ` bugzilla-daemon
2011-06-10 5:05 ` bugzilla-daemon
2011-06-10 7:50 ` bugzilla-daemon
2011-06-10 15:10 ` bugzilla-daemon [this message]
2011-06-10 16:55 ` bugzilla-daemon
2012-08-20 15:53 ` 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=201106101510.p5AFAeaZ006190@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.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.