[Dell Inspiron 17R 5737] Video looks 1 byte shifted

Bug #1318531 reported by GortiZ
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned
Trusty
Triaged
Medium
Unassigned

Bug Description

The video looks like it's shifted by 1byte or so. Red looks green, blue looks violet, green looks dark violet. (almost everything looks between green and violet as in the attached snapshot.

WORKAROUND: Change GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" in /etc/default/grub to:
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset acpi_backlight=vendor"

---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: kubuntu 4499 F.... pulseaudio
 /dev/snd/controlC0: kubuntu 4499 F.... pulseaudio
CasperVersion: 1.340
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
LiveMediaBuild: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
MachineType: Dell Inc. Inspiron 5737
Package: linux (not installed)
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
RfKill:
 1: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: yes
StagingDrivers: rts5139
Tags: trusty staging
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 045YHR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5737:pvrA07:rvnDellInc.:rn045YHR:rvrA00:cvnDellInc.:ct8:cvrA07:
dmi.product.name: Inspiron 5737
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

Revision history for this message
GortiZ (mlista6) wrote :
Revision history for this message
GortiZ (mlista6) wrote :
Revision history for this message
GortiZ (mlista6) wrote :

Changing the GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" option in the /etc/default/grub file into
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset acpi_backlight=vendor"
seems to bring back the proper colors to the monitor.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1318531

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
GortiZ (mlista6)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

GortiZ, please boot into a Trusty live environment, and execute the following in a terminal:
apport-collect 1318531

description: updated
description: updated
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
GortiZ (mlista6) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected staging trusty
description: updated
Revision history for this message
GortiZ (mlista6) wrote : BootDmesg.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : CRDA.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : CurrentDmesg.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : IwConfig.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : Lspci.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : AlsaInfo.txt

apport information

description: updated
Revision history for this message
GortiZ (mlista6) wrote : BootDmesg.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : CRDA.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : CurrentDmesg.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : IwConfig.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : Lspci.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : Lsusb.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : ProcEnviron.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : ProcInterrupts.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : ProcModules.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : PulseList.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : UdevDb.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : UdevLog.txt

apport information

Revision history for this message
GortiZ (mlista6) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
GortiZ (mlista6) wrote :

I forgot to add that I can confirm that using kernel 3.15.0-rc2-trusty the screen is behaving properly as in bug #1300349, thus the question:
Will it be fixed only on 3.15 once released or will it be backported to 3.13?
Thanks for your time.

Revision history for this message
penalvch (penalvch) wrote :

GortiZ, the next step is to fully reverse commit bisect in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

description: updated
tags: added: kernel-fixed-upstream-3.15.0-rc2 latest-bios-a06 needs-reverse-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
GortiZ (mlista6) wrote :

The bisection shows that the issue has been fixed between 3.14.3-utopic and 3.15-rc1-trusty.
I'll go on with the guide bisecting the error in the torvald repository using the ubuntu configuration as in this guide:

https://wiki.ubuntu.com/KernelTeam/GitKernelBuild#Using_Ubuntu_Kernel_Configuration

Let me know if I should use vanilla instead.

Revision history for this message
GortiZ (mlista6) wrote :
Download full text (5.9 KiB)

Ok, this is where the bisect ended, this should be the first working commit (I can confirm that this commit works)

git bisect start
# good: [455c6fdbd219161bd09b1165f11699d6d73de11c] Linux 3.14
git bisect good 455c6fdbd219161bd09b1165f11699d6d73de11c
# bad: [c9eaa447e77efe77b7fa4c953bd62de8297fd6c5] Linux 3.15-rc1
git bisect bad c9eaa447e77efe77b7fa4c953bd62de8297fd6c5
# good: [cd6362befe4cc7bf589a5236d2a780af2d47bcc9] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next
git bisect good cd6362befe4cc7bf589a5236d2a780af2d47bcc9
# good: [d2b150d0647e055d7a71b1c33140280550b27dd6] Merge tag 'sh-3.15' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
git bisect good d2b150d0647e055d7a71b1c33140280550b27dd6
# good: [5fb6b953bb7aa86a9c8ea760934982cedc45c52b] include/linux/syscalls.h: add sys_renameat2() prototype
git bisect good 5fb6b953bb7aa86a9c8ea760934982cedc45c52b
# bad: [ffddc5fd19b219f557fd4a81168ce8784a4faced] fs/ncpfs/dir.c: fix indenting in ncp_lookup()
git bisect bad ffddc5fd19b219f557fd4a81168ce8784a4faced
# bad: [978c6050165bba52eab7ef3581d447eb215def77] Merge branch 'drm-docs' of ssh://people.freedesktop.org/~danvet/drm into drm-next
git bisect bad 978c6050165bba52eab7ef3581d447eb215def77
# good: [262de1453184f65e5ccfe45790f93d41f7339d49] drm/i915: Directly return the vma from bind_to_vm
git bisect good 262de1453184f65e5ccfe45790f93d41f7339d49
# bad: [2fae6a860ca9adb0c881f6dcd633df775c2520e9] drm/i915: Go OCD on the Makefile
git bisect bad 2fae6a860ca9adb0c881f6dcd633df775c2520e9
# good: [ee7fa12ce4683e92e3ab0c43c36af5fb5f6b1054] drm/i915: Fix VLV forcewake after reset
git bisect good ee7fa12ce4683e92e3ab0c43c36af5fb5f6b1054
# good: [9ad6ce51026204cbb2fda4c63f3544c3eb637471] drm/i915: Remove unused to_gem_object() macro
git bisect good 9ad6ce51026204cbb2fda4c63f3544c3eb637471
# bad: [319be8ae8aec7550371ac58f0fd29e9e51207b5b] drm/i915: add port power domains
git bisect bad 319be8ae8aec7550371ac58f0fd29e9e51207b5b
# bad: [70bf407c8deb5d2e26468a99f1af19a166bb89e7] drm/i915: fold in __intel_power_well_get/put functions
git bisect bad 70bf407c8deb5d2e26468a99f1af19a166bb89e7
# bad: [38aecea0ccbb909d635619cba22f1891e589b434] drm/i915: reverse dp link param selection, prefer fast over wide again
git bisect bad 38aecea0ccbb909d635619cba22f1891e589b434
# good: [5babf0fc26ae5596c2c113702568167fb7f8cf9b] drm/i915: No need to put forcewake after a reset
git bisect good 5babf0fc26ae5596c2c113702568167fb7f8cf9b
# first bad commit: [38aecea0ccbb909d635619cba22f1891e589b434] drm/i915: reverse dp link param selection, prefer fast over wide again

