[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).
Hello.
I apologize for not testing the latest v4.16 kernel, but I've decided to
wait for an update to the v4.4 kernel used in "Xenial". And it seems,
that everything is okay now and 'kaslr' option is working again. After
update Linux kernel to the v4.4.0-117-generic (v4.4.114) version, system
boots normally. I've done some tests:
● boot system via GRUB (add 'kaslr' option and press 'CTRL + X')
● edit '/etc/default/grub' file and add 'kaslr' option to the
'GRUB_CMDLINE_LINUX_DEFAULT='
Everything is fine, system starts normally etc. There is no problem, as
I've described in my post #4. So, some of the patches (see 1.) fixed
this issue.
Thanks, best regards.
_
1.
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=fc74a5c4a98418105b4b246b935e3be90d6a635c
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
--
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/1748710
Title:
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Bug description:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
Unfortunately, the USB keyboard does not work and does not respond.
The only way to solve this issue is a "hard reset" and in GRUB menu
choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
everything works okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not
contain PTI yet, right? I'm asking, because mentioned -proposed
updates contains a couple of PTI-related patches and bugs in PTI can
cause a few different signatures of crashes etc. For example:
→ Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
→ Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.
NOTE: if it's about PCID, which is mentioned in a second point, there
is one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
'/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
series. So, I don't know if mentioned patches are good for this type
of processor etc.? Especially on i386/x86_32 architecture.
● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
this issue. After booting the latest v4.4.0-115.139 kernel, I've had
the same problems as described above. However, after removing 'kaslr'
option from a command line via GRUB menu, system started normally etc.
The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
According to all of this I think, that 'kaslr' is not compatible with
some "Spectre & Meltdown" mitigation patches and fixes etc.
✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
✗ Architecture: i386/x86_32
✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]
Thanks, regards.
1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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
[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).
Here is a new, separate bug report about 'kASLR' and system booting
issues (v4.4.0-113.136 - v4.4.0-115-generic kernel versions):
● https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748936
--
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/1748710
Title:
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
Unfortunately, the USB keyboard does not work and does not respond.
The only way to solve this issue is a "hard reset" and in GRUB menu
choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
everything works okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not
contain PTI yet, right? I'm asking, because mentioned -proposed
updates contains a couple of PTI-related patches and bugs in PTI can
cause a few different signatures of crashes etc. For example:
→ Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
→ Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.
NOTE: if it's about PCID, which is mentioned in a second point, there
is one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
'/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
series. So, I don't know if mentioned patches are good for this type
of processor etc.? Especially on i386/x86_32 architecture.
● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
this issue. After booting the latest v4.4.0-115.139 kernel, I've had
the same problems as described above. However, after removing 'kaslr'
option from a command line via GRUB menu, system started normally etc.
The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
According to all of this I think, that 'kaslr' is not compatible with
some "Spectre & Meltdown" mitigation patches and fixes etc.
✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
✗ Architecture: i386/x86_32
✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]
Thanks, regards.
1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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
[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).
Good day, Mr Salisbury.
Yes, I can test the latest kernel, but I have a few very naive questions
(I just want to be sure for one hundred percent etc.) So, because it's
an i386/x86_32 architecture I should:
✗ download
'linux-headers-4.16.0-041600rc1-generic_4.16.0-041600rc1.201802120030_i386.deb'
and
'linux-image-4.16.0-041600rc1-generic_4.16.0-041600rc1.201802120030_i386.deb'
packages;
✗ use, for example, dpkg(1) command to install these two packages ($ sudo dpkg
-i ...);
✗ add "kaslr" option to the '/etc/default/grub' file (in
'GRUB_CMDLINE_LINUX_DEFAULT' option);
✗ update GRUB with update-grub(8) command to generate a grub2 config file etc.;
✗ reboot.
Once again: I apologize for such a naive questions. Mr Salisbury, can
You confirm if what I've wrote is okay? Generally: is it a proper way to
test the latest kernel? And what about dpkg(1) command: I should use
'-i, --install' action only, right? I'm asking, because there is - for
example - a 'gdebi' package, which is a simple tool to install deb files
etc.
Geez, what a shame...
Thanks.
--
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/1748710
Title:
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
Unfortunately, the USB keyboard does not work and does not respond.
The only way to solve this issue is a "hard reset" and in GRUB menu
choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
everything works okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not
contain PTI yet, right? I'm asking, because mentioned -proposed
updates contains a couple of PTI-related patches and bugs in PTI can
cause a few different signatures of crashes etc. For example:
→ Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
→ Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.
NOTE: if it's about PCID, which is mentioned in a second point, there
is one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
'/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
series. So, I don't know if mentioned patches are good for this type
of processor etc.? Especially on i386/x86_32 architecture.
● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
this issue. After booting the latest v4.4.0-115.139 kernel, I've had
the same problems as described above. However, after removing 'kaslr'
option from a command line via GRUB menu, system started normally etc.
The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
According to all of this I think, that 'kaslr' is not compatible with
some "Spectre & Meltdown" mitigation patches and fixes etc.
✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
✗ Architecture: i386/x86_32
✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]
Thanks, regards.
1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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
[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: pti
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
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/1748710
Title:
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
Unfortunately, the USB keyboard does not work and does not respond.
The only way to solve this issue is a "hard reset" and in GRUB menu
choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
everything works okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not
contain PTI yet, right? I'm asking, because mentioned -proposed
updates contains a couple of PTI-related patches and bugs in PTI can
cause a few different signatures of crashes etc. For example:
→ Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
→ Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.
NOTE: if it's about PCID, which is mentioned in a second point, there
is one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
'/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
series. So, I don't know if mentioned patches are good for this type
of processor etc.? Especially on i386/x86_32 architecture.
● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
this issue. After booting the latest v4.4.0-115.139 kernel, I've had
the same problems as described above. However, after removing 'kaslr'
option from a command line via GRUB menu, system started normally etc.
The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
According to all of this I think, that 'kaslr' is not compatible with
some "Spectre & Meltdown" mitigation patches and fixes etc.
✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
✗ Architecture: i386/x86_32
✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]
Thanks, regards.
1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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
[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).
** Description changed:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
Unfortunately, the USB keyboard does not work and does not respond. The
only way to solve this issue is a "hard reset" and in GRUB menu choosing
an earlier kernel, which is linux 4.4.0-112.135. Now, everything works
okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not contain
PTI yet, right? I'm asking, because mentioned -proposed updates contains
a couple of PTI-related patches and bugs in PTI can cause a few
different signatures of crashes etc. For example:
- ✗ Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
- ✗ Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.
+ → Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
+ → Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.
NOTE: if it's about PCID, which is mentioned in a second point, there is
one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
'/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
series. So, I don't know if mentioned patches are good for this type of
processor etc.? Especially on i386/x86_32 architecture.
- I hope, that all mitigations and fixes for "Metldown & Spectre_v1.2"
- atacks will be available for 32-bit x86 architecture. (OpenSUSE
- Developers are working on such a fixes/patches, right?) If I could
- provide some more informations, please let me know. Here are some
- technical informations:
+ ● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for this
+ issue. After booting the latest v4.4.0-115.139 kernel, I've had the same
+ problems as described above. However, after removing 'kaslr' option from
+ a command line via GRUB menu, system started normally etc. The latest,
+ working kernel with 'kaslr' option is v4.4.0-112.135. According to all
+ of this I think, that 'kaslr' is not compatible with some "Spectre &
+ Meltdown" mitigation patches and fixes etc.
- ● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
- ● Architecture: i386/x86_32
- ● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]
+ ✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
+ ✗ Architecture: i386/x86_32
+ ✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]
Thanks, regards.
1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html
** Tags added: kaslr
--
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/1748710
Title:
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
Unfortunately, the USB keyboard does not work and does not respond.
The only way to solve this issue is a "hard reset" and in GRUB menu
choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
everything works okay.
Proposed update to the Linux 4.4.0-113.136
[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).
Hello. There is the same problem with a new, latest Linux
4.4.0-115-generic kernel (updated today). I've tried to boot system with
'nosplash' option (set via GRUB etc.) and it seems, that there is a
problem with:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=* does not exist. Dropping to a shell!
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a lost of built-in commands.
(initramfs) _
However, I've decided try to boot v4.4.0-115-generic kernel once again,
because above 'ALERT!' message was very interesting for me, but this
time, without 'kaslr' option. So, in a GRUB menu I removed this option
and press CTRL + x. Everything was okay - system boot normally.
It seems, that there is a problem with a 'kaslr' in latest 16.04 LTS
Release kernels (I'm having this problem since update to the
v4.4.0-113.136 kernel version.
Should I create a new bug report about 'kaslr' and latest kernel
versions?
--
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/1748710
Title:
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
Unfortunately, the USB keyboard does not work and does not respond.
The only way to solve this issue is a "hard reset" and in GRUB menu
choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
everything works okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not
contain PTI yet, right? I'm asking, because mentioned -proposed
updates contains a couple of PTI-related patches and bugs in PTI can
cause a few different signatures of crashes etc. For example:
✗ Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
✗ Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.
NOTE: if it's about PCID, which is mentioned in a second point, there
is one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
'/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
series. So, I don't know if mentioned patches are good for this type
of processor etc.? Especially on i386/x86_32 architecture.
I hope, that all mitigations and fixes for "Metldown & Spectre_v1.2"
atacks will be available for 32-bit x86 architecture. (OpenSUSE
Developers are working on such a fixes/patches, right?) If I could
provide some more informations, please let me know. Here are some
technical informations:
● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
● Architecture: i386/x86_32
● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]
Thanks, regards.
1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+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
[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).
** Summary changed:
- Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell.
+ Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
** Description changed:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
- plymouth freezes during start, and keys on a keyboard were in-active.
- After several seconds, the BusyBox screen appeared. It looks this way:
+ plymouth freezes during start, and keys on an USB keyboard were in-
+ active. After several seconds, the BusyBox shell screen appeared. It
+ looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
- Unfortunately, the keyboard does not work and does not respond. The only
- way to solve this issue is a "hard reset" and in GRUB menu choosing an
- earlier kernel, which is linux 4.4.0-112.135. Now, everything works
+ Unfortunately, the USB keyboard does not work and does not respond. The
+ only way to solve this issue is a "hard reset" and in GRUB menu choosing
+ an earlier kernel, which is linux 4.4.0-112.135. Now, everything works
okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not contain
PTI yet, right? I'm asking, because mentioned -proposed updates contains
a couple of PTI-related patches and bugs in PTI can cause a few
different signatures of crashes etc. For example:
✗ Crashes in early boot, especially around CPU bringup. Bugs in the
trampoline code or mappings cause these.
✗ Userspace segfaults early in boot, sometimes manifesting as mount(8)
failing to mount the rootfs. These have tended to be TLB invalidation issues.
Usually invalidating the wrong PCID, or otherwise missing an invalidation.
NOTE: if it's about PCID, which is mentioned in a second point, there is
one patch in -proposed update: "x86/mm/32: Move
setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
cause of a boot failure? There are no errors in log files, such as
- '/var/log/syslog' or '/var/log/kern.log'. Maybe only that one (but I
- have no idea if it's important)?
+ '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
+ series. So, I don't know if mentioned patches are good for this type of
+ processor etc.? Especially on i386/x86_32 architecture.
- ✗ PCI: Using host bridge windows from ACPI; if necessary, use
- "pci=nocrs" and report a bug
-
- If I could provide some more informations, please let me know. Here are
- some technical informations:
+ I hope, that all mitigations and fixes for "Metldown & Spectre_v1.2"
+ atacks will be available for 32-bit x86 architecture. (OpenSUSE
+ Developers are working on such a fixes/patches, right?) If I could
+ provide some more informations, please let me know. Here are some
+ technical informations:
● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
● Architecture: i386/x86_32
● PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode])
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express
bridge [1458:026f]
Thanks, regards.
1. https://lists.ubuntu.com/archives/xenial-
changes/2018-February/020108.html
--
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/1748710
Title:
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
plymouth freezes during start, and keys on an USB keyboard were in-
active. After several seconds, the BusyBox shell screen appeared. It
looks this way:
,--
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`--
Unfortunately, the USB keyboard does not work and does not respond.
The only way to solve this issue is a "hard reset" and in GRUB menu
choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
everything works okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates
(please see 1.) It's an i386/x86_32 architecture, which does not
contain PTI yet, right? I'm asking, because mentioned -proposed
updates contains a couple of PTI-related patches and bugs in PTI can
cause a few different signatures of crashes etc. For example:
✗ Crashes in early boot, especially
