Created attachment 46512 [details] [review] an excerpt of /var/log/messages with some comments and an example of the output to tty1 Radeon driver reports EDID errors every 10 seconds, which causes related log files increased over 100M in size every day and makes the system hardly usable because of the output every 10 seconds to tty1 (and ttyS0 in my case). See also my related LKML message: https://lkml.org/lkml/2011/4/14/661 I get every 10 seconds: radeon 0000:01:05.0: HDMI-A-1: EDID block 0 invalid. together with a block of zeroes (only on tty1, see attachment). OS: Debian GNU/Linux 6.0.1 (squeeze) kernel: Linux 2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1) (it was the same with Linux 2.6.32-5-amd64 (2.6.32-31)) Mainboard: ASUS M2A-VM Chipset (onboard): ATI Technologies Inc RS690 [Radeon X1200 Series] aka 01:05.0 0300: 1002:791e
Argh, bad typo: (it was the same with Linux 2.6.32-5-amd64 (2.6.32-31)) should have been: (it was the same with Linux 2.6.38-2-amd64 (2.6.38-3)) What I wanted to say: It doesn't matter if the 2.6.38 from wheezy or the backported 2.6.38 is used, but that may be obvious. I'm really sorry for that bad copy&paste mistake.
RS690 did not support displayport. I'm not sure how you have one on your board.
drm_kms_helper.poll=0 will disable the output polling
As you can see in the corresponding LKML thread, I already know about the drm_kms_helper.poll=0 option (and use it), but this is just a workaround to make the system usable and prevent the logfiles of being bloated. It doesn't fix the original problem (but I appreciate your intention to point me at this).
(In reply to comment #2) > RS690 did not support displayport. I'm not sure how you have one on your > board. I'm sorry. I confounded two boards. The one has displayport, the other one does not. This one does not. It only has DVI-D and VGA (D-Sub/RGB). I'm sorry for this mistake.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/191.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.