Kernel 3.19.0-58 freezes Ubuntu 14.04 on Dell XPS 15 9530

[V B]

The latest security patch for 3.19.0 for Ubuntu 14.04 started freezing my laptop (Dell Inc. XPS 15 9530). All the patches before this one for the kernel 3.19.0 for Ubuntu 14.04 were OK. From log, the last message before freezing was "kernel: ...[drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling", as you can see below:

Apr 6 14:46:17 xxx-ubuntu dbus[1001]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper)
Apr 6 14:46:17 xxx-ubuntu dbus[1001]: [system] Successfully activated service 'org.freedesktop.hostname1'
Apr 6 14:46:17 xxx-ubuntu kernel: [ 945.147481] systemd-hostnamed[11982]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Plea
se install nss-myhostname!
Apr 6 14:50:36 xxx-ubuntu sudo: pam_ecryptfs: pam_sm_authenticate: /home/xxx is already mounted
Apr 6 15:00:01 xxx-ubuntu CRON[12829]: (root) CMD (if [ -x /usr/sbin/backupninja ]; then /usr/sbin/backupninja; fi)
Apr 6 15:02:29 xxx-ubuntu kernel: [ 1916.954839] sound hdaudioC0D0: HDMI: ELD buf size is 0, force 128
Apr 6 15:02:29 xxx-ubuntu kernel: [ 1916.954877] sound hdaudioC0D0: HDMI: invalid ELD data byte 0
Apr 6 15:07:35 xxx-ubuntu kernel: [ 2222.796696] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling

This is the same symptom as described in the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552333, which is a bug raised for 4.2 kernel running on Ubuntu 14.04 using the same laptop and the same Ubuntu installation as for this bug.

At the moment I switched back to kernel 3.19.0-51 that does not cause this problem, but the possibility that from now on all future security patches for 3.19.0 might freeze my laptop sounds very bad.
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: valentinbrasov 3187 F.... pulseaudio
 /dev/snd/controlC2: valentinbrasov 3187 F.... pulseaudio
 /dev/snd/controlC0: valentinbrasov 3187 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (192 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Dell Inc. XPS 15 9530
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash crashkernel=384M-:128M vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-51-generic N/A
 linux-backports-modules-3.19.0-51-generic N/A
 linux-firmware 1.127.20
Tags: trusty
Uname: Linux 3.19.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/30/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: XPS 15 9530
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 15 9530
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.

[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 1567237

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.

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

apport information

[V B (valentin-brasov)]

I did run "apport-collect 1567237" and went through the "Authorize application to access Launchpad on your behalf" page and allowed it, then a screen popped up asking to send some info and I accepted it. At the end I saw in the console as last message:

dpkg-query: no packages found matching linux

However I did run the apport-collect command AFTER switching back to 3.19.0-51-generic, which does not freeze the laptop. In fact, I have been using the 3.19.0 kernel on Ubuntu 14.04 and installing all the incoming patches for that kernel for many months and it NEVER FROZE my laptop until I installed and started using the 3.19.0-58 patch.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt19-vivid/

[V B (valentin-brasov)]

Hi Joseph,

Sorry to answer so late, but I am very busy for a while in the office. That is why I cannot try that yet. In a few days I hope to be less busy and then I will try that and let you know the result.

Cheers,
V

[V B (valentin-brasov)]

I just installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt19-vivid/ the following:

linux-image-3.19.8-031908ckt19-generic_3.19.8-031908ckt19.201604151431_amd64.deb
linux-headers-3.19.8-031908ckt19-generic_3.19.8-031908ckt19.201604151431_amd64.deb
linux-headers-3.19.8-031908ckt19_3.19.8-031908ckt19.201604151431_all.deb

as described in https://wiki.ubuntu.com/KernelMainlineBuilds. Then I booted using that kernel and the problem still happens. Here is what I saw in the syslog around the freezing moment (the log shows the moments up to the freeze and the reboot that I triggered afterwards by pressing the power button for 5 secs):

Apr 21 10:53:04 my-ubuntu NetworkManager[1402]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Apr 21 10:53:48 my-ubuntu kernel: [ 79.996117] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B
Apr 21 10:53:48 my-ubuntu kernel: [ 79.996140] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
Apr 21 10:54:44 my-ubuntu dnsmasq[1957]: reading /etc/resolv.conf
Apr 21 10:54:44 my-ubuntu dnsmasq[1957]: using nameserver 127.0.1.1#53
Apr 21 10:58:23 my-ubuntu kernel: [ 355.430721] usb 2-2: USB disconnect, device number 2
Apr 21 11:00:01 my-ubuntu CRON[4139]: (root) CMD (if [ -x /usr/sbin/backupninja ]; then /usr/sbin/backupninja; fi)
Apr 21 11:00:08 my-ubuntu kernel: [ 459.955933] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling
Apr 21 11:18:06 my-ubuntu rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="712" x-info="http://www.rsyslog.com"] start
Apr 21 11:18:06 my-ubuntu rsyslogd: rsyslogd's groupid changed to 104
Apr 21 11:18:06 my-ubuntu rsyslogd: rsyslogd's userid changed to 101
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpuset
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpu
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] Linux version 3.19.0-51-generic (buildd@lgw01-44) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1) ) #58~14.04.1-Ubuntu SMP Fri Feb 26 22:02:58 UTC 2016 (Ubuntu 3.19.0-51
.58~14.04.1-generic 3.19.8-ckt13)
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash crashkernel=384M-:128M vt.handoff=7
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] KERNEL supported cpus:
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] Intel GenuineIntel
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] AMD AuthenticAMD
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] Centaur CentaurHauls
Apr 21 11:18:06 my-ubuntu kernel: [ 0.000000] e820: BIOS-provided physical RAM map:

