Wow. In my opinion, this bug is extremely severe. It is sad that this is
years old.
--
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/1890865
Title:
Nouveau X.org: Stale texture data and fl
The way it is currently done, I don't think valid CPU frequency listing
via "scaling_cur_freq", or /proc/cpuinfo, is expected to work. Why not?
Because the required code is never executed, on purpose. Here is an
excerpt from a commit (see the bit about NOHZ full)
commit f3eca381bd49d708073ba1a9af
CPU frequency scaling driver: intel_pstate
CPU frequency scaling governor: powersave
HWP: disabled.
Purpose to verify that the driver is working correctly, regardless of CPU
frequencies reported.
A single threaded load was applied to CPU 5 at 347 hertz sleep/work frequency.
The load was increase
There is a high probability that the root issue here is related to some work
done in August September.
There was already an outstanding issue with intel_cpufreq driver / schedutil
governor, hwp enabled.
References:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d5
I redid the Phoronix Stress-NG 0.16.04: Socket Activity test, the one
that showed such a dramatic difference in their test. I increased to
number of test runs from 3 to 10 and time per run from 30 to 60 seconds.
I got:
250Hz kernel (generic): 6608.74 Bogo Op/s, Deviation 0.56%
1000Hz kernel (lowla
of the incorrectly reported
scaling_cur_freq can be anywhere from wrong to correct.
Example 1: 100% load on all 12 CPUs; acpi-cpufreq; schedutil:
doug@s19:~$ grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:485
/sys/devices
I confirm your findings.
In my case I am using: The intel_pstate CPU frequency scaling driver;
powersave CPU frequency scaling governor; HWP, HardWare Pstate, control
is disabled; A mainline kernel, 6.8-rc1, compiled with the kernel
configuration changes being considered in that other bug report.
For the Stress-NG 0.16.04: pts/stress-ng-1.11.0 [Test: Socket Activity]
I get:
6633.31 Bogo Ops/s on a 1000Hz kernel. 0.9% improvement.
6572.92 Bogo Ops/s on a 250 Hz kernel.
I did this in a hurry, and will re-test tonight or tomorrow.
--
You received this bug notification because you are a mem
Before my post yesterday, I had never used the stress-ng utility, and
only did so to repeat the originally posted test case. However, there
was run to run variability with the stress-ng test that I could not
understand for a 100% user, 0% system, type program. I decided to retest
using one my own C
I found this bug report by accident, while searching for something else.
I pretty much only use mainline kernels and only 1000 Hertz.
I support this proposed default Ubuntu kernel configuration change.
The tick ISR is incredibly efficient (less than 2 uSec on my test
system), and I do not understa
Following up on my initial comment: please ignore my comment about
accessing USB drives. It isn't relevant.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049242
Title:
Public bug reported:
Today I noticed that my two primary Ubuntu boxes were running at high
load. After investigation, I discovered at that unmounting their CIFS
shares alleviating the high load.
I rebooted to the previous kernel, linux-modules-6.2.0-39-generic, and
saw that the load was low afte
Mount options (all names and IPs redacted):
# mount | grep mount-name | sed -e's/,/\n,/g'
//server-name/mount-name on /mnt/mount-name type cifs (rw
,relatime
,vers=3.1.1
,cache=strict
,username=client-name
,domain=domain-name
,uid=0
,noforceuid
,gid=0
,noforcegid
,addr=192.1.1.123
,file_mode=0600
alid
Status in libvirt package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I downloaded the 2021.11.14 daily:
-rw-rwxr--+ 1 doug doug 1277655040 Nov 14 09:12 jammy-live-server-
amd64.iso
I tried to install it as a VM on a debian 11 server host and a
Interestingly, I looked deeper and even before I wrote the comment
above, the patch had already been added to the 5.10 and 5.15 stable
trees. It seems that for some reason it wasn't added to the 5.4 tree.
Weird...I wonder if it doesn't cleanly apply or something.
--
You received this bug notifica
Technically this fix hasn't actually landed in an official kernel yet.
Right now they are in the part of the cycle where they release weekly
release candidate builds of 5.17. This fix first showed up in v5.17-rc3.
I would expect v5.17-rc6 to be released today, and the final 5.17 to be
released in (
I believe this bug was caused by this commit in the kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/usb/quirks-
table.h?id=48827e1d6af58f219e89c7ec08dccbca28c7694e
A patch to fix the issue was committed to the kernel 11 days ago:
https://git.kernel.org/pub
Hi Chris,
Not sure I understand how this worked but I ran the below command after
doing a bit of research and after rebooting the wifi started working again.
"sudo modprobe cfg80211"
A quick search showed this on the system:
doug@doug-Latitude-E6430:~$ ls -l
/lib/modules/5.4.0-96-
Hi Chris,
I guess I got the module name wrong. At any rate my broadcom wifi is
broken after the last patch. This is about the tenth time this has
happened. I think I'm going to switch to a different distro until this
gets resolved.
Thanks,
Doug
doug@doug-Latitude-E6430:~$ apport-co
Public bug reported:
uname -r 5.4.0-94-lowlatency
lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
Booting under previous kernel (5.4.0-92-lowlatency) does not resolve the
issue.
lspci -vnn | grep Network
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gig
I would still likes to know what MSR 0x64F says, as per comment #20.
Yes, thermald should have been disabled for all of this stuff, and I
thought it was.
Recall one the askubuntu threads, where I suggested writing 0x4005C to
MSR 0x1FC. Do so at your own risk.
Your hardware seems to have issues,
Your processor is indicating this:
PROCHOT# or FORCEPR# Event (bit 2, RO) — Indicates whether PROCHOT# or FORCEPR#
is being
asserted by another agent on the platform.
The related sticky log bit is also set.
This is something I suspected a couple of months ago, on one of those
askubuntu threads.
Sorry, 0x16f was wrong, it should have been 0x64F. I have no idea why
you are doing strace on this stuff. Since you haven't used my decoder,
it will be sometime before I manually decode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ther
ts to indicate the reasons it is
throttling, which is the next place to look. Myself, I am tried of
decoding the common MSR bits, so I wrote a decoder. It is at (coded so
as to avoid bots):
double u double u double u dot smythies dot com /~doug/temp_kernel/
Both the c code and compiled, msr-decoder.c
r
When the frequency seems stuck at 800 MHz, then please put a load on a
CPU and look at the pstate request and granted MSR's.
Example, where I force CPU 2:
$ taskset -c 2 yes > /dev/null
and then look at the request and granted pstates:
$ sudo rdmsr --bitfield 15:8 -u -a 0x199
8
8
48
8
30
8
8
8
Try changing to the powersave governor. If something else set another
pstate request and the intel_pstate driver doesn't know about it, then
with the performance governor it might never send a new pstate request.
All of this is very similar to a few months ago, on askubuntu and the path of
invest
If the intel_pstate scaling driver is "active" then "powersave" is the
default governor. If the driver "passive" or the is the acpi-cpufreq
driver during boot, then the default governor will be "ondemand". Note
that "active-powersave" is crudely the equivalent of "passive-ondemand".
You can elimina
He is using the intel_pstate CPU frequency scaling driver. Now by
default processors without HWP will boot into the intel_pstate driver in
passive mode (A.K.A. intel_cpufreq).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubu
ore information is saved as:
# /home/doug/sguide-1310/cg01/hs_err_pid2950.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
#
Aborted (core dumped)
make: *** [serverguide-
Verified with 5.13.0-1007.
** Tags added: cqa-verified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1938298
Title:
[EHL][Graphic]Removing force probe protection from EHL pl
Verified fixed with 5.13.0-1007.
** Tags added: cqa-verified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1938413
Title:
[ehl] Shutdown hangs on board
Status in intel:
Fix Co
TGL-Aaeon:
20.04LTS Desktop: Detects both interfaces and allows them to get an IP#
when you plug in a cable.
IOTG Desktop (Oct. 13 build): Detects both interfaces and allows them to
get an IP# when you plug in a cable. (Desktop Manual network tests
pass.)
IOTG Core (Oct. 14 build): If you perfor
I see this same behavior on the TGL-Aaeon running Core.
I even tried to manually edit /etc/netplan/00-snapd-config.yaml but I
could not make it bring the interface up.
When the cable is plugged in the link lights are on but the system
doesn't seem to acknowledge the connection.
The other port wo
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1936903
Title:
CDTS Network (Ethernet) failures
Status in intel:
New
Status in Ubuntu:
Incomplete
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1936899
Title:
[IoTG] [TGL-H] TPM tests fail
Status in intel:
Invalid
Status in linux-intel package
Public bug reported:
Laptop: Dell XPS-15-9500
OS: Ubuntu Desktop 20.04.3
I plugged in the headphones while watching a video in Firefox.
I expected Ubuntu to detect the headphones and use them for audio
output.
Instead the laptop's built-in speakers continued to be used.
Audio settings did not
Actually I made a mistake. I filed these with iotg-focal-
desktop-20210706.img
This is the only image I've used on the EHL board. I got confused with
the TGL-H board which I've used both Desktop and Core.
So, What is the old kernel you want me to use?
--
You received this bug notification beca
Which is the Old Kernel you want me to try?
All these bugs were filed using
iotg-focal-core-20210722.img (5.11.0-1011-intel)
I then used the patch you gave me on this kernel and retested.
I have managed to have the system hang on booting after a shutdown
twice, but after another 10 shutdowns, it
I spoke too soon.
If you continually shutdown/boot the system, it will hang, about 20% of
the time, at the splash screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1938413
Titl
System shuts down properly after this workaround. Fan stops, board LEDs
remain on (system has no LED power indicator.) System boots properly
upon unplugging/plugging back in.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in
Applied the patch as instructed in
https://bugs.launchpad.net/bugs/1938413:
Hi @Doug,
Please use this test kernel to verify this issue.
version: 5.11.0-1011-intel #12+lp1938408~lp1938413
[Installation steps]
1. tar -zxvf revert.tgz
2. cd revert
3. sudo dpkg -i *.deb
After the patch was
This is still an issue all the way up to 21.04. Debian finally turned on
dummy_hcd in their kernel fairly recently:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868771
https://salsa.debian.org/kernel-team/linux/-/commit/1ae90a1f1c938c83abadfb80733a07a1e314a0b5
** Bug watch added: Debian Bug
Within the context of this bug report it is valid, as it is specifically
about the mainline PPA.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
When we try to help people, either here on launchpad or on forums, very
often we would like them to try the latest mainline kernel, just as a
test to determine if the issue has already been fixed upstream. This bug
prevents that useful option for previous Ubuntu versions.
This dependency should be
I think commit c592cca3691db causes MCE IR remotes to spuriously repeat
keys.
A few users on the mythtv-users list have been experiencing problems after
upgrading to 5.8.0-49 and later.
I reverted the changes in the following files:
* drivers/media/rc/ir-mce_kbd-decoder.c
* drivers/media
I was able to run the ubuntu-drivers install command without problems on
a liveusb (kubuntu 20.04, the same as my system). There seems to be
something wrong with my installation. I'm sorry for posting this as a
bug.
--
You received this bug notification because you are a member of Kernel
Packag
Public bug reported:
Following the latest update of nvidia-drivers-460, my second monitor
stopped working. I purged that package and attempted to reinstall with
ubuntu-drivers autoinstall. The following error occured:
linux-modules-nvidia-460-generic : Depends: nvidia-kernel-common-460 (<=
460.
Public bug reported:
Modern Intel Processors (since Skylake) with HWP (HardWare Pstate)
control enabled and Idle State 2, C1E, enabled can incorrectly drop the
CPU frequency with an extremely slow recovery time.
The fault is not within HWP itself, but within the internal idle
detection logic. One
*** This bug is a duplicate of bug 1910496 ***
https://bugs.launchpad.net/bugs/1910496
Public bug reported:
The crash occurred during apt-get upgrade.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-440 440.100-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-34.37~2
*** This bug is a duplicate of bug 1910496 ***
https://bugs.launchpad.net/bugs/1910496
Public bug reported:
The crash occurred during apt-get upgrade.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-440 440.100-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-34.37~2
Not an issue here on my optimus laptop (slightly aged as latest laptop
is nvidia only
$ uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-48-generic #52~18.04.1-Ubuntu SMP Thu Sep
10 12:50:22
For what it's worth, the versions of things in my test computers, all
servers, no GUI:
name: serv-ff (a 20.04 VM, that has not had an update since around February
12th):
initramfs-tools: 0.133ubuntu14
kmod; 26-3ubuntu1
name: s18 (a physical i5-9600K based computer, up to date as of a few days ag
** Changed in: kmod (Ubuntu)
Status: New => 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/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() c
I have a 20.04 VM that I had not run for awhile (Feb 12th). It has kmod
version 26-3ubuntu1, and installed mainline kernel
5.6.0-050600rc4-lowlatency fine.
The other two physical 20.04 test servers have kmod version 27-1ubuntu1,
and both spew the error 5600 times during kernel installation the fir
per module):
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not
open builtin file '/home/doug/temp-k-git/linux/debian/linux-
image/lib/modules/5.6.0-rc4-stock/modules.builtin.bin'
but the file is there (well, afterwards at least).
I didn't notice this with kern
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
t.
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
t.
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
-
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
PRIME Synchro
set either thru kernel parameter or a modeprobe.d file.
reboot.
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_6
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
PRIME Synchro
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
.
reboot.
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
-
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
PRIME Synchro
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
PRIME Synchro
obe.d file.
reboot.
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchro
t.
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
PRIME Synchro
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
ep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PRIME Synchronization: 0
PRIME Synchronization: 1
PRIME Synchroniza
all 440 driver
Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file.
reboot.
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP M
ither thru kernel parameter or a modeprobe.d file.
reboot.
Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16
22:34:19 UTC 2019 x86_64 x8
must already be loaded). Example (requested, granted,
100% load on CPU 3):
root@s15:/home/doug/temp-git-git# rdmsr --bitfield 15:8 -d -a 0x199
16
16
16
38
16
16
16
16
root@s15:/home/doug/temp-git-git# rdmsr --bitfield 15:8 -d -a 0x198
36
35
36
36
36
36
36
36
Where 38 is the max and 16 in the min
There is only one PLL (Phase Locked Loop) in the processor, all CPUs get
the resulting clock. When they go into deep idle states (deeper than C1,
at least for my processor) then they give up their vote into the PLL as
to what the frequency should be. Your single 100% task is dedicating the
CPU freq
@Davide Sangalli: What you describe and show in your comment #80 is
correct and exactly what should happen. Your processor is spending an
extraordinary amount of time in C1 as opposed to deeper idle states. At
what sampling frequency do you run i7z? I would suggest once every 15
seconds or so, so t
Ever since the default changed to never blanking the screen, and after I
whined in comment #18 above, I have been running this in
/etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT=" consoleblank=300 "
always save a copy of grub first, and do "sudo update-grub afterwards",
then re-boot.
--
You recei
Public bug reported:
There are 4 possibly problem points, placement, names, tooltips, help.
The 1st 3 are somewhat linked.
The new profile, NVIDIA On-Demand is currently placed between the 2 previous &
historical ones of NVIDIA.. & Intel..
The placement and name could lead one to believe that it
This isn't x86 specific, ppc64el is similarly affected
** Tags removed: amd64 cosmic
** Tags added: verification-done-cosmic
--
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/1845704
Title:
Public bug reported:
[Impact]
Xen guest time is not stable after a migration.
[Test Case]
Create a Xen guest and migrate it. Check dmesg.
[ 187.249951] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 187.251137] OOM killer disabled.
[ 187.251137] Freezing remaining freezable
This is fixed in bionic with Ubuntu-4.15.0-59.66. Looking to get this
ported into 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/1845033
Title:
xenbus: Avoid deadlock during susp
Public bug reported:
[Impact]
Xen guests may hang during resume after a migration or suspend.
[Test Case]
Create a Xen guest and run this script and then suspending the VM:
import pyxs, time
c = pyxs.client.Client(xen_bus_path="/dev/xen/xenbus")
c.connect()
c.transaction()
ti
** 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/1844201
Title:
turbostat is over constrained by dependencies
Status
You do not need any logs for this bug report.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1844201
Title:
turbostat is o
Public bug reported:
For processors on which it works, turbostat is a very very good
diagnostic tool. For many upstream escalations, it is the preferred
tool. However the Ubuntu implementation doesn't actually execute
turbostat directly, but rather goes to some script with incredibly
tight, and un
the source code for the serverguide is migrating to a different markup
language for 20.04. The migration was done a few days before these
revisions were committed. They need to be copied to the new source. I am
attempting to add "target to series" stuff to this bug report, but it is
not working, li
Several posters are asking for the mainline builds to be fixed. The
mainline builds are an exact reflection of the upstream git master
repositories. Therefore they have to wait for Seth's patch submission,
which has been picked up and accepted by the kbuild team, to propagate
it's way to the mainli
This is duplicate with bug 1830961.
--
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/1836373
Title:
Mainline builds for 5.1 and 5.2 failing for amd64 and i386
Status in linux package in U
If I make the same changes to the Makefile as per the link in comment
#16, then the kernel compiles fine and without the zillions of warnings
I mentioned in comment #13. However I can not find this anywhere
"upstream" as the notes seem to indicate.
doug@serv-ee:~/temp-k-git/linux$ git
Being duped here with a more specific bug, i.e
19.10
optimus hardware
No login to ubuntu session possible with gdm, lightdm is ok
Maybe a few comments.
This bug orig. suggests that one could actually login on optimus hardware with
nvidia-drm.modeset=1 thru gdm. That was once the case, it no
18.04
> Package: linux-image-4.15.0-26-generic 4.15.0-26.28
> ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18
> Uname: Linux 4.15.0-26-generic x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.9-0ubuntu7.2
> Architecture: amd64
> AudioDevicesInUs
ii screen-resolution-extra0.17.4 all Extension for the
GNOME screen resolution applet
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1822937
Title:
NVIDIA setting
What one would see from terminal (pkexec ls works fine)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in
activate_name_owner
return self.get_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owne
/dev/snd/controlC0: doug 1705 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 31 11:48:02 2019
InstallationDate: Installed on 2019-03-15 (16 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312)
Lsusb:
Bus 002 Device 002: ID 125f:a3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: doug 1705 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 31 11:48:02 2019
InstallationDate: Installed on 2019-03-15 (16 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - A
Public bug reported:
Test case
Install nvidia-410 driver, enable Nvidia DRM KMS, reboot
Log into wayland session
What should happen: Get nvidia driver rendering
What does happen:
If using hybrid hardware then it falls back to Intel device
If using recent nvidia gpu hardware only (10xx and newer)
This update breaks the use of nvidia drivers in both 14.04 & 16.04
See https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1816768
** Tags removed: verification-done-xenial
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member o
Yeah, appears this kernel update is in proposed for both 14.04 & 16.04.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794
So if it's intended to be promoted the nvidia driver should be fixed..
** Tags added: xenial
--
You received this bug notification because you are a member of Ker
Public bug reported:
With the update to linux-meta-lts-xenial (4.4.0.143.124 nvidia fails to
load. Reinstalling the driver (nvidia-384) shows this
Building initial module for 4.4.0-143-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/nvidia-384.0.crash'
Error! Bad return
1 - 100 of 321 matches
Mail list logo
