Display Corruption Using KMS on Radeon HD 3400

Bug #579671 reported by darren
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

There are little green dashes across the screen randomly. This is on a Toshiba Satellite Pro laptop with an RV620 Radeon HD 3400 display.

Throughout using Karmic this was absolutely fine using the Radeon driver. To get 3d support I started using the Xorg-edgers PPA and then 3d support was fine too.

Now from upgrading to Lucid the display corruption is there from Plymouth onwards. It does start off worse and then get slightly better on one laptop but on an identical laptop the corruption is slightly worse. Obviously the clocks are slightly off between laptops. It's still not perfect on any though.

Using nomodeset on the kernel options sorts it out but then the virtual desktop has to be set before changing display properties.

I've tested with the mainline kernel (2.6.34-999) which is exactly the same.

As an aside, these Toshiba laptops seem to have a dodgy implementation of the RV620 - fglrx has always just hard-locked on X start, now this works but gives very bad display corruption. Using Windows on them is fine though so I can't blame the laptops specifically.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: darrenm 1772 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd6500000 irq 22'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1179ff1e,00100003 HDA:11c11040,11790001,00100200'
   Controls : 18
   Simple ctrls : 10
Date: Wed May 12 21:57:42 2010
HibernationDevice: RESUME=UUID=deb72699-9fb1-48d0-af64-b2a5a99e7a89
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
MachineType: TOSHIBA Satellite Pro A300
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=bdbaba16-e57a-40fd-a959-a53824959e66 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 08/18/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.40
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.40:bd08/18/2008:svnTOSHIBA:pnSatelliteProA300:pvrPSAGDE-003003EN:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite Pro A300
dmi.product.version: PSAGDE-003003EN
dmi.sys.vendor: TOSHIBA

Revision history for this message
darren (darrenm) wrote :
Revision history for this message
GopNick (80502905788-mail) wrote :

Got this bug too on Toshiba Satellite A 300 (Radeon 3470). Lucid with the latest updates installed.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi darren,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
GopNick (80502905788-mail) wrote :

I've tested with the mainline kernel (2.6.34-999) which is exactly the same.

Revision history for this message
darren (darrenm) wrote :

I also tested with 2.6.34-020634-generic (latest a few days ago) and this was the same again.

tags: removed: needs-upstream-testing
tags: added: kernel-graphics
removed: graphics
Revision history for this message
GopNick (80502905788-mail) wrote :

Any comments?

Revision history for this message
darren (darrenm) wrote :

Not sure why this is marked as incomplete?

Should I be taking this upstream?

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
GopNick (80502905788-mail) wrote :

Any comments ???

Revision history for this message
madbiologist (me-again) wrote :

If this is the same bug as https://bugs.freedesktop.org/show_bug.cgi?id=30029 it may be fixed upstream in kernel 2.6.36-rc5. This patch is also in kernel 2.6.35.5, which is schedule as a future Maverick update.

Revision history for this message
madbiologist (me-again) wrote :

Is this still occurring on Ubuntu 13.04 "Raring Ringtail"?

Revision history for this message
penalvch (penalvch) wrote :

darren, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.