Rod B., the next step is to fully reverse commit bisect from kernel 4.4
to 4.16 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
I discovered that reducing the BIOS setting for DVMT Pre-Allocated
Memory below 512M gets around the bug. IE: The three problem kernels
listed in this report will boot if DVMT Pre-Allocated is set less then
512M. As mentioned in this report kernels 4.4.0-116 and before worked
fine with DVMT
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1767360
Title:
16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-
Used kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/
It boots/works.
Added tag and changed status as requested. 1st time Launchpad user so hope I
did it correctly.
Thanks for the help.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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
6 matches
Mail list logo
