Public bug reported:
While debugging a bug 1945868 I found something that I think is a separate
issue to that original report, hence this new bug.
I found the virtio-net behavior changing in an unexpected way in
5.4.0-89-generic that is currently in Focal-proposed.
1. 5.4.0-86-generic
$ sudo et
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530995/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5531000/+files/WifiSyslog.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/bug
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5531001/+files/acpidump.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/19
Hi Markus, thanks for the report.
While the good/bad switch with the kernels suggest a reason in there, knowing
more about the exact configuration of the guest would help in any case. The
reason easily is that myself and million others use virtio-net in focal guests
just fine, so there must be s
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530996/+files/ProcEnviron.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/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530992/+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/1946185
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530997/+files/ProcInterrupts.txt
** Tags removed: apport-collected focal uec-images
** Tags added: regression-proposed
--
You received this bug notification because you are a me
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530994/+files/Lsusb-v.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/1946
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530991/+files/CurrentDmesg.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
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530998/+files/ProcModules.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/b
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530993/+files/Lspci-vt.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/19
Tagged as regression-proposed because until we know better that is what it
appears to me.
Ran apport-collect to silence the bot complaining about missing details :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1946185/+attachment/5530999/+files/UdevDb.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/1946185
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: focal
--
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/1946185
Title:
large-re
This change was made by a bot.
** Changed in: linux (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/1946183
Title:
[Impish] No HDMI sound (AMD)
Kai-Heng, thank you for providing the test kernel.
Folks, if you need to add pci=nocrs to your kernel-commandline to get
your touchpad to work, please test this kernel:
https://people.canonical.com/~khfeng/lp1878279/
With pci=no_e820 on the kernel commandline (replacing pci=nocrs). If the
touchp
current version in impish seems to build fine with 5.14
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1944417
Tit
Looking at the delta I found this change (referencing the upstream
commit which was received via upstream stable):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dbcf24d153884439dad30484a0e3f02350692e4c
This sounds like LRO should not have been configurable and they
** Summary changed:
- NVIDIA 470 kernel warning
+ NVIDIA 470 kernel WARNING: CPU: 11 PID: 352896 at
/var/lib/dkms/nvidia/470.63.01/build/nvidia-drm/nvidia-drm-drv.c:574
nv_drm_master_set+0x27/0x30 [nvidia_drm]
--
You received this bug notification because you are a member of Kernel
Packages, w
** Summary changed:
- Update the 470 NVIDIA driver
+ Update the 470 NVIDIA driver to 470.74
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1944955
Title:
Update th
Thanks Stefan,
that at least explains why it changed!
I think without knowing broken use-cases I'm ok with it then.
Not what I'd expect to be ok under SRU terms but IIRC it was added in a similar
way back then, so I'm not stopping you to remove/fix it under similar terms.
I'm setting the state to
Also on: 2021.09.27/bionic/linux-azure-4.15/4.15.0-1125.138
(Standard_B1ms, Standard_D48_v3)
** Tags added: hinted
--
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/1836694
Title:
memcg_te
Can someone please retest on Ubuntu 21.10?
http://cdimage.ubuntu.com/daily-live/current/
** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia-grap
Public bug reported:
Starting in impish with nvidia-470 and the latest gdm3 and xwayland
packages, Wayland is fully supported in theory but you never get any
option to select Wayland on the login screen. There is no session menu
and you always get Xorg instead.
WORKAROUND:
Edit /etc/default/grub
I can no longer reproduce this bug. I assume it got fixed at some point,
either intentionally or as a side effect of some other upstream change.
Marking it as invalid – I assume that's the right status for bugs that
can no longer be reproduced?
** Changed in: linux (Ubuntu)
Status: Triaged
Test from AWS:
* 8 minutes to run on H-aws-5.11 a1.medium
* 8 minutes to run on F-aws-5.4 t2.small
* 8 minutes to run on F-aws-5.11 a1.medium
* 8 minutes to run on F-aws-5.11 t2.small
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Is this bug still present in Ubuntu 21.10? If you find slightly
different issues there then we should open new bugs for them.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: Confirmed =>
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=40b4e82c5331e672c023ba15f779e5eee988d89a
--
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/1836694
Title:
memcg_te
Thanks Daniel, how did you enable the driver? That's probably bug
#1943816 if that's a new installation, the issue is that ubuntu-drivers
is the one writing the kms option since
https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.2 but
you only get that set if you enable the driver by
I use:
sudo apt install nvidia-driver-470
out of habit, and also because of bug 1946196.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1946200
Title:
With Nvid
Also it's not a new installation.
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/
Is anyone still seeing a similar issue on current mainline?
** Tags added: sts
--
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/1711407
Title:
unregister_netdevice: waiting for lo to be
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in Linux:
Incomplet
Public bug reported:
L2303GL usb to serial chips are not recognised by the pl2303 module in
5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux (the current 21.10 candidate kernel). These
chips are fairly common so it will cause a problem for users.
I repor
It will be fixed in 22.04 at least:
https://git.launchpad.net/~bluetooth/bluez/commit/?h=ubuntu-
next&id=355b9c9e65f0c381aa606b9ce603f4ec70f8dc49
** Changed in: bluez (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (van
This change was made by a bot.
** Changed in: linux (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/1946216
Title:
PL2303GL chips not recognised
Found on:
2021.09.27/bionic/linux-azure-fips/4.15.0-2037.41
2021.09.27/bionic/linux-azure-4.15/4.15.0-1125.138
--
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/1836694
Title:
memcg_test_3
Found on 2021.09.27/trusty/linux-azure/4.15.0-1125.138~14.04.1
--
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/1821905
Title:
umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4
Status
Found on:
2021.09.27/trusty/linux-azure/4.15.0-1125.138~14.04.1
2021.09.27/bionic/linux-azure-fips/4.15.0-2037.41
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1940261
Title:
ubu
Public bug reported:
== Impact ==
After configuration multipath with io uring virtio_blk module is stuck
== Fix ==
The issue was introduced by one of the stable updates merged in the base kernel
Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced
any more.
commit d67
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://b
Public bug reported:
When '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' exists (after a fresh OS
installation & after updates to the 'linux-firmware' package)--wifi
fails to function:
$ lspci -knn | grep Net -A3
93:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a)
S
The crux of the issue seems to be the use of privileged ports, which are
(and should be) blocked by network ACL in our environment:
The functional server instance is using a non-privileged port 56242:
tcp 0 0 10.99.19.46:56242 10.99.16.151:2049 ESTABLISHED
The non-functional server is trying to u
Alberto, what's the rational to have ubuntu-drivers doing the kms
configuration there? Wouldn't it be more robust to have it in the deb or
generated in the postinst?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-4
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bu
Found on 2021.09.27/bionic/linux-azure-fips/4.15.0-2037.41 only instance
Standard_D48_v3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1831043
Title:
move_pages12 test from ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-oem-5.10 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Impish)
S
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1943923
Title:
Fix i915 warnings on skl_dra
Hey Ian, thanks for the bug report! I'm checking this on AWS.
--
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/1946149
Title:
Bionic/linux-aws Boot failure downgrading from Bionic/linu
Public bug reported:
the esp8266 development boards like wemos D1 mini have an integrated
usb-uart converter which allows to flash/monitor/debug the esp8266 by
usb cable and a tool called esptool on linux, which is either standalone
(esptool package) or integrated into some IDE (platformio + visi
Confirmed it does work to first upgrade bionic/linux-5.4 from
5.4.0-1056-aws to 5.4.0-1058-aws and then update to 4.15.0-1113-aws
--
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/1946149
Today's first report. Is there anything useful in these logs?
** Attachment added: "prevboot-2021-10-06-a.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5531096/+files/prevboot-2021-10-06-a.txt
--
You received this bug notification because
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.
If I remove these patches the instance correctly boots the 4.15 k
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1015.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exist
Tested against 5.14 and 5.11.0-38 on amd64 against the ubuntu ZFS
regression tests, all pass OK.
Marking this as verified.
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-lin
It's been 3 days since I switch to nvidia drivers 460 and there have
been no freeze or crash so far. I really hope that it is not a
coincidence since most freeze/crash seemed to happen randomly.
If this is indeed a problem with the specific version of the nvidia
driver, is there anything I can do
** Changed in: clamav (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown
It looks like it's not a problem with the patchset in general,
maybe it's specific to aws 4.15?
The patchset is in 5.4.0-1058-aws and it booted fine here too.
I'll check the patchset in 4.15.0-1113-aws.
A difference from your comment is that I could _not_ boot it
after 5.4.0-1058-aws, which worke
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
BTW, do you know of the differences between r5.metal and r5.24xlarge?
Per the specs they seem to be the same as in cpu/ram/nic/_nvme_ storage,
but differ in baremetal vs nitro hypervisor?
The reason I ask is because downgrading from 5.4.0-1056-aws to 4.15.0-1113-aws
worked/booted fine on r5.24xla
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
This bug was fixed in the package thermald - 2.4.3-1ubuntu3
---
thermald (2.4.3-1ubuntu3) hirsute; urgency=medium
* AlderLake CPU support (LP: #1942181)
- 0015-Add-AlderLake-cpu-model.patch
- 0016-Update-sysfs-paths-for-Alader-Lake.patch
-- Colin King Mon, 31 Aug 2021 0
You have been subscribed to a public bug:
~$ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04
Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
ZTE Modem USB stick is not recognized. Fails with 'rejecting I/O to dead
** Package changed: ubuntu => linux (Ubuntu)
--
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/1946229
Title:
ZTE Modem USB stick not recognized
Status in linux package in Ubuntu:
New
B
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1946229
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
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/1946249
Title:
Impish update: v5.13.18 upstream stable rel
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
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/1946242
Title:
Impish update: v5.13.15 upstream stable rel
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
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/1946247
Title:
Impish update: v5.13.17 upstream stable rel
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
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/1946245
Title:
Impish update: v5.13.16 upstream stable rel
apport information
** Tags added: apport-collected
** Description changed:
~$ lsb_release -rd
Description: Ubuntu 21.04
Release: 21.04
Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
ZTE Modem USB stick is no
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1946229/+attachment/5531114/+files/CRDA.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Created attachment 1158
broken dsdt from notebook
--
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/1942215
Title:
OOPs on boot: invalid opcode: [#1] SMP NOPTI
Status in Linux:
In P
Today's 2nd crash report. Is there anything useful in these logs?
** Attachment added: "prevboot-2021-10-06-b.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5531117/+files/prevboot-2021-10-06-b.txt
--
You received this bug notification bec
Discovered how do to it, had to add 'cgroup_enable=memory
cgroup_memory=1' to '/ubuntu-seed/cmdline' of the sd card.
--
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/1945369
Title:
memory
Public bug reported:
* Explain the bug(s)
Fix psample compilation issue and add tunnel support
* brief explanation of fixes
Enhance psample
* How to test
Add tc rule with tunnel and sample actions and run traffic. Verify sample
traffic on the sample interface.
* What it could break.
psample co
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1946219
Title:
liburing stops working a
For the record, 4.15.0-1113-aws works in r5.metal w/ kexec.
Booted it 10 times successfully from both 5.4.0-1058-aws
and 4.15.0-1113-aws (itself.)
(not that it was expected to make a difference as the issue
happens on normal boot, which doesn't have previous kernel.)
Right after that, in the sam
Hi mate, thanks for getting back to me, I have checked the dmesg after
touchpad freezing, but I couldn't see anything related to i2c. Any idea?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Hello,
I’d just like to report that I haven’t seen this problem in a while. The
last time I see the “retry page fault” messages in my log was on August 9.
I’ve been using the ‘amdgpu/picasso*‘ files from linux-firmware commit
c46b8c364b82 (“ice: update package file to 1.3.26.0”) so apparently t
Public bug reported:
A Windows 10 iGVT-g guest is crashing if left idle for too long. "Too
long" can mean hours or even minutes with no load. The QEMU command line
is:
/usr/bin/qemu-system-x86_64 -name Windows 10 -nodefaults -M pc,usb=true
-machine kernel_irqchip=on -enable-kvm -mem-prealloc -me
Today's 3rd crash report. Is there anything useful in these logs?
** Attachment added: "prevboot-2021-10-06-c.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5531156/+files/prevboot-2021-10-06-c.txt
--
You received this bug notification bec
You can either:
* Stay on Nvidia-460; or
* Wait and just test each new update of Nvidia-470.xx as it is
released; or
* Report the problem to Nvidia directly.
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Incomplete => New
** Summary changed:
- [nvidia] System freeze
Hello Tim,
thanks for the report, these are actually failing with something like:
Downloading the image index
ERROR: Invalid signature for /tmp/tmp.u1JHG6CYmL/index.asc
And the api_test.py is failing with this issue as well.
I will modify the bug title / description for this.
** Summary
Public bug reported:
Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake
from suspend. It does start running again, but there is no video output. I'm
attaching text for two crashes from kernel log output. First is:
/var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967
Public bug reported:
- This GPU is needed for AMD R21M-P50-50
- amdgpu upstream driver already landed kernel v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
[git.kernel.org]
/* BEIGE_GOBY */
{0x1002, 0x742
The kernel driver targets oem-5.14 and Impish has 5.13, so only Focal is
nominated for now.
** Changed in: linux-firmware (Ubuntu)
Status: New => Won't Fix
** Changed in: linux-firmware (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Focal)
Import
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/linux-firmware-
staging starting from 1.187.19+staging.28
--
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/1946304
Title:
amdgpu
verified linux-firmware/focal-proposed version 1.187.19 has identical
blobs with those tested and proposed.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
On 20.04, I'm getting repeated errors on my system when the nvdidia
drivers are installed. This sequence of errors is logged multiple times
per second:
Oct 7 01:45:29 kangaroo systemd-udevd[499101]: nvidia: Process '/sbin/modprobe
nvidia-drm' failed with exit code 1.
Oct
** Attachment added: "Output of lshw"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946312/+attachment/5531190/+files/lshw
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubu
98 matches
Mail list logo