Dell Latitude E7440 crash on lid close (MATE 16.04)

[Ken D'Ambrosio]

Fresh install of 16.04 (installed twice, now -- same issue both times; apt-get update; apt-get dist-upgrade run in both cases, so latest packages). On lid close, system hard freezes, requiring power cycle. On opening lid, is frozen on lockscreen. No mouse movement, no keyboard movement, <ctl><alt><f1> does nothing. Freezes ~80% of the time; occasionally (perhaps related to WiFi not being enabled), it suspends properly.

[Ken D'Ambrosio (ken-jots)]

NOTE: I install to btrfs. I don't imagine that plays a role, but it is something that's probably a differentiator for my system vs. others'.

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

[Brad Figg (brad-figg)]

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

apport-collect 1585462

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.

[Ken D'Ambrosio (ken-jots)]

Hi. Original poster, here. Indeed, I am unable to run that command, as the system is hard frozen, and requires a full power cycle. (<alt><sysrq><b> does nothing, but this appears to be a key mapping issue, so I don't know if the kernel has actually panic, or if the UI is simply 100% crashed.) I did think to add the remainder of the syslog, though:

[Ken D'Ambrosio (ken-jots)]

I killed lightdm and shut the lid from the command prompt. System was largely unresponsive after opening -- I was still able to switch between virtual consoles, but that was *it*; console accepted no input, nor did any of the login prompts. After 120 seconds (I presume), and error about kworker blocking for 120 seconds came up, however nothing else seemed to transpire.

[Ken D'Ambrosio (ken-jots)]

Unsure what has changed; don't recall installing or updating any new packages, or altering any settings after my initial post, but I can't make it crash any more. I'm not outright closing this, as it happened *so many times* that I'm hesitant to call it gone, but neither do I want someone spending resources until I can make it reproducible.

[penalvch (penalvch)]

Ken D'Ambrosio, could you please provide the results requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585462/comments/3 ?

Don't worry about timing it to the crash.

[alekos (alekos)]

I just upgraded to 16.04 and I started having the exact same issue.
I'm attaching my output of apport.

[alekos (alekos)]

Re-attacching output of apport.

[alekos (alekos)]

Interestingly enough, after 2 days of constant crashing, it has now stopped doing it.

[Launchpad Janitor (janitor)]

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