Boots to corrupted/unusable screen

[Parag Warudkar]

iMac12 often boots to a corrupted / unusable screen with artifacts. VTs are unusable. SSH login works and killing and restarting Xorg/lightdm fixes the screen corruption problem.

[ Update: Seems to be reproducible independent of kernel version - both -17 and -18 give the same results.]

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: parag 1805 F.... pulseaudio
 /dev/snd/controlC0: parag 1805 F.... pulseaudio
Date: Tue Nov 6 12:33:38 2012
HibernationDevice: RESUME=UUID=a0842c63-8b1e-47c2-8f1a-bdec366ad5bd
InstallationDate: Installed on 2012-11-05 (1 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121017.3)
MachineType: Apple Inc. iMac12,1
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=0c41b65c-406b-4dc3-b100-95f28347cd76 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/12
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM121.88Z.0047.B1F.1201241648
dmi.board.name: Mac-942B5BF58194151B
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-942B5BF58194151B
dmi.modalias: dmi:bvnAppleInc.:bvrIM121.88Z.0047.B1F.1201241648:bd01/24/12:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
dmi.product.name: iMac12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Parag Warudkar (parag-warudkar)]

Just reproduced with -17 kernel as well. Attached dmesg out from problem boot with -18.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Parag Warudkar (parag-warudkar)]

Stopping and restarting X server makes the problem go away. Here are problem case and problem-free case Xorg logs - Xorg.0.log.good is without problem after restart, Xorg.0.log is first log when screen is corrupted.

[Parag Warudkar (parag-warudkar)]

Xorg log - after restarting X.

[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.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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.

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.7-rc4-raring/

[Parag Warudkar (parag-warudkar)]

Currently testing mainline build 3.7.0-030700rc4-generic - first boot looks ok - will provide final feedback after testing a bit more. Thanks!

[Parag Warudkar (parag-warudkar)]

Confirmed fixed in mainline build 3.7.0-030700rc4-generic .

[penalvch (penalvch)]

Parag Warudkar, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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>

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]