Thanks. The only relevant problem I can see there is in the kernel
graphics driver:
[drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
** Summary changed:
- Screen freeze at the moment of login
+ Screen freeze at the moment of login on VirtualBox
** Summary changed:
- Screen freeze
** Also affects: linux-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.15 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17
You have been subscribed to a public bug:
The problem started to appear 2 weeks ago after one of my daily updates.
It also happens after I re-install the system from a freshly downloaded
ISO file. The system freezes at the moment, it starts the gnome display
manager.
I file the bug-report after
@timo, ok, I will add RPL-P as well in the SRU patches.
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Thanks for the bug report.
This appears to be either a hardware problem or a bug in the Nvidia
driver. I think most likely it's due to insufficient HDMI cable
bandwidth. Please ensure you are using an HDMI 2.1 certified cable
capable of at least 40 Gbit/s. An HDMI 2.0 cable will not be good
You have been subscribed to a public bug:
in the setting,when i set a refresh rate>60Hz, there will be a black
screen for about half a minute and the refresh rate is automatically
reset to 60Hz.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature:
@Luke
Thanks for the link! I don't need to prepare for the SRU \o/
We're using the test from tools/testing/selftests/ for ubuntu_kernel_selftests,
so once the patchset was applied we will get the updated test case.
--
You received this bug notification because you are a member of Kernel
It would be great if you can do the following:
(1) Upload a copy of /etc/netplan
(2) Find out where it's stuck. Preferably generate and attach a kernel
crashdump (https://ubuntu.com/server/docs/kernel-crash-dump) or perhaps
the hung_task_panic=1 kernel option will cause it to print out where
it's
I have the same issue. Using Ubuntu 22.04 and also other linux distros.
This guy form Nvidia says that is a a bug ...
https://lore.kernel.org/all/v_ODhOndx3g1l-BhfKGCB6_nLY83LTc5vz1YDrVEVVF5CmgKUs1x9bmROyWXhmYkeQRVVnvfBnyrFyHaEKqtoZE5P7lKJJ1j_vE0J1Piq2Y=@protonmail.com/T/
There is a
** Tags added: originate-from-1989421
--
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/1988461
Title:
intel_pmc_core not load on Raptor Lake
Status in HWE Next:
New
Status in linux
** Tags added: verification-done-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/1984011
Title:
[SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal
Status in linux
Comment from lukenow:
@PHLin The test case should definitely be updated for this, we want that config
** Also affects: qa-regression-testing
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I have the same problem, disabling the fTPM in BIOS solved the
suspending problem.Running kernel 5.15.0-47.
--
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/1970957
Title:
suspend problem
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/1990203
Title:
NMI watchdog: Watchdog
Public bug reported:
After the error message as in the title is output, the computer stops.
After rebooting, the bug was reported through the "apport-bug linux"
command.
It happens about once a day, and I googled it, but couldn't find a
suitable solution.
Also I attach a separate log as per
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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/1990178
Title:
Seemingly random
Public bug reported:
SRU Justification
[Impact]
This is a 2nd attempt with this patch set. The first attempt [1] caused
a regression.
The Hyper-V vPCI driver (pci-hyperv) doesn't work with a PCIe devcie
that supports multiple MSI interrupts (Note: MSI-X has been working
fine). Recently Jeffrey
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 1990156
and then change the status of the bug to 'Confirmed'.
If, due to the
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
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/1990156
Title:
Ubuntu
** Attachment added: "dmesg from a boot which works fine"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990178/+attachment/5617177/+files/dmesg-5.15.0-47-generic-working.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "dmesg from a boot exhibiting the problems mentioned in
the bug report"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990178/+attachment/5617176/+files/dmesg-5.15.0-47-generic-task-blocked.txt
--
You received this bug notification because you are a member of
You have been subscribed to a public bug:
Hi!
We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems.
The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter"
network cards.
When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) the
network
Public bug reported:
I'm running Ubuntu MATE 22.04.1 LTS on a ASUS Vivobook S14 (model number
M3402QA) laptop.
When I boot Ubuntu on my laptop, there is a high probability (I guess
somewhere between 80-90%) that the system "won't work properly." And by
that I mean the following symptoms:
- The
Ah @Po-Hsu Lin didnt see you already found the commit :) FYI the
patchset I sent here https://lists.ubuntu.com/archives/kernel-
team/2022-September/133062.html also includes a new test case for the
initial regression that that patch fixes. Don't know if you need to
update anything with testing for
Public bug reported:
When launching large arm64 instances on the focal or jammy ami, cma
allocation errors appear in the dmesg out:
[0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096
pages, ret: -12
As far as I can tell, this does not impact instance launch in a
meaningful
Public bug reported:
[Impact]
proc_thermal driver is not loaded
[Fix]
Add RPL-S id on device id table of powercap/intel_rapl.
[Test Case]
1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal
[Where problems could occur]
Low, only add RPL-S id on powercap/intel_rap but
Hi Jeff:
Intel Linux Virtualization is preparing to validate Intel Virtualized features
in Ubuntu 22.10.
What kernel and qemu versions can we expect?
From: Lai, Paul C
Sent: Friday, September 16, 2022 7:48 AM
To: Fang, Xun ; Pathi, Pragyansri
; Sethi, Puneet
Subject: RE: Confirm new features
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1990153
Title:
package linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49
We might be missing this patch "ip: fix triggering of 'icmp redirect'"
that I sent to the kt-ML as one of the backport request patchsets from
the Author of that commit that is breaking things. I think applying that
will make the behavior consistent and get those tests to pass.
--
You received
Public bug reported:
Multiple times this issue has occured
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules:
Hi list,
I get this bug, too. It is not related to samba or Fedora, but the
kernel, I assume. Something seems to have changed in the ext4 driver in
the kernel starting with roughly 5.13.
I copy large amount of files and hardlinks onto my filesystem and
suddenly it stops working with the
Focal will also be affected since it contains 5.4.207 which has the
break commit and needs the related fix for it from 5.4.213.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in:
Jeff, Thanks for the quickly providing the test kernel. It passed the
sanity test.
Any ETA of the release build with integration of these patches for our
QA team to verify.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package lttng-modules -
2.10.8-1ubuntu2~18.04.4
---
lttng-modules (2.10.8-1ubuntu2~18.04.4) bionic; urgency=medium
* Backport upstream fix to handle removal of random tracepoints in the
kernel (LP: #1986921):
-
Okay, as this is needed for the new batch of kernels, is verified and no
errors related to the package seem to be present in errors.ubuntu.com,
let me release this earlier.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Test kernel with commit eb55dc09b works as expected:
https://people.canonical.com/~phlin/kernel/lp-1990124-icmp-redirect/
This test is not failing anymore.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: makedumpfile (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
I already opened a new bug for kernel 5.15.0-47-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989941
The previous Kernel 5.15.0-46-generic doesn't show this issue on my
machine.
--
You received this bug notification because you are a member of Kernel
Packages, which is
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 1987595
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Jammy)
This commit seems to be the cause, test passed by reverting it:
commit 07e4bcbce061bb58f109ed746b770adea5914d80
Author: Nicolas Dichtel
Date: Wed Jul 13 13:48:52 2022 +0200
ip: fix dflt addr selection for connected nexthop
BugLink: https://bugs.launchpad.net/bugs/1988351
This issue can be found since J-gkeop 5.15.0-1001
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gkeop in Ubuntu.
https://bugs.launchpad.net/bugs/1990127
Title:
ubuntu_lttng_smoke_test failed with module build on J-gkeop (error:
** Description changed:
Issue found on J-gkeop 5.15.0-1003.5, and this can be reproduced with
J-gkeop 5.15.0-1002 as well.
Build log:
- Running 'cat /var/lib/dkms/lttng-modules/*/build/make.log'
- DKMS make.log for lttng-modules-2.13.1 for kernel 5.15.0-1003-gkeop (x86_64)
- Fri Sep
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 1990124
and then change the status of the bug to 'Confirmed'.
If, due to the
Confirming the fix also works with bionic/linux-hwe-5.4 which builds for
all arches:
* amd64 -
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l/lttng-modules/20220914_114635_72fb4@/log.gz
* arm64 -
: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags: 5.15 jammy sru-20220919 ubuntu-kernel-selftests
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status
** Changed in: linux
Status: Unknown => New
** Changed in: mutter
Status: Unknown => Fix Released
--
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/1990089
Title:
Screen
The same workaround would fix https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4830
** Tags added: dt-651
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4830
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4830
--
You received this bug notification because you are
PipeWire is not supported in 22.04, but it will be supported in 22.10.
Do you still experience this bug without PipeWire in 22.04?
** Tags added: jammy
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Tags added: a2dp
--
You received
** Tags added: kern-4363
--
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/1989941
Title:
Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode
5.15.0-47-generic - Wifi
53 matches
Mail list logo
