linux-kernel - Re: Regression: DisplayPort stops working between 2.6.37-rc1 and rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 21 Nov 2010 17:59:27 +0100
From:	Maciej Rutecki <maciej.rutecki@...il.com>
To:	Kjell Rune Skaaraas <kjella79@...oo.no>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Regression: DisplayPort stops working between 2.6.37-rc1 and rc2

On środa, 17 listopada 2010 o 17:45:54 Kjell Rune Skaaraas wrote:
> I couldn't find a smaller list for graphics, so here goes. Between
> 2.6.37-rc1 and 2.6.37-rc2 my DisplayPort monitor has stopped working. I
> can reboot between the kernel versions and reproduce this, so it's not due
> to any other package upgrade. If I go into the system settings I now only
> have three ports listed, DisplayPort-0 is missing.
> 
> This is on a Radeon HD5850 using the open source radeon drivers. Kernels
> are Ubuntu kernel PPA mainline builds, all the X11 packages follow the
> xorg-edgers PPA and are close to git. Going from the rc2 change log these
> would be suspects:
> 
> Alex Deucher (5):
>       drm/radeon/kms/evergreen: add missing pm.vblank_sync update in vbl
> handler drm/radeon/kms: make the connector code less verbose
>       drm/radeon/kms: don't disable shared encoders on pre-DCE3 display
> blocks drm/radeon/kms: add support for clock/data path routers
>       drm/radeon/kms: fix thermal sensor reporting on rv6xx
> Michel Dänzer (1):
>       drm/radeon/kms: Fix retrying ttm_bo_init() after it failed once.
> Tyson Whitehead (1):
>       drm/radeon/kms: fix bugs in ddc and cd path router code
> 
> I'm not all that great with git so haven't worked out how to pin down what
> commit is actually causing it.
> 

I created a Bugzilla entry at 
https://bugzilla.kernel.org/show_bug.cgi?id=23482
for your bug report, please add your address to the CC list in there, thanks!


-- 
Maciej Rutecki
http://www.maciek.unixy.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/