From: "Robin H. Johnson" <robbat2@gentoo.org>
To: linux-kernel@vger.kernel.org
Subject: KMS/radeon regression: failure to set modes on CEDAR & TAHITI; v3.11 vs 3.12-rc5/rc7
Date: Sun, 3 Nov 2013 18:48:32 +0000 [thread overview]
Message-ID: <20131103184832.GD5763@orbis-terrarum.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2712 bytes --]
(Please CC, not sub'd to LKML; Was originally posted to
xorg-driver-ati@lists.x.org, dri-devel@lists.freedesktop.org, but I
think the dmesg attachments got it eaten as spam).
I apologize for not sending this sooner, but I wanted to be really sure that I
wasn't introducing the bug elsewhere, and I was lacking time to even narrow it
down this far.
TL;DR:
3.11 kernel does proper modeset for dual 1920x1200 outputs
3.12-rc5/rc7 kernel fails to do proper modeset, blank screen after radeon loaded
Symptoms:
- With implicit video= modes, after the radeon module loads, both monitors just go blank.
Kernel message: radeon 0000:01:00.0: No connectors reported connected with modes
X does not visible start, screen stays black.
- With explicit video= modes, after the radeon module loads, both monitors during the
kernel boot display very garbled output; after X starts, they are in
1024x768, with no higher modes listed.
Attached are four dmesg [1] runs, on v3.11 vs v3.12-rc7, with both explicit
video parameters, and implicit video parameters; as well as drm.debug=0x06 in
ALL cases; as well as two xorg logs (both from the implicit variants).
testcase 1 (implicit): modeset=1 fbcon=map:0 drm.debug=0x06
testcase 2 (explicit): video=HDMI-A-1:1920x1200e video=DVI-I-1:1920x1200e modeset=1 fbcon=map:0 drm.debug=0x06
I have produced this bug with three different cards:
CEDAR 0x1002:0x68F9 0x1043:0x03CA (used for all these bug reports)
CEDAR 0x1002:0x68F9 0x174B:0xE164
TAHITI 0x1002:0x6798 0x1458:0x2261 (7970, borrowed before)
This happened as far back as 3.12-rc5 for me, but I didn't debug more at the
time.
Monitors:
(Left) Dell U2410 via DVI
(Center) Dell U2413 via HDMI
(Right is another U2410, not connected at all)
Userspace:
xorg-server-1.14.3
mesa-9.2.1
xf86-video-ati-7.2.0
I think the error might be and off by one in the connector probing, based on
this:
3.11:
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:15:HDMI-A-1]
[drm:radeon_atombios_connected_scratch_regs], DFP1 connected
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:15:HDMI-A-1] probed modes :
3.12-rc7:
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:16:HDMI-A-1]
[drm:radeon_process_i2c_ch], hw_i2c error
[drm:radeon_atombios_connected_scratch_regs], DFP1 disconnected
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:16:HDMI-A-1] disconnected
[1] yes I know about the bonding error, that's a separate issue I need
to mail to LKML/netdev.
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
[-- Attachment #1.2: 3.11.0-working-explicit.gz --]
[-- Type: application/octet-stream, Size: 26611 bytes --]
[-- Attachment #1.3: 3.11.0-working-implicit.gz --]
[-- Type: application/octet-stream, Size: 26378 bytes --]
[-- Attachment #1.4: 3.11.0-working-implicit-xorg.gz --]
[-- Type: application/octet-stream, Size: 9330 bytes --]
[-- Attachment #1.5: 3.12.0-rc7-broken-explicit.gz --]
[-- Type: application/octet-stream, Size: 27341 bytes --]
[-- Attachment #1.6: 3.12.0-rc7-broken-implicit.gz --]
[-- Type: application/octet-stream, Size: 25820 bytes --]
[-- Attachment #1.7: 3.12.0-rc7-broken-implicit-xorg.gz --]
[-- Type: application/octet-stream, Size: 7468 bytes --]
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 460 bytes --]
next reply other threads:[~2013-11-03 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 18:48 Robin H. Johnson [this message]
2013-11-07 14:13 ` Veaceslav Falico
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=20131103184832.GD5763@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®