** Description changed:
+ [Impact]
+
+ Commit d653420532d580156c8486686899ea6a9eeb7bf0 in bionic enabled kernel
+ page table isolation for x86_32, but also introduced regressions. One of
+ them ("BUG_ON() condition in vmalloc_sync_one()") has been addressed by
+ bug 1830433, but there are other
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel
Michael, first of all thanks for testing. It seems that (in your case at
least) the problem was fixed by the extra commits that I backported into
4.15.0-54, so I think it's worth to have them applied.
To answer your questions, 1) you may want to install also linux-
Thanks Andrea, much appreciated.
Have installed your latest test kernel on my ASUS W1N Pentium M (banias)
machine running 18.04 Xubuntu, and it appears to work! Have shutdown
normally and rebooted several times with no problems. (Note: unable to
test on the HO6710b machine that originally
My output:
uname -a
Linux TEPL-ET2013 4.15.0-54-generic #58+lp1827884 SMP Wed Jul 3 10:05:45 UTC
2019 i686 i686 i686 GNU/Linux
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic
root=UUID=63b3d2c0-b9a9-4112-97eb-de501efd9205 ro quiet splash
cat
Thanks for the tests and the feedback @dima2017 and @valia0906! Could
you also post the output of the following commands?
$ uname -r
$ cat /proc/cmdline
$ cat /sys/devices/system/cpu/vulnerabilities/meltdown
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
I've rechecked the last test version. Previous problem is gone, but xorg
doesn't start. Xorg doesn't start even with the "nopti" option.
BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-54-generic
root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@
ipv6.disable=1 zswap.enabled=0
But I use Lubuntu Xenial. Probably this is why xorg doesn't start with
the last test version. I can upload dmesg or something else if it is
needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I`ve tried second kernel test version on ubuntu 18.04(bionic), the
problem still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48
Seems I used wrong kernel for previous test. Sorry.
This new kernel works, but xorg doesn't start.
I'm testing on Lubuntu xenial. How to add "Xenial" under the "Bionic" on the
top of this thread?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
So, it looks like bug 1830433 didn't fix this problem... assuming it's
still an x86/mm issue, it'd be interesting to test another kernel (I've
applied a few more x86/mm-related fixes).
This new test kernel is available at the same place:
https://kernel.ubuntu.com/~arighi/LP-1827884/
As
I`ve tried kernel test version, the problem is still happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
I've tried. It's still happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To manage notifications about this
On 2019-07-02 16:36:27, Andrea Righi wrote:
> This might be a duplicate of 1830433, could you give it a try with this
> test kernel and see if the problem is still happening?
>
> https://kernel.ubuntu.com/~arighi/LP-1827884/
For everyone who is able to try out that test build, please remember to
This might be a duplicate of 1830433, could you give it a try with this
test kernel and see if the problem is still happening?
https://kernel.ubuntu.com/~arighi/LP-1827884/
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48
I also tested kernel version 4.15.0-54.58, problem still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To
It still present in 4.15.0-54.58 (Tested with lowlatency kernel version
on Toshiba Sattelite L300-11Q). "nopti" helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems
The problem also exists in kernel version 4.15.0.52.54.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To manage
Changed kernel parameter on Dell D620 and Dell 530s - both booting
properly first time since upgrade from kernel 47. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot
Changed kernel parameter to "nopti" on all my machines. It worked.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48
When I add kernel parameter "nopti" the problem also disappears. I
tested kernel version 4.15.0.50.52 and 4.15.0.51.53, all boots were
successful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
@Tyler: Thanks a lot for the great help! Please tell, if I can help by
providing logs or anything else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to
Thanks Tyler, greatly appreciated
nopti workaround all good on Asus W1N Pentium M banias also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel
On 2019-06-07 17:32:04, Thomas Lenarz wrote:
> Boot switch "nopti" solves the problem as well on Asus X51R (Laptop).
> However, I think it is not a final solution, cause its Processor Celeron M
> 520 is on the vulnerability list.
It most definitely isn't a final solution. However, the i386 PTI
Boot switch "nopti" solves the problem as well on Asus X51R (Laptop).
However, I think it is not a final solution, cause its Processor Celeron M 520
is on the vulnerability list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Similar/same problem affects me on
Asus X51R (Laptop).
OS: Lubuntu 18.04. 32-Bit
Occured after automatic update including Kernel probably around
4.15.0-48
Ubuntu seems to boot up, switches on and off screen several times.
Logon screen does NOT appear.
Instead, it restarts itself. After
On 2019-06-07 16:11:07, Brad Evans wrote:
> The nopti switch is working for me with 4.15.0-51-generic.
>
> I think possibly the mitigations=off was not working for me because I
> positioned it at the wrong part (the end) of the linux arguments list.
The 'mitigations=off' option wasn't working
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To manage notifications about this bug go to:
The nopti switch is working for me with 4.15.0-51-generic.
I think possibly the mitigations=off was not working for me because I
positioned it at the wrong part (the end) of the linux arguments list. I
put nopti closer to the front of the arguments list.
--
You received this bug notification
Hello - The 'mitigations=off' option is not the best workaround as it
disables all CPU mitigations.
Since this bug is about 4.15.0-48.51 and i386 installations, the bug is
most likely caused by the addition of Page Table Isolation (PTI) for
i386. It landed in the aforementioned kernel release.
Hi @kaihengfeng
Yes, mitigations=off works on my ASUS pentium M (banias) machine with with ATI
Mobility Radeon graphics, for all of 4.15.0-48, 4.15.0-50 and 4.15.0-51.
At the moment, unable to check on the HP6710b laptop this bug was originally
reported on, as I've loaned it to my brother.
Q:
Hi,
Adding "mitigations=off" to kernel parameters solved issue for me too.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48
Also tried on very old Thinkpad Pentium M (Banias) Mobility Radeon 7500,
Xubuntu 18.04, Kernel 4.15.0-51.
It Works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after
When I add kernel parameter "mitigations=off" the problem disappears. I
tested kernel version 4.15.0.47.49 and 4.15.0.51.53, all boots were
successful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've tried on a Pentium M (Dothan) + Mobility Radeon X600 graphics: it works.
I'm still concerned about security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after
P.S. Kernel 4.15.0-51
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To manage notifications about this bug go to:
I tried again to set mitigations=off for kernel 4.15.0-48 after reading
off Treno70's success. I had one successful boot out of six.
I have read of security concerns in using this setting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Q: does adding "mitigations=off" as kernel parameter put hardware at
risk?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48
On Celeron M (Dothan) + i915 graphics setting "mitigations=off" seems to
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48
Setting mitigations=off did not make any difference for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To manage
Does kernel parameter "mitigations=off" help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To manage notifications
This problem does not exist in kernel 4.18.0-21 (linux-generic-hwe-18.04),
but exists in kernel 5.0.0-16 (linux-generic-hwe-18.04-edge)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
I confirm.
This bug affects all my intel i386 machines (three with intel graphics and one
with amd graphics).
The 64 bit systems are all working fine.
Latest working kernel was 4.15.0-47
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This problem also exists in kernel 4.15.0-51 version on Ubuntu 18.04
(i386).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48
I have precisely the same issue:
Dell Latitude D530
Intel graphics GM965/GL960
Lubuntu 18.04 (32 bit)
Kernel 4.15.0-50
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems
I have the same issue on 3 Laptops (2 HP nc6230 and 1 Asus, all 32bit systems),
only solution so far is to revert to Linux 4.15.0-47. I could not find any
useful hint in any of the logs.
One strange thing is that only every second boot fails. After hard power-off a
hanging boot the next boot
I have a Lenovo G500 (32 bit laptop about 5 years old).
I am seeing the same behavior on my system. Booting 4.15.0-47-generic works
fine, but both
4.15.0-48-generic and 4.15.0-50-generic usually hang at boot time. If I enter
grub at boot and select 4.15.0-50-generic, it usually hangs at this:
I have three different machines running Xubuntu 18.04 i386. All are
affected.
After upgrade to kernel 4.15.0-48 the boot process will stop to an almost black
screen with a few multi-coloured lines.
Problem still persists with kernel 4.15.0-50.
Everything works fine with kernel 4.15.0-47.
--
I am seeing a similar problem.
Linux Mint 18.3 XFCE, Lenovo Thinkpad T60 i686 / ATI Radeon RV515 GPU
After upgrade to kernel 4.15.0-48, I get a black screen and frozen
keyboard once the boot splash screen exits, when the login screen should
appear. There is no mouse pointer, and I can't escape
This problem also exists in kernel 4.15.0-50 version on Ubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
This problem affected all Intel CPUs we have, except for Atoms
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To
Update:
HP Laptop: I have upgraded BIOS on the HP6710b laptop to F16, which included
upgrade of video BIOS. It had no effect on the boot behaviour.
ASUS Laptop: I have realised that I CAN get the grub menu - its just
that the screen is black and I can´t see it. (ie: I can navigate the
grub
apport information
** Description changed:
NOTE: Boot problems on TWO different laptops after Software Updater
updated to kernel 4.15.0-48
Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu desktop.
Both fresh installs from minimal CD in early April, originally kernel
apport information
** Tags added: apport-collected
** Description changed:
NOTE: Boot problems on TWO different laptops after Software Updater
updated to kernel 4.15.0-48
Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu desktop.
Both fresh installs from minimal CD in
Here is the Ubuntu-bug data collection for my other Dell the exibits the
same problem.
** Attachment added: "apport.xorg.984s28cq.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+attachment/5263261/+files/apport.xorg.984s28cq.apport
--
You received this bug notification
I have two old Dell computers which experience a problem similar to what
Michael describes. They work fine at Linux 4.15.0-47 but at 4.15.0-48
they show a corrupted display while booting. I can revert to 4.15.0-47
and await a fix.
I will attach the output file of ubuntu-bug made in 4.15.0-48
You'll probably want the boot.log?
** Attachment added: "boot.log (copy)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+attachment/5261899/+files/boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
59 matches
Mail list logo