So it froze at 11:00:08, while I was away from my desk, then at 11:18:06, when I came back to my desk I had to restart it by pressing long the power button.

[V B (valentin-brasov)]

However there is something that is very worrying about marking this bug as duplicate of the one for 4.2 kernel: the other bug was marked as medium importance because I always could use the 3.19 series of kernels to get security patches. But now that the 3.19 series of kernels also got broken, I am left with no good option to further get security patches. I could downgrade to 3.16 series of kernels to see if that series is still OK, but I do not want to do that. I would rather switch to another operating system rather that downgrade my kernel lower than 3.19. That is why I do not agree that this bug will not be looked at and the other one (for 4.2 kernels) is less important. Could you change this the other way around: make the other bug a duplicate of this one and keep this one opened with its higher importance and focus on this one? I think that would make it also easier to figure out what got broken: by looking at the changes between 3.19.0-51 kernel (which works) and 3.19.0-58 kernel (which doesn't) it should be easier to figure out what is the problem than by comparing 3.19.0-51 kernel with a 4.2 kernel.

[V B (valentin-brasov)]

Hi,

I installed today (pushed by the software update) the kernel 3.19.0-59 and I got the same problem with it. Here is the part of the syslog around the freezing point:

May 10 11:44:27 my-ubuntu wpa_supplicant[1311]: wlan0: CTRL-EVENT-CONNECTED - Connection to 02:18:5a:8f:fe:13 completed [id=0 id_str=]
May 10 11:44:27 my-ubuntu NetworkManager[1258]: <info> (wlan0): supplicant interface state: associated -> completed
May 10 11:44:27 my-ubuntu NetworkManager[1258]: <info> (wlan0): roamed from BSSID 02:18:4A:8F:FC:B3 (FD_Staff) to 02:18:5A:8F:FE:13 (FD_Staff)
May 10 11:44:42 my-ubuntu wpa_supplicant[1311]: wlan0: CTRL-EVENT-SCAN-STARTED
May 10 11:50:36 my-ubuntu kernel: [ 2724.303310] sound hdaudioC0D0: HDMI: ELD buf size is 0, force 128
May 10 11:50:36 my-ubuntu kernel: [ 2724.303348] sound hdaudioC0D0: HDMI: invalid ELD data byte 0
May 10 11:55:42 my-ubuntu kernel: [ 3030.170491] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling
May 10 12:32:31 my-ubuntu rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="1099" x-info="http://www.rsyslog.com"] start
May 10 12:32:31 my-ubuntu rsyslogd: rsyslogd's groupid changed to 104
May 10 12:32:31 my-ubuntu rsyslogd: rsyslogd's userid changed to 101
May 10 12:32:31 my-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpuset
May 10 12:32:31 my-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpu

So you can see in the above log fragment the last line before freezing:

May 10 11:55:42 my-ubuntu kernel: [ 3030.170491] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling

I also tried the 4.2.0-36 kernel that was pushed today (for the duplicate bug) and got the same problem:

May 10 09:17:01 my-ubuntu CRON[6013]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 10 09:36:50 my-ubuntu compiz: pam_ecryptfs: seteuid error
May 10 10:00:01 my-ubuntu CRON[7191]: (root) CMD (if [ -x /usr/sbin/backupninja ]; then /usr/sbin/backupninja; fi)
May 10 10:06:44 my-ubuntu kernel: [ 7264.163450] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling
May 10 10:35:57 my-ubuntu rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="986" x-info="http://www.rsyslog.com"] start
May 10 10:35:57 my-ubuntu rsyslogd: rsyslogd's groupid changed to 104
May 10 10:35:57 my-ubuntu rsyslogd: rsyslogd's userid changed to 101
May 10 10:35:57 my-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpuset

May I please ask of a status update, please? When will this bug be fixed? Has anybody tried to look at the changes between the kernels 3.19.0-58 and 3.19.0-51 and try to figure out why is this problem happening? If so, may I please at least get a clarification here about the cause?

Because at the moment I am unable to install anymore any security patched kernels that you guys are pushing.

Thank you.

[penalvch (penalvch)]

V B, could you please test the latest mainline kernel (4.7-rc1) and advise to the results?

[V B (valentin-brasov)]

Hi Christopher,

