From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15166] Changing brightness of backlight freezes kernel with radeon kms enabled.
Date: Mon, 26 Apr 2010 17:38:26 GMT [thread overview]
Message-ID: <201004261738.o3QHcQTP015352@demeter.kernel.org> (raw)
In-Reply-To: <bug-15166-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=15166
Aurélien Couderc <zecoucou@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zecoucou@free.fr
--- Comment #36 from Alexey Diomin <DiominAY@gmail.com> 2010-04-15 15:04:51 ---
fixs not helped
mesa & xf86-video-ati from git, but all tests in runlevel 3 (without starting
X)
when run F13-Beta-i686-Live-KDE.iso (del rhgb) freeze after start kms
http://ivctrans.by/temp/PIC-0032.jpg
on f12 (tested half of the year earlier) has message as on f13 beta now
--- Comment #37 from Aurélien Couderc <zecoucou@free.fr> 2010-04-26 17:38:07 ---
Lenovo X100e also affected.
(Radeon HD 3200)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-04-26 17:38 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15166-2300@https.bugzilla.kernel.org/>
2010-04-14 12:20 ` [Bug 15166] Changing brightness of backlight freezes kernel with radeon kms enabled bugzilla-daemon
2010-04-14 14:14 ` bugzilla-daemon
2010-04-14 14:18 ` bugzilla-daemon
2010-04-14 19:45 ` bugzilla-daemon
2010-04-14 19:47 ` bugzilla-daemon
2010-04-15 15:06 ` bugzilla-daemon
2010-04-26 17:38 ` bugzilla-daemon [this message]
2010-04-27 16:52 ` bugzilla-daemon
2010-04-27 17:35 ` bugzilla-daemon
2010-04-28 3:39 ` bugzilla-daemon
2010-04-28 16:43 ` bugzilla-daemon
2010-04-29 8:49 ` bugzilla-daemon
2010-04-29 15:58 ` bugzilla-daemon
2010-04-30 23:44 ` bugzilla-daemon
2010-05-03 8:35 ` bugzilla-daemon
2010-05-03 21:58 ` bugzilla-daemon
2010-05-04 22:59 ` bugzilla-daemon
2010-05-05 15:00 ` bugzilla-daemon
2010-05-12 11:28 ` bugzilla-daemon
2010-05-14 20:57 ` bugzilla-daemon
2010-05-15 12:02 ` bugzilla-daemon
2010-05-15 12:35 ` bugzilla-daemon
2010-05-15 15:24 ` bugzilla-daemon
2010-05-16 10:47 ` bugzilla-daemon
2010-05-19 8:33 ` bugzilla-daemon
2010-05-24 0:14 ` bugzilla-daemon
2010-05-28 19:53 ` bugzilla-daemon
2010-05-28 20:31 ` bugzilla-daemon
2010-05-29 23:47 ` bugzilla-daemon
2010-01-28 21:02 [Bug 15166] New: " bugzilla-daemon
2010-01-28 21:08 ` [Bug 15166] " bugzilla-daemon
2010-01-28 21:12 ` bugzilla-daemon
2010-01-28 21:28 ` bugzilla-daemon
2010-01-28 22:21 ` bugzilla-daemon
2010-01-30 23:45 ` bugzilla-daemon
2010-01-30 23:49 ` bugzilla-daemon
2010-01-31 0:18 ` bugzilla-daemon
2010-02-01 19:20 ` bugzilla-daemon
2010-02-01 21:20 ` bugzilla-daemon
2010-02-03 22:16 ` bugzilla-daemon
2010-02-03 22:22 ` bugzilla-daemon
2010-02-03 23:30 ` bugzilla-daemon
2010-02-04 14:16 ` bugzilla-daemon
2010-02-05 20:07 ` bugzilla-daemon
2010-02-05 20:35 ` bugzilla-daemon
2010-02-05 21:58 ` bugzilla-daemon
2010-02-05 22:03 ` bugzilla-daemon
2010-02-08 13:33 ` bugzilla-daemon
2010-02-08 21:36 ` bugzilla-daemon
2010-02-08 21:40 ` bugzilla-daemon
2010-02-08 21:42 ` bugzilla-daemon
2010-02-08 21:44 ` bugzilla-daemon
2010-02-09 20:58 ` bugzilla-daemon
2010-02-10 11:28 ` bugzilla-daemon
2010-02-10 11:29 ` bugzilla-daemon
2010-02-19 14:47 ` bugzilla-daemon
2010-02-19 14:56 ` bugzilla-daemon
2010-02-19 14:56 ` bugzilla-daemon
2010-02-19 16:27 ` bugzilla-daemon
2010-02-19 22:15 ` bugzilla-daemon
2010-02-25 18:06 ` bugzilla-daemon
2010-02-25 18:09 ` 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=201004261738.o3QHcQTP015352@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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.