commit 38aecea0ccbb909d635619cba22f1891e589b434
Author: Daniel Vetter <email address hidden>
Date: Mon Mar 3 11:18:10 2014 +0100

    drm/i915: reverse dp link param selection, prefer fast over wide again

    ... it's this time of the year again. Originally we've frobbed this to
    fix up some regressions, but maybe our DP code improved sufficiently
    now that we can dare to do again what the spec recommends.

    This reverts

    commit 2514bc510d0c3aadcc5204056bb440fa36845147
    Author: Jesse Barnes <email address hidden>
    Date: Thu Jun 21 15:13:50 201...

Read more...

GortiZ (mlista6)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: cherry-pick reverse-bisect-done
removed: needs-reverse-bisect
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@GortiZ, I'll build a Trusty test kernel with a cherry-pick of commit 38aecea0ccbb909d635619cba22f1891e589b434. I'll post a link to the test kernel once it's built.

Changed in linux (Ubuntu Trusty):
importance: Undecided → Medium
status: New → Triaged
importance: Medium → Low
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a test kernel with a cherry-pick of 38aecea0ccbb909d635619cba22f1891e589b434. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1318531/

Can you test this kernel and see if it resolves this bug?

Revision history for this message
GortiZ (mlista6) wrote :

Sorry, can you build a 32bit image? I'm currently using the laptop and formatting it to place a 64bit is not possible.

Revision history for this message
GortiZ (mlista6) wrote :

@Joseph: If you don't have time to build a 32bit or it's not possible for you, just let me know if you have a repository I can clone or a place where I can download the source and I'll build and test it.
Thanks.

GortiZ (mlista6)
Changed in linux (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
GortiZ (mlista6) wrote :

Sorry for the status change, I wrongly cliked and I couldn't put it back to triaged.
Anyway finally I had the chance to test your x64 version and the screen seems to work fine, anyway the screen doesn't have the proper resolution (it's not listed at all, the only resolution present is 1024x768), furthermore I don't have the ethernet nor wifi driver neither so I think that your version has a different modules config than the "standard" ubuntu one (when I built the kernel during the bisection I never had those issues).

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Fix Committed → Triaged
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Sorry for the delay, yes I'll build a 32 bit kernel.

Revision history for this message
GortiZ (mlista6) wrote :

Hi Joseph,
as I wrote in the past comment, don't worry.
I had the time to format and install the 64bit version and it worked for what concerns the colors, but it seems that your kernel misses several modules with respect to the *buntu standard one.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a 32 bit test kernel with a cherry-pick of 38aecea0ccbb909d635619cba22f1891e589b434. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1318531/

Can you test this kernel and see if it resolves this bug?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Also, you will need to install both the linux-image and linux-image-extra .deb packages. That may be the cause of the missing modules for you.

Revision history for this message
GortiZ (mlista6) wrote :

Hi Joseph and Christopher,
sorry for the delay, but I've been busy. I've installed all the packages you provided me (linux-image-extra too) and I can confirm that it's working properly (also screen resolution, wifi, ...)

So for me the bug has been fixed.
Thanks for the support and let me know if you need more testing to port this to the main kernel.

Regards,
Giuseppe.

Revision history for this message
Peter-jezdec (peter-jezdec) wrote :

Also sorry about the delay.

I can confirm that http://kernel.ubuntu.com/~jsalisbury/lp1318531/ fixes the problem.

And, the bug has made it back into the upstream kernel. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you see if this issue still affects the latest upstream 3.13 kernel?

Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 stable kernel[0].

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] kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.6-trusty/

Changed in linux (Ubuntu):
importance: Low → Medium
Changed in linux (Ubuntu Trusty):
importance: Low → Medium
status: Triaged → Incomplete
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Peter-jezdec (peter-jezdec) wrote :

This issue does still affect the latest upstream 3.13 kernel.

It affects:
kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.6-trusty/

It also affects:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15.7-utopic/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15.10-utopic/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.1-utopic/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/

It does not affect:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15.6-utopic/

I've also tested most versions between v3.15-rc2-trusty and v3.15.6-utopic, none of which are affected. The regression returned in v3.15.7-utopic which is affected.

Note: In bug #1300349 I mistakenly wrote that v3.15.6-utopic is affected, but it is not. Version v3.15.7-utopic is affected.

tags: added: confirmed kernel-bug-exists-upstream
tags: removed: confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Trusty):
status: Incomplete → Confirmed
Revision history for this message
GortiZ (mlista6) wrote :

I can confirm that it affect the latest upstream 3.13 kernel, too.

penalvch (penalvch)
Changed in linux (Ubuntu Trusty):
status: Confirmed → Triaged
Changed in linux (Ubuntu):
status: Confirmed → Triaged
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.