Public bug reported:
This issue doesn't happen with Nnvidia version 525 or 535 but it happens
with 545 and 550.
Steps to reproduce:
- Run window manager or desktop environment without compositor manager.
For example XFCE with Settings – Window Manager Tweaks – Compositor and
disable Enable
Public bug reported:
I'm using XFCE + picom for my graphical desktop and the system is using
Nvidia GTX 1060 3 GB graphics adapter. Whenever the system is waking
from S3 sleep, the graphical desktop freezes once for 10–20 seconds when
I resize any existing window or launch a new program.
$ apt
Public bug reported:
I'm running MATE desktop and I installed NVIDIA GTX 1060 GPU to my
system and Xorg crashes after entering password.
I proceeded to run strace with startx trying to debug this and it seems
that the window manager `marco` does some (yet unknown) command which
causes Xorg to
Public bug reported:
$ man ip-address
...
SYNOPSIS
...
ip address { add | change | replace } ...
However, the subcommands "change" and "replace" are not documented
anywhere. As these may be used in scripts, there should be clear
definition of these features or nobody can know if a script using
Public bug reported:
I'm running Ubuntu 18.04 LTS with latest lowlatency kernel. In practice
I've installed package linux-lowlatency-hwe-18.04-edge which has
resulted packages linux-image-5.4.0-117-lowlatency and linux-
modules-5.4.0-117-lowlatency to be installed right now.
$ dpkg -L
After more experience with different settings it seems that the behavior
of vfs_cache_pressure was changed a lot between linux kernel version 5.3
and 5.4.
For cases where vfs_cache_pressure=1 did work nicely with version 5.3
you need something in range 30-90 for linux kernel version 5.4 to get
One of the systems was using package linux-generic and in practice
Linux pedabackup 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version_signature
Ubuntu 5.4.0-80.90-generic 5.4.124
--
You received this bug notification because you are
I think I've seen this issue once per two different systems so I think
this is software issue. Does anybody know if patch in comment #6 is
going to be included in Ubuntu 20.04 LTS?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Still warning messages emitted to kernel log each boot.
Ubuntu 20.04.1 LTS
5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux
I'm running over 10 year old systems and I don't need built-in support
for EISA. Does anybody even know anybody running old
Could somebody that is seeing this problem try to boot with kernel flag
"iommu=off". Some hardware that used to work with older kernels may be
broken and fails to work with modern kernels which default to using
IOMMU.
Note that disabling IOMMU is a heavy handed workaround, not a proper
fix. For
See also: https://www.smartmontools.org/wiki/SAT-with-UAS-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/1810215
Title:
for Seagate USB drive enclosures, SAT (e.g. smartmontools,
For more information about this issue, see
https://askubuntu.com/a/1106020/50254
TL;DR: Linux kernel disables 12 and 16 bit SATA Commands over UAS when
used with Seagate HDD enclosures. This usb_storage quirk is "t" instead
of "u" which forces the device into USB BOT mode. The only way to make
See also: https://patchwork.kernel.org/patch/8519201/
--
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/1703960
Title:
ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Status in linux
I did not select option for "poor CPU performance" during install. I
also previously disabled "ondemand" service after finding that Ubuntu
12.04 LTS had non-performance mode by default. After upgrade to Ubuntu
16.04 LTS (via Ubuntu 14.04 LTS) my CPU has been silently turned to non-
performance
I think that *-lowlatency-* kernels should include CONFIG_LATENCYTOP by
default. I agree that *-generic-* kernels do not need that. If
administrator has installed lowlatency kernel they clearly are
interested in lowest possible latency and Ubuntu should provide tools to
figure out where the
Public bug reported:
Actual behavior:
$ sudo latencytop
mount: none is already mounted or /sys/kernel/debug busy
Please enable the CONFIG_LATENCYTOP configuration in your kernel.
Exiting...
$ grep -i latencytop /boot/config-`uname -r`
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
# CONFIG_LATENCYTOP is not
16 matches
Mail list logo
