Bug 56441 - video error with ubuntu 12.10 and kernels after 3.50.21, and generic_3.8.0-030800rc6
Summary: video error with ubuntu 12.10 and kernels after 3.50.21, and generic_3.8.0-03...
Status: NEW
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: 2013-04-09 21:34 UTC by Carlo Rizzardo
Modified: 2013-11-16 18:59 UTC (History)
2 users (show)

See Also:
Kernel Version: generic_3.8.0-030800rc6
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
patch 1/2 (2.64 KB, patch)
2013-04-09 23:16 UTC, Alex Deucher
Details | Diff
patch 2/2 (1.31 KB, patch)
2013-04-09 23:16 UTC, Alex Deucher
Details | Diff

Description Carlo Rizzardo 2013-04-09 21:34:42 UTC
I have this problem on Ubuntu 12.10, so I first posted on Launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1112898).

Here I copy the same description:

After the update to the kernel 3.50.22 when I rebooted the computer It only displayed some orange vertical lines instead of the login page (image 3), moving the mouse up it's point appears (over a black line)(image 5) and moving the mouse on the top-right corner the lines became grey(image 4) and clicking they became dark grey (the color of the shut-down menu) (image 6).
Sometimes instead of the lines it shows the screen as shifted to the right (the right half of the screen ison the left and the left part on the right)(images 1 and 2 are of two different times I used the computer).
The same happens with the 3.50.23 kernel.
Booting with the 3.50.21 it works fine.
(I don't know where I put the links for the images, if you need them I'll post them again)

I noticed that putting the system in stand-by and then waking it solves the problem.

I tried the generic_3.8.0-030800rc6 kernel and the problem persisted, I did the bisecting and the result was this:

8f53b5444a25b5be3bfe0164316f9bc7845279c9 is the first bad commit
commit 8f53b5444a25b5be3bfe0164316f9bc7845279c9
Author: Alex Deucher <alexander.deucher@amd.com>
Date: Wed Aug 15 17:18:42 2012 -0400

    drm/radeon: properly handle mc_stop/mc_resume on evergreen+ (v2)

    BugLink: http://bugs.launchpad.net/bugs/1091251

    commit 62444b7462a2b98bc78d68736c03a7c4e66ba7e2 upstream.

    - Stop the displays from accessing the FB
    - Block CPU access
    - Turn off MC client access

    This should fix issues some users have seen, especially
    with UEFI, when changing the MC FB location that result
    in hangs or display corruption.

    v2: fix crtc enabled check noticed by Luca Tettamanti

    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    [ herton: adjust context ]
    Signed-off-by: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>

:040000 040000 3f24b41f6ebf38caa2f3ca512169cd6a150aa561 58e0037d2d28684e65d4c5980ef7a385ce2888ee M drivers

On the launchpad page you can find the automatically generated information.

thank you.
Comment 1 Alex Deucher 2013-04-09 23:16:09 UTC
Created attachment 97911 [details]
patch 1/2

Do the attached patches help?
Comment 2 Alex Deucher 2013-04-09 23:16:29 UTC
Created attachment 97921 [details]
patch 2/2
Comment 3 Carlo Rizzardo 2013-04-10 17:47:32 UTC
I'm not sure on how to apply the patches, I tried downloading the ubuntu kernel with git (command "git clone git://kernel.ubuntu.com/ubuntu/ubuntu-quantal.git"), copying the patches to the source folder and doing "cat 0001-drm-radeon-update-wait_for_vblank-for-evergreen.patch | patch -p1 --dry-run". it failed saying this:

patching file drivers/gpu/drm/radeon/evergreen.c
Hunk #1 FAILED at 1174.
Hunk #2 succeeded at 111 with fuzz 1 (offset -1073 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/gpu/drm/radeon/evergreen.c.rej

Should I use the linux kernel (not ubuntu's)? If so which version? (and where can I find the sources?)
Or simply this isn't the right way to apply the patch?
Comment 4 Alex Deucher 2013-04-10 17:56:05 UTC
For ease of testing, just try my drm-next-3.10 branch:
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.10-wip

git clone git://people.freedesktop.org/~agd5f/linux
git checkout -b drm-next-3.10-wip origin/drm-next-3.10-wip
Comment 5 Carlo Rizzardo 2013-04-10 21:26:07 UTC
I built that kernel (not perfectly knowing what I was doing...) and I managed to get it installed. (using the two git commands you posted, make localmodconfig for the configuration and generating the deb packet with "make-kpkg --rootcmd fakeroot --initrd kernel_image")

But it has the same problem: this time it showed the orange vertical lines.
Comment 6 Alex Deucher 2013-11-13 21:14:51 UTC
Is this still an issue with a more recent kernel?  We've gone back to turning off the displays completely when updating the MC.
Comment 7 Carlo Rizzardo 2013-11-16 13:11:24 UTC
Now, with the kernel ubuntu currently uses,  it works without any problem.

I don't know if it has to do with this or is useful but while turning on ubuntu displays for about a second the message "[   17.074823] radeon 0000:01:00.0: Invalid ROM contents"
Comment 8 Alex Deucher 2013-11-16 18:59:32 UTC
(In reply to Carlo Rizzardo from comment #7)
> Now, with the kernel ubuntu currently uses,  it works without any problem.
> 

Good.

> I don't know if it has to do with this or is useful but while turning on
> ubuntu displays for about a second the message "[   17.074823] radeon
> 0000:01:00.0: Invalid ROM contents"

You can ignore that.

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