** Changed in: linux-aws (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1991833
Title:
VRF Kernel Module Does Not Exist
Status in linux-aws
Well I didn't realize I could just install them with linux-modules-
extra-$(uname -r) package. I was able to do this and get the needed
kernel module.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560023/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560022/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Applied the "apport-collect 1960344" command as requested. Note that
this is while using the 5.4.0-94 kernel, because I cannot successfully
log in with the 5.4.0-99 kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560021/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560024/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560016/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560013/+files/Lsusb.txt
--
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/1960344
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560017/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560020/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560011/+files/Lspci.txt
--
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/1960344
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560015/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560018/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560012/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560009/+files/CRDA.txt
--
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/1960344
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560019/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560014/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560010/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected una
** Description changed:
When I boot with kernel 5.4.0-94 my Linux system properly asks me for
the passphrase to my encrypted drive (full disk encryption) and then
after that successfully gets me to the user login screen. But when I
kernel: blk_update_request: I/O error, dev sr0, sector 661504 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sr0, logical block 82688, async page read
Description:Ubuntu 20.04.3 LTS
Release:20.04
Machine:
Type: Desktop Mobo: Micro-Star
model:
Similar problem occurred during upgrade to linux-firmware (1.187.20);
initial install failed, but was able to successfully install after a
reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Appears to have installed successfully after a reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1945845
Title:
package linux-firmware 1.187.16 failed to install/upgrade:
Public bug reported:
Description:Ubuntu 20.04.3 LTS
Release:20.04
linux-firmware:
Installed: 1.187.16
Candidate: 1.187.17
Version table:
1.187.17 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
500
$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
linux-headers-5.11.0-34-generic linux-hwe-5.11-headers-5.11.0-34
The following NEW
This is with the NVIDIA 460 driver. At present, I can't successfully
switch to the 470 driver, because it tries to use the 5.11.0-34.36
kernel files as part of the install.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in
Public bug reported:
Description:Ubuntu 20.04.3 LTS
Release:20.04
\linux-headers-5.11.0-34-generic:
Installed: (none)
Candidate: 5.11.0-34.36~20.04.1
Version table:
5.11.0-34.36~20.04.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
Public bug reported:
Description:Ubuntu 20.04.2 LTS
Release:20.04
linux-modules-nvidia-460-5.8.0-59-generic:
Installed: 5.8.0-59.66~20.04.1
Candidate: 5.8.0-59.66~20.04.1
Version table:
*** 5.8.0-59.66~20.04.1 500
500 http://us.archive.ubuntu.com/ubuntu
The same thing happens to me with 5.11.0-18, I have to use 5.11.0-16 for now.
I also have a AMD Radeon RX 6700 XT
--
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/1928355
Title:
linux
This bug is not present with other distro's I use, that is Arch. This
indicates that it can be distribution centric. Ubuntu has the bug, Arch
does not. A workaround is if your system has this Intel device use
another distro. It is not convenient but it works.
--
You received this bug
Has there been any progress on this.
I still have the same problem on both kernel 4.15 and 5.4.
I still have to modify logrotate to limit logging or more recently I
have tried stopping the logging of any errors which was not as simple as
I expected as rsyslog uses socket activation under
syslog and kern.log grew until the filesystem was full. This happened
twice. It can be replicated. My workaround is to regress to 19.10.
I have a system on 20.04 that does not use wireless and there is no
error.
--
You received this bug notification because you are a member of Kernel
** Changed in: linux (Ubuntu)
Assignee: Hui Wang (hui.wang) => tony curtis (tonyc433)
--
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/1827967
Title:
There are 4 HDMI/Displayp
ic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: curtis 8167 F pulseaudio
/dev/snd/controlC2: curtis 8167 F pulseaud
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
Thanks for following up. I had forgotten about this bug as I haven't had
trouble with this in probably 6 months or more. Other than installing
software updates, I didn't do anything to fix it. But it seems to be
resolved for me.
--
You received this bug notification because you are a member of
*** 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.
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
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.
--
I have the same flooding of /var/log/syslog about every 200 msecs with:
Oct 27 21:17:01 helios kernel: [11807.295919] ACPI Error: Method
parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE
(20170831/psparse-550)
Oct 27 21:17:02 helios kernel: [11807.497617] ACPI Error: Needed
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
** 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.
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
** 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.
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
After testing for the last week, the new kernel has not completely
solved the problem, though bluetooth does crash less frequently (once
every day or two instead of multiple times per day) when using the new
kernel.
--
You received this bug notification because you are a member of Kernel
Sure thing. I've updated to 4.17.0-041700-generic and will post back
early next week after testing. 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/1775443
Title:
Ubuntu 18.04
** No longer affects: linux-signed (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1775443
Title:
Ubuntu 18.04 Bluetooth Crash
Status in linux package in Ubuntu:
** Description changed:
+ I am having trouble with the bluetooth connection between the laptop and
+ my Logitech MX Master wireless mouse. The computer will lose connection
+ with the mouse multiple times per day. When this happens, the bluetooth
+ icon in the upper right-hand corner of the
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149479/+files/WifiSyslog.txt
** Description changed:
- Posted a question here and it was recommended that I file a kernel bug
- report:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149474/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149475/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149477/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149476/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149478/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149473/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149472/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149467/+files/CRDA.txt
--
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/1775443
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149470/+files/Lspci.txt
--
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/1775443
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149471/+files/Lsusb.txt
--
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/1775443
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149469/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Posted a question here and it was recommended that I file a kernel bug
report: https://askubuntu.com/questions/1044235/18-04-bluetooth-crashing
$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1775443/+attachment/5149468/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Posted a question here and it was recommended that I file a kernel bug
report: https://askubuntu.com/questions/1044235/18-04-bluetooth-crashing
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ apt-cache policy bluez
bluez:
Installed:
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.
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
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]
** 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
** 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
** 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.
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
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.
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.
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
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
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
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)
** 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
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
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
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.
We've been seeing this problem as well in testing. What is the
possibility of seeing patches landing in a Trusty (4.4) kernel release?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is there a work-around like disabling c-states?
--
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/1598529
Title:
On update_blocked_averages function issue
Status in linux package in
** Tags added: jujuqa
--
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/1616949
Title:
guest on bridge becomes inaccessible
Status in linux package in Ubuntu:
Confirmed
Bug
fsck.btrfs is now just a dummy program to return exit code 0.
Source: $ man fsck.btrfs
** Changed in: btrfs-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a
I can also confirm that the 3.19.0.49-generic kernel solves the problem
for me.
--
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/1488426
Title:
High CPU usage of kworker/ksoftirqd
Status
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
Similar to Bela Berczi (bberczi). This was on a new HP Envy 13t. It
works fine with Windows 10, but will only connect as "All Types", and
will not work as a mouse, on the 14.04.3 release.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I have tried the test patch provided by Mathias Nyman in http://linux-
kernel.2935.n7.nabble.com/TESTPATCH-v2-xhci-fix-usb2-resume-timing-and-
races-tc1250796.html#a1256745 and rebuilt a Wily 4.2 kernel and that has
prevented High CPU usage of kworker/ksoftirqd under all the
circumstances I have
@Aditya Thanks for the clarification. I had been trying to find out if
the patch had been merged.
The issue is not however fixed for me with 4.2 nor was it for lpuser in
#8 who tried a number of kernels. However it an improvement as I said in
#17
The following shows the problem first without BT
I have carried out some more comprehensive tests using the kernel in #4 over
the weekend and found it does improve my situation far more than my initial
quick test showed. Most of the rather bizarre behaviour has gone include the
changes with power from battery to external and the importance of
I also have a similar problem which does Not seem to be solved by the
patched kernel although the perf report looks very similar and plugging
in a USB device clears the problem. The starting and inhibiting of the
kworker spinning is very specific and rather bizare on my new Skylake
machine running
** Tags added: lxc network
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 109 matches
Mail list logo
