garbled screen during wake up from hibernation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu 9.10
Release: 9.10
linux:
Installed: (none)
Candidate: 2.6.31.14.27
Version table:
2.6.31.14.27 0
500 http://
Video card : ATI Mobility Radeon HD 4570
I am using fglrx drivers from ubuntu repo
When the computer was resuming from hibernated state i.e. waking up , whole of the screen was garbled (mostly green) for almost 15-20 seconds then the top portion of screen was garbled (mostly red) and remaining black and after a few seconds the password box was presented . However the computer was perfectly in usable state after all this but the garbled screen was scary !
When using "ubuntu-bug -p linux" command i got error saying "The problem cannot be reported:This is not a genuine Ubuntu package". So i have uploaded additional files.
---
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: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc500000 irq 22'
Mixer name : 'IDT 92HD73C1X5'
Components : 'HDA:111d7675,
Controls : 16
Simple ctrls : 10
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfc010000 irq 17'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 4
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
CurrentDmesg:
[ 18.902235] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 18.902238] tg3: eth0: Flow control is on for TX and on for RX.
[ 18.902741] ADDRCONF(
[ 29.162528] eth0: no IPv6 routers present
[ 29.438075] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Dell Inc. Studio 1555
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_IN
SHELL=/bin/bash
ProcVersionSign
Regression: No
RelatedPackageV
Reproducible: Yes
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
Tags: lucid hibernate resume needs-upstream-
Uname: Linux 2.6.32-21-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/29/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0C234M
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Studio 1555
dmi.product.
dmi.sys.vendor: Dell Inc.
tags: | added: kernel-series-unknown |
tags: |
added: karmic removed: kernel-series-unknown |
Hi Tanuj,
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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux 483718
Also, if you could 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/KernelMainl ineBuilds . 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.]