[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
> 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. -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Fix Released Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic
> 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 non-backward compatible change, which is the update of the ioctl commands list (for an example see [2]). So instead of cherry-picking the 2 commits mwhudson mentions, I'd rather update to 5.19 since the default kernel for kinetic is 5.19 (both commits belong to this version). [1] https://lists.strace.io/pipermail/strace-devel/2022-August/011094.html [2] https://github.com/strace/strace/commit/22f61979141fa5c9732d01ea69c23f46a3e2868a -- 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/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: Fix Released Status in strace package in Ubuntu: Triaged Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"
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. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992458] [NEW] Disable VMAP_STACK as it causes crash in EFI
*** 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, the kernel switches to the EFI page table which is created during the boot process *but* is never updated during the life of the kernel: as CONFIG_VMAP_STACK allocates the kernel stack in the vmalloc region and maps it in the *kernel page table*, the EFI page table never has this new mapping and then segfaults when trying to access the kernel stack of the current process. This is easier to reproduce on the Unmatched than on QEMU (never reproduced on this platform): ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/* Which gives rise to a kernel crash, gdb traces below: (gdb) bt #0 handle_exception () at /home/alex/work/linux/arch/riscv/kernel/entry.S:27 #1 0x8080741a in efi_virtmap_load () at /home/alex/work/linux/arch/riscv/include/asm/current.h:31 #2 0x in ?? () (gdb) p/x $stval $1 = 0xffc8946cbc38 (gdb) display /i $sepc 1: x/i $sepc 0x8000392c :sd ra,8(sp) (gdb) p/x $sp $6 = 0xffc8946cbc30 A workaround can be to disable CONFIG_VMAP_STACK but actually any mapping in the kernel page table that is not also added to the EFI page table can cause such crash: but I'm not sure this can happen and this workaround was enough in the previous release to fix this bug and to be able to live install a system. I advise to implement this workaround for now as I'm implementing the proper patch which consists in updating the EFI page table before switching to it, just like x86 does. [ Test Plan ] Use a kernel with CONFIG_VMAP_STACK disabled and simply enter the following command, preferably on the Unmatched: ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/* This should not trigger a crash. [ Where problems could occur ] As said above, just disabling CONFIG_VMAP_STACK may not be enough. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1967130 rcu_sched detected stalls on CPUs/tasks -- 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/1992458 Title: Disable VMAP_STACK as it causes crash in EFI Status in linux-riscv package in Ubuntu: New Bug description: [ 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, the kernel switches to the EFI page table which is created during the boot process *but* is never updated during the life of the kernel: as CONFIG_VMAP_STACK allocates the kernel stack in the vmalloc region and maps it in the *kernel page table*, the EFI page table never has this new mapping and then segfaults when trying to access the kernel stack of the current process. This is easier to reproduce on the Unmatched than on QEMU (never reproduced on this platform): ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/* Which gives rise to a kernel crash, gdb traces below: (gdb) bt #0 handle_exception () at /home/alex/work/linux/arch/riscv/kernel/entry.S:27 #1 0x8080741a in efi_virtmap_load () at /home/alex/work/linux/arch/riscv/include/asm/current.h:31 #2 0x in ?? () (gdb) p/x $stval $1 = 0xffc8946cbc38 (gdb) display /i $sepc 1: x/i $sepc 0x8000392c : sd ra,8(sp) (gdb) p/x $sp $6 = 0xffc8946cbc30 A workaround can be to disable CONFIG_VMAP_STACK but actually any mapping in the kernel page table that is not also added to the EFI page table can cause such crash: but I'm not sure this can happen and this workaround was enough in the previous release to fix this bug and to be able to live install a system. I advise to implement this workaround for now as I'm implementing the proper patch which consists in updating the EFI page table before switching to it, just like x86 does. [ Test Plan ] Use a kernel with CONFIG_VMAP_STACK disabled and simply enter the following command, preferably on the Unmatched: ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/* This should not trigger a crash. [ Where problems could occur ] As said above, just disabling CONFIG_VMAP_STACK may not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1992458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991790] [NEW] Disable sv57 as the userspace is not ready
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 the kernel to downgrade to sv48, so we must patch the kernel. diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] Build an image with the new kernel and make sure snapd started correctly, or that you can compile a simple helloworld written in Go. [ Where problems could occur ] The patch could be wrong, but I already built a kernel with it and it worked fine. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- 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/1991790 Title: Disable sv57 as the userspace is not ready Status in linux-riscv package in Ubuntu: New Bug description: [ 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 the kernel to downgrade to sv48, so we must patch the kernel. diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c index 2c4a64e97aec..18a0c70ed313 100644 --- a/arch/riscv/mm/init.c +++ b/arch/riscv/mm/init.c @@ -775,6 +775,10 @@ static __init void set_satp_mode(void) disable_pgtable_l4(); } + /* UBUNTU: Force disable sv57 and fallback to sv48 */ + if (pgtable_l5_enabled) + disable_pgtable_l5(); + memset(early_pg_dir, 0, PAGE_SIZE); memset(early_p4d, 0, PAGE_SIZE); memset(early_pud, 0, PAGE_SIZE); [ Test Plan ] Build an image with the new kernel and make sure snapd started correctly, or that you can compile a simple helloworld written in Go. [ Where problems could occur ] The patch could be wrong, but I already built a kernel with it and it worked fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1991790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931432] Re: crash FTBFS on riscv64
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. https://bugs.launchpad.net/bugs/1931432 Title: crash FTBFS on riscv64 Status in crash package in Ubuntu: Confirmed Status in crash source package in Focal: Confirmed Status in crash source package in Groovy: Confirmed Bug description: Crash fails to build from source on riscv at least for Focal and Groovy, later releases may also be affected but I haven't confirm it. Examples of failed builds : Groovy : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864 Focal : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982559] [NEW] gpio-poweroff probe failed
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 enabled SBI SRST extension which now handles the poweroff/reset, we could either do nothing or remove the gpio-poweroff node from the device tree (introduce a delta with upstream). ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- 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/1982559 Title: gpio-poweroff probe failed Status in linux-riscv package in Ubuntu: New Bug description: 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 enabled SBI SRST extension which now handles the poweroff/reset, we could either do nothing or remove the gpio-poweroff node from the device tree (introduce a delta with upstream). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1982559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973168] [NEW] Package still suggests to install crda whereas it was removed
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: wireless-regdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1973168 Title: Package still suggests to install crda whereas it was removed Status in wireless-regdb package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1973168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955042] Re: SBI SRST extension is missing
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: SBI SRST extension is missing Status in linux-riscv package in Ubuntu: Fix Released Bug description: 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: https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/ or use the attached patch. I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and it allows to successfully reboots the board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1955042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967130] Re: rcu_sched detected stalls on CPUs/tasks
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 should go for this workaround: @xnox what do you think? Thanks -- 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/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: New Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967130] Re: rcu_sched detected stalls on CPUs/tasks
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 efi_virtmap_load and then switch_mm, if the stack of the worker is in a vmalloc area not yet synchronized with efi_mm (since RISC-V lazily populates vmalloc area), an attempt to access this stack will trigger a fault which can't be resolved since when trying to save the context, a new trap will be triggered and so on. So disable VMAP_STACK for now until we figure out the correct fix. And I'm working on the proper fix which consists in synchronizing the efi page table with the page table of the calling thread before switching to efi mm. -- 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/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: New Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964796] Re: Fix unmatched ASMedia ASM2824 PCIe link training
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 it, this should be cherry-picked for 22.04. A similar patch for u-boot exists, I'll report a new bug there. Thanks [1] https://patchwork.kernel.org/project/linux- riscv/patch/20220318152430.526320-1-ben.do...@codethink.co.uk/ -- 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/1964796 Title: Fix unmatched ASMedia ASM2824 PCIe link training Status in linux-riscv package in Ubuntu: New Bug description: https://lore.kernel.org/all/alpine.deb.2.21.2202010240190.58...@angie.orcam.me.uk/raw It has been discovered that Unmatched board ships ASMedia ASM2824 PCIe which frequently fails to complete link training and negotiate stable and fast speeds. To ensure PCIe devices on Unmatched board can operate with stable and predictable link speeds cherry-pick upstream submitted patch that resolves the issue. It is currently applied as a SAUCE patch, whilst the upstream inclusion review is ongoing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955042] [NEW] SBI SRST extension is missing
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: https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/ or use the attached patch. I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and it allows to successfully reboots the board. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Attachment added: "0001-RISC-V-Use-SBI-SRST-extension-when-available.patch" https://bugs.launchpad.net/bugs/1955042/+attachment/5548032/+files/0001-RISC-V-Use-SBI-SRST-extension-when-available.patch -- 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: SBI SRST extension is missing Status in linux-riscv package in Ubuntu: New Bug description: 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: https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/ or use the attached patch. I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and it allows to successfully reboots the board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1955042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943030] Re: Enable riscv64 build of nvidia-settings
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 seems like a bad user experience to me whereas it does not cost that much to enable. But I'm quite new to this, so feel free to explain where I'm wrong :) -- 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: Incomplete Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943030] Re: Enable riscv64 build of nvidia-settings
** 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: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943030] [NEW] Enable riscv64 build of nvidia-settings
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 ** Attachment added: "nvidia_settings_debdiff.patch" https://bugs.launchpad.net/bugs/1943030/+attachment/5523773/+files/nvidia_settings_debdiff.patch -- 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: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
