Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel

Bug #1813795 reported by Ryan Budney
72
This bug affects 16 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have a Dell 5290 2-in-1 tablet that has been running Ubuntu 18.04 successfully for several months. Today I upgraded the kernel from 4.15.0-43 to 4.15.0-44. The tablet functions normally until it is plugged into its docking station, then the screen freezes.

Technically, the screen flickers a few times, then goes blank, leaving only the frozen mouse pointer. The system is still running, though as I can ssh into my tablet. sudo reboot will not reboot the tablet, but sudo reboot -f will.

When I force the tablet to load 4.15.0-43, the tablet functions normally. i.e. even when I plug it into its docking station, it continues to perform properly. It's only with 4.15.0-44 that it freezes.

As you can see from the linked question and forum thread, this appears to be affecting many Dell tablets and laptops. It also appears clear that the bug is not present in 4.15.0-43.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rybu 1971 F.... pulseaudio
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=35ab6535-9677-4ec9-9b70-33d75778947f
InstallationDate: Installed on 2018-11-09 (81 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Latitude 5290 2-in-1
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-44-generic N/A
 linux-backports-modules-4.15.0-44-generic N/A
 linux-firmware 1.173.3
Tags: bionic
Uname: Linux 4.15.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 08/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.3
dmi.board.name: 0M27Y3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 32
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.4.3:bd08/27/2018:svnDellInc.:pnLatitude52902-in-1:pvr:rvnDellInc.:rn0M27Y3:rvrA00:cvnDellInc.:ct32:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5290 2-in-1
dmi.sys.vendor: Dell Inc.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/1813795/+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.]

tags: added: bot-comment
Revision history for this message
Ryan Budney (delooper) wrote :

Forum thread:

https://askubuntu.com/questions/1113743/after-most-recent-kernel-update-4-15-0-44-generic-my-tablet-freezes-whenever-p

Launchpad question:

https://answers.launchpad.net/ubuntu/+question/678174

Let me know if there are any things I should look for in log files. Would be happy to include them, but not certain what to look for. Should be easy to find as I can log into the frozen tablet by ssh.

Paul White (paulw2u)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1813795

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
Revision history for this message
Ryan Budney (delooper) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic
description: updated
Revision history for this message
Ryan Budney (delooper) wrote : CRDA.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : IwConfig.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : Lspci.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : Lsusb.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : ProcModules.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : PulseList.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : RfKill.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : UdevDb.txt

apport information

Revision history for this message
Ryan Budney (delooper) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Corben (tobias-krummen) wrote :

Looks like I'm affected by this issue with my Surface Pro 3 too.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813796

Revision history for this message
Dag Blakstad (dag-blakstad) wrote :

After updating to 4.15.0-44-generic it is not possible to unlock when docked (Thinkpad X1 Carbon 4th gen). Blank (black screen) and not possible to switch to another console. Sometimes a frozen mouse pointer is the only thing shown after boot.

Revision history for this message
Adar Malik (adarmalik) wrote :

I have an Lenovo T470s with current NEON (Ubuntu 18.04 based) with the same problem. If I disconnect it from the docking station it freezes.
After reverting back to the 4.15.0.43 kernel the issue is gone.

Revision history for this message
Jérôme Steunou (jsteunou) wrote :

I have the same issue with a Dell Vostro & business dock WD15

4.15.0-43 works well, I saved that choice on GRUB to be safe.

Dell Vostro
Intel® Core™ i5-8250U CPU @ 1.60GHz × 8
Intel® UHD Graphics 620 (Kabylake GT2)

Revision history for this message
limod (limod) wrote :

I have the same issue with a Thinkpad T440p. My external monitors connected via the dockingstation remain black after booting and also after i lock my computer. The internal monitor works for booting, but as soon as i lock my computer, it also remains black.

No issues with 4.15.0-43

Revision history for this message
andyczerwonka (andy-czerwonka) wrote :

Delll 5530 and the TB16. Works great with 4.15.0-43, freezes with 4.15.0-44. Had to revert.

Revision history for this message
rathboma (beekeeper-studio) wrote :

Same as limod using a Thinkpad X1 Carbon 5th gen. Totally freezes the system actually, doesn't just blackout the monitors. Nothing responds.

Also happens with 4.15.0-45

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.