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
So this timeout is reproduced only on ARM64? And only when its run
cgroup -> memcg test order? Ill also look into this issue
--
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:
Removing packages from kinetic:
llvm-toolchain-12 1:12.0.1-21 in kinetic
clang-12 1:12.0.1-21 in kinetic amd64
clang-12 1:12.0.1-21 in kinetic arm64
clang-12 1:12.0.1-21 in kinetic armhf
clang-12 1:12.0.1-21 in kinetic i386
Also is this reproducible on anything modern (like 14 or 15G hardware?)
What is the config of this system?
What is the storage set up like?
--
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 glibc - 2.36-0ubuntu2
---
glibc (2.36-0ubuntu2) kinetic; urgency=medium
* Add patches to fix build with GCC 12:
- d/patches/0001-Avoid-undefined-behaviour-in-ibm128-implementation-o.patch
-
I can confirm that the camera is now working (but not thoroughly tested)
on my Dell XPS 13 (9315) running stock kernel (5.15.0-46-generic
#49-Ubuntu SMP) and following the steps in Comment #40:
$ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
$ sudo apt install libcamhal-ipu6ep0
--
Removing packages from kinetic:
opencl-clang-12 12.0.0-4 in kinetic
libopencl-clang-12-dev 12.0.0-4 in kinetic amd64
libopencl-clang-12-dev 12.0.0-4 in kinetic arm64
libopencl-clang-12-dev 12.0.0-4 in kinetic armhf
Removing packages from kinetic:
spirv-llvm-translator-12 12.0.0-4 in kinetic
libllvmspirvlib-12-dev 12.0.0-4 in kinetic amd64
libllvmspirvlib-12-dev 12.0.0-4 in kinetic arm64
libllvmspirvlib-12-dev 12.0.0-4 in kinetic armhf
I think the linux-meta which takes over the oem-22.04 metapackages
should migrate to the kinetic release pocket first. It is currently
blocked.
** Changed in: linux-meta-oem-5.17 (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of
Potentially we can demote it to kinetic-proposed, if we must migrate
v5.19.0 kernels.
** Changed in: linux-intel-iotg (Ubuntu)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Tags added: block-proposed-kinetic
--
You received this bug notification because you are a member of Kernel
tjaalton: Indeed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1987869
Title:
Remove linux-oem-5.17 from kinetic
Status in linux-meta-oem-5.17 package in Ubuntu:
Triaged
One interesting finding on ARM64 node appleton-kernel with Jammy
5.15.0-46-generic
If you run the memcg_test_3 directly, it's fairly quick to finish:
However, if you run the cgroup test first (as the order in controller
suite), it will timeout even with 2hr threshold.
controllers suite test
i am getting inconsistent response about this
** Changed in: linux-intel-iotg (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux-meta-intel-iotg (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux-restricted-modules-intel-iotg (Ubuntu)
Status: Triaged =>
Public bug reported:
Remove linux-intel-iotg from kinetic
This kernel should not exist in kinetic-release, as it is jammy-only
thing.
At least for the time being.
** Affects: linux-intel-iotg (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux-meta-intel-iotg
Public bug reported:
Remove linux-oem-5.17 from kinetic
this kernel should not exist in kinetic-release, as it is jammy-only
thing
** Affects: linux-meta-oem-5.17 (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
The fix for the issue boils down to these commits:
314e1105831b net/mlx5e: Add post act offload/unoffload API
8300f225268b net/mlx5e: Create new flow attr for multi table actions
a81283263bb0 net/mlx5e: Use multi table support for CT and sample actions
2a829fe25d28 net/mlx5e: TC, Clean redundant
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Can anyone answer my questions in comment #9?
--
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/1976511
Title:
[SRU]x86, sched: Treat Intel SNC topology as default, COD as exception
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/1987837
Title:
Network (NIC) won't work
Public bug reported:
Network interface (NIC) won't respond or work after resuming from
suspend to RAM. The device will still appear under commands such as
`lshw -c network` or `lspci`, but the network communication will be
nonetheless broken.
In my particular case, this happens with a "88E8056
Hey Jeremy,
Understood; thanks for clarifying!
I thought that maybe having upstream input could be helpful
(as Julian mentioned to avoid diverging further), but if it
is so much different nowadays, as you mentioned, it likely
won't be that helpful anyway.
By the way, appreciate that "newbie"
Hi Mauricio,
From the patch set in this ticket:
```
+0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch
+0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch
+0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch
Note: first booting into Windows 11 and then rebooting into Ubuntu
"fixes" it.
Threads: 656 total, 2 running, 654 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0,1 us, 0,1 sy, 0,0 ni, 99,7 id, 0,0 wa, 0,0 hi, 0,0 si, 0,0 st
MiB Mem : 15684,6 total, 12946,2 free,793,6 used, 1944,7
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+attachment/5611859/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In my case, I am running Ubuntu 22.04 uptodate.
This trackpad bug has been around a while, and due to the slight process
naming differences between platforms, it can be hard to link them
together.
For myself, this happens on my XPS 13 9385, after coming out of sleep,
with a similarly named
Having the same problem on Ubuntu 22.04 with 5.15 kernel running on Dell
Precision 7730.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1973098
Title:
Intermittent
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-oem-5.14 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.14 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/1987829
Title:
LG Gram 12gen high CPU use
** Attachment added: "perf-report.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+attachment/5611852/+files/perf-report.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Same problem, two identical machines (CPU, GPU, RAM size, SSD, etc), one
with 20.04, the other with 22.04 and the difference is almost night and
day. Tried the iommu workaround and didn't seem to make any difference
on improving the performance with 22.04
--
You received this bug notification
Public bug reported:
LG Gram laptop 17Z90Q with a Core i7-1260P CPU.
Whenever an external monitor is connected to USB-C/Thunderbolt 4,
average load goes above 3.0 and the machine is getting very hot.
Output from top -H shows a lot of kworker CPU usage:
top - 11:45:06 up 33 min, 2 users, load
** Attachment removed: "asus_touchpad_dev"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+attachment/5608408/+files/asus_touchpad_dev
** Attachment added: "laptop_numpad_layouts"
Just to say I seem to have the same problem as Henning and that
iommu=off seems to have helped a lot. I even see my cpu go above 2GHz
now!
Lenovo P15s, CPU 1165G7.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980829
Title:
System freeze after resuming from
Eek, sorry for missing this yesterday
The version in #7 did not exhibit the bug
That looks good for my use case
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1981087
Title:
35 matches
Mail list logo
