From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26552] New: Screen flickering with 2.6.37 [ATI X1600]
Date: Tue, 11 Jan 2011 22:54:00 GMT [thread overview]
Message-ID: <bug-26552-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=26552
Summary: Screen flickering with 2.6.37 [ATI X1600]
Product: Drivers
Version: 2.5
Kernel Version: 2.6.37
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: andrea_iob@yahoo.it
Regression: Yes
Created an attachment (id=43282)
--> (https://bugzilla.kernel.org/attachment.cgi?id=43282)
dmesg when flickering is present
Starting from 2.6.37 the screen on my Toshiba Satellite A100 flickers as soon
as kernel modesetting is initialized. The flickering does not occur always:
sometimes the screen is almost unreadable, sometimes there is no flickering at
all.
With 2.6.36 (and previous versions) I've never experienced flickering problems.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next reply other threads:[~2011-01-11 22:54 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 22:54 bugzilla-daemon [this message]
2011-01-11 22:54 ` [Bug 26552] Screen flickering with 2.6.37 [ATI X1600] bugzilla-daemon
2011-01-11 23:10 ` bugzilla-daemon
2011-01-12 15:14 ` bugzilla-daemon
2011-01-12 17:18 ` bugzilla-daemon
2011-01-12 18:28 ` bugzilla-daemon
2011-01-12 22:03 ` bugzilla-daemon
2011-01-12 22:04 ` bugzilla-daemon
2011-01-12 22:08 ` bugzilla-daemon
2011-01-13 1:02 ` bugzilla-daemon
2011-01-13 12:47 ` bugzilla-daemon
2011-01-13 16:54 ` bugzilla-daemon
2011-01-13 17:34 ` bugzilla-daemon
2011-01-13 20:26 ` bugzilla-daemon
2011-01-13 22:16 ` bugzilla-daemon
2011-01-15 14:06 ` bugzilla-daemon
2011-01-16 21:45 ` bugzilla-daemon
2011-01-17 16:06 ` bugzilla-daemon
2011-01-17 18:06 ` bugzilla-daemon
2011-01-18 18:56 ` bugzilla-daemon
2011-01-18 21:45 ` bugzilla-daemon
2011-01-19 6:58 ` bugzilla-daemon
2011-01-19 12:16 ` bugzilla-daemon
2011-01-19 21:15 ` bugzilla-daemon
2011-01-19 22:28 ` bugzilla-daemon
2011-01-19 22:30 ` bugzilla-daemon
2011-01-21 19:49 ` bugzilla-daemon
2011-01-21 23:55 ` bugzilla-daemon
2011-01-21 23:57 ` bugzilla-daemon
2011-01-24 12:56 ` bugzilla-daemon
2011-01-24 23:02 ` bugzilla-daemon
2011-01-27 13:58 ` bugzilla-daemon
2011-01-31 19:26 ` bugzilla-daemon
2011-01-31 19:30 ` bugzilla-daemon
2011-01-31 21:52 ` bugzilla-daemon
2011-02-03 0:14 ` bugzilla-daemon
2011-02-03 8:20 ` bugzilla-daemon
2011-02-08 0:38 ` bugzilla-daemon
2011-02-08 16:05 ` bugzilla-daemon
2011-02-09 19:51 ` bugzilla-daemon
2011-02-09 22:35 ` bugzilla-daemon
2011-02-10 0:20 ` bugzilla-daemon
2011-02-11 7:00 ` bugzilla-daemon
2011-02-11 7:32 ` bugzilla-daemon
2011-02-11 19:41 ` bugzilla-daemon
2011-02-11 19:43 ` bugzilla-daemon
2011-02-12 1:14 ` bugzilla-daemon
2011-02-12 3:08 ` bugzilla-daemon
2011-02-12 7:27 ` bugzilla-daemon
2011-02-12 10:37 ` bugzilla-daemon
2011-02-12 13:36 ` bugzilla-daemon
2011-02-12 17:38 ` bugzilla-daemon
2011-02-12 21:31 ` bugzilla-daemon
2011-02-12 23:17 ` bugzilla-daemon
2011-02-13 23:51 ` bugzilla-daemon
2011-02-14 1:05 ` bugzilla-daemon
2011-02-17 15:58 ` bugzilla-daemon
2011-02-21 0:56 ` bugzilla-daemon
2011-02-21 4:28 ` bugzilla-daemon
2011-02-21 5:29 ` bugzilla-daemon
2011-02-21 5:40 ` bugzilla-daemon
2011-02-22 21:03 ` 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-26552-2300@https.bugzilla.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.