@iLogin That does revert the troublesome commit and mainline at that
commit boots for me.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
** Package changed: linux (Ubuntu) => linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
revert a broken PAT commit that broke a number of systems
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2a025defd804be938f8acffe62e4801a3ed1601
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
** Description changed:
I have an HP Spectre x360 Convertible laptop with an Intel 5500U SoC. In
short, I am completely unable to boot kernel 4.12-rc3, even though I
could boot from 4.12-rc2 perfectly fine. The loading screen does not
appear at all, instead GRUB remains stuck on "Loading i
I am unable to run apport-collect running 4.12-rc3, because I cannot
actually boot my computer (an immediate kernel panic occurs, as
evidenced by adding the output from earlyprintk=efi), so I'm marking
this bug as confirmed. Please also see relevant discussion about this
issue on the Linux Kernel m
It appears a kernel panic is happening immediately while attempting to boot
4.12-rc3, it doesn't happen on 4.12-rc2.
Adding earlyprintk=efi to the grub command line options, I get the following
message (which explains why the bootloader stops at 'loading initial
ramdisk...'):
This was meticulou