I tried the kernel v4.7-rc2-yakkety and the freezing still happened with the same message in the log before freezing:

Jun 7 10:28:52 my-ubuntu avahi-daemon[826]: Invalid response packet from host fe80::8eae:4cff:feff:1bf2.
Jun 7 11:29:42 my-ubuntu avahi-daemon[826]: Invalid response packet from host fe80::6a5b:35ff:febd:7254.
Jun 7 11:45:15 my-ubuntu compiz: pam_ecryptfs: seteuid error
Jun 7 11:51:40 my-ubuntu avahi-daemon[826]: Invalid response packet from host 192.168.24.110.
Jun 7 11:55:52 my-ubuntu kernel: [101154.754902] [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling

By the way, I have a colleague who runs on the same laptop model as mine Arch Linux with 4.4.5 kernel and he does not get this problem.

[penalvch (penalvch)]

V B, the next step is to fully commit bisect from the last known good kernel to the first identified bad one in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[V B (valentin-brasov)]

Sorry to answer so late, but I was very busy.

I am starting bisecting through the kernel commits taken from git://kernel.ubuntu.com/ubuntu/ubuntu-vivid.git

This will take a while, as I have to use each kernel version that I build up to 2 days in order to make sure that it does not freeze...

[V B (valentin-brasov)]

Trying to build the kernel for the commit 3ee7c0679b1f375ec013c82be13441dab8a69248, I get an error:

    drivers/media/dvb-frontends/drxd : 1
    drivers/mfd/ucb1400_core : 1
    drivers/media/tuners/tda18271 : 1
    drivers/media/dvb-frontends/stv0299 : 1
II: Done
make: *** [abi-check-generic] Error 1

[V B (valentin-brasov)]

Any suggestions or help please for the above error?

[V B (valentin-brasov)]

Marked as "Confirmed" again with the hope doing this will attract somebody's attention and help with my kernel compilation error (while kernel bisecting...).

[penalvch (penalvch)]

V B, if it fails to build, move on to the next kernel bisection point. There isn't support to address fail to builds on EOL, upstream kernels.

[V B (valentin-brasov)]

Hi,

So the breaking commit is somewhere between the "Ubuntu-3.19.0-51.58" tag and the "Ubuntu-3.19.0-53.59" tag. The trouble is that no matter what commit I build between these 2 tags it builds the same kernel version - 3.19.0-51.58 - (no matter what I change at the top of debian.master/changelog - as described in https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel), so after installing what I build, I am not sure whether I am booting the original 3.19.0-51.58 (that works OK) or the one I built through bisecting...

[V B (valentin-brasov)]

So after bisecting more, I could build the commit

[424b84001e19318fa3f6e0fd5941b157ad5583af] drm/radeon: clean up fujitsu quirks

and I think I managed to install the kernel built from it and it seems to work (I mean not freeze my laptop). But after that, I tried a bunch of commits between the commit 424b84001e19318fa3f6e0fd5941b157ad5583af and tag "Ubuntu-3.19.0-53.59", without being able to compile any of them.

[V B (valentin-brasov)]

Hi Christopher,

Any updates on this?

Thank you.

[V B (valentin-brasov)]

I could also build the commit [6957c68d1e9255a31d2d916b6a6451b736460761] "nfs: Fix race in __update_open_stateid()" and I installed the kernel built from it and it does not freeze the laptop. So the commit that triggers the problem must be after the above commit and up to (including) the tag "Ubuntu-3.19.0-53.59".

[V B (valentin-brasov)]

I could also build the commit [16d6150e634786fbe497c0659fbcbf9b543e0204] "NFS: Ensure we revalidate attributes before using execute_ok()" and I installed the kernel built from it and it does not freeze the laptop. So the commit that triggers the problem must be after the this commit and up to (including) the tag "Ubuntu-3.19.0-53.59".

[V B (valentin-brasov)]

Any updates to this problem?

How likely is that I get the same problem if I upgrade my 14.04 LTS system to 16.04 LTS? To me it seems VERY-VERY LIKELY that I will get the freezes. And if the freezes happen, then it is very bad as I cannot install anymore a 3.19.0-51 kernel on 16.04 LTS, that kernel version being the last one that still works on 14.04 LTS without freezes.

Any advice please?

Valentin

[penalvch (penalvch)]

V B, you would want to do two things:
1) Continue bisecting as last discussed on 2016-07-27.
2) To keep this relevant to upstream, continue to test the latest mainline kernel as they are released (now 4.8-rc3).

[V B (valentin-brasov)]

I installed the xenial kernel and that did not freeze my laptop anymore. So after using that xenial kernel for 3 days or so, I decided to upgrade to Ubuntu 16.04 LTS. The upgrade FAILED (while updrading mysql server) and left my laptop unrecoverable (because the entire disk was encrypted and it was not booting anymore either), so I had to wipe my laptop clean and install from scratch Ubuntu 16.04 LTS, which does not freeze my laptop anymore. So much about Ubuntu upgrade process...

[penalvch (penalvch)]

V B, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567237/comments/39 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.