8086:29c2 [HP Pavilion a6613es Desktop PC] Graphical corruption

[José Vidal]

My HP Pavilion a6613es Desktop PC with integrated graphics Intel G33 / G31 Express chipset GMA3100 (D VGA connector) displays graphical corruption (with Ubuntu 15.10 and 16.04):
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509721/+attachment/4547578/+files/Captura%20de%20pantalla%20de%202016-01-09%2021-43-19.png
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509721/+attachment/4547579/+files/Captura%20de%20pantalla%20de%202015-10-20%2020-36-50.png
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509721/+attachment/4547591/+files/Captura%20de%20pantalla%20de%202015-10-22%2019-36-47.png

ElementaryOs, Windows 7 and Ubuntu 14.04 with the same resolution at the same frequency looks good.

---
.tmp.unity.support.test.0:

ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2a6f]
InstallationDate: Installed on 2016-01-07 (2 days ago)
InstallationMedia: It
MachineType: HP-Pavilion FR531AA-ABE a6613es
Package: xorg 1:7.7+12ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=es_ES
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic root=UUID=6585cb0d-dec1-4200-925f-f0f868bff85f ro quiet splash
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Tags: xenial ubuntu reproducible compiz-0.9
UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev'
Uname: Linux 4.3.0-5-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.43
dmi.board.name: Benicia
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.01
dmi.chassis.asset.tag: Asset-1234
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnFR531AA-ABEa6613es:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: FR531AA-ABE a6613es
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65-3
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sun Jan 10 18:19:39 2016
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input MOSART Semi. Wireless Keyboard & Mouse KEYBOARD, id 8
 input MOSART Semi. Wireless Keyboard & Mouse KEYBOARD, id 9
xserver.errors: systemd-logind: failed to get session: PID 739 does not belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 1657
 vendor SAM
xserver.version: 2:1.17.3-2ubuntu2

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1509721/+editstatus and add the package name in the text box next to the word Package.

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

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rob (robtigeir)]

Hopefully I'm putting this to the right package...

[José Vidal (josevidal)]

Hi, thanks for the help, now just wait for the solution to be included in the updates.

[Timo Aaltonen (tjaalton)]

Wang, why did you close this without any explanation?

[José Vidal (josevidal)]

Hello, I tested with Intel driver installer, but remains the same. In Ubuntu 14.04 small faults occur, but do not bother. In 1510 it looks so bad it can not read text.

https://www.dropbox.com/s/05dws5l8sb0jvbt/Captura%20de%20pantalla%20de%202015-12-02%2019%3A45%3A54.png?dl=0

I executed the following command
https://www.dropbox.com/s/7cs4bxjo40631s2/Captura%20de%20pantalla%20de%202015-12-02%2019%3A49%3A50.png?dl=0

https://www.dropbox.com/s/zlcdkdbav45aewd/Captura%20de%20pantalla%20de%202015-12-02%2020%3A11%3A37.png?dl=0

Is the virtual device can cause these failures?

[José Vidal (josevidal)]

Hi, I tried the version 16.04 of ubuntu and also looks bad. The problem may be the kernel?
I installed w7 on the computer, ubuntu 14.04 and ubuntu 16.06. With w7 always looks good, with ubuntu 14.04 there are small errors but I can work, with ubuntu 15.10 and 16.04 are many texts that can not work look so bad.

Do you need some additional information to include in the bug report?

https://www.dropbox.com/s/d5lw8crx5qs19gs/Captura%20de%20pantalla%20de%202016-01-09%2021-42-04.png?dl=0

https://www.dropbox.com/s/83sqxqdn4x77kdc/Captura%20de%20pantalla%20de%202016-01-09%2021-42-31.png?dl=0

https://www.dropbox.com/s/7z2xnlwqvu5d4rs/Captura%20de%20pantalla%20de%202016-01-09%2021-43-19.png?dl=0

https://www.dropbox.com/s/relv1zyg1qjfuvy/Captura%20de%20pantalla%20de%202016-01-09%2021-44-24.png?dl=0

https://www.dropbox.com/s/hqhxy0h0uy59wd2/Captura%20de%20pantalla%20de%202016-01-09%2021-44-05.png?dl=0

[penalvch (penalvch)]

José Vidal, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal as it will automatically gather and attach updated debug information to this report:
apport-collect -p xorg 1509721

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

apport information

[José Vidal (josevidal)]

Christopher M. Penalver, I thank you for answering me and for helping me to better expose the problem. I know it is not easy to resolve these issues without proper information.

[penalvch (penalvch)]

José Vidal, could you please attach uncompressed/untarred pictures of the strange display directly to this report (not Dropbox URLs)?

[José Vidal (josevidal)]

Thanks for the help about the steps. I have been testing with the guidance that you mention, but I can not start ubuntu. After choosing the kernel 4.4.0-994 in grub just a loading message about the kernel, and then the screen remains black appears, only the combination of teclasAlt + Imp + REISUB it allows me to reboot.

[José Vidal (josevidal)]

Hello Christopher, I tested with the latest stable mainline kernel and it not start. Although it listed as kernel available with dpkg -l | grep "linux \ - [a-z] * \ -" and with dpkg --get-selections | grep linux-image, despite "sudo update-grub2" when I start the computer, this kernel doesn't appear in the grub.

[penalvch (penalvch)]

José Vidal, at your earliest convenience, could you please test the next most latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[José Vidal (josevidal)]

Thanks. Now, it is already fixed this bug.

On my previous comment "does not appear in kernel grub" was corrected by making "sudo update-grub2" in the main partition, with Ubuntu 14.04.3 (I use 3 partitions with 3 different OS,). In previous tests I did run "sudo update-grub2" in ubuntu 15.10 just after installing the kernel.

[penalvch (penalvch)]

José Vidal, the next step is to fully reverse commit bisect from kernel 4.3 to 4.4-rc8 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[José Vidal (josevidal)]

Hello, I checked several kernel, with the following result:
4.4rc7 good
4.4rc6 bad

I have yet to learn how to do the following steps you telling me

[Launchpad Janitor (janitor)]

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