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
Public bug reported:
SRU Justification:
[Impact]
This is a cherry-pick fix from upstream to drop Tx network packet when Tx
TmFIFO is full.
[Fix]
Starting from Linux 5.16 kernel, Tx timeout mechanism was added
in the virtio_net driver which prints the "Tx timeout" warning
message
** Also affects: linux-oem-6.5 (Ubuntu Noble)
Importance: Medium
Assignee: Andy Chi (andch)
Status: Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051846
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:
** Merge proposal linked:
https://code.launchpad.net/~dannf/livecd-rootfs/+git/livecd-rootfs/+merge/459549
--
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/2045586
Title:
The test passed w/ flock as well:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-loop/noble/amd64/l/livecd-rootfs/20240131_104633_df869@/log.gz
274 successful iterations before the timeout killed it.
I've updated the MP:
@Sunit: use the PPA until(if?) Ubuntu fixes this:
https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
** Tags added: architecture-ppc64le bugnameltc-205066 severity-medium
targetmilestone-inin---
--
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/2049924
Title:
WireGuard broken on Noble
The patch seems be accepted and will be merged to v6.9.
We'll skip this fix on Mantic as the patchset grouth and affects all PCI
devices, and will try backporting it to Noble kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
It's only a workaround. Sometimes workarounds force you to use older
software.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Title:
nvidia-dkms-*
** Package changed: linux-oem-6.1 (Ubuntu) => pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2051895
Title:
Lenovo XT99 BT headset can't work in HFP profile
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Noble)
Status: New =>
Public bug reported:
[Summary]
When use the ThinkPluse xt99 bluetooth head set to run the test
com.canonical.certification::bluetooth/audio_record_playback, it cannot record
the sound and playback.
It seems this device cannot switch to Hand free mode in this platform.
[Steps to reproduce]
@Robie,
The proposed patches, binaries are first included in intermediate PPAs
meant for oem integration since the day it's confirmed effective for the
issue, and then SRU process proceeds to ensure these changes will be
included in targeted milestones. That is, while -proposed packages for
** Tags added: oem-priority originate-from-2044064 somerville
--
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/2051896
Title:
Fix spurious wakeup caused by Cirque touchpad
Status in HWE
If you need nvidia-390 on 22.04 then the best workaround I can suggest
is to boot an older kernel like 6.2 instead.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
BTW bug 2050743 is making the situation worse on noble. It will be fixed
shortly.
--
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/1970069
Title:
Annoying boot messages interfering with
** Bug watch added: Mozilla Bugzilla #1876614
https://bugzilla.mozilla.org/show_bug.cgi?id=1876614
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1876614
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
I have the same problem and every time I upgrade systemd, it kills my
network access to the server. I therefore had to disable automatic
updates and always run a shutdown -r 10 command before upgrading
--
You received this bug notification because you are a member of Kernel
Packages, which is
@vanvugt: Isn't 6.2 EOL now though?
https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Public bug reported:
[Impact]
Spurious wakeup event caused by Cirque touchpad, prevent the system from
sleep properly.
[Fix]
Skip SET_POWER SLEEP so there won't be any IRQ raised by the touchpad.
[Test]
Suspend the system 100 times and make sure non of the wakeup event is
caused by the touchpad
Testing was done with the Ubuntu 22.04.1 ISO, booted off disk, no persistence.
The Nvidia GPU was an RTX 3080 (mobile).
The gcc-12 and the generic hwe packages were installed, then the Nvidia
driver 535 selected in the Software & Updates/Additional Drivers tab. Clicked
the apply button, and the
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: noble
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5
Status changed to 'Confirmed' because the bug affects multiple users.
** 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-hwe-6.5 in Ubuntu.
Also confirmed on Noble, same machine.
The workaround in comment #3 seems to work, but so does just changing
the refresh rate in Settings to the *other* 120Hz mode. After that the
bug doesn't occur no matter how many times I change the refresh rate.
The screen is advertised as "48-120 Hz" in
Not enough information.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2051763
Title:
RTL8821CE did not work
Status in
> You could detect both parameters to avoid that corner case.
Sure one can check for "splash nomodeset" to avoid the confusion in most
cases, but that wouldn't fix it for "splash $DRIVER.modeset=0" or less
common architectures which might have no primary framebuffer. I guess we
can tell people
** Description changed:
[Impact]
Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs.
mt8370-evk (G510):
https://github.com/alsa-project/alsa-ucm-conf/pull/380
https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97
** Patch added: "noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+attachment/5744075/+files/noble.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
** Changed in: linux (Ubuntu Mantic)
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/2051129
Title:
Mantic update: v6.5.12 upstream stable
** Changed in: linux (Ubuntu Mantic)
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/2051142
Title:
Mantic update: v6.5.13 upstream stable
@Robert thanks for keeping this bug alive and updated!
1) More debug info required?
@Robert, reading your post
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/50 again,
I am wondering if you asked me to provided more debug info with NVM 4.4 on my
E810 NICs? Would this
This issue exists in ubuntu 22.04 desktop after the kernel is upgraded
to Linux version 6.5.0-15-generic.
--
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/2037490
Title:
UBSAN:
[7.182980]
[7.187100] UBSAN: array-index-out-of-bounds in
/build/linux-hwe-6.5-BV4m5T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptsas.c:2446:22
[7.192943] index 1 is out of range for type
Nominating for focal means the 5.4 GA kernel version. Which is not
affected.
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Also affects: linux-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.15 (Ubuntu Jammy)
Status: New =>
Fix was upstream v6.7-rc5.
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: New => Triaged
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Noble)
Status: New =>
Hmm, no plymouthd isn't starting quite early enough in Noble:
2.799s - plymouthd starts
4.080s - first show-splash attempt (rejected because DRM hasn't started yet)
5.290s - found /dev/dri/card0
5.364s - showing splash screen
What this means is that any attempt to fix the bug in plymouthd itself
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.26 and linux-oem-6.5/jammy-proposed
version 6.5.0-1014.15.
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-6.5 (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
** Changed in: linux (Ubuntu Mantic)
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/2051117
Title:
Mantic update: v6.5.11 upstream stable
My bad that's 6.6, not 6.9. I'll backport it asap so that will be in the
next cycle
--
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/2049027
Title:
The display becomes
> Note also, in my case, the CPU frequencies actually seem to be scaling
properly, it is just that they are not being reported properly via
"/sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq".
To be clear, I cannot be sure whether that was also the case in my
testing. I didn't test the actual
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051584 is picking 6.6
which includes the fix.
And it's going to be included for the next cycle for mantic and therefore
hwe-6.5.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
** Description changed:
- It is exactly this bug:
- https://gitlab.freedesktop.org/drm/intel/-/issues/8685
+
+ SRU Justification:
+
+ [Impact]
+
+ Multiple users have reported frozen displays when external HDMI device
+ is connected on systems with intel graphics chipsets.
+
+ [Fix]
+
+ *
** Description changed:
- This is with the kernel from jammy-proposed (linux-
- image-5.15.0-94-generic 5.15.0-94.104).
+ SRU Justification:
+
+ [Impact]
+
+ * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
+ but now returns EINVAL, breaking partprobe due to commit
+
** Changed in: linux (Ubuntu Mantic)
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/2051231
Title:
Mantic update: upstream stable patchset
Skipped "net: tls, update curr on splice as well" because it is already
applied as CVE-2024-0646.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-0646
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification
A new attempt at a kernel patch. While this is pleasingly simple and
reliable in my own testing, it has a bug when "splash" is used at the
same time as there being no primary framebuffer (like with "nomodeset").
I'm not sure if that's a realistic concern and am reluctant to go back
to delays to
Skipped (already applied as CVE-2024-0582):
- io_uring: enable io_mem_alloc/free to be used in other parts
- io_uring/kbuf: defer release of mapped buffer rings
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-0582
** Changed in: linux (Ubuntu Mantic)
Status: In Progress
Skipped "appletalk: Fix Use-After-Free in atalk_ioctl" because it is
already applied as CVE-2023-51781.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-51781
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification
** Changed in: linux (Ubuntu Mantic)
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/2036239
Title:
Intel E810-XXV - NETDEV WATCHDOG: (ice):
After splitting ubuntu_kselftests_ftrace out and run test cases one-by-
one, we can see it's failing with the second test case, ftrace:test.d--
00basic--basic2.tc, on J-intel-iotg-5.15.0-1048.54 with node rizzo.
However I was unable to reproduce this manually on rizzo:
* Passed with running
The generic Ubuntu kernel has dynamic preempt enabled. This allows the
preemption model to be changed at runtime between: none, voluntary (the
default), and full.
It would be super interesting to test what impact this has for latency
sensitive workloads, and whether this can help you make the
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Roxana Nicolescu (roxanan)
** Changed in: linux (Ubuntu Mantic)
Assignee:
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
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/2049027
Title:
The display becomes frozen after some time when
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/2049935
Title:
Focal update: v5.4.264 upstream stable
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from
** Changed in: linux (Ubuntu Mantic)
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/2051176
Title:
Update Ubuntu.md
Status in linux package
Looking at the firmware-sof SRU, it looks like both this package and the
kernel need updating to complete the hardware enablement. So have these
been tested from -proposed together? It looks like verification was done
separately for the kernel and for the userspace package, and that makes
no sense
Public bug reported:
[Impact]
The mic mute/audio mute LEDS are not work on HP ZBook Power
[Fix]
It needs the specific quirk for the hardware layout.
Thus, add the quirks to make it works.
[Test]
After applying the quirk, the audio/mic mute LEDs are working good.
[Where problems could occur]
If
** Summary changed:
- linux-image-5.15.0-94-generic breaks partprobe on empty loopback device
+ partproke is broken on empty loopback device
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@christian-rhomann "Fix committed" here means that the patches have been merged
into Ubuntu's kernel tree for that specific release. The patch Robert submitted
is the one from upstream, not the test patch from the comments here.
E.g. for Jammy:
You could detect both parameters to avoid that corner case.
Alternatively this is something I feel simpledrm will help you avoid
hitting too.
Otherwise it sounds good to me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags added: oem-priority originate-from-2046339 stella
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Andy Chi (andch)
** Changed in: oem-priority
Status: New => Fix Committed
--
You received this bug
** 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/2049930
Title:
Yes, this happens also with the mainline kernel.
It also happens with the intel_cpufreq CPU frequency scaling driver
(i.e. the intel_pstate driver in passive mode), and all governors. It
also happens with the acpi-cpufreq CPU frequency scaling driver, and all
governors. However the manifestations
** Description changed:
This is a duplicate bug report for bug 2044003. All duplicates are
linked to this bug because they cannot be linked to 2044003 (LP times
out due to too many bug tasks, sigh). See bug 2008514 for that problem.
Problem: Some kernels incorrectly provide
yes mantic as well
--
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/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
I have run a quick `7z b` benchmark on the lowlatency kernel with and
without `nohz_full` parameter, and the results are fairly close:
No `nohz_full` parameter:
Compressing | Decompressing
Dict Speed UsageR/U Rating | Speed UsageR/U
so are we saying this would be 'fixed' in 22.04.4? And when is that
expected? Asking cause this has rather let me either using the noveau
drive(which is laggy) or get a new graphic card(which am unsure would
even work?)
--
You received this bug notification because you are a member of Kernel
72 matches
Mail list logo
