I think the firmware is available now
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=79b5dac115c89c28c4be5abe9443971512bde278
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubunt
Same problem here with an Asus Expertbook P5405CSA. Which -94 firmware
are you referring to? The `iwlwifi-bz-b0-fm-c0-94.ucode`? Or is there a
bz-b0-gf-a0 firmware somewhere that I haven't been able to find yet?
--
You received this bug notification because you are a member of Kernel
Packages, wh
** Package changed: linux-signed (Ubuntu) => slurm-wlm (Ubuntu)
** Changed in: slurm-wlm (Ubuntu)
Status: Confirmed => Invalid
** Summary changed:
- cgroup2 broken since 5.15.0-90-generic?
+ load_ebpf_prog() fails for long bpf() logs
--
You received this bug notification because you are
So turns out this is not a kernel bug after all. As @hedrick mentioned
it is indeed related to the bpf logs. I suppose kernel 5.15 just
produces longer logs here than the newer kernels.
Here is the original bug report for Slurm
https://bugs.schedmd.com/show_bug.cgi?id=17210 that includes a patch.
@hedrick: Regarding that workaround you mentioned above, I would guess
it only suppresses the error message but doesn't fix the problem with
broken cgroup confinement. Is that correct?
I've done more testing and have identified the following commit:
https://github.com/torvalds/linux/commit/2516d
** Summary changed:
- cgroup2 appears to be broken
+ cgroup2 broken since 5.15.0-90-generic?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2050098
Title:
cgroup2 broken since 5.
** Package changed: linux (Ubuntu) => linux-signed (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2050098
Title:
cgroup2 appears to be broken
Status in linux-signed pack
** Description changed:
We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource
allocation with Slurm. With kernel version
linux-image-5.15.0-91-generic 5.15.0-91.101
amd64
- I'm seeing a
I narrowed this down a bit further. Last working kernel version is
5.15.0-89-generic. The problem starts to show up with 5.15.0-90-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/20
Seems like the problem occurs here
```
[2024-01-22T17:13:16.819] [63786.0] cgroup/v2: cgroup_p_constrain_apply:
CGROUP: EBPF Closing and loading bpf program into
/sys/fs/cgroup/system.slice/slurmstepd.scope/job_63786/step_0/user
[2024-01-22T17:13:16.819] [63786.0] error: load_ebpf_prog: BPF load
I just noticed that 5.15.0-94.104 is available in jammy-proposed and
tested that. Same problem as with -91
I've enabled debug messages for slurmd with regards to cgroup, log
attached.
** Attachment added: "Slurmd cgroup debug log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050098/+
Public bug reported:
We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource
allocation with Slurm. With kernel version
linux-image-5.15.0-91-generic 5.15.0-91.101
amd64
I'm seeing a new issue. This mu
Happy to provide more info/logs/whatever if you can tell me where to
look ;-)
--
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/1950792
Title:
No boot possible - Cannot open root device
St
I am having similar problems since updating from 3.0 to the latest
release 3.2.6
We mainly use legacy boot (instead of UEFI) and the boot order of all our nodes
is set to:
1. Network/PXE
2. harddisk
A deployed node would boot PXE and then immediately MAAS tells it (not
sure how exactly) to boot
It looks like this has been fixed here:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=3b931173c97b0d73f80ea55b72bb2966a246167f
and here:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe&id=3b931173c97b0d73f80ea55b72bb2966
Public bug reported:
On Ubuntu 18.04
linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
According to https://www.mail-archive.com/ceph-
us...@ceph.io/msg00940.html the same happens on Disco with this kernel
version.
Processes that read data from CephFS get stuck, the system becomes
unsta
16 matches
Mail list logo
