> Without linux-image-5.19.0-21-generic i915-fix the USB Live will never
boot in an intel Tiger Lake/Alder Lake IGPU
Indeed the live desktop installer fails to boot on a 12th intel cpu: I
have lots of kernel backtraces in dmesg caused by nouveau driver. The
kernel from the installer is 5.19.0-21.
> In general, does strace get a release for each kernel release? Should
it be updated in parallel?
I tried to find an answer to this question and I would say yes. As is
stated in [1], strace follows the same release cycle as the kernel. In
addition, every strace release at least comes with a
Hi Alberto,
Sorry I did not get notified of your answers...Thanks for your
investigation: did you file a bug against the kernel then?
Thanks,
Alex
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1967130 ***
https://bugs.launchpad.net/bugs/1967130
Public bug reported:
[ Impact ]
The kernel crashes when trying to access the EFI runtime
services/variables if the kernel is configured with CONFIG_VMAP_STACK.
Indeed, to access EFI variables/services,
Public bug reported:
[ Impact ]
sv57 breaks Go since Go uses the upper bits of a pointer to store data,
and it is not ready for sv57 yet. It probably breaks other type of
software using this "pointer tagging" technic. The following patch fixes
this: at the moment, there is no way to indicate to
Progress is being made and crash could be available for 5.20:
https://lore.kernel.org/all/20220813031753.3097720-1-xianting.t...@linux.alibaba.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
Public bug reported:
I observe the following message in 5.15.0-1015-generic:
[0.656680] poweroff-gpio gpio-poweroff: gpio_poweroff_probe: pm_power_off
function already registered
[0.665278] poweroff-gpio: probe of gpio-poweroff failed with error -16
It happens because we
Public bug reported:
This package still suggests crda to be installed whereas it was removed
from jammy already: simply remove this from debian/control as done in
[1].
[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13612257/+listing-
archive-extra
** Affects:
This fix was merged in 5.15.0-1005.5.
** Changed in: linux-riscv (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1955042
Title:
The workaround built successfully in my PPA:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13413205/+listing-
archive-extra
I tested it successfully with the RISC-V live installer (where this
problem was seen).
I did not have time yet to work on the proper fix so I think we
I have a workaround for this:
UBUNTU: SAUCE: riscv: Disable VMAP_STACK since it fails with efi
When VMAP_STACK is enabled, kernel threads have their stacks in the vmalloc
region.
So when The kworker responsible for handling efi work queue (efi_call_rts)
calls
A similar patch that solves the same issue was actually merged for 5.18
[1].
I encountered this bug with our current u-boot (2022.01+dfsg-2ubuntu1)
and linux kernel (5.15.0-1004.4): I applied the patch in [1] on top of
5.15.0-1004.4 successfully and it solved the problem. So as you already
tagged
Public bug reported:
SBI SRST extension is needed for handling sifive unmatched reboot and
with the reset now merged into openSBI package, enabling SRST extension
finally gives us the possibility to reset the board.
The patch to enable SRST extension can be found here:
I may be wrong here but I'd see things differently: when the binaries
get available, we won't be notified and people will start trying to
install it and it will fail since we decided not to make it available. A
few people will take the time to file a bug report, others will get
disappointed: this
** Tags added: fr-1689
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943030
Title:
Enable riscv64 build of nvidia-settings
Status in nvidia-settings package in Ubuntu:
Public bug reported:
Please enable the build on riscv64 architecture of nvidia-settings since
it works fine using the attached debdiff:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736
** Affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
**
16 matches
Mail list logo
