From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35697] New: System locks up when watching fullscreen flash video
Date: Sat, 26 Mar 2011 09:21:10 -0700 (PDT) [thread overview]
Message-ID: <bug-35697-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35697
Summary: System locks up when watching fullscreen flash video
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: realnc@gmail.com
(I have no idea if I filled the bug details correctly; I'm simply assuming this
is DRI related. Could be a mesa bug or xf86-video-ati problem, or whatever;
I've no idea.)
There is a regression in kernel 2.6.38 that was not there in 2.6.37: When
switching a flash video to fullscreen, three things can happen:
* The system locks up completely (not even SysRq works)
* The screen becomes black but the system is still
responding (switching to a console and restarting X works)
* The screen stops updating (old windows are still there even
after closing them.)
There's no dmesg nor any X.org.0 output when any of the above happen.
I'm running Gentoo AMD64, kernel 2.6.38.1, x11-drivers/xf86-video-ati Git
master, mesa Git master, xorg-server 1.9.5. My graphics card is a Radeon
HD4870. I'm using KMS and Gallium and I'm on KDE 4.6.1 with desktop effects
enabled.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-03-26 16:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 16:21 bugzilla-daemon [this message]
2011-03-26 16:24 ` [Bug 35697] System locks up when watching fullscreen flash video bugzilla-daemon
2011-03-26 16:27 ` bugzilla-daemon
2011-03-26 16:31 ` bugzilla-daemon
2011-03-27 8:29 ` bugzilla-daemon
2011-03-27 19:58 ` bugzilla-daemon
2011-03-27 20:23 ` bugzilla-daemon
2011-03-27 20:41 ` bugzilla-daemon
2011-03-27 20:55 ` bugzilla-daemon
2011-03-27 20:59 ` bugzilla-daemon
2011-03-28 1:48 ` bugzilla-daemon
2011-03-28 2:18 ` bugzilla-daemon
2011-03-28 2:28 ` bugzilla-daemon
2011-03-28 9:01 ` bugzilla-daemon
2011-03-28 10:00 ` bugzilla-daemon
2011-03-29 14:19 ` bugzilla-daemon
2011-03-29 14:27 ` bugzilla-daemon
2011-03-29 15:07 ` bugzilla-daemon
2011-03-29 15:26 ` bugzilla-daemon
2011-03-29 15:30 ` bugzilla-daemon
2011-03-30 6:43 ` bugzilla-daemon
2011-05-13 11:58 ` bugzilla-daemon
2011-06-17 16:47 ` bugzilla-daemon
2011-06-17 17:00 ` bugzilla-daemon
2011-06-17 17:40 ` bugzilla-daemon
2011-07-14 20:43 ` bugzilla-daemon
2011-07-14 21:03 ` bugzilla-daemon
2011-07-26 12:28 ` 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-35697-502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox