Bug 14574 - using a displayport connector results in stack in dmesg and blank screen
Summary: using a displayport connector results in stack in dmesg and blank screen
Status: CLOSED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-10 05:46 UTC by Wil Reichert
Modified: 2012-06-14 16:55 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.32-rc6
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg output (57.66 KB, text/plain)
2009-11-10 05:46 UTC, Wil Reichert
Details
dmesg from 2.6.33 and dp connector (73.77 KB, text/plain)
2010-03-03 05:46 UTC, Wil Reichert
Details
dmesg from 2.6.33 and dvi connector (75.52 KB, text/plain)
2010-03-03 05:47 UTC, Wil Reichert
Details

Description Wil Reichert 2009-11-10 05:46:51 UTC
Created attachment 23719 [details]
dmesg output

Using a Radeon 4890 / Dell 3008WFP, a day or 2 old git kernel & kms built into the kernel.  Works fine with DVI.

stack trace:

[    0.577043] WARNING: at drivers/gpu/drm/drm_crtc_helper.c:1031 drm_helper_initial_config+0x41/0x5c()
[    0.577048] Hardware name: OEM
[    0.577050] No connectors reported connected with modes
[    0.577053] Modules linked in:
[    0.577057] Pid: 1, comm: swapper Not tainted 2.6.32-rc6-linus #6
[    0.577060] Call Trace:
[    0.577066]  [<ffffffff81038fc9>] warn_slowpath_common+0x77/0x8f
[    0.577070]  [<ffffffff8103902e>] warn_slowpath_fmt+0x3c/0x3e
[    0.577074]  [<ffffffff812c6e56>] drm_helper_initial_config+0x41/0x5c
[    0.577080]  [<ffffffff8130604a>] radeon_modeset_init+0x521/0x532
[    0.577085]  [<ffffffff812f4590>] radeon_driver_load_kms+0xd9/0xe9
[    0.577089]  [<ffffffff812cee70>] drm_get_dev+0x356/0x462
[    0.577094]  [<ffffffff814c7c09>] radeon_pci_probe+0x10/0x12
[    0.577099]  [<ffffffff8125aa7b>] local_pci_probe+0x12/0x16
[    0.577103]  [<ffffffff8125b284>] pci_device_probe+0x60/0x8f
[    0.577107]  [<ffffffff81331e90>] ? driver_sysfs_add+0x47/0x6c
[    0.577112]  [<ffffffff81331fd4>] driver_probe_device+0xa6/0x137
[    0.577116]  [<ffffffff813320bd>] __driver_attach+0x58/0x7c
[    0.577120]  [<ffffffff81332065>] ? __driver_attach+0x0/0x7c
[    0.577124]  [<ffffffff8133182e>] bus_for_each_dev+0x4e/0x83
[    0.577128]  [<ffffffff81331e47>] driver_attach+0x19/0x1b
[    0.577133]  [<ffffffff813311c6>] bus_add_driver+0xb8/0x204
[    0.577137]  [<ffffffff81332394>] driver_register+0x98/0x109
[    0.577141]  [<ffffffff8125b4ca>] __pci_register_driver+0x53/0xc3
[    0.577146]  [<ffffffff814d2e10>] ? printk+0x3c/0x44
[    0.577151]  [<ffffffff817a4634>] ? radeon_init+0x0/0xc1
[    0.577155]  [<ffffffff812cac30>] drm_init+0x6b/0xd1
[    0.577159]  [<ffffffff817a4634>] ? radeon_init+0x0/0xc1
[    0.577163]  [<ffffffff817a46f3>] radeon_init+0xbf/0xc1
[    0.577168]  [<ffffffff8100905f>] do_one_initcall+0x59/0x149
[    0.577172]  [<ffffffff81782658>] kernel_init+0x14b/0x1a1
[    0.577177]  [<ffffffff8100bdea>] child_rip+0xa/0x20
[    0.577181]  [<ffffffff8178250d>] ? kernel_init+0x0/0x1a1
[    0.577185]  [<ffffffff8100bde0>] ? child_rip+0x0/0x20
[    0.577191] ---[ end trace 182f58d67963377a ]---

full dmesg attached
Comment 1 Alex Deucher 2009-11-10 17:39:12 UTC
Displayport isn't supported yet.
Comment 2 Wil Reichert 2009-11-10 18:56:29 UTC
Not a big deal, this was just a curiosity on my part.  Any plans for support in the near future or does the lack of existing hardware make it a moot point right now?
Comment 3 Jason Tibbitts 2009-11-10 19:06:10 UTC
Perhaps some useful information at http://fedoraproject.org/wiki/Features/RadeonDisplayPort

Displayport already works on Intel hardware to some degree.
Comment 4 Jérôme Glisse 2009-11-12 13:53:39 UTC
It's quite high on the TODO list of feature we want to support soon.
Comment 5 Wil Reichert 2010-03-03 05:46:14 UTC
Created attachment 25334 [details]
dmesg from 2.6.33 and dp connector

Just tried again with the same hardware and the final 2.6.33 kernel.  Stack from dmesg is gone but screen still blanks with 5 thin vertical lines across it.
Comment 6 Wil Reichert 2010-03-03 05:47:40 UTC
Created attachment 25335 [details]
dmesg from 2.6.33 and dvi connector

For reference, same boot w/ dvi connector

Note You need to log in before you can comment on or make changes to this bug.