From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)
Date: Wed, 12 Oct 2011 03:07:04 -0700 (PDT) [thread overview]
Message-ID: <20111012100704.58C7B13005E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-41668-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=41668
--- Comment #10 from Michel Dänzer <michel@daenzer.net> 2011-10-12 03:07:04 PDT ---
(In reply to comment #6)
> > > running glxgears just shows an empty black box.. all other glx demos are the
> > > same empty boxes..
> >
> > Do they work with the environment variable vblank_mode=0? If yes, does the
> > number for radeon increase in /proc/interrupts once the problem occurs?
>
> setting vblank_mode=0 works and displays an output.. but not much change in
> /proc/interrupts (irq 46 for radeon)
Not much change for the radeon number, or none at all? If the latter,
apparently the IRQ for the radeon card stops working for some reason, which
would explain the core symptoms of the freeze.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-10-12 10:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 5:08 [Bug 41668] New: Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300) bugzilla-daemon
2011-10-11 5:09 ` [Bug 41668] " bugzilla-daemon
2011-10-11 5:09 ` bugzilla-daemon
2011-10-11 5:10 ` bugzilla-daemon
2011-10-11 5:12 ` bugzilla-daemon
2011-10-11 5:12 ` bugzilla-daemon
2011-10-11 5:13 ` bugzilla-daemon
2011-10-11 9:34 ` bugzilla-daemon
2011-10-11 16:28 ` bugzilla-daemon
2011-10-11 16:30 ` bugzilla-daemon
2011-10-12 2:25 ` bugzilla-daemon
2011-10-12 2:27 ` bugzilla-daemon
2011-10-12 2:28 ` bugzilla-daemon
2011-10-12 2:42 ` bugzilla-daemon
2011-10-12 10:07 ` bugzilla-daemon [this message]
2011-10-12 10:24 ` bugzilla-daemon
2011-10-13 6:27 ` bugzilla-daemon
2011-10-13 13:01 ` bugzilla-daemon
2011-10-24 23:46 ` bugzilla-daemon
2011-10-24 23:47 ` bugzilla-daemon
2011-12-15 1:38 ` bugzilla-daemon
2011-12-15 1:39 ` bugzilla-daemon
2011-12-15 7:21 ` bugzilla-daemon
2011-12-15 14:20 ` bugzilla-daemon
2011-12-15 15:19 ` bugzilla-daemon
2012-02-12 8:59 ` bugzilla-daemon
2012-02-13 13:40 ` bugzilla-daemon
2012-02-13 14:20 ` bugzilla-daemon
2012-02-19 11:19 ` bugzilla-daemon
2012-02-19 12:25 ` bugzilla-daemon
2012-04-24 8:37 ` bugzilla-daemon
2012-04-26 2:44 ` bugzilla-daemon
2013-01-11 21:11 ` bugzilla-daemon
2013-01-14 13:10 ` 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=20111012100704.58C7B13005E@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).