Thanks for the suggestion @kaihengfeng. I installed linux-generic-
hwe-16.04-edge, which gave me a working 4.15.0-23-generic after a
reboot.
The log from 4.13.0-45 failed at this point:
[2.444002] DMAR-IR: IOAPIC id 10 under DRHD base 0xdfffe000 IOMMU 0
[2.52] DMAR-IR: IOAPIC id 9
Maybe try the -hwe-edge kernel instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to linux-image-extra-4.13.0-26-generic the system does
not start at all
To
Another data point, 4.13.0-45 crashes on boot even with acpi=off. It
looks like a different call trace though, which I can transcribe on
request if anyone thinks it will help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is a transcription of the latest kernel boot panic.
This is the Oops:
[2.62] BUG: unable to handle kernel NULL pointer dereference at (null)
[2.62] IP: __bitmap_intersects+0x10/0x70
[2.62] PGD 0
[2.62] P4D 0
[2.62]
[2.62] Oops: [#1]
I am still experiencing the same bug. I regularly pull down the latest
updates with apt update and apt dist-upgrade, and if a kernel update is
included then I always test it.
This morning my system got updated with both linux-
image-4.13.0-45-generic and linux-image-4.4.0-128-generic. I have
Here is a new bug report for a new bug caused by recent updates that
fixed #1742675:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753010
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
I'm author of this bug report.
The bug has been resolved by the recent upgrade.
BUT... during recent days the system freezed rather often and required restart
to be usable again. It happened randomly in the following circumstances, for
example:
a) manipulation with complex js widgets by mouse;
I updated again this morning and installed the latest 4.13.0-36-generic
kernel. Unfortunately it still panics on boot. I've attached another
slo-mo video.
** Attachment added: "Slo-mo video of failing boot of 4.13.0-36-generic"
Also lates vanilla 4.15.3 works OK so it looks like 100% problem with
Ubuntu kernel patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to
Sadly issue returned with kernel 4.13.0-35. As i can see from changelog
some Spectre patches have been changed to different approach to fix this
issue. So this is probably reason for this behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags removed: pti
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to
I can confirm that kernel 4.13.0-33.36 work ok on my hardware (Asus Zenbook
UX305) and this kernel has applied all patches for Spectre+Meltdown.
The same result with kernel 4.15.2 from Canonical mainline ppa. So you have
choice - vanilla kernel or Ubuntu kernel.
--
You received this bug
Upgrading to kernel 4.13.0-33.36 from ppa:canonical-kernel-team/ppa solved the
issue.
No need to use "acpi=off"
System works stable. (Dell E5570 i5-6300U Skylake)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorri for unintentional misinformation about kernel 4.14.0-17. In fact
it has patches for Meltdown. But not for Spectre.
Anyway let's hope that soon kernel 4.15 will be on this PPA (if
Canonical decides to go with non-LTS kernel for LTS version).
--
You received this bug notification because
I can confirm that kernel 4.14.0-17 runs also on my hardware (in fact
even without any additional boot options).
As I understand it's mainly because this kernel haven't received any
Spectre+Meltdown patches. So time will show how it will be with these
patches. But for now it's best option to have
ad #27:
for a very recent kernel, you could try 4.14.0-17 from the canonical-
kernel-team PPA: for me (Dell e6500) it runs reliably.
However, you need the boot option acpi=off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ad #28:
you need to use the canonical-kernel-team/unstable PPA!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to linux-image-extra-4.13.0-26-generic the system
I am also affected - all version of 4.13 released so far do not boot. I
also have reverted to 4.10.0.42. Xubuntu 16.04.3 installed on Dell
e6430 laptop Intel/nVidia Graphics no dual-boot. I would echo the
sentiments of an earlier poster - how can this continue through 3+
releases with no
I am affected as well: cannot boot from kernels 4.13.0-26 and 4.13.0-31 even
when acpi=off. Reverted to 4.10.0-42.
Lubuntu 16.04 32 bit on Intel NUC 5PPYH.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since it is probably due to Meltdown+Spectre patches we've probably
missed additional parameter - intel microcode used to build initramfs.
It has changed 2018-01-08 to new one but was changed back to old one
yesterday because many users reported boot and stability problems. It
for sure affects
ad #22 and 23:
same with me: 4.13.0-31 not working
BUT 4.4.0-112 working (without boot options) (32bit installation)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to
After standard system update to 4.13.0-31 the problem still persist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to linux-image-extra-4.13.0-26-generic the system
3 additional tests:
1. Latest standard Ubuntu 16.04 kernel from 4.4 series works OK and
additionally provides fill Spectre+Meltdown protection - linux-
image-4.4.0-111-generic
1. Latest proposed Ubuntu 16.04 kernel from 4.4 series doesn't work -
linux-image-4.4.0-112-generic
3. I've tried
Yes, probably differences in results due to different hardware.
But based on your and my test results i see 2 probably different
problems:
1. Mine looks quite well as a result of some Ubuntu patch applied in
4.13.0-26 and above - i can use without problems all mainline kernels
and all kernels up
ad #19
I've tried 4.14.14 as well: no boot without additional boot options.
With the above mentioned 5 boot options it fails to boot "sometimes"; one out
of three, may be.
It should mention that I'm using a dell latitude e6500 for these tests; the
discrepancy between our results will probably
I've tried your 5 options with linux-image-4.13.0-30-generic but without luck.
On the other hand I've tried mainline 4.14.14 (compiled today) and as all
mainline kernels it works without problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
ad #16:
in my case, mainline kernels, including 4.15-rc8, do also not work (even
with acpi=off).
However, 4.15-rc8 boots when adding (in grub) the 5 (!) options (all
seem to be necessary) acpi=off noapic nolapic irqpoll pnpbios=off (the
first 3 options are not sufficient; the last two options
Similar thing in my situation - all kernel including linux-
image-4.13.0-25-generic work OK on my Asus Zenbook UX305FA but linux-
image-4.13.0-26-generic makes my laptop almost unusable (everything is
many times slower) and any newer version up to current linux-
image-4.13.0-30-generic hang
Question for experienced Ubuntu developers/sysadmins/users:
how long such bugs like this one usually stay non-fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to
for me,lubuntu,16.04, 32 bit installation, no kernels 4.13 and 4.14
boot, neither without or with acpi=off. Without acpi=off, boot stops
right after leaving the grub menu; with acpi=off after the message
"starting to show plymouth boot screen".
Neither does kernel 4.14.14-041414 boot; it fails
** Attachment added: "Slo-mo video of failing boot (3s)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+attachment/5039509/+files/Failed%204.13.0-26-generic%20boot.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It still fails for me with acpi=off.
A bit of background, this PC has been running fine for the past 12
months or so, with regular updates including kernel updates. It's only
started failing since 4.13.0-26-generic.
** Attachment added: "grub command line"
I have the same issue, an automatic upgrade to 4.13.0-30-generic and now
I can't boot. Just kernel panics right away. If I boot with 4.10.0 it
works fine. I'm also attaching a screenshot of my kernel panic message.
** Attachment added: "2018-01-18 20.16.06.jpg"
Using ukuu, I tried 4.14.13-041413.201801101001 and it too fails without
acpi=off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to linux-image-extra-4.13.0-26-generic
I have a Dell Optiplex 960 that exhibits a reboot during boot with
4.13.0-26 with no kernel panic message (though 4.10.0-42 works fine). I
managed to get console dump via serial, which had no information.
Initially I thought it was an out of date BIOS. The machine had A03, so
I updated to A17.
** Attachment added: "Kernel panic from 4.13.0-30-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+attachment/5038840/+files/IMG_0803.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@jsalisbury
Thanks, I followed the instructions and tried booting 4.13.0-30-generic.
I still get a kernel panic. I've attached a screenshot from grub with
the kernel version visible, and a screenshot of the panic.
Thanks
** Attachment added: "grub screenshot"
I prefer to avoid testing it on working computer.
However, I can try to test it on VirtualBox if it is acceptable for this bug.
Just explain all steps, please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
** Tags added: pti
** Tags added: kernel-da-key needs-bisect
--
You
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742675
Title:
after upgrade to linux-image-extra-4.13.0-26-generic the system
I suppose, the following 2 bugs are related to the fact that I work under
linux-image-extra-4.10.0-42-generic. Both appeared in Phpstorm only recently
after this main bug:
a) Once some PHP files edited through Phpstorm were cached somewhere deeply in
Ubuntu. So, when i ran them through local
I noticed that Dell BIOS A09 was ancient, so I upgraded to a (slightly)
newer version, A16 from 2013. It still crashes with 4.13.0-26-generic
but the panic message is different.
** Attachment added: "Screenshot with newer BIOS"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is affecting me as well. I had to connect up a monitor and keyboard
to see what's happening - it's a kernel panic on boot. Machine is a Dell
Precision T5500.
Another data point, 4.13.0-26-generic (recovery mode) works OK.
Screenshot attached.
** Attachment added: "Screenshot of kernel
44 matches
Mail list logo
