8086:2a02 Errors/glitches in displaying windows

[Grzegorz Pawlik]

Description: Ubuntu 12.04.1 LTS
Release: 12.04

After some time after restarting i get those "glitches" on my screen. It sometimes affects walpaper also, allways some program windows (but not allways every - now phpstorm window looks fine)

I would gladly provide some more info if I could.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-31-generic 3.2.0-31.50
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: greg 1972 F.... pulseaudio
CRDA:
 country PL:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0500000 irq 47'
   Mixer name : 'Silicon Image SiI1392 HDMI'
   Components : 'HDA:14f15051,1179ff51,00100000 HDA:10951392,ffffffff,00100000'
   Controls : 21
   Simple ctrls : 9
Date: Thu Oct 4 14:15:32 2012
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=cfc3dba8-491e-4d04-9685-6e183e557c7b
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: TOSHIBA Satellite U400
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic root=UUID=410c07af-5d7a-4b98-83b3-5cf15912cd4a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-31-generic N/A
 linux-backports-modules-3.2.0-31-generic N/A
 linux-firmware 1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V3.00
dmi.board.name: Satellite U400
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV3.00:bd07/12/2008:svnTOSHIBA:pnSatelliteU400:pvrPSU40E-02300JPL:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite U400
dmi.product.version: PSU40E-02300JPL
dmi.sys.vendor: TOSHIBA

[Grzegorz Pawlik (grzegorzpawlik)]

ps. Restarting those apps (like chrome) doesn't fix the view

[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.6 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.6-quantal/

[Grzegorz Pawlik (grzegorzpawlik)]

I have recently switched to kernel 3.6. Don't know what triggers that error though, so I'll just wait day or two and observe if it happens.

Thanks!

[Grzegorz Pawlik (grzegorzpawlik)]

Ok, unfortunately bug still exists in 3.6 kernel.

My observations: last time exiting game "Torchlight" triggered it somehow. Changing resolution back and forth doesn't remove the glitches. Neither restarting gnome shell (alt+fr, ther "r").

Log out and it removes glitches as well as restarting computer (which is not good enough workaround of course).

[penalvch (penalvch)]

Grzegorz Pawlik, could you please provide the full computer model as noted on the sticker?

[Grzegorz Pawlik (grzegorzpawlik)]

Hi Christofer,
I didn't have this problem for a longer time (can't remember how long). As I said - it happened quite randomly and I have no idea after which update it dissapeared.

Toshiba Satelite U400 - 12P (serial number is unreadable already).

[penalvch (penalvch)]

Grzegorz Pawlik, as per http://www.toshiba.eu/innovation/jsp/supportMyProduct.do?service=EU an update is available for your BIOS (4.70). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Thank you for your understanding.

[Grzegorz Pawlik (grzegorzpawlik)]

Christopher M. Penalver - please note that I don't have this bug anymore (please read previous message), so I can't confirm if the BIOS update was helpful.

[penalvch (penalvch)]

Grzegorz Pawlik, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1061570/comments/10 regarding you don't have the bug anymore. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.