Kernel crash when booting laptop with hdmi monitor connected

[Sandy Patterson]

When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port, it usually shows only a blank screen after grub and I have to hard power off the laptop. The issue is present when the bios and grub are in mirror mode to both screens. I can see the following stack trace in journalctl:

syslog contains:
 kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq LA2405wg connected via HDMI-to-DVI adapter.

WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen shows up.

WORKAROUND2: Remove "splash" from kernel command line parameters by editing /etc/default/grub file.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 17:22:20 2018
InstallationDate: Installed on 2018-04-28 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see the same issue although the system now randomly crashes later on.
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: apatterson 1965 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
InstallationDate: Installed on 2018-04-28 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Inspiron 7559
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015"
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-20-generic N/A
 linux-backports-modules-4.15.0-20-generic N/A
 linux-firmware 1.173
Tags: bionic wayland-session
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 09/26/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.5
dmi.board.name: 0H0CC0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7559
dmi.product.version: 1.2.5
dmi.sys.vendor: Dell Inc.

[Sandy Patterson (xandey)]

syslog stack trace

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1768139

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.

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

apport information

[Sandy Patterson (xandey)]

I also confirmed the issue still persists as I captured the apport data.

[penalvch (penalvch)]

Sandy Patterson, please address all of the following:

1. Is this something that started to happen after an update? If so, which and when precisely?

2. In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

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 mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible 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 the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, 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.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[Sandy Patterson (xandey)]

1) This started when I did a clean install of 18.04. I was running 17.10 on the same hardware with the same kernel parameters (the "acpi_osi=!Windows 2015"). I'm afraid I can't tell you which kernel exactly, but I keep things up to date. I upgraded a few days before this report. I think it was release day actually.

2) This issue appears fixed in mainline.
4.17.0-041700rc6-generic #201805202330 SMP Sun May 20 23:31:40 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Sandy Patterson, the next step is to fully reverse commit bisect from kernel 4.15 to 4.17-rc7 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit from a kernel version bisect is not fully commit bisecting.

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

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.

[Sandy Patterson (xandey)]

penalvch, I'm having a bit of trouble. Is there instructions on building the ubuntu kernel from git? I wasn't able to find a mainline kernel which fails.

[penalvch (penalvch)]

Sandy Patterson:

>"penalvch, I'm having a bit of trouble. Is there instructions on building the ubuntu kernel from git?"

Yes, the instructions previously provided.

>"I wasn't able to find a mainline kernel which fails."

Without providing which kernels you tested nobody may understand why this happened.

[Sandy Patterson (xandey)]

Christopher Penalver:

> Without providing which kernels you tested nobody may understand why this happened.
I hadn't finished my testing. But i did test some of the mainline kernels below. I'm not certain that I installed them correctly. I was hoping to get the ubuntu kernels to build to see if I could get a negative result to confirm I'm testing properly.
linux-image-4.15.0-041500-generic (no hdmi problem)
linux-image-4.15.3-041503-generic (no hdmi problem)
linux-image-4.15.18-041518-generic (no hdmi problem)

> Yes, the instructions previously provided.
I went to https://wiki.ubuntu.com/Kernel/KernelBisection
I then went to https://launchpad.net/ubuntu/bionic/+source/linux in an attempt to install previously built kernels, and installed the packages matching the pattern
linux-headers-4.13.0-17-generic_4.13.0-17.20_amd64.deb (685.9 KiB)
linux-headers-4.13.0-17_4.13.0-17.20_all.deb (10.4 MiB)
linux-image-4.13.0-17-generic_4.13.0-17.20_amd64.deb (19.9 MiB)
once I booted this kernel the system didn't modeswitch on bootup. It didn't crash, but I dont' think it was a proper test.

