** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1742721
Title:
linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic
fail to boot
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
In Progress
Bug description:
== SRU Justification ==
The following mainline commit introduced a regression in v4.11-rc1:
c075b6f2d357ea9 ("staging: sm750fb: Replace POKE32 and PEEK32 by inline
functions")
This regression caused the bug reporters system to crash and exhibited no
display
output.
A "Reverse" bisect was performed and it was found that this regression is
fixed by commit 16808dcf605e6, which was added to mainline in v4.15-rc1.
== Fix ==
commit 16808dcf605e6302319a8c3266789b76d4c0983b
Author: Huacai Chen <che...@lemote.com>
Date: Mon Nov 6 08:43:03 2017 +0800
staging: sm750fb: Fix parameter mistake in poke32
== Regression Potential ==
Low. This patch fixes a current regression. It was cc'd to upstream stable
so had additional upstream review.
## Original Bug Description#
I've updated the machine to the linux-hwe kernels, and experienced an almost
instant crash when booting. Nothing is shown on the VGA output, so no stack
traces are available.
I've tried booting a few kernels with the following results:
- linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up
fine
- linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic: fails
to boot
- linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
- linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic: fails
to boot
- linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic: boots
up fine
After that I've tried some mainline kernels from
http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem
is the upstream or ubuntu patches:
- linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb:
boots up fine
- linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb:
fails to boot
- linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb:
boots up fine
- linux-image-4.13.14-041314-generic_4.13.14-041314.201711180632_amd64.deb:
fails to boot
- linux-image-4.13.15-041315-generic_4.13.15-041315.201711211030_amd64.deb:
boots up fine
So, it seems, the problem is fixed either in patches between 4.13.14
and 4.13.15 upstream, or ubuntu configs/patches applied to mainline
kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742721/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
