Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi! On Thu, May 05, 2011 at 05:07:05PM -0500, Jonathan Nieder wrote: Mm, I have read your report carefully enough yet, but: did you get any response upstream? I would suggest filing a bug at [1], product DRI, component DRM/Radeon, version unspecified (yes, this is the place for kernel DRI bugs), mentioning which versions worked and did not work, pointing to your lkml message and attaching logs. No, I did not. I followed your suggestion and filed a bug at bugs.freedesktop.org. That way one could be sure upstream knows about the problem. :) That's the point. I thought by mailing to the LKML upstream would get informed about this, but that seems to be not the case. Then I thought the debian kernel team would inform upstream, but that seems to be not the case either... If you do so, do please send us the bug number. Here it is: Bug 37040 Best regards, Martin pgpUbUxyaYPyE.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi, sorry, this was just a bad copypaste mistake: (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)) See the bug. I already mentioned it there. On Mon, May 09, 2011 at 08:15:05PM -0500, Jonathan Nieder wrote: forwarded 624549 https://bugs.freedesktop.org/show_bug.cgi?id=37040 quit Martin Teufel wrote: Here it is: Bug 37040 Thanks! Marking it. 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)) That's interesting. Are there any previous versions that did not exhibit the problem? pgpFbdguRvX99.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi, I want and have to rectify my last mail: This patch is obviously not applied in 2.6.38-bpo.2 because I get: [5.924366] drm: Unknown parameter `edid_strict' Could you get this applied to the next version of a linux backport? Best regards, Martin On Tue, May 03, 2011 at 10:29:27PM +0200, Martin Teufel wrote: Hi together, does someone know if this patch has been applied already to linux-image-2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1)? I installed this image yesterday and had the idea to test the drm.edid_strict=0 parameter on it today. - It works like a charm. ;) Dunno why my patch didn't work... (But I don't have the time nor the mood to track this down atm.) Nevertheless: Thank you for trying to help me. - And sorry for bugreporting this twice and not cc-ing the last mail. Reason for the first was that I never used reportbug on this machine before and therefore had no .reportbugrc on it which caused in a nonexistent mail address due to some circumstances. Best regards, Martin pgpqYJjKngagh.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi, On Thu, May 05, 2011 at 03:56:31PM -0500, Jonathan Nieder wrote: So that leaves us with a puzzle: does that mean that 2.6.38-3~bpo60+1 fixed it (forgetting about the drm.edid_strict parameter for a moment)? no. Without drm.edid_strict=0 the error occurs (every 10 seconds ...). With drm.edid_strict=0 given, the error doesn't occur but KMS gets disabled (don't know why and figured this out only today, when I got to the machine (did this test via a serial line behind a ssh connection on tuesday). Ah, sorry I wasn't clearer before. The edid_strict patch is something Alex had been thinking about but it is not in appliable shape (it does not have strict enough buffer size checks to cope with e.g. maliciously made hardware). And of course it's even better if it is possible through a driver change to get an uncorrupted edid. Hm, I see (and agree). So we/I'll wait for a fix from upstream. I got back to drm_kms_helper.poll=0 for now. Regards, Martin pgpMLOGHxYeu7.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi together, does someone know if this patch has been applied already to linux-image-2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1)? I installed this image yesterday and had the idea to test the drm.edid_strict=0 parameter on it today. - It works like a charm. ;) Dunno why my patch didn't work... (But I don't have the time nor the mood to track this down atm.) Nevertheless: Thank you for trying to help me. - And sorry for bugreporting this twice and not cc-ing the last mail. Reason for the first was that I never used reportbug on this machine before and therefore had no .reportbugrc on it which caused in a nonexistent mail address due to some circumstances. Best regards, Martin On Tue, May 03, 2011 at 02:01:08PM -0500, Jonathan Nieder wrote: Thanks; cc-ing the bug log. So, my only other suggestion is a few rounds of bisection. It works like this: apt-get install git build-essential git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git cd linux-2.6 git bisect start git bisect bad v2.6.37 git bisect good v2.6.32;# or whichever was known to be good # now it checks out a version half-way between make localmodconfig;# minimal configuration make deb-pkg ... install the package, reboot, test ... git bisect good;# if it doesn't spam dmesg git bisect bad; # if it does git bisect skip;# if some other bug makes it hard to test # okay, next iteration... make oldconfig make deb-pkg At the end of this process, we would know what the first bad commit is, which can be very helpful for tracking it down. Just narrowing down the regression range with a few rounds is already useful; in that case, if you send git bisect log output at the end we should be able to use it to figure something out. If you are the visual sort of person like I am, git bisect visualize with gitk installed can show what's going on between steps. Thanks again for working on this, and sorry I don't have more useful advice. Regards, Jonathan pgpQtbXKFdczR.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi, I applied this patch to the source tree of linux 2.6.38 with debian patches (package linux-source-2.6.38 of wheezy), compiled the kernel with the same config as of debians linux-image-2.6.38-2-amd64 (wheezy) and set 'drm_kms_helper.poll=0', but it had absolutely no affect. Same messages every 10 seconds. Any further suggestions? Best regards, Martin On Fri, Apr 29, 2011 at 04:46:08PM -0500, Jonathan Nieder wrote: Thanks for letting us know. Could you try the patch from https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 and boot with the drm.edid_strict=0 option? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110503020306.ga5...@hekate.rbi.informatik.uni-frankfurt.de
Bug#624549: linux-image-2.6.38-2-amd64: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Package: linux-2.6 Version: 2.6.38-3 Severity: important Tags: upstream Hi, I encountered a bug in the radeon driver module of 2.6.37 which still exists in 2.6.38. I have a mainboard called M2A-VM which has VGA, DVI and display port as graphic output ports. When I boot Debian GNU/Linux with Linux 2.6.37 or 2.6.38 I get every 10 seconds: radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID This error message is spamming to tty1 (and because of my configuration to ttyS0 too). With radeon.modeset=0 set, I get rid of this messages by disabling KMS for this driver. This behaviour is also described here: http://ubuntuforums.org/showthread.php?t=1607778 My board has no HDMI port btw. - I think the driver should either not search for the HDMI-A-1: EDID block 0 resp. a HDMI connected monitor while the board has no HDMI port at all or just probe for it once instead of every 10 seconds. I don't see any reason for probing every 10 seconds but I don't know if there is one. I already reportet this on the LKML btw. Regards, Martin -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=UUID=c491e50b-1626-4ab2-bb2f-9d9c795a0ea9 ro console=tty0 console=ttyS0,115200n8 drm_kms_helper.poll=0 ** Not tainted ** Kernel log: [7.020103] input: PS/2 Logitech Mouse as /devices/platform/i8042/serio1/input/input4 [7.029227] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.034620] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034623] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034626] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034628] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034631] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034633] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034636] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034639] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034641] [7.086413] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.091835] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091838] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091840] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091843] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091845] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091848] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091850] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091853] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091855] [7.142701] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.148085] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148088] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148090] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148093] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148095] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148098] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148101] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148103] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148105] [7.198952] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.204332] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204335] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204337] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204340] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204343] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204345] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204348] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204350] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204352] [7.205893] radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [7.211985] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID [7.224664] [drm] fb mappable at 0xFA04 [7.228916] [drm] vram apper at 0xFA00 [7.233062] [drm] size 2150400 [7.236169] [drm] fb depth is 8 [7.239361] [drm]pitch is 1792 [7.250869] Console: switching to colour frame buffer device 200x75 [
Bug#624486: linux-image-2.6.38-2-amd64: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Package: linux-2.6 Version: 2.6.38-3 Severity: important Hi, I encountered a bug in the radeon driver module of 2.6.37 which still exists in 2.6.38. I have a mainboard called M2A-VM which has VGA, DVI and display port as graphic output ports. When I boot Debian GNU/Linux with Linux 2.6.37 or 2.6.38 I get every 10 seconds: radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID This error message is spamming to tty1 (and because of my configuration to ttyS0 too). With radeon.modeset=0 set, I get rid of this messages by disabling KMS for this driver. This behaviour is also described here: http://ubuntuforums.org/showthread.php?t=1607778 My board has no HDMI port btw. - I think the driver should either not search for the HDMI-A-1: EDID block 0 resp. a HDMI connected monitor while the board has no HDMI port at all or just probe for it once instead of every 10 seconds. I don't see any reason for probing every 10 seconds but I don't know if there is one. I already reportet this on the LKML btw. Regards, Martin -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=UUID=c491e50b-1626-4ab2-bb2f-9d9c795a0ea9 ro console=tty0 console=ttyS0,115200n8 drm_kms_helper.poll=0 ** Not tainted ** Kernel log: [7.020103] input: PS/2 Logitech Mouse as /devices/platform/i8042/serio1/input/input4 [7.029227] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.034620] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034623] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034626] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034628] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034631] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034633] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034636] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034639] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034641] [7.086413] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.091835] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091838] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091840] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091843] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091845] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091848] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091850] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091853] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091855] [7.142701] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.148085] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148088] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148090] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148093] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148095] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148098] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148101] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148103] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148105] [7.198952] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.204332] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204335] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204337] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204340] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204343] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204345] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204348] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204350] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204352] [7.205893] radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [7.211985] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID [7.224664] [drm] fb mappable at 0xFA04 [7.228916] [drm] vram apper at 0xFA00 [7.233062] [drm] size 2150400 [7.236169] [drm] fb depth is 8 [7.239361] [drm]pitch is 1792 [7.250869] Console: switching to colour frame buffer device 200x75 [7.259926] fb0:
