'Invalid' for the kernel. It was always Mutter's fault for using a
realtime thread, and itself not being adequately threaded enough to meet
realtime performance deadlines.
The issue remains open in bug 2077216 and bug 2093179, but a universal
fix is coming in Mutter 48 (Ubuntu 25.04).
** Changed
Hello Jeff and Micahel,
We found that Xe and i915 already exist in ubutnu 24.10 version,
will these two drivers be integrated into 24.04.2 verison?
If yes, when will the outlook release?
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Merge proposal linked:
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/478980
** Merge proposal linked:
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/478982
** Merge proposal linked:
https://code.
Xorg might have a heuristic to ignore simpledrm if something else
exists. But now I'm just guessing...
If 6.8 has regressed I'll update bug 2083329 to show that better.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drive
Cover Letter:
https://lists.ubuntu.com/archives/kernel-team/2025-January/156198.html
Patches:
https://lists.ubuntu.com/archives/kernel-team/2025-January/156199.html
https://lists.ubuntu.com/archives/kernel-team/2025-January/156201.html
https://lists.ubuntu.com/archives/kernel-team/2025-January/1562
Sapphire Rapids Intel(R) Xeon(R) Platinum 8468
22.04 LTS Jammy
5.15.0-130-generic
Outside VM
cpuid 2700
cpuid 2822
cpuid 2699
cpuid 2698
cpuid 2698
Inside VM
cpuid 51108
cpuid 54513
cpuid 51389
cpuid 53783
cpuid 53998
5.15.0-130-generic+TEST403286v20250107b1
Outside VM
cpuid 2752
cpuid 2771
cp
Could you please document the testing (particularly: the versions
tested) done to verify this update? As the acceptance comment says:
"If this package fixes the bug for you, please add a comment to this
bug, mentioning the version of the package you tested, what testing has
been performed on the p
Not sure I have a general answer to that. My personal solution is to
ensure my networks have different names for each frequency, and don't
join the 2.4GHz ones unless it's absolutely necessary.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Sapphire Rapids Intel(R) Xeon(R) Platinum 8468
24.10 Oracular
6.11.0-13-generic
Outside VM
cpuid 3307
cpuid 3384
cpuid 3348
cpuid 3374
cpuid 3280
Inside VM
cpuid 67659
cpuid 67748
cpuid 69626
cpuid 67772
cpuid 65224
6.11.0-13-generic+TEST403286v20250107b1
Outside VM
cpuid 3450
cpuid 3499
cpuid
Sapphire Rapids Intel(R) Xeon(R) Platinum 8468
24.04 LTS Noble
6.8.0-51-generic
Outside VM
cpuid 3527
cpuid 3384
cpuid 3467
cpuid 3300
cpuid 3544
Inside VM
cpuid 68395
cpuid 58364
cpuid 65254
cpuid 68554
cpuid 66905
6.8.0-51-generic+TEST403286v20250107b1
Outside VM
cpuid 3253
cpuid 3416
cpuid
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2093146
[Impact]
The CPUID instruction is particularly slow on newer generation processors,
with Intel's Emerald Rapids processor taking significantly longer to execute
CPUID than Skylake or Icelake.
This introdu
Thank you for running those tests. Just a quick ping to let you know I'm
still looking into this. My next thought was a kernel bisect, but I was
having some issues mapping between the upstream version tags and what's
in our repos. Let me consult with a colleague tomorrow to see if I can
get to the
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2093146
[Impact]
The CPUID instruction is particularly slow on newer generation processors,
with Intel's Emerald Rapids processor taking significantly longer to execute
CPUID than Skylake or Icelake.
This introdu
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2093146
[Impact]
The CPUID instruction is particularly slow on newer generation processors,
with Intel's Emerald Rapids processor taking significantly longer to execute
CPUID than Skylake or Icelake.
This introdu
** Changed in: gnome-control-center
Status: New => 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/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default,
I've validated this with the test case from the description. A local run
of the ZFS test suite with the package from -proposed also points to
this issue being fixed, so I'm marking this as verified.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a me
kernels 6.8.0-50 and 6.8.0-51 have regressed, for the same reasons as
kernel 6.11: the simple-framebuffer device in sysfs is no longer at
/sys/devices/platform/simple-framebuffer.0 (comment #99)
But for some reason, I only get a phantom display in Wayland. Instead,
comment #29 previously mentioned
Hi Kimse (0-kh),
> When I connect an external display via HDMI to my laptop, the entire
system locks up for approximately 30 seconds, and the external display
is never detected. However, if I boot the machine with the external HDMI
display already connected, there are no issues, then the display w
** Tags removed: sru-next
--
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/1988018
Title:
[SRU][mlx5] Intermittent VF-LAG activation failure
Status in linux package in Ubuntu:
Fix Commi
I have met the same questions. I tried many times to reinstall Ubuntu
including 24.04 and 22.04.5 but failed. I have installed 22.04.4 with
kernel 6.5.018 and it worked very well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
I tested netplan.io 0.107.1-3ubuntu0.22.04.2 from jammy-proposed, all looking
good!
The intermittent failures reported in comment #12 are resolved.
First of all, the eswitch/switchdev functionality is not available on Jammy's
GA 5.15 kernel,
so I upgraded to the HWE kernel and installed Netplan
** Attachment added: "dmesg_OK.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059738/+attachment/5850118/+files/dmesg_OK.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/2
Here the same.
Neither poweroff nor reboot works.
I had to use SysReq-SUB to reboot (power off is not working via SysReq, too).
dmesg shows some entries with BUG Oops and RIP
After I blacklist module nouveau in /etc/modprobe.d/blacklist.conf, execute the
commands:
>grub-mkconfig -o /boot/grub/grub
How do you prevent the machine from using 2.4GHz? It seems that they
removed that selector from the plasma nm client.
--
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/2092655
Title:
Audio
Public bug reported:
Multiple display freezes and/or gnome session crashes since upgrade to 24.10
seems related to nouveau driver
2025-01-07T09:11:14.611749+01:00 pc1 kernel: nouveau :01:00.0: fifo: fault
00 [READ] at 00140785b000 engine 00 [GR] client 02 [GPC0/PE_0] reason 00
[PDE] on
This bug was fixed in the package firmware-sof - 2023.12.1-1ubuntu1.3
---
firmware-sof (2023.12.1-1ubuntu1.3) noble; urgency=medium
* Add missing sof firmware for Dell GhostRider platform. (LP: #2086250)
- Add missing links for SOF v2.11.1 signed Intel binaries
- Add new 2.1
The verification of the Stable Release Update for firmware-sof 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 encoun
This bug was fixed in the package firmware-sof - 2023.12.1-1ubuntu1.3
---
firmware-sof (2023.12.1-1ubuntu1.3) noble; urgency=medium
* Add missing sof firmware for Dell GhostRider platform. (LP: #2086250)
- Add missing links for SOF v2.11.1 signed Intel binaries
- Add new 2.1
This bug was fixed in the package firmware-sof - 2023.12.1-1ubuntu1.3
---
firmware-sof (2023.12.1-1ubuntu1.3) noble; urgency=medium
* Add missing sof firmware for Dell GhostRider platform. (LP: #2086250)
- Add missing links for SOF v2.11.1 signed Intel binaries
- Add new 2.1
The verification of the Stable Release Update for firmware-sof 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 encoun
The verification of the Stable Release Update for firmware-sof 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 encoun
** Changed in: linux-oem-6.11 (Ubuntu Plucky)
Status: New => Invalid
** Changed in: linux-oem-6.11 (Ubuntu Oracular)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://bugs
** Changed in: linux-oem-6.11 (Ubuntu)
Status: In Progress => Invalid
--
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/2089891
Title:
[SRU] Add audio rt713 and rt718 support on Thin
That said, "Input/output error" suggests the hard disk is faulty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2093165
Title:
package bluez 4.101-0ubuntu13.3 failed to install/upgrade:
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
plucky is already based on 6.12, so this is fixed there
** Changed in: linux (Ubuntu Plucky)
Status: In Progress => 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/20875
** Package changed: ubuntu => bluez (Ubuntu)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2093165
Title:
package bluez 4.101-0ubuntu13.3 failed t
** Tags added: amd oem-priority originate-from-2092170
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Sta
MR for firmware-sof
Noble:
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/478980
Oracular:
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/478982
Plucky:
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmwa
You have been subscribed to a public bug:
install packages have unmet dependencies
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bluez 4.101-0ubuntu13.3
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-210-generic i686
ApportVersion: 2.20.1-0ubuntu2.30
Arc
Verified on GSR4P-DVT1-C1X_202409-35546 by linux-oem-6.11/6.11.0-1010.10
kernel with the (alsa-ucm-conf 1.2.10-1ubuntu5.4 + firmware-
sof/2023.12.1-1ubuntu1.3). And same kernel with alsa-ucm-
conf/1.2.10-1ubuntu6.3 + firmware-sof/2024.06-1ubuntu1.2). Audio
features verified pass.
aplay -l shows c
Public bug reported:
The context of it is a security risk that user turns off microphone in
BIOS on Lenovo system but it still works in Ubuntu. The patch fixes it
to look at what BIOS changes to decide whether to enable microphone.
*
https://github.com/torvalds/linux/commit/88438444f0244c8b2
Nominated for the older series as this still needs fixing. Working on
it...
** Also affects: apport (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux-base (Ubuntu Oracular)
Hi! Not a suspebd/resume issue. I think this might be caused by fwupd
somehow. As it's a work laptop I'll need to check if I can try mainline
in it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launc
included in 6.13
--
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/2085406
Title:
[SRU] add support of QCA BT 0489:e0fc
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
6.12 is already uploaded to the ppa
** Changed in: linux (Ubuntu Plucky)
Status: In Progress => 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/2089556
Title:
Enable
I've just updated to kernel 6.8.0-51, but it suffers from the same
issue. I'm attaching full boot logs from journalctl -b.
** Attachment added: "Boot logs for kernel 6.8.0-51 from journalctl -b"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092703/+attachment/5849970/+files/kernel-6.8.
Another thing worth trying is to disable Bluetooth rescanning:
bluetoothctl
scan off
quit
--
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/2092655
Title:
Audio dropouts with bluetoo
The first thing I would do is make sure the machine is not trying to use
a 2.4GHz wifi network at the same time.
--
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/2092655
Title:
Audio dropo
This looks like the primary issue:
bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start:
Connection timed out (110)
So it sounds like a kernel/buffering/hardware/environment problem. Just
because BlueZ is the first to report the issue doesn't make it a BlueZ
bug.
** Tags added: a2d
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
This bug is awaiting verification that the linux-mtk/5.15.0-1036.43
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
62 matches
Mail list logo
