Change package to arpon.
** Package changed: linux (Ubuntu) => arpon (Ubuntu)
** Description changed:
Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
(ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
2.7.
It seems that ArpON ver. 2.7 has a
Public bug reported:
Hello. Because on Ubuntu 12.04 LTS an ArpON package is pretty outdated
(ver. 2.0-2.1 0) I've decided to use a version from a Vivid release -
2.7.
It seems that ArpON ver. 2.7 has a bug related to a DARPI anti Arp
Poisoning techniques. Because I am using a DHCP method to
Hi. The same problem here. Release 16.04.2 LTS, iptables 1.6.0-2ubuntu3
etc. I noticed this one in dmesg entry:
$ sudo dmesg |grep iptables
[ 1168.282586] nf_conntrack: automatic helper assignment is deprecated and it
will be removed soon. Use the iptables CT target to attach helpers instead.
Hello.
I just wanto to confirm: everything seems to be okay after updating
Linux kernel to v4.4.0-123-generic. However, I would like to ask a
question about 'intel-microcode' and 'amd64-microcode' packages. During
system updating process via apt(8), there was an information that "The
following
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)
Public bug reported:
Hello.
It seems, that 'kaslr' option is responsible for issues with system
booting. The latest working kernel is v4.4.0-112.135. Every next
release: v4.4.0-113.136 and v4.4.0-115.139 are unable to boot if 'kaslr'
option is in use etc. Everything is described in my previous
** 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
Please see "Ubuntu Kernel Bot (ubuntu-kernel-bot)" comment and answer.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi. I can not enter mentioned command, because during system boot
plymouth freezes and keyboard is unresponsive. After several seconds
plymouth disappears and BusyBox v1.22.1 "console" appears (here,
keyboard does not work and does not respond either). The only solution
is to use hard reboot and
** 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
Public bug reported:
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
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
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
** Changed in: linux (Ubuntu)
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/1790688
Title:
x86/pti: 32-Bit x86 systems support already available.
Hello.
One more thing: since kernel page-table isolation is already available
on 32-Bit x86 systems (see Bug Description), maybe "SpectreAndMeltdown"
information page (see 1.) should be updated, because of such a statement
(see "Current Status"):
"No fix is currently available for Meltdown on
Public bug reported:
Hello.
Linux kernel v4.19 release candidate [1], finally have kernel page-table
isolation ('PTI', previously known as 'KAISER') support for x86_32
architecture. As we know, 'PTI' provides protection against attack,
known as the "Meltdown" (CVE-2017-5754), that breaks
** Summary changed:
- x86/pti: 32-Bit x86 systems support already available.
+ x86/pti: 32-bit x86 systems support already available.
** Description changed:
Hello.
- Linux kernel v4.19 release candidate [1], finally have kernel page-table
- isolation ('PTI', previously known as 'KAISER')
Hello.
I've noticed this issue with blank '/boot/retpoline-*' files in 16.04
LTS Release (i386/x86_32) after Linux kernel update to the v4.4.0-115
version. (Generally, I've started to seeing these files when
"Spectre_V12" patches were available for i386 architecture. I wanted to
ask a question or
** Summary changed:
- Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
built-in shell (initramfs).
+ Linux 4.4.0-113.136 (i386/x86_32): failed to boot when 'kaslr' option is in
use.
--
You received this bug notification because you are a member of Kernel
Packages, which
Hello.
Retpoline file, is not empty now. After update Linux kernel to the
v4.4.0.117.123 (v4.4.114) version in 16.04 LTS Release (i386/x86_32
architecture), '/boot/retpoline-4.4.0-117-generic' file contains some
data etc. (2,0K size). Previous files (see post #4) are empty, of
course.
Thanks.
Linux kernel v4.4.0-117-generic (v4.4.114) works okay and 'kaslr' option
can be used again.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello. 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. So, some of the patches (see
1.) fixed this issue.
Thanks, best regards.
_
1.
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
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
** Summary changed:
- kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels ("Spectre
& Meltdown" patches.)
+ kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139
Hello.
Today, I noticed the same entries in a log files such as
'/var/log/syslog' and via dmesg(1) on 16.04 LTS Release (i386/x86_32
arch) with v4.4.0-120-generic (4.4.117) Linux kernel. The one thing,
that is different is 'use_ibrs' value. In my case it's:
[~]$ sudo dmesg
[ 464.877859]
Hello.
Yes, Mr. Kamal Mostafa is right. Linux kernel v4.4.0-123.147 will
contain a fix for all of these issues with, for example,
'/var/log/syslog' flooding with 'ibrs_dump', 'use_ibrs/ibpb' and
'sysctl_ibrs{,ibpb}_enabled' entries. Now, a "proposed" kernel is
v4.4.0-122.146 with a fix for
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1751021
Title:
retpoline abi files are empty on i386
Hello. I would like to note, that "Meltdown" mitigation - for i386
architecture - among others improvements, is already available in
OpenBSD 6.4 release (see "Security improvements" section [in:]
https://www.openbsd.org/64.html).
Best regards.
--
You received this bug notification because you
Hello.
There is a similar raport about failed 'nvidia_304' module build on
latest '-proposed' v4.4.0-143-generic kernel:
✗ https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-304/+bug/1815858
Mentioned issue happened on both: amd64 and i385/i686 architectures.
Best regards.
--
Hello.
Once agains - I'm sorry for writing post by post, but there is a very
interesting comment I found, while checking patches/fixes in Linux
v4.4.0-143.169 version (see '1.'). This is excatly the same error, that
happened when I updated kernel to the latest '-proposed' release etc. In
both
*** This bug is a duplicate of bug 1658219 ***
https://bugs.launchpad.net/bugs/1658219
Hello.
I would like to note, that when Linux kernel has been updated to
4.4.0-160.188 version[1] (with, among others, patches for LP:#1658219
and LP:#1838090), I've had to update a few profiles (such as
Hello.
I would like to note, that when Linux kernel has been updated to
4.4.0-160.188 version[1] (with, among others, patches for LP:#1658219
and LP:#1838090), I've had to update a few profiles (such as Audacious,
Parole, Xorg, Logrotate etc.), because of a lot of "DENIED" entries in
system log
Hello H Buus.
Thank You for a comment. According to BUGs with call traces from
'kern.log' file (I mean especially 'unable to handle kernel NULL pointer
dereference at 0008' messages etc.) I think you should report all
these informations on the linux-kernel mailing list (please see 1).
Also, I
Hello.
Today, I've noticed two entries about 'ecryptfs_decrypt_page' and
'ecryptfs_readpage' errors in `/var/log/syslog` file. I have no idea if
there was/is more such entries. However, it looks this way:
,[ ✖ Error ]
| kernel: [25312.360714] ecryptfs_decrypt_page: Error attempting to read
34 matches
Mail list logo
