video error with ubuntu 12.10 and kernels after 3.50.21

[Carlo]

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.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-21-generic 3.5.0-21.32
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: carlo 1942 F.... pulseaudio
 /dev/snd/controlC0: carlo 1942 F.... pulseaudio
CRDA:
 country CN:
  (2402 - 2482 @ 40), (N/A, 20)
  (5735 - 5835 @ 40), (N/A, 30)
Date: Fri Feb 1 20:50:31 2013
HibernationDevice: RESUME=UUID=f7396edd-251d-4f47-8145-4a527cc77325
InstallationDate: Installed on 2012-11-26 (67 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Hewlett-Packard p6-2312el
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=2e9203a8-b83b-4542-9464-0573af420737 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-21-generic N/A
 linux-backports-modules-3.5.0-21-generic N/A
 linux-firmware 1.95
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2012
dmi.bios.vendor: AMI
dmi.bios.version: 8.07
dmi.board.name: 2ADA
dmi.board.vendor: Foxconn
dmi.board.version: 1.00
dmi.chassis.asset.tag: CZC2388M2J
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:bvr8.07:bd08/29/2012:svnHewlett-Packard:pnp6-2312el:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: p6-2312el
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc6-raring/

[Carlo (x-carlo94)]

I tried the kernel generic_3.8.0-030800rc6 (installing both "linux-image-3.8.0-030800rc6-generic_3.8.0-030800rc6.201301312135_amd64.deb" and "linux-image-extra-3.8.0-030800rc6-generic_3.8.0-030800rc6.201301312135_amd64.deb") and it doesn't fix the problem.

[Carlo (x-carlo94)]

I noticed that running one of the involved kernels if I suspend the system and then wake it, it works correctly. And sometimes the 3.50.22 kernel starts correctly.

[madbiologist (me-again)]

According to http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html kernel 3.50.22 is based on the mainline kernel 3.5.7.2. According to http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.2-quantal/0003-debian-changelog.patch there are not many patches that affect your Caicos Radeon. One that might is drm/radeon: Don't destroy I2C Bus Rec in radeon_ext_tmds_enc_destroy().

[Carlo (x-carlo94)]

so...is there anything I can do?

[madbiologist (me-again)]

Do you feel like bisecting? See https://wiki.ubuntu.com/Kernel/KernelBisection?highlight=%28BISECTING%29#Bisecting_Ubuntu_kernel_versions

[Carlo (x-carlo94)]

I've done the bisecting and the result is this:

8f53b5444a25b5be3bfe0164316f9bc7845279c9 is the first bad commit
commit 8f53b5444a25b5be3bfe0164316f9bc7845279c9
Author: Alex Deucher <email address hidden>
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 <email address hidden>
    [ herton: adjust context ]
    Signed-off-by: Herton Ronaldo Krzesinski <email address hidden>

:040000 040000 3f24b41f6ebf38caa2f3ca512169cd6a150aa561 58e0037d2d28684e65d4c5980ef7a385ce2888ee M drivers

[madbiologist (me-again)]

Nice work. It seems I was looking at the wrong changelog. As well as being listed in bug #1091251 that patch is listed at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.2-quantal/CHANGES

The next step is to file a kernel bug at https://bugzilla.kernel.org/ or at least email Alex Deucher, the author of the patch. In either case, it will probably be helpful to refer to this bug report.

[Carlo (x-carlo94)]

done, here's the link to the report: https://bugzilla.kernel.org/show_bug.cgi?id=56441

[Carlo (x-carlo94)]

if I update to ubuntu 13.04 can I still use the 3.50.21 kernel?

[Carlo (x-carlo94)]

If I could update to 13.04 I would check the new kernels

[Julian Wiedmann (jwiedmann)]

Carlo,
since 3.5.0-22.34, several MC related patches[0] have landed in the kernel for quantal. Could you please try the latest version available from -updates and see if this is still an issue? Thanks.

[0]
54fce73 drm/radeon: disable the crtcs in mc_stop (evergreen+) (v2)
0dfac2f drm/radeon: properly lock disp in mc_stop/resume for evergreen+
16bf4c2 drm/radeon/evergreen+: wait for the MC to settle after MC blackout
9d49c9d drm/radeon: fix MC blackout on evergreen+

[Carlo (x-carlo94)]

yes, the 3.5.0-34 works!
So also the latest version of 3.8 kernel of ubuntu 13.04 should work?

[Julian Wiedmann (jwiedmann)]

Great, thanks for the quick testing!
As the kernel in raring has the same patches applied, I'd assume that it's been fixed too.

[Carlo (x-carlo94)]

thank you all!