Public bug reported:
I try to install package zfs-dkms on a riscv64 system running Ubuntu
24.04. Installation fails with "GPL-incompatible module zfs.ko uses GPL-
only symbol 'PageHuge'". See appended make.log.
Installed kernel:
Architecture: riscv64
Source: linux-riscv
Version: 6.5.0-9.9.1
Pro
Public bug reported:
When booting I see a message:
`kded5' uses wireless extensions which will stop working for Wi-Fi 7 hardware;
use nl80211
which is described in https://bugs.kde.org/show_bug.cgi?id=466467
Fedora suggests to disable the outdated wireless extensions:
https://fedoraproject.org/w
Flash-kernel contains a database matching device-tree machine values
with devicetree names.
There is no necessity to remove entries for architectures that are not
supported in Ubuntu. We should try to minimize the differences to
Debian. So setting this to won't fix for flash-kernel.
** Changed in
Public bug reported:
When trying to boot the Kinetic preinstalled image
ubuntu-22.10-preinstalled-server-riscv64+licheerv.img.xz
(https://cdimage.ubuntu.com/releases/22.10/release/ubuntu-22.10-preinstalled-
server-riscv64+licheerv.img.xz) with a 0fe6:9700 "ICS Advent DM9601 Fast
Ethernet Adapter"
Closing this as the linked patches are outdated. Upstream work for PCIe
on the Icicle kit is still ongoing.
** Changed in: linux-riscv (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv
The following Nvidia packages are installed:
libnvidia-cfg1-515* libnvidia-common-515* libnvidia-compute-515*
libnvidia-decode-515* libnvidia-egl-wayland1* libnvidia-encode-515*
libnvidia-extra-515* libnvidia-fbc1-515*
libnvidia-gl-515* libnvidia-gl-515:i386*
linux-modules-nvidia-515-5.19.0
Public bug reported:
After the update to 6.2.0-18-generic booting with Nvidia drivers fails.
The last message is:
Job gpu-manager.service start running (3min 22s / no limit)
With 6.1.0-16-generic the problem does not occur.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0
*** This bug is a duplicate of bug 2012559 ***
https://bugs.launchpad.net/bugs/2012559
** This bug has been marked a duplicate of bug 2012559
6.2 kernel won't boot, may be nvidia related?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Duplicate bug report LP #2012706 contains some more logs.
--
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/2012559
Title:
6.2 kernel won't boot, may be nvidia related?
Status in linux pac
After unplugging and replugging the keyboard:
$ lsusb
Bus 001 Device 019: ID 046a:0011 Cherry GmbH G83 (RS 6000) Keyboard
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation
Public bug reported:
I am testing the Allwinner Nezha D1 board according to
http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results
Hitting a key on the USB keyboard (that was plugged in at boot) results
in
[ 760.275027] usb 3-1: device descriptor read/64, error -
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
https://bugs.launchpad.net/bugs/2013743
Title:
USB not working on Nezha D1
Status in linux-allwinner package in Ubuntu:
New
Bug de
@Kai-Heng Feng (kaihengfeng)
Concerning your question in LP #2007829: If this is a regression cannot be
answered as the test case did not cover it.
** Changed in: linux-allwinner (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Pa
*** This bug is a duplicate of bug 2013743 ***
https://bugs.launchpad.net/bugs/2013743
** This bug has been marked a duplicate of bug 2013743
USB not working on Nezha D1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
The upgrade of 515 worked fine I now can work with kernel
6.2.0-18-generic.
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers-515 (Ubuntu Lunar)
Status: In Progress => Fix Released
--
You received this bug notification because
Kernel 5.19.0-1009-allwinner does not show this issue.
** Changed in: linux-allwinner (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single
patch missing:
https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug noti
** Patch added: "zfs-linux-0.8.3-1ubuntu12.15..0.8.3-1ubuntu12.16.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+attachment/5664989/+files/zfs-linux-0.8.3-1ubuntu12.15..0.8.3-1ubuntu12.16.debdiff
--
You received this bug notification because you are a member of Ker
Public bug reported:
/lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
StarFive VisionFive board which uses the starfive kernel flavor.
The file was available in Jammy and only recently removed from Mantic.
File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding i
*** This bug is a duplicate of bug 2038546 ***
https://bugs.launchpad.net/bugs/2038546
** This bug has been marked a duplicate of bug 2038546
/lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
--
You received this bug notification because you are a member of Kernel
Packages, whi
** Patch added:
"linux-firmware-20230919.git3672ccab-0ubuntu2..20230919.git3672ccab-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+attachment/5707392/+files/linux-firmware-20230919.git3672ccab-0ubuntu2..20230919.git3672ccab-0ubuntu3.debdiff
--
You re
linux-firmware - 20230919.git3672ccab-0ubuntu3 is available in
ppa:xypron/gnu-efi
--
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/2038546
Title:
/lib/firmware/brcm/brcmfmac43430-
Public bug reported:
Running http://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on QEMU
with
qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
/usr/lib/u-boot
** Attachment added: "syslog.gz"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038893/+attachment/5708199/+files/syslog.gz
--
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/
$ uname -a
Linux ubuntu 6.5.0-9-generic #9.1-Ubuntu SMP Sat Oct 7 17:18:31 UTC 2023
riscv64 riscv64 riscv64 GNU/Linux
--
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/2038893
Title:
Public bug reported:
On the Nezha D1 board USB does not work correctly.
I have connected a USB key board and get errors like:
[ 4458.313671] usb 1-1: device descriptor read/64, error -71
[ 4459.189686] usb 1-1: device descriptor read/64, error -71
[ 4460.157594] usb 4-1: device descriptor read/6
I was able to use the keyboard after removing and plugging in again.
--
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/2038920
Title:
Nezahl D1: usb 1-1: device descriptor read/64, er
** Description changed:
On the Nezha D1 board USB does not work correctly.
- I have connected a USB key board and get errors like:
+ I have connected a USB keyboard and get errors like:
[ 4458.313671] usb 1-1: device descriptor read/64, error -71
[ 4459.189686] usb 1-1: device descript
Public bug reported:
I have been running the Mantic preinstalled image on the VisionFive 2 1.3B
board.
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz
Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3
[ 4050.418337] Unable to handl
Trying again booting the preinstalled image the reported error did not
come up.
--
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/2038893
Title:
probe-bcache[132]: unhandled signal 11
Public bug reported:
I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
output is not working.
There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get the
HDMI PHY".
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcV
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+attachment/5708302/+files/syslog
--
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/2
--
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/2038928
Title:
Unable to handle kernel paging request at virtual address
ff8a012abe1a
Status in linux-riscv package in Ubuntu:
echo blacklist jh7110_tdm > /etc/modprobe.d/blacklist-jh7110_tdm.conf
did not solve the issue. I still get oopses like:
[ 201.478403] Oops [#1]
[ 201.480681] Modules linked in: tls cfg80211 binfmt_misc nls_iso8859_1 cdns3
cdns_usb_common udc_core cdns3_starfive ofpart cmdlinepart spi_nor mtd
a
** Tags added: iso-testing
--
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/2038933
Title:
sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY
Status in linux-riscv package in Ubu
The problem seems to be related to a U-Boot reporting the wrong memory
size on a VisionFive 2 with 4GiB.
--
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/2038928
Title:
Unable to han
This patch for upstream U-Boot seems to resolve the issue:
https://lore.kernel.org/u-boot/20231011044813.122941-1-heinrich.schucha...@canonical.com/T/#u.
I will retest the image.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv
** Summary changed:
- Nezahl D1: usb 1-1: device descriptor read/64, error -71
+ Nezha D1: usb 1-1: device descriptor read/64, error -71
--
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/bug
With u-boot-starfive - 2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa4 from
ppa:ubuntu-risc-v-team/release the problem is resolved.
** Changed in: linux-riscv (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
board using
https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
server-riscv64.img.gz
I have connected an Nvidia GT710 graphics card to the NVMe connector and
see rcu_sched stalls. I have
@itrue
The issue is described on
https://wiki.ubuntu.com/RISC-V/PolarFire%20SoC%20FPGA%20Icicle%20Kit.
Upstream kernel patches are still under discussion. Reopening the issue
does not help unless there are upstream patches that we can merge into
our kernel.
Here is the latest work on cleaning up
Dear Dimitri,
it is unclear to me why U-Boot should have any influence on the
(non-)inclusion of a driver in the initramfs. Could you, please, add the
missing information.
There is no guarantee that any update of U-Boot runs after the kernel
change. A user can choose only to update the kernel. Th
Public bug reported:
When running EDK2 as payload for QEMU using KVM a crash occurs in the
VM:
$ qemu-system-riscv64 -M virt,acpi=off -accel kvm -m 4096 -nographic
-drive if=pflash,format=raw,unit=0,file=RISCV_VIRT_CODE.fd,readonly=on -drive
if=pflash,format=raw,unit=1,file=RISCV_VIRT_V
The crash output is generated in EDK II,
UefiCpuPkg/Library/BaseRiscV64CpuExceptionHandlerLib/CpuExceptionHandlerLib.c
Here we could add code showing the failing instruction. Only showing the
registers is not helpful.
U-Boot creates output like:
Unhandled exception: Illegal instruction
EPC:
The problem is reproducible with Ubuntu 24.10 running kernel
6.8.0-31-generic riscv64.
** Also affects: edk2 (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux-meta-riscv (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug not
** Changed in: linux-meta-riscv (Ubuntu Noble)
Importance: Undecided => Low
** Changed in: linux-meta-riscv (Ubuntu Oracular)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-riscv in Ubuntu.
h
Debugging the EDK II payload in QEMU under KVM fails with:
qemu-system-riscv64: -gdb tcp::1234: gdbstub: current accelerator doesn't
support guest debugging
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-riscv in Ubuntu.
https
Public bug reported:
The last kernel that successfully boots on my Lenovo X13s system is
6.5.0-1004-laptop.
With 6.8.0-20-generic no output whatsoever is shown.
---
ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: arm64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/se
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763505/+files/IwConfig.txt
--
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
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763515/+files/Lspci.txt
--
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/2060868
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763504/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763503/+files/AlsaInfo.txt
--
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
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763516/+files/Lsusb.txt
--
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/2060868
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763517/+files/Lsusb-t.txt
--
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/2060
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763518/+files/Lsusb-v.txt
--
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/2060
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763521/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763519/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763522/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763520/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763525/+files/WifiSyslog.txt
** Summary changed:
- Lenovo X13s fails to boot on 6.8.0-20-generic
+ Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
--
You receive
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763523/+files/RfKill.txt
--
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/2060868
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2060868/+attachment/5763524/+files/UdevDb.txt
--
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/2060868
6.8.0-22-generic with earlycon=efifb stops after the output in the
appended screenshot.
** Attachment added: "sc20240410_223341.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+attachment/5763528/+files/sc20240410_223341.jpg
--
You received this bug notification because you
--
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/2060868
Title:
Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
Status in linux package in Ubuntu:
New
Bug description
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+attachment/5768195/+files/dmesg.txt
--
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/
Public bug reported:
On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:
[ +0.000917] [drm] Display Core failed to initialize with v3.2.266!
[ +0.24] Unable to handle kernel access to user memory without uaccess
routines at virtual address 0008
A Radeon R230 wo
With 6.8.0-31-generic I am not able to get any HDMI output on the LicheeRV Dock.
Unplugging and reconnecting did not help.
[0.133313] platform 546.tcon-top: Fixed dependency cycle(s) with
/soc/hdmi@550
[0.141438] platform 546.tcon-top: Fixed dependency cycle(s) with
/soc/hdmi
Public bug reported:
A 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter was only detected
after reconnecting the USB Hub. It should have been detected while
booting.
$ lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
|__ Port 001: Dev 008, If 0, Class=Hub
The problem did not occur on every boot.
--
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/2063300
Title:
On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not
dete
With 6.8.0-31-generic I am not able to get any HDMI output on the Nezha D1
either.
Unplugging and reconnecting did not help.
--
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/2038933
T
Public bug reported:
After connecting a monitor to an SiFive HiFive Unmatched board running
kernel 6.8.0-28-generic I saw:
nouveau :05:00.0: timer: stalled at
nouveau :05:00.0: Xorg[3338]: nv50cal_space: -16
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-ima
When connected before boot the HDMI output works fine.
--
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/2063309
Title:
RISC-V: nouveau :05:00.0: timer: stalled at fff
On my LicheeRV Dock it dos not work for me with HDMI plugged in at
start. I just get
[ 67.521944] sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY
[ 67.613930] sun4i-drm display-engine: Couldn't bind all pipelines components
and no output. On the Nezha D1 I did not have this issue.
When
@glathe
We used to have packate linux-image-laptop-23.10 which provided file
/usr/share/initramfs-tools/modules.d/laptop. This contained
qcom_q6v5_pas. It have recreated this file manually but this does not
resolve my problems.
Which follow up package provided with the X13s installer image defin
Public bug reported:
Booting the SiFive Unmatched no output on the monitor was shown.
Zillions of messages like the following were written:
[ +0.007867] [ cut here ]
[ +0.13] nouveau :05:00.0: timeout
[ +0.000374] WARNING: CPU: 2 PID: 2028 at
drivers/gpu/drm/no
The error occurred with a monitor that was in a low power state.
Rebooting with the monitor powered on showed no issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2054325
T
Public bug reported:
Starting the lxd-agent.service service fails with kernel
6.5.0-9-generic.
# /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
available for device config
[ 1239.456813] 9pnet_virtio: no channels available for device config
Couldn't mount virtiofs or 9p, fa
The installed snap version is 5.20-f3dd836.
--
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/2054814
Title:
lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic
Status in li
** Package changed: linux-riscv (Ubuntu) => lxd-agent-loader (Ubuntu)
--
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/2054814
Title:
lxd-agent-setup cannot be started on riscv64 6.5
I would suggest not to invest in enabling a new feature in Focal now
that we have two newer LTS releases. Setting to won't fix.
** Changed in: zfs-linux (Ubuntu Focal)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
With ubuntu-x13s-settings installed I can boot into kernel
6.8.0-31-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/2060868
Title:
Lenovo X13s fails to boot on 6.8.0-20-generic a
$ https://github.com/openzfs/zfs
$ cd zfs/
$ git grep -n fsnotify
shows that notification was never implemented.
So this works as designed. Closing as "invalid".
Best regards
Heinrich
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: fatrace (Ubuntu)
Stat
The following patch sets reasonable values for CONFIG_NR_CPUS on RISC-V:
[PATCH v3] RISC-V: Increase range and default value of NR_CPUS
https://lore.kernel.org/all/20220420112408.155561-1-apa...@ventanamicro.com/
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
The following patches should be considered for inclusion into the v5.15
linux-image-generic kernel for the Jammy release:
commit f6f7fbb89bf8dc9132fde55cfe67483138eea880
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:42 2021 +
riscv: dts: sifive unmatched: Link
** Summary changed:
- riscv: Improve support for the SiFive Unmathed board
+ riscv: Improve support for the SiFive Unmatched board
--
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/1958
Works with nvidia 510 driver. So I set the issue to fixed release for
this. Is there anybody using the 470 driver who could confirm it works
there too?
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you a
Public bug reported:
Please, add microchip/microchip-mpfs-icicle-kit.dtb to the list of
created device-trees.
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Public bug reported:
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
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+attachment/5574773/+files/dmesg
--
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/196
apport information
** Tags added: apport-collected
** Description changed:
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 a
efi: Make efi_rts_work accessible to efi page fault handler
https://lore.kernel.org/all/20200318090253.ga32...@duo.ucw.cz/T/#mcbd236122ec0ae61f1ee9c22b8d7910ffc2276a0
addressed a similar issue on x86.
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches
the number of hardware threads on a typical desktop CPU (AMD Ryzen
5950X). Our Linux kernel should support this number of harts.
Best regards
Heinrich
** Affects: linux-riscv (Ubuntu)
Importance: Und
** Tags added: fr-2245
--
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/1967562
Title:
jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
Status in grub2 package in Ubun
On riscv64 we cannot boot without the LoadFile2 protocol. So the short
term fix of forcing to 0 must be architecture specific. Check for
__riscv not defined.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
As the log below shows grub_net_fini_hw() is called before entering the
kernel and before the LoadFile2 protocol is executed:
loader/efi/linux.c:478: kernel @ 0xf63d8000
net/net.c:1559: fs_close() name: /casper/vmlinuz
net/net.c:1510: fs_open() name: /casper/initrd
loader/efi/linux.c:396: LoadFile
As long as the kernel stub does not invoke the SNP protocol itself it is
safe for GRUB to assume that it is still in a good state when reaching
the Load File2 protocol call.
I am not aware of any requirement in the UEFI specification to leave the
network adapter in a specific state on ExitBootServ
As we are close to release date we should simply disable Load File2 protocol on
ARM in Jammy:
https://code.launchpad.net/~xypron/grub/+git/grub/+merge/419407
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Public bug reported:
The size of kernel modules on RISC-V indicates that there is a build
problem:
kernel/drivers/ata/sata_mv.ko
amd64: 81713 bytes
arm64: 85505 bytes
riscv64: 601417 bytes
objdump -h shows that there is no section beyond 0xc6fc in the riscv64 file.
The size of the sections match
If I compile Linux v5.15.26 with RISC-V defconfig + CONFIG_SATA_MV=y,
I get a drivers/ata/sata_mv.ko with 103960 bytes.
With additionally CONFIG_MODULE_SIG=y after make modules_install: 104673
bytes.
So the problems seems not to exist in upstream.
--
You received this bug notification because y
** Changed in: linux-riscv (Ubuntu)
Status: New => Confirmed
--
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/1964335
Title:
Excessive size of kernel modules on RISC-V - modul
1 - 100 of 399 matches
Mail list logo
