Using 6.8.0-60 and has the same issue. The video driver workaround
works.
--
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/2091753
Title:
Plymouth fails with kernel 6.8.0-50 to 6.11.0-17
Seems to be a zfs problem. Not raspi specific.
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.11 in Ubuntu.
https://bugs.launchpad.net/bug
** Also affects: linux-raspi (Ubuntu Questing)
Importance: Undecided
Assignee: Juerg Haefliger (juergh)
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/21074
** Changed in: bluez (Ubuntu)
Status: New => Invalid
** Summary changed:
- Logitech MX Anywhere and MX Keys need to re-pair after suspend after
upgrading to 25.04
+ Logitech MX Anywhere and MX Keys need to re-pair after suspend after
upgrading to kernel 6.14
--
You received this bug no
Sadly, systemd 257.6-1ubuntu1 didn't fix this. It only fixed bug
2113455.
This bug has returned after being masked for a while by bug 2113455. To
work around this bug 1970069 in Questing I have to use fsck.mode=skip.
So that sounds very much like a systemd issue still.
** Changed in: systemd (Ub
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Hi Juerg,
Is there any other info you need for this bug?
--
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/2098944
Title:
Failed to achieve more than 80% of the bandwidth on a 100Gbps
co
** Changed in: linux-gke (Ubuntu)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gke in Ubuntu.
https://bugs.launchpad.net/bugs/2113905
Title:
Compile multi-gen LRU in ke
The 6.11 kernel will get the stable paches from 6.12 longterm tree, so
6.11 will include the fix automatically.
Since you are the author of the fix, if you could backport the fix to 6.6
longterm tree, the ubuntu-6.8 kernel will include the fix automatically as well.
thx.
** Changed in: linux
Public bug reported:
SRU Justification
[Impact]
Google has previously requested multi-gen LRU to be disabled due to a bug (see
https://bugs.launchpad.net/bugs/2084716), however, this prevents customers from
opting into usage of multi-gen LRU at all. This bug requests that multi-gen LRU
be buil
** Tags removed: verification-needed-oracular-linux-intel
** Tags added: verification-done-oracular-linux-intel
--
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/2104893
Title:
WARNING: CPU
Booted back into 6.11.0-26-generic, which is the kernel it used to run
before the upgrade, but otherwise with the 25.04 rootfs and bluez 5.79.
The mouse and keyboard worked immediately, just as they used to,
including across reboots, power cycling the devices and suspending the
laptop.
Booted into
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
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/2109993
Title:
v3 uploaded to N/O/P now
--
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/2106394
Title:
[SRU] enable cs42l43 and cs35l56 audio on Intel LNL
Status in HWE Next:
New
Status in a
@heinrich: The boot log shows 0 VS mode imsic files. Is this intentional
?
[ 237.243627] kvm [2917]: AIA available with 0 guest external
interrupts
Can you share your qemu command line for both inner and outer VM ?
--
You received this bug notification because you are a member of Kernel
Packag
Same issue with a Tyan S8056GME-HOV-B and all the Genoas I could test: 9124,
9254, 9454, 9554 and 9654.
Adding "blacklist ae4dma" to /etc/modprobe.d/blacklist.conf fixes the issue.
A similar issue was mentioned in
https://lore.kernel.org/lkml/38868fe1-9194-4346-b7fd-b8d56e410...@amd.com/ and
pat
you have the nvidia driver installed, no wonder things are broken
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: gtk-engines (Ubuntu)
Status: New => Invalid
** Changed in: gnome-text-editor (Ubuntu)
*** This bug is a duplicate of bug 2073399 ***
https://bugs.launchpad.net/bugs/2073399
Aborting removal of the running kernel
** This bug has been marked a duplicate of bug 2073399
Aborting the removal of the running kernel triggers apport
--
You received this bug notification because yo
Here are the files requested
** Attachment added: "5.15.0-138.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2112145/+attachment/5883169/+files/5.15.0-138.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
zoom crash
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-image-6.11.0-26-generic 6.11.0-26.26~24.04.1
ProcVersionSignature: Ubuntu 6.11.0-26.26~24.04.1-generic 6.11.11
Uname: Linux 6.11.0-26-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.7
Architecture: amd64
** 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/2113756
Title:
Intel Wireless-AC 9260 Bluetooth: Repeated "Invalid exception type"
errors ca
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
This bug is awaiting verification that the linux-intel/6.11.0-1010.10
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-oracular-linux-intel' to 'verification-done-
oracular-linux-intel'
https://people.canonical.com/~hwang4/lp2111521/test10
--
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/2111521
Title:
nvme no longer detected on boot after upgrade to 6.8.0-60
Status in l
This bug was fixed in the package systemd - 257.6-1ubuntu1
---
systemd (257.6-1ubuntu1) questing; urgency=medium
* Merge with Debian unstable (LP: #2112075). Remaining changes:
- debian/tests/boot-and-services: skip apparmor tests on armhf
- debian/systemd.postinst:
+
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encou
** Tags removed: verification-done-oracular
** Tags added: verification-needed-oracular
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2106464
Title:
Change the default output vo
plucky got released by mistake, please test [4] too on noble/oracular
and then mark verified..
** Tags removed: verification-done-oracular-linux
** Tags added: verification-needed-oracular-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encou
Wait, only noble was tested? Test O too, P got released :/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2106464
Title:
Change the default output volume of headphone for Realtek
Here is the second file
** Attachment added: "5.15.0-139.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2112145/+attachment/5883170/+files/5.15.0-139.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
And both of your machines have the pcie root port
8086:2030/8086:2031/8086:2032 for nvme disks, maybe the problem is only
for the combination of (this root port + this nvme disk)?
I will build a test10 kernel with:
diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
index 29883525b1a2..21837434
This bug was fixed in the package alsa-ucm-conf - 1.2.12-1ubuntu1.2
---
alsa-ucm-conf (1.2.12-1ubuntu1.2) plucky; urgency=medium
* Import patches that have already been applied to noble and oracular,
but not yet to plucky. This and previous uploads are dependent on
these pat
This bug was fixed in the package alsa-ucm-conf - 1.2.12-1ubuntu1.2
---
alsa-ucm-conf (1.2.12-1ubuntu1.2) plucky; urgency=medium
* Import patches that have already been applied to noble and oracular,
but not yet to plucky. This and previous uploads are dependent on
these pat
This bug was fixed in the package alsa-ucm-conf - 1.2.12-1ubuntu1.2
---
alsa-ucm-conf (1.2.12-1ubuntu1.2) plucky; urgency=medium
* Import patches that have already been applied to noble and oracular,
but not yet to plucky. This and previous uploads are dependent on
these pat
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Plucky)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Plucky)
Status: New => In Progress
** Changed in: linux (Ubuntu Plucky)
Assignee: (unassigned) => Manuel Diewald (die
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
test9 still had the issue, here's the dmesg.
** Attachment added: "LP2111521-dmesg-test9.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111521/+attachment/5883145/+files/LP2111521-dmesg-test9.txt
--
You received this bug notification because you are a member of Kernel
Packages, w
built a new testing kernel (test9), in the test9, applied the below
trial fix to test8, after testing the test9 kernel, please also upload a
complete dmesg since I put some printk() in the test9:
https://people.canonical.com/~hwang4/lp2111521/test9/
diff --git a/drivers/pci/probe.c b/drivers/pci/
A random occurrence for me after resume from suspend. But regular enough
to be annoying. I'm not 100% sure on timing but this feels like
something that has started happening in the last 1-3 months.
22.04, Dell XPS 13 with usb external keyboard
--
You received this bug notification because you ar
HI, Zixing Liu (liushuyu-011)
Added the data. We are also able to recreate this issue with
6.8.0-60.generic kernel.
Currently, this issue is blocking us from deploying Ubuntu-based hosts
in our production environment.
Moving the issue to "New" from "Incomplete".
Thanks Sarabjot
** Changed
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2112304/+attachment/5883142/+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/2112304/+attachment/5883143/+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/21
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2112304/+attachment/5883137/+files/ProcCpuinfo.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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2112304/+attachment/5883141/+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/2112304
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2112304/+attachment/5883139/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2112304/+attachment/5883135/+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/21
apport information
** Tags added: apport-collected noble
** Description changed:
Steps:
Connect the hosts to the NVMeOF enclosure and run the IOs on the drives.
Observation :
Observing the IO Tool process got blocked continuously, followed by all
drives connected.
*From S
Verified on noble:
linux-firmware:
Installed: 20240318.git3b128b60-0ubuntu2.13
Candidate: 20240318.git3b128b60-0ubuntu2.13
Version table:
*** 20240318.git3b128b60-0ubuntu2.13 2000
400 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
100 /var/lib/dpkg/statu
@Ian,
There should be lines starting with "hh" in your dmesg.
At least there are them in Marks's dmesg.
@Marks,
>From your log, all reset are the type of probing-reset (power on reset),
it's why that the quirk doesn't work here.
>From the line "h", the returned value is
dmesg from booting on test8 attached.
** Attachment added: "LP2111521-dmesg-test8.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111521/+attachment/5883125/+files/LP2111521-dmesg-test8.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
Verified on plucky:
ubuntu@mustang-118102:~$ apt-cache policy linux-firmware
linux-firmware:
Installed: 20250317.git1d4c88ee-0ubuntu1.2
Candidate: 20250317.git1d4c88ee-0ubuntu1.2
Version table:
*** 20250317.git1d4c88ee-0ubuntu1.2 2000
400 http://archive.ubuntu.com/ubuntu plucky-prop
Verified on oracular
ubuntu@mustang-118102:~$ apt-cache policy linux-firmware
linux-firmware:
Installed: 20240913.gita34e7a5f-0ubuntu2.8
Candidate: 20240913.gita34e7a5f-0ubuntu2.8
Version table:
*** 20240913.gita34e7a5f-0ubuntu2.8 2000
400 http://archive.ubuntu.com/ubuntu oracular-p
Public bug reported:
Since kernel v6.7, GRO offloading of UDP-encapsulated ESP packets is
supported. This is enabled for individual UDP sockets via the
UDP_ENCAP_ESPINUDP and UDP_GRO options.
Unfortunately, the original implementation caused issues in some cases.
In particular, if the esp4_offloa
Verified linux-firmware noble-proposed version
20240318.git3b128b60-0ubuntu2.13 and oracular-proposed version
20240913.gita34e7a5f-0ubuntu2.8.
** Tags added: verification-done-noble verification-done-oracular
--
You received this bug notification because you are a member of Kernel
Packages, whic
I think this is the bug I'm experiencing on a computer that I installed
Ubuntu 24.04.2 from scratch on.
The Linux version is 6.11.0-26-generic. Every now and then the screen
randomly starts to flicker, after a while it stops or I have to restart
the computer. Very annoying.
The computer has a UHD
** Changed in: linux-hwe-6.8 (Ubuntu)
Assignee: (unassigned) => Kuba Pawlak (kuba-t-pawlak)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2113674
Title:
package linux-heade
On oracular, issue is reproducible with bluez 5.77-0ubuntu2, not
reproducible with 5.77-0ubuntu2.2, tested with nvidia-driver-570
(570.133.07-0ubuntu0.24.10.1) and Jabra Speak2 55 UC portable conference
speaker.
** Tags removed: verification-needed-oracular
** Tags added: verification-done-oracul
On plucky, issue is reproducible with bluez 5.79-2ubuntu1, not
reproducible with 5.79-2ubuntu1.1, tested with nvidia-driver-570
(570.133.07-0ubuntu2) and Jabra Speak2 55 UC portable conference
speaker.
** Tags removed: verification-needed verification-needed-plucky
** Tags added: verification-don
72 matches
Mail list logo
