Dell XPS 15Z Requires Kernel Parameters to Boot Correctly

[md_5]

This bug is still present on both the Ubuntu 14.04 kernel (3.13) as well as the latest mainline kernel (3.17). In addition the mainline kernel causes additional issues with regards to brightness control.

WORKAROUND: I have used the boot param noapic to run Ubuntu on this laptop since 12.04, however acpi=off, acpi=noirq or acpi_backlight=vendor dell_laptop.backlight=0 all also fix the issue. Using the last option however causes poor brightness control as the dell backlight driver is not properly optimized.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-37-generic 3.13.0-37.64
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michael 2066 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Oct 19 15:50:18 2014
HibernationDevice: RESUME=UUID=79996bc0-bea3-4008-9182-e2afa0585224
InstallationDate: Installed on 2014-01-31 (260 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Dell System XPS 15Z
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=4c859e77-4949-474c-9531-c6da9ef27187 ro noapic quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-37-generic N/A
 linux-backports-modules-3.13.0-37-generic N/A
 linux-firmware 1.127.7
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-16 (185 days ago)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 060G42
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn060G42:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS 15Z
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[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.18 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/

[md_5 (md-5)]

I am genuinely surprised. Despite 3.17 having worse issues (bugged display dimming as well), 3.18 RC1 appears to work fine without any paramaters at all:
Linux XPS-15Z 3.18.0-031800rc1-generic #201410192135 SMP Mon Oct 20 01:37:04 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Looking forward to 15.04 I guess :)

[penalvch (penalvch)]

md_5, this is not Fix Committed as outlined in https://wiki.ubuntu.com/Bugs/Status .

Despite this, the next step is to fully reverse commit bisect the linux kernel 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 ?

Once the commit has been identified, then please mark this Status Confirmed.

[md_5 (md-5)]

Sorry Chris,

"Fix CommittedFixed, but not available until next release." made it sound like the upstream commit had been made and would fix the issue once 3.18 was merged in 15.04.

With regards to the bisect I can say with certainty it is one of these: https://lkml.org/lkml/2014/10/6/515

Is there any merit to me narrowing down a more specific commit? Would a patch be backported, or should I just wait for 15.04?

[penalvch (penalvch)]

md_5, if you would like a backport to a current release, then the specific commit would need to be identified and tested on your hardware. Once testing verifies it fixes the issue, then it would be considered for a backport. Otherwise, you would wait until whichever release contains a fix for your issue.

[md_5 (md-5)]

The following commit resolves this issue: https://github.com/torvalds/linux/commit/0b8db271f1592e118feef7300f6da85bea9366da

It applies cleanly to 3.17.1, backported from 3.18RC1.

Thanks