*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920
** This bug has been marked a duplicate of bug 1759920
intel-microcode 3.20180312.0 causes lockup at login screen(w/
linux-image-4.13.0-37-generic)
--
You received this bug notification because you
Hello,
I can also confirm that there are no boot problems with 4.15.0-15.16 and
noibpb disabled in GRUB_CMDLINE_LINUX
--
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/1745349
Title:
Hard
No problem with boot on 4.15.0-15.16 (noibpb disable in
GRUB_CMDLINE_LINUX=)
--
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/1745349
Title:
Hard lockup during boot with
Thanks for testing, Mike. That is the kernel that will ship with
18.04(Bionic). We may need to perform a "Reverse" kernel bisect to
identify the commit in Bionic that fixes this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I've just rebooted five times without any lock ups.
I'll leave it running, and see what happens.
--
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/1745349
Title:
Hard lockup during boot
Can those affected by this bug, please test the following kernel:
https://launchpad.net/ubuntu/+source/linux/4.15.0-15.16/+build/14530348
To test the kernel, install both the linux-image and linux-image-extra
.deb packages.
--
You received this bug notification because you are a member of
Confirmed, 4.4.0-119-generic #143 does not solve this problem, still a
hard freeze during boot. Adding "noibpb" to GRUB_CMDLINE_LINUX= in
/etc/default/grub allowed the machine to boot. Interestingly enough my
server is on VMware, so the problem exists there too
--
You received this bug
Thanks broadmind (gustavo-vegas).
I also have a same problem lockup during boot with newly installed updates
today (4/4/2018). The kernel version is 4.4.0-119-generic #143. I also tried to
boot with an older one (4.4.0-116 perhaps)to no avail. I can only boot in
upstart mode on these kernels,
I have experienced a similar lockup during boot with newly installed
updates today (4/4/2018). The kernel version is 4.4.0-119-generic #143.
I also tried to boot with an older one (4.4.0-116 perhaps)to no avail.
Adding "noibpb" to GRUB_CMDLINE_LINUX= in /etc/default/grub allowed the
machine to
I have very similar issues with 4.4.0-116-generic #140-Ubuntu SMP Mon
Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Booting with
the noibpb option does help and I am currently using it as a workaround.
--
You received this bug notification because you are a member of Kernel
Packages,
This bug is probably a duplicate of bug 1746418 in Artful.
--
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/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
I'm afraid that 4.4.0-117-generic #141 - Ubuntu SMP Tue Mar 13 11:58:07
doesn't cure the problem for me. I still get the Watchdog Hard Lockups.
--
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 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!
--
You received this bug notification because you are a member of Kernel
I'll ping the patch author for feedback.
--
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/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
Status in linux
linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64
and
linux-image-4.16.0-041600rc1-generic_4.16.0-041600rc1.201802120030_amd64
both are working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If i remember correct then from 4.15 the retpoline fixes are used for
spectre mitigation so the noibpb code is not used.
--
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/1745349
Title:
To narrow down the number of commits that could have fixed this, can you
test the following two kernels as welL:
v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/
v4.16-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/
--
You received this bug notification because
System works with
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/linux-
image-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
Too funny. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Before I request feedback from upstream, can you see if this bug is
already fixed in the mainline kernel? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
linux-image-4.4.0-116-generic_4.4.0-116.140~lp1745349Commitb0c3e8bd0405Reverted_amd64
seems to work here, 3 reboots in a row on one machine without hard locks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The bisect reported the following as the first bad commit:
b0c3e8bd0405 ("x86/mm: Only set IBPB when the new thread cannot ptrace current
thread")
I built a Xenial test kernel with a revert of this commit. The test kernel can
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349
No success, hard locks with b0c3e8bd040
--
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/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
Status in linux package
I built the next test kernel, up to the following commit:
b0c3e8bd040546f4dfedff77e3a171a9b15c6571
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
47a07600efe does not work here, hard lock on two pcs.
--
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/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
Status in
That one, 47a0... , failed.
Unfortunately, that is the last one that I can test for you until next
week, as I have to go away for a few days.
I hope that someone else can help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I built the next test kernel, up to the following commit:
47a07600efeb2a180b847bb0e3e99e138a49198c
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Linux golf 4.4.0-110-generic #133~lp1745349Commit49bb7a3cbf5 SMP Tue Mar
6 16:37:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux doesn't seem to have
the problem,.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I built the next test kernel, up to the following commit:
49bb7a3cbf55099e79b27c611176b8db5533d566
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
That one (e233e...) failed.
--
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/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
Status in linux package in Ubuntu:
I built the next test kernel, up to the following commit:
e233ec086ab77c1fc5714368e93a0d6c99d92226
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Yay!
Three boots in a row worked with
linux-image-4.4.0-110-generic_4.4.0-110.133~lp1745349Commit7de295e2a47849_amd64
Was only able to test on one machine though, all my users are logged in.
More testing tomorrow.
--
You received this bug notification because you are a member of Kernel
That one, Linux golf 4.4.0-110-generic
#133~lp1745349Commit7de295e2a47849 SMP Tue Mar 6 13:00:57 UTC 20 x86_64
x86_64 x86_64 GNU/Linux doesn't appear to have the problem.
It has been running for a lot longer than it usually does.
--
You received this bug notification because you are a member of
I built the next test kernel, up to the following commit:
7de295e2a47849488acec80fc7c9973a4dca204e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
No luck, unfortunately.
linux-image-4.4.0-110-generic_4.4.0-110.133~lp1745349Commitd3d0f0a209ee_amd64
shows the same hard lock.
--
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/1745349
I'm definitely running from your 110 kernel, and it exhibits the
Watchdog Hard Lockup problem, when running without noipbp.
--
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/1745349
Title:
I started a kernel bisect between 4.4.0-109 and 4.4.0-110. The kernel
bisect will require testing of about 5 - 6 test kernels.
I built the first test kernel, up to the following commit:
d3d0f0a209ee29cf553b8b5580eb954b0d4aa970
The test kernel can be downloaded from:
Sorry, no improvement on ASUS H110M-C Board with
linux-image-4.4.0-116-generic_4.4.0-116.140~lp1745349Commitff2699cReverted_amd64
Still 4 out of 5 boots result in hard lock.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
uname -a shows:-
Linux golf 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
so I obviously haven't implemented your kernel correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
@Mike Turner, you can confirm which kernel you are running by running
the following command from a terminal: uname -a
@Lars Behrens, as the original bug reporter, can you test the kernel
posted in comment #14?
--
You received this bug notification because you are a member of Kernel
Packages,
I'm afraid that I am not an expert at Ubuntu. I think that I have
installed your test kernel correctly, but I don't know how to prove it.
I used sudo dpkg -i *.deb .
If I have installed it correctly, then it doesn't cure the problem. It
runs fine with noibpb, but fails in the same way if I try to
Hello, I also have the same issue on a Dell E7470 laptop using Ubuntu
16.04 LTS.
I tried the kernel with the reverted commit and it works fine.
I have also noticed the same issue on 4.13.0-32 and 4.13.0-36 hwe kernels
Let me know if you need any logs from my side
Cheers
--
You received this
I built an Artful test kernel with a revert of commit: ff2699c
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745349
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu
Correction - 4.4.0-116-generic does not solve the problem.
The server was up for over an hour before hanging. As it doesn't usually
have a console, I can't be certain of the cause of the hang. However, a
subsequent reboot, with a console, involving rebuilding a 10TB RAID 5
array, showed exactly
4.4.0-116-generic does appear to solve the problem on my Asus Prime
Z270K.
--
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/1745349
Title:
Hard lockup during boot with
Am 22.02.2018 um 09:05 schrieb ake sandgren:
> The 4.4.0-116-generic still hangs my laptop during boot the same way
> -112 did. And noibpb still solves the problem.
Confirming for Asus H110M-C boards, still the hardlocks.
--
You received this bug notification because you are a member of Kernel
The 4.4.0-116-generic still hangs my laptop during boot the same way
-112 did. And noibpb still solves the problem.
--
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/1745349
Title:
Hard
I can prevent the issue by addning the "noibpb" boot parameter to my
kernel arguments.
--
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/1745349
Title:
Hard lockup during boot with
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5046867/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Any more info that you need? The bug is still tagged as "incomplete"
--
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/1745349
Title:
Hard lockup during boot with
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5042847/+files/WifiSyslog.txt
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+attachment/5046863/+files/WifiSyslog.txt
**
Am 25.01.2018 um 21:45 schrieb Joseph Salisbury:
> Can you see if either of the following two kernels also exhibit the bug:
>
> 4.4.0-110: https://launchpad.net/~canonical-kernel-security-
> team/+archive/ubuntu/ppa/+build/14231477
>
> 4.4.0-111: https://launchpad.net/~canonical-kernel-security-
I have similar issues on my DELL R630 server but only on those with
extra NIC:s.
In my case it is not triggerd on boot but when I start the openstack
neutron agents components that starts configuring the extra nic (Intel
10-Gigabit X540-AT2 rev 01).
[ 204.789174] NMI watchdog: Watchdog detected
Can you see if either of the following two kernels also exhibit the bug:
4.4.0-110: https://launchpad.net/~canonical-kernel-security-
team/+archive/ubuntu/ppa/+build/14231477
4.4.0-111: https://launchpad.net/~canonical-kernel-security-
team/+archive/ubuntu/ppa/+build/14241947
** Changed in:
54 matches
Mail list logo
