kernel crash with lite-on sata controller Dell XPS 13 9343

[Carolin Latze]

I have a Dell XPS 13 (2015) which has a Lite-On Sata controller:
03:00.0 SATA controller: Lite-On Technology Corporation Device 0224 (rev 10)

Right from the beginning, I have issues with that one under Linux (not Windows). It might happen that the notebook just dies (loosing its SSD), or it might not even boot. Whenever it does not boot, it usually stops with a message around "job 1 of 12 ..." (I don't find them in any logs ). Sometimes when I boot into Windows and then immediately reboot into Linux it works. It usually helps to boot a 3.19.x kernel, although even that one can have the same issues (although way less than 4.x).

The system almost always crashes completely when I run the dump tool.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-18-generic 4.2.0-18.22
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: latze 1599 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sat Nov 14 09:29:04 2015
HibernationDevice: RESUME=UUID=b8662265-a1f0-487e-9d85-2731c765b3eb
InstallationDate: Installed on 2015-08-23 (82 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp.
 Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
 Bus 001 Device 002: ID 8087:0a2a Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9343
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=9e67912b-c59e-47ac-b2f1-3ef39e3d38fb ro debug
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic N/A
 linux-firmware 1.149.1
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-31 (13 days ago)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Carolin Latze, thank you for reporting this and helping make Ubuntu better.

Could you please test the 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 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 two numbers corresponding to the kernel version, and Z is one release candidate number if applicable.

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.

[Carolin Latze (carolin-latze)]

same issue unfortunately. I rebooted several times (it seems to happen randomly as with the previous kernels) and were able to reproduce the same error messages. always something around SATA. I could take a picture of them if it helps (since I don't know if they are captured in any log ;-))

[penalvch (penalvch)]

Carolin Latze, did this issue not occur in a release prior to 15.10?

[Carolin Latze (carolin-latze)]

It did occur with 15-04 as well, however much less (that was kernel 3.19.x I believe). It would almost always happen when running the dump tool, but rarely during boot. With 4.x, it happens way more often during the boot, but less when running the dump tool (this sounds already weird when I write it, but this is what I observe)

[Carolin Latze (carolin-latze)]

Ah, one more detail: With the first 3.19.x kernels that I used, the SATA controller was detected as:

03:00.0 SATA controller: Broadcom Corporation (Wrong ID) Device 0224 (rev 10)

Now (I discovered that 2 days ago, when I opened this bug, sorry for not mentioning), it is:

03:00.0 SATA controller: Lite-On Technology Corporation Device 0224 (rev 10)

[penalvch (penalvch)]

Carolin Latze, could you please capture information from a failed boot via https://wiki.ubuntu.com/DebuggingKernelBoot ?

[Carolin Latze (carolin-latze)]

Sorry, it took long until I could produce another error. I hope those pictures help somewhat

[penalvch (penalvch)]

Carolin Latze, in the future, please don't tar/compress attachments as it makes it more difficult for folks to review the attachment.

Despite this, could you please the latest mainline kernel (4.4-rc2+cod1) and advise to the results?

[Carolin Latze (carolin-latze)]

Ok, it failed during the first 2 boot trials, only succeeded on 3rd boot.

uname -a returns

Linux ylvi 4.4.0-040400rc2-generic #201511231054 SMP Mon Nov 23 10:56:43 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Attached the picture of the first boot

[Carolin Latze (carolin-latze)]

and the second (failing) boot

[Carolin Latze (carolin-latze)]

I don't know whether it is relevant, but I ran an apt-get update / apt-get upgrade today and since then I cannot boot anymore at all on the newer kernels. I always see the messages now that you see on the images. The only kernel I was able to boot, is "4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux". I guess it has something to do with Ubuntu updates that is not aware of the newer kernels, but still I thought, I better mention it.

Those were the packages that I updated today:
2015-12-10 09:28:18 install libaudio2:amd64 1.9.4-3 1.9.4-3
2015-12-10 09:28:18 install libgsoap7:amd64 <none> 2.8.22-1
2015-12-10 09:28:18 install libmysqlclient18:amd64 5.6.27-0ubuntu1 5.6.27-0ubuntu1
2015-12-10 09:28:19 install dkms:all <none> 2.2.0.3-2ubuntu6.1
2015-12-10 09:28:19 install libqt4-network:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8
2015-12-10 09:28:19 install libqt4-script:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8
2015-12-10 09:28:20 install libqt4-sql:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8
2015-12-10 09:28:20 install libqt4-xmlpatterns:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8
2015-12-10 09:28:20 install libqtgui4:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8
2015-12-10 09:28:21 install libqt4-declarative:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8
2015-12-10 09:28:22 install libqt4-opengl:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8
2015-12-10 09:28:22 install libqt4-sql-mysql:amd64 <none> 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8
2015-12-10 09:28:22 install libvncserver1:amd64 <none> 0.9.10+dfsg-3
2015-12-10 09:28:22 install virtualbox-dkms:all <none> 5.0.10-dfsg-2ubuntu1
2015-12-10 09:28:23 install virtualbox:amd64 <none> 5.0.10-dfsg-2ubuntu1
2015-12-10 09:28:25 install virtualbox-qt:amd64 <none> 5.0.10-dfsg-2ubuntu1

[penalvch (penalvch)]

Carolin Latze, that's going to be a different problem, not scoped under this report. Hence, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Carolin Latze (carolin-latze)]

I think this second issue is somehow related to virtualbox. Will file a bug once I have more data points. The first problem remains though. Any news about this?

[penalvch (penalvch)]

Carolin Latze, it's best to continue testing the latest mainline kernel (now 4.4-rc5) as they come out, in order to quickly identify a candidate for backporting. Could you please test this and advise to the results?

[Carolin Latze (carolin-latze)]

Booting is more reliable now. I did not see a freeze during boot yet. (kernel runs for 4 days now). However I still see freezes while running

[penalvch (penalvch)]

Carolin Latze:
>"I did not see a freeze during boot yet."

Staying focused to this, how many boots did you attempt? We would want to ensure this is robust across a reasonable number of boots so it's not improved but less intermittent.

[Carolin Latze (carolin-latze)]

Ok, I will try to boot and reboot more often. I did it now around 10 times and it always came up perfectly. With the other kernels, it would not boot in 1 out of 3 tries at least.

[Carolin Latze (carolin-latze)]

No luck. Again crash during boot. Right after "Started initializing hardware monitoring sensors" . :( I was not able to boot any Linux kernel following that crash. (tried 3-4 different versions down to 3.19.). So I booted into Windows, and rebooted again into 4.4. That worked.

[penalvch (penalvch)]

Carolin Latze, could you please update your test to 4.5-rc1 and advise to this?

[Carolin Latze (carolin-latze)]

failed after the 3rd boot. following that crash, I booted into windows, but that did not help this time. tried 4.4 - did not boot. Now I am back on 3.19 for today.

[penalvch (penalvch)]

Carolin Latze, as a potential WORKAROUND, could you please add the following kernel boot parameter and advise to the results:
libata.force=noncq,1.5G

[Carolin Latze (carolin-latze)]

done. will keep you posted

[Carolin Latze (carolin-latze)]

no luck. after about the 5th boot, it crashed again during boot.

Not sure that is relevant: it happened after I booted into Windows. It was a cold boot, no reboot.

[penalvch (penalvch)]

Carolin Latze, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (Hans de Goede and Tejun Heo, CC linux-ide)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.