Finally I attempted to build from source directly (perhaps I didn't have modules for the kernel version?)

I checked out from git: git clone git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git

Now I attempted to follow the linked wiki page from KernelBisection
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

* sudo apt-get build-dep linux-image-$(uname -r) # this didn't work until I enabled the source repos
* I have tried adding something like "+test1" to the chanelog in debian.master
* I also had to install libusb-dev and libpci-dev perhaps this had something to do with me installing bionic using new minimal install option.

I then did
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic binary-perarch
(which takes 45 minutes)

but I only get the ../*_all.deb file.

Also, should there be modules files?

Sorry for the long post. I figured I had missed some instructions, thats why i asked first.

[Sandy Patterson (xandey)]

I also found the mapping between ubuntu versions and mainline versions and so tried mainline linux-image-4.15.17-041517-generic which also did not exhibit the issue.

[penalvch (penalvch)]

Sandy Patterson a few follow up questions:

1) Does the OS crash consistently if you boot up with the external monitor plugged in, or does it only happen sometimes? If sometimes, how often specifically?

2) Does the OS crash if you connect the external monitor after fully booting up and logging in?

3) As per the sticker of the monitor itself (not from the Bug Description, or the result of a terminal command), could you please provide the full manufacturer and model?

4) Are you using any dongles/converters between the computer and monitor?

[Sandy Patterson (xandey)]

re building. I think i've gotten it building. "time fakeroot debian/rules binary" takes a long time, but seems to be working

re your questions:
1) it's consistent. only when booting right after grub I get a kernel crash. Every time when my monitor is connected via the HDMI connector on my laptop.

2) no, i can connect the monitor as soon as I see the ubuntu loading screen and use it no problem. I can also connect monitors after logging in. Also, cold boot reboot doesn't seem to matter.

3) I have tried two monitors,

at work right now:
Dell UltraSharp U2515H 25" 6ms WQHD Widescreen LED Backlight LCD Monitor IPS panel 350 cd/m2, HDMI/MHL, DisplayPort, USB3.0Hub, Height&Pivot adjustable
(connect via straight hdmi cable)

at home:
HP Compaq LA2405wg - connect via hdmi - dvi adapter + dvi cable

4) see above

PS still working on that bisect.

[Sandy Patterson (xandey)]

Small update. I've gone back to try and see what I can learn from installing pre-built kernels:

1) for some reason when I reboot sometimes I see the grub screen in mirror mode and sometimes one monitor is blank. This issue happens whenever grub is mirrored between both monitors. It is always mirrored on cold boots.

2) I went back to older ubuntu kernel versions. (https://launchpad.net/ubuntu/bionic/+source/linux)

I can confirm that the issue persists as far back as 4.15.0-18.19.

I attempted 4.15.0-17.18, but the build files here: (https://launchpad.net/ubuntu/+source/linux/4.15.0-17.18, https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+build/14768117) do not include linux-modules-* and linux-modules-extra-*, and when I don't install those the monitor doesn't seem to be detected and there is no modeswitch after grub.

I then went back to 4.15.0-18.17 and uninstalled linux-modules-extra-4.15.0-18.17 and found the same no monitor modeswitch problem.

I will attempt to build 4.15.0-17.18 myself and see if I can get the modules to build and properly test, but this is very slow going at this point. Please let me know if there is another way to test that doesn't involve long builds.

[penalvch (penalvch)]

Sandy Patterson:

Regarding 4.15.0-17.18 not having linux-modules-* here are a couple options:

1) Test the next oldest version until you can do a proper test.

2) Contact the Ubuntu Kernel Team via https://wiki.ubuntu.com/KernelTeam and inquire if the linux-modules-* can be provided for that version.

[Sandy Patterson (xandey)]

Christopher Penalver:

I figured out the modules thing. It seems older kernels don't have separate debs for the modules. I needed the extra package regardless (if both linux-modules-extra and linux-image-extra were missing I don't think the test is right).

I went back further:
4.14.0-16-generic_4.14.0-16.19 - is GOOD, no issue
4.15.0-9-generic 4.15.0-9.10 - is bad

I'm confirming my build system which has gotten me a few builds, and I'm starting in on the bisect.

[penalvch (penalvch)]

Sandy Patterson:

>"I figured out the modules thing. It seems older kernels don't have separate debs for the modules. I needed the extra package regardless (if both linux-modules-extra and linux-image-extra were missing I don't think the test is right)."

To clarify, you were able to test 4.15.0-17.18 successfully?

>"I went back further: 4.14.0-16-generic_4.14.0-16.19 - is GOOD, no issue 4.15.0-9-generic 4.15.0-9.10 - is bad I'm confirming my build system which has gotten me a few builds, and I'm starting in on the bisect."

To advise, you are performing a reverse bisect. Hence, you are looking for the next most recent kernel after 4.15.0-9-generic 4.15.0-9.10 where it is working.

[Sandy Patterson (xandey)]

Christopher Penalver:

>"To clarify, you were able to test 4.15.0-17.18 successfully?"

Yes. I was able to test 4.15.0-17.18 which exhibited the issue.

>"To advise, you are performing a reverse bisect. Hence, you are looking for the next most recent kernel after 4.15.0-9-generic 4.15.0-9.10 where it is working."

Exactly. Some of these kernel builds are asking me to select kernelconfig options. I think the tests are still valid though. I'm trying to confirm my starting commits for the bisect before I use git to do it.

[penalvch (penalvch)]

Sandy Patterson, a couple follow ups:

1) Regarding kernel parameter acpi_osi=!Windows 2015 could you please advise why you need to use it, if at all? If you don't, you will want to remove it during your bisect tests to mimic a default install.

2) Regarding your Bug Description change, you change "consistently" to "it usually shows". Is this because it doesn't always cause a blank screen? If so, could you advise an approximate number (ex. 9/10 boots)?

[Sandy Patterson (xandey)]

Christopher Penalver:

1) I removed the kernel parameters and I am getting the same behavior. I'll leave it off, I had to set it to boot the live cd. There is a bug report somewhere where I found this workaround. It seems to work now, perhaps this acpi problem has been fixed.

2) I'd say probably 9/10 boots. I only saw it boot OK twice where I saw the bios load in mirror mode and then boot fine. Initially it tripped me up thinking that the new kernel version installed had fixed things, but when I repeated the test it failed again. I just did 5 in a row with 4.15.0-22 that all exhibited the issue. I guess i haven't figured out the cause of this occasional working behavior yet.

3) I'm stalled out on kernel builds for the moment. I got back to d4814b5f3812ca78b9a21af3189caeec0181187e in ubuntu-bionic repository (this commit did exhibit the issue), it had to change some of the config options during the build... I guess this happens during the experimental phase? I then tried 2c21160b4023c7f38e5c4fc3cf472efe85a052d5 which made me change a lot more config options during the build and then failed to build. I can try a few more commits perahps it was a temporary build failure. Seems odd that they'd tag a build that didn't compile. Maybe it was rebased and never tested? I'll see if I can contact the kernel guys and ask for some help.

basically I can't start the rebase because I can't find a commit which will build and doesn't exhibit the issue.

[Sandy Patterson (xandey)]

Few final comments on the work I did to narrow this:

* Issue is present in ubuntu but not in mainline (4.15.17 I think is closest? I have tried a bunch though 4.15.0, 4.15.18, 4.15.16...)
* I compiled mainline kernel 4.15.17 from linux-stable with ubuntu config from /boot/config-4.15.0-22-generic, that did not show issue.
* I attempted to go backwards in ubuntu-bionic git history and made it back to 4.15.0-1_4.15.0-1.2 which was the last build that succeeded for me. This exhibited the issue.

Let me know if I can do any more testing.

[penalvch (penalvch)]

Sandy Patterson:

>"Let me know if I can do any more testing."

Please reach out to the Ubuntu Kernel team via https://wiki.ubuntu.com/KernelTeam for testing build requests that revert the offending commit(s)/apply the fix commit(s).

[Joshua R. Poulson (jrp)]

Have you tried it with this patch backed out?

http://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/drivers/gpu?id=3fd668d6f93978f0b67264ab6a99d5f801cbd9b0

[Sandy Patterson (xandey)]

Joshua R. Poulson:

I will try reverting that patch, but I see the same behavior in Ubuntu-4.15.0-9.10 which I believe is before that commit.

[Sandy Patterson (xandey)]

I got some help from #ubuntu-kernel Thadeu Cascardo suggested I try drm.debug=0x4

The crash seems to happen every time when the laptop has been off for a while, but sometimes it doesn't if I power it down then bootup. So I captured two logs attached, one where the system booted normally, and one where it crashed.

[Timo Aaltonen (tjaalton)]

note that d4814b5f3812ca7 is not the same as building off 'Ubuntu-4.15.0-1.2' -tag, which you can find here:
lp:~ubuntu-kernel/ubuntu/+source/linux/+git/unstable

d4814b5f3812ca7 is actually based on v4.15 with the packaging and SAUCE from -1.2 added on top.

There is no diff to drm/i915 in the distro kernel compared to upstream which would explain this.. So I assume you just haven't hit racy bug with mainline builds yet? Try newer versions too, 4.16 and 4.17.

[Timo Aaltonen (tjaalton)]

the diff between the working an non-working case is this on the working one:
May 31 11:37:08 exposure kernel: [drm:intel_dp_dual_mode_set_tmds_output [i915]] Enabling DP dual mode adaptor TMDS output

but even the crashing one seems to detect that correctly
May 31 11:59:32 exposure kernel: [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode adaptor ID: a0 (err 0)

but then for some reason fails the check in intel_dp_dual_mode_set_tmds_output()

[Sandy Patterson (xandey)]

Timo Aaltonen:

I had tested rc7 I think for 4.17. I'm attaching the dmesg from startup using 4.17.0 with drm.debug=0x4 too (I just tried 4.17.0).

I'll start on the unstable repo, It'll take a few days probably as I haven't figured out how to do a really incremental build. Please let me know if you think this won't be helpful but I assume it would be of value.

[Sandy Patterson (xandey)]

Using the lp:~ubuntu-kernel/ubuntu/+source/linux/+git/unstable repository, I was able to narrow the issue down to between two tags: Ubuntu-4.15.0-0 (issue present) and Ubuntu-4.14.0-17.20 (ubuntu-bionic, no issue present). I also tried Ubuntu-4.14.0-11.13 from the unstable branch which doesn't have the issue.

I tried bisecting in unstable, but as soon as I got a few commits back from Ubuntu-4.15.0-0 the build started failing.

[Sandy Patterson (xandey)]

bisect result: lp:~ubuntu-kernel/ubuntu/+source/linux/+git/unstable shows this commit.

I built using the mainline config-4.15.0-041500rc2-generic file and accepted default options. I also had to apply ff6fa2d396b0476988c749664f600b1e177bcf9b in order to get the neighboring commits to build.

it does appear to stop the flicker, but also seems to cause the boot failure.

commit 77a113c1ac1458856ca8e82a9046efff8ca87f09
Author: Andy Whitcroft <email address hidden>
Date: Wed Apr 16 19:40:57 2014 +0100

    UBUNTU: SAUCE: vt -- maintain bootloader screen mode and content until vt switch

    Introduce a new VT mode KD_TRANSPARENT which endevours to leave the current
    content of the framebuffer untouched. This allows the bootloader to insert
    a graphical splash and have the kernel maintain it until the OS splash
    can take over. When we finally switch away (either through programs like
    plymouth or manually) the content is lost and the VT reverts to text mode.

    BugLink: http://bugs.launchpad.net/bugs/1308685
    Signed-off-by: Andy Whitcroft <email address hidden>

:040000 040000 b0f28f7ecaeaf8037832299ee421886dcd9dfc25 3e051b4e05da82a1184bdb45a71d3317e8c74445 M drivers
:040000 040000 22bdb68e3e9757318cf57f010231c1af7db61cc1 ce199b29dcc261c74b4b2cdfd26dc3993ecbd970 M include

[Sandy Patterson (xandey)]

I also built ubuntu-bionic: Ubuntu-4.15.0-23.25 reverting d8a077b6271ef3d7620f0e95d4a343ec1661fe5d (which is the same commit in the ubuntu-bionic repo).

I see that there is a brief text terminal between grub and the ubuntu loading screen, but at least it seems to boot reliably with a second monitor connected.

Maybe there is another way to have a pretty boot process with the newer kernels?

[Kai-Heng Feng (kaihengfeng)]

Does this issue still happens on latest Ubuntu kernel?

[Sandy Patterson (xandey)]

Kai-Heng Feng,

Yes it does. I just confirmed the issue is still present in 4.15.0-34-generic. I also upgraded my bios to the latest 1.2.8. See attached syslog which contains backtrace. I don't notice any difference.

I was also able to find another workaround by removing "splash" from the kernel command line. Which I found from the above mentioned commit.

[Sandy Patterson (xandey)]

Kai-Heng Feng,

I also found the problem commit but I'm not sure how to properly tag this bug report.

[Kai-Heng Feng (kaihengfeng)]

Ok, that patch is for LP: #1308685.

Not sure if this patch is still necessary, so subscribing Andy...

[Kai-Heng Feng (kaihengfeng)]

I'll work on this when I find some time.

In the meantime, can you try Cosmic live USB/CD? It uses 4.18 kernel.

[Kai-Heng Feng (kaihengfeng)]

You can download it here: http://cdimages.ubuntu.com/daily-live/current/

[Sandy Patterson (xandey)]

Kai-Heng Feng: I am working on testing with cosmic. I think I need some time though. I can't figure out how to change the grub menu in the usb live image. I need to add apci_osi='!Windows 2015" and I think my typing screws with the startup timing. Do you know of a way to change the grub config on the live image? Do i need to make my own?

I did boot twice manually changing this option, I'll try more tonight.

[Sandy Patterson (xandey)]

Kai-Heng Feng: I did some more testing and I don't see the problem in the cosmic proposed kernel 4.18.0-9.10.
1) the live CD appeared to boot fine, but I didn't totally trust the test procedure.
2) I installed cosmic 4.18.0-9.10 from https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+build/15513541 and then booted the same way. This also booted fine with splash enabled.
3) I confirmed that booting the current release for bionic still caused the problem: 4.15.0-36

I also thought perhaps i was missing some module which caused the problem, but I confirmed that noveau is getting loaded in both cases.

[You-Sheng Yang (vicamo)]

Tried following kernel versions with system upgraded w/ or w/o nvidia-driver-390 (version 390.116-0ubuntu0.18.04.1) installed. Booting with HDMI cable connected doesn't have any problem for X, and I got dual screen working as expected.

* 4.15.0-1035-oem
* 4.15.0-20-generic
* 4.15.0-36-generic
* 4.15.0-47-generic
* 4.18.0-15-generic
* 4.18.0-18-generic

I'm closing this as INVALID. Should there be any further finding, please don't hesitate to reopen it.