[Kernel-packages] [Bug 2049441] [NEW] zfs-dkms: GPL-incompatible module zfs.ko uses GPL-only symbol 'PageHuge'
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
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: zfs-dkms 2.2.2-0ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Tue Jan 16 01:06:40 2024
InstallationDate: Installed on 2023-12-04 (42 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 (20231204)
PackageArchitecture: all
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug noble riscv64
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/2049441/+attachment/5739731/+files/make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049441
Title:
zfs-dkms: GPL-incompatible module zfs.ko uses GPL-only symbol
'PageHuge'
Status in zfs-linux package in Ubuntu:
New
Bug description:
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
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: zfs-dkms 2.2.2-0ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.27.0-0ubuntu6
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Tue Jan 16 01:06:40 2024
InstallationDate: Installed on 2023-12-04 (42 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
PackageArchitecture: all
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2049441/+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 2049952] [NEW] `kded5' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
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/wiki/Changes/RemoveWirelessExtensions
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:zfsdt 3088 F pipewire
/dev/snd/controlC0: zfsdt 3091 F wireplumber
/dev/snd/controlC1: zfsdt 3091 F wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Jan 19 22:29:55 2024
InstallationDate: Installed on 2021-07-01 (932 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated
Camera (1280x720@30)
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=/dev/mapper/vgubuntu-root ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.6.0-14-generic N/A
linux-backports-modules-6.6.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2023
dmi.bios.release: 1.63
dmi.bios.vendor: LENOVO
dmi.bios.version: R0UET83W (1.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KV0008GE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.63
dmi.modalias:
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
dmi.product.family: ThinkPad E585
dmi.product.name: 20KV0008GE
dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
dmi.product.version: ThinkPad E585
dmi.sys.vendor: LENOVO
** Affects: kded (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
** Also affects: kded (Ubuntu)
Importance: Undecided
Status: New
--
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/2049952
Title:
`kded5' uses wireless extensions which will stop working for Wi-Fi 7
hardware; use nl80211
Status in kded package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
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/wiki/Changes/RemoveWirelessExtensions
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:zfsdt 3088 F pipewire
/dev/snd/controlC0: zfsdt 3091 F wireplumber
/dev/snd/controlC1: zfsdt 3091 F wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Jan 19 22:29:55 2024
InstallationDate: Installed on 2021-07-01 (932 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated
Camera (1280x720@30)
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=/dev
[Kernel-packages] [Bug 2048864] Re: Remove armhf support
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: flash-kernel (Ubuntu Noble) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2048864 Title: Remove armhf support Status in flash-kernel package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in flash-kernel source package in Noble: Won't Fix Status in linux-raspi source package in Noble: New Bug description: Noble and newer don't support armhf for Pi anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2048864/+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 2002090] [NEW] Kernel crash with preinstalled Kinetic image
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" plugged in the following crash occurs: [ 163.933818] Unable to handle kernel paging request at virtual address fffdf54d0289 [ 163.941784] Oops [#1] [ 163.944072] Modules linked in: binfmt_misc cfg80211 snd_soc_hdmi_codec dw_hdmi_i2s_audio dw_hdmi_cec sr9700 dm9601 usbnet pwrseq_simple sunxi_cir rc_core sun8i_drm_hdmi dw_hdmi sun8i_mixer sunxi phy_generic sunxi_cedrus(C) snd_soc_simple_card v4l2_mem2mem sun20i_codec snd_soc_dmic videobuf2_dma_contig snd_soc_simple_card_utils videobuf2_memops videobuf2_v4l2 sun4i_drm videobuf2_common sun4i_frontend sun4i_tcon sun8i_tcon_top display_connector drm_cma_helper snd_soc_core videodev snd_compress ac97_bus snd_pcm_dmaengine drm_kms_helper snd_pcm leds_sun50i_r329 led_class_multicolor mc snd_timer fb_sys_fops snd syscopyarea sysfillrect sysimgblt leds_gpio backlight soundcore nls_iso8859_1 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 efivarfs raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 raid0 multipath linear [ 164.030015] CPU: 0 PID: 668 Comm: (d-logind) Tainted: G C 5.17.0-1003-allwinner #3-Ubuntu [ 164.039517] Hardware name: Sipeed Lichee RV Dock (DT) [ 164.044578] epc : __update_blocked_fair.isra.0+0xb6/0x3ca [ 164.050012] ra : __update_blocked_fair.isra.0+0xa6/0x3ca [ 164.055437] epc : 80060b1e ra : 80060b0e sp : ffd8056d7650 [ 164.062678] gp : 81e93b80 tp : ffd804023e80 t0 : 000e [ 164.069918] t1 : t2 : 0407 s0 : ffd8056d76d0 [ 164.077156] s1 : ffd806012800 a0 : a1 : d4be6efdf54d01a9 [ 164.084395] a2 : 0007 a3 : 81ea6540 a4 : ffd80461e780 [ 164.091634] a5 : ffd80493db98 a6 : a7 : [ 164.098873] s2 : ffd806012940 s3 : 1000 s4 : ffd81ecc2780 [ 164.106114] s5 : s6 : b67e s7 : ffd8056d76d7 [ 164.113354] s8 : 80e7d600 s9 : 00262b36e925 s10: 0100 [ 164.120595] s11: ffd804432400 t3 : 001c t4 : 016cddfa32cc [ 164.127835] t5 : 0407 t6 : 0407ab360ba9 [ 164.133162] status: 00020100 badaddr: fffdf54d0289 cause: 000d [ 164.141097] [] update_blocked_averages+0x124/0x1d2 [ 164.147475] [] newidle_balance+0x120/0x3b6 [ 164.153160] [] pick_next_task_fair+0x4e/0x318 [ 164.159102] [] __schedule+0x144/0x630 [ 164.164354] [] schedule+0x50/0xc2 [ 164.169253] [] io_schedule+0x4c/0x66 [ 164.174413] [] folio_wait_bit_common+0x218/0x396 [ 164.180630] [] filemap_update_page+0x2cc/0x2da [ 164.186660] [] filemap_get_pages+0x1f2/0x314 [ 164.192516] [] filemap_read+0xaa/0x276 [ 164.197851] [] generic_file_read_iter+0xf2/0x14e [ 164.204054] [] ext4_file_read_iter+0x60/0x160 [ 164.210007] [] __kernel_read+0xfc/0x23c [ 164.215433] [] kernel_read+0x58/0x8e [ 164.220594] [] search_binary_handler+0x64/0x240 [ 164.226710] [] exec_binprm+0x54/0x14a [ 164.231956] [] bprm_execve.part.0+0x178/0x1d2 [ 164.237899] [] bprm_execve+0x56/0x80 [ 164.243059] [] do_execveat_common+0x16e/0x1ee [ 164.248999] [] sys_execve+0x3c/0x48 [ 164.254072] [] ret_from_syscall+0x0/0x2 ** Affects: linux-allwinner (Ubuntu) Importance: Undecided Status: New -- 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/2002090 Title: Kernel crash with preinstalled Kinetic image Status in linux-allwinner package in Ubuntu: New Bug description: 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" plugged in the following crash occurs: [ 163.933818] Unable to handle kernel paging request at virtual address fffdf54d0289 [ 163.941784] Oops [#1] [ 163.944072] Modules linked in: binfmt_misc cfg80211 snd_soc_hdmi_codec dw_hdmi_i2s_audio dw_hdmi_cec sr9700 dm9601 usbnet pwrseq_simple sunxi_cir rc_core sun8i_drm_hdmi dw_hdmi sun8i_mixer sunxi phy_generic sunxi_cedrus(C) snd_soc_simple_card v4l2_mem2mem sun20i_codec snd_soc_dmic videobuf2_dma_contig snd_soc_simple_card_utils videobuf2_memops videobuf2_v4l2 sun4i_drm videobuf2_common sun4i_frontend sun4i_tcon sun8i_tcon_top display_connector drm_cma_helper snd_soc_core video
[Kernel-packages] [Bug 1989566] Re: [FFe] PolarFire Icicle Kit: enable PCIe support
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 in Ubuntu. https://bugs.launchpad.net/bugs/1989566 Title: [FFe] PolarFire Icicle Kit: enable PCIe support Status in linux-riscv package in Ubuntu: Invalid Bug description: The PolarFire Icicle Kit provides a PCIe slot. With our 5.19 kernel it is not usable. Please, add the following patches: # https://lore.kernel.org/linux-riscv/20220901133403.3392291-5-conor.doo...@microchip.com/ riscv: dts: microchip: add pci dma ranges for the icicle # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: move the mpfs' pci node to # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: update pci address # https://lore.kernel.org/linux-riscv/20220901133403.3392291-8-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: re-jig fabric peripheral # https://lore.kernel.org/linux-riscv/20220902142202.2437658-3-daire.mcnam...@microchip.com/ riscv: dts: microchip: add fabric address translation # https://lore.kernel.org/linux-riscv/20220902142202.2437658-4-daire.mcnam...@microchip.com/ PCI: microchip: add fabric address translation properties All patches are strictly restricted to the PolarFire Icicle Kit and have no impact on any other RISC-V boards that we support. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1989566/+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 2012706] Re: linux-image-6.2.0-18-generic booting with Nvidia drivers fails
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-19-generic* linux-modules-nvidia-515-5.19.0-21-generic* linux-modules-nvidia-515-6.1.0-16-generic* linux-modules-nvidia-515-6.2.0-18-generic* linux-modules-nvidia-515-generic* linux-objects-nvidia-515-5.19.0-19-generic* linux-objects-nvidia-515-5.19.0-21-generic* linux-objects-nvidia-515-6.1.0-16-generic* linux-objects-nvidia-515-6.2.0-18-generic* linux-signatures-nvidia-5.19.0-21-generic* linux-signatures-nvidia-6.1.0-16-generic* linux-signatures-nvidia-6.2.0-18-generic* nvidia-compute-utils-515* nvidia-driver-515* nvidia-kernel-common-515* nvidia-kernel-source-515* nvidia-prime* nvidia-settings* nvidia-utils-515* xserver-xorg-video-nvidia-515* ** Summary changed: - linux-image-6.2.0-18-generic booting with Nvidia drivers fails + linux-image-6.2.0-18-generic: booting with Nvidia drivers fails -- 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/2012706 Title: linux-image-6.2.0-18-generic: booting with Nvidia drivers fails Status in linux package in Ubuntu: New Bug description: 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-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 24 09:29:48 2023 InstallationDate: Installed on 2021-05-26 (666 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012706/+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 2012706] [NEW] linux-image-6.2.0-18-generic: booting with Nvidia drivers fails
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-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 24 09:29:48 2023 InstallationDate: Installed on 2021-05-26 (666 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2012706 Title: linux-image-6.2.0-18-generic: booting with Nvidia drivers fails Status in linux package in Ubuntu: New Bug description: 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-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 24 09:29:48 2023 InstallationDate: Installed on 2021-05-26 (666 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-pac
[Kernel-packages] [Bug 2012706] Re: linux-image-6.2.0-18-generic: booting with Nvidia drivers fails
*** 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 subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012706 Title: linux-image-6.2.0-18-generic: booting with Nvidia drivers fails Status in linux package in Ubuntu: Confirmed Bug description: 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-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Mar 24 09:29:48 2023 InstallationDate: Installed on 2021-05-26 (666 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012706/+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 2012559] Re: 6.2 kernel won't boot, may be nvidia related?
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 package in Ubuntu: Confirmed Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-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-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+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 2013743] Re: USB not working on Nezha D1
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 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub But that is not how it is meant to work. -- 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 description: 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 -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb 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 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2013743] [NEW] USB not working on Nezha D1
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 -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb 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 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor : 0 hart : 0 isa: rv64imafdc mmu: sv39 uarch : thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-allwinner (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug cloud-image lunar riscv64 -- 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 description: 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 -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb 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 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2013743] Re: USB not working on Nezha D1
** 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 description: 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 -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb 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 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2013743] Re: USB not working on Nezha D1
@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 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: Confirmed Bug description: 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 -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb 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 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2007829] Re: USB keyboard not detected
*** 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 Ubuntu. https://bugs.launchpad.net/bugs/2007829 Title: USB keyboard not detected Status in linux package in Ubuntu: Incomplete Bug description: I am currently testing the Nezha image according to http://iso.qa.ubuntu.com/qatracker/milestones/442/builds/271832/testcases/1755/results When I plugin a USB keyboard after the system is up it is correctly discovered. When I power up the device with a plugged in USB keyboard it is not detected. See the relevant kernel messages below. [ +0.000651] usbcore: registered new interface driver usbfs [ +0.000162] usbcore: registered new interface driver hub [ +0.000128] usbcore: registered new device driver usb [ +0.001479] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ +0.000489] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ +0.000532] uhci_hcd: USB Universal Host Controller Interface driver [ +0.000787] usbcore: registered new interface driver uas [ +0.000157] usbcore: registered new interface driver usb-storage [ +0.000300] usbcore: registered new interface driver usbserial_generic [ +0.000104] usbserial: USB Serial support registered for generic [ +0.000118] usbcore: registered new interface driver ch341 [ +0.94] usbserial: USB Serial support registered for ch341-uart [ +0.007873] ehci-platform 4101000.usb: EHCI Host Controller [ +0.005820] ehci-platform 4101000.usb: new USB bus registered, assigned bus number 1 [ +0.008338] ehci-platform 4101000.usb: irq 107, io mem 0x04101000 [ +0.014689] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00 [ +0.006889] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.17 [ +0.008389] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007304] usb usb1: Product: EHCI Host Controller [ +0.004955] usb usb1: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd [ +0.006776] usb usb1: SerialNumber: 4101000.usb [ +0.006016] hub 1-0:1.0: USB hub found [ +0.006124] ehci-platform 420.usb: EHCI Host Controller [ +0.005820] ehci-platform 420.usb: new USB bus registered, assigned bus number 2 [ +0.008177] ehci-platform 420.usb: irq 109, io mem 0x0420 [ +0.019500] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00 [ +0.006924] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.17 [ +0.008406] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007308] usb usb2: Product: EHCI Host Controller [ +0.004956] usb usb2: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd [ +0.006773] usb usb2: SerialNumber: 420.usb [ +0.006015] hub 2-0:1.0: USB hub found [ +0.030690] ohci-platform 4101400.usb: Generic Platform OHCI controller [ +0.006797] ohci-platform 4101400.usb: new USB bus registered, assigned bus number 3 [ +0.008115] ohci-platform 4101400.usb: irq 108, io mem 0x04101400 [ +0.069475] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.17 [ +0.008365] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007300] usb usb3: Product: Generic Platform OHCI controller [ +0.006002] usb usb3: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd [ +0.006775] usb usb3: SerialNumber: 4101400.usb [ +0.005758] hub 3-0:1.0: USB hub found [ +0.006081] ohci-platform 4200400.usb: Generic Platform OHCI controller [ +0.006750] ohci-platform 4200400.usb: new USB bus registered, assigned bus number 4 [ +0.008506] ohci-platform 4200400.usb: irq 110, io mem 0x04200400 [ +0.068747] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.17 [ +0.008395] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007335] usb usb4: Product: Generic Platform OHCI controller [ +0.006003] usb usb4: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd [ +0.006778] usb usb4: SerialNumber: 4200400.usb [ +0.006154] hub 4-0:1.0: USB hub found [ +0.016572] usb 2-1: new high-speed USB device number 2 using ehci-platform [ +0.613864] usb 4-1: new low-speed USB device number 2 using ohci-platform [ +0.207989] usb 4-1: device descriptor read/64, error -62 [ +0.304014] usb 4-1: device descriptor read/64, error -62 [ +0.29] usb 4-1: new low-speed USB device number 3 using ohci-platform [ +0.208012] usb 4-1: device descriptor read/64, error -62 [ +0.303984] usb 4-1: device descriptor read/64, error -62 [ +0.112175] usb usb4-port1: attempt power cycle [ +0.511829] usb 4-1: new low-speed USB device number 4 using ohci-platform [ +0.431956] usb 4-1: device not accepting address
[Kernel-packages] [Bug 2012559] Re: 6.2 kernel won't boot, may be nvidia related?
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 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 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in linux source package in Lunar: Invalid Status in nvidia-graphics-drivers-515 source package in Lunar: Fix Released Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-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-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+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 2013743] Re: USB not working on Nezha D1
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/bugs/2013743 Title: USB not working on Nezha D1 Status in linux-allwinner package in Ubuntu: Fix Released Bug description: 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 -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb 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 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+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 2016881] [NEW] Building for Focal fails on riscv64
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 notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2016881 Title: Building for Focal fails on riscv64 Status in zfs-linux package in Ubuntu: New Bug description: Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single patch missing: https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2016881] Re: Building for Focal fails on riscv64
** 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 Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2016881 Title: Building for Focal fails on riscv64 Status in zfs-linux package in Ubuntu: New Bug description: Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single patch missing: https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2038546] [NEW] /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
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 it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. ** Affects: linux-firmware (Ubuntu) Importance: High Status: Confirmed ** Tags: iso-testing mantic riscv64 ** Tags added: iso-testing mantic riscv64 ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High -- 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-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Confirmed Bug description: /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 it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2037065] Re: Wifi not working on StarFive VisionFive
*** 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, which is subscribed to linux-starfive in Ubuntu. https://bugs.launchpad.net/bugs/2037065 Title: Wifi not working on StarFive VisionFive Status in linux-starfive package in Ubuntu: New Bug description: I am currently testing http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/20230920/mantic-preinstalled-server- riscv64+visionfive.img.xz according to http://iso.qa.ubuntu.com/qatracker/milestones/448/builds/287116/testcases/1754/results 'nmcli dev wifi list' and 'ip a' do not show the WiFi device. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-5.19.0-1014-starfive 5.19.0-1014.16 ProcVersionSignature: Ubuntu 5.19.0-1014.16-starfive 5.19.17 Uname: Linux 5.19.0-1014-starfive riscv64 ApportVersion: 2.27.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230920 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Sep 22 09:05:10 2023 ProcCpuinfoMinimal: processor: 1 hart : 0 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc SourcePackage: linux-starfive UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive/+bug/2037065/+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 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
** 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 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-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Confirmed Bug description: /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 it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2038546] Re: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
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-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Confirmed Bug description: /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 it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+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 2038893] [NEW] probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004
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/qemu-riscv64_smode/uboot.elf -device virtio-net- device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio a crash was reported: Starting systemd-udevd version 253.5-1ubuntu6 [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044 [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.921064] Hardware name: riscv-virtio,qemu (DT) [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 7fffce174160 [3.921750] gp : 5fd56800 tp : 7fffade18780 t0 : 1000 [3.922110] t1 : 5fd53a3c t2 : 0034e6b4 s0 : 7fffae006ae0 [3.922422] s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 7fffae006ae0 [3.922751] a2 : 00022560 a3 : 7fff a4 : [3.923121] a5 : 00380045 a6 : 0007d436 a7 : 001d [3.923576] s2 : 0001 s3 : 7fffae005d80 s4 : 0003 [3.923913] s5 : 7d4352a0 s6 : s7 : 7fffce174160 [3.924251] s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 7fffce174178 [3.924585] s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : [3.924897] t5 : 7fffadfdda40 t6 : 7fffadfde028 [3.925090] status: 00024020 badaddr: 00380044 cause: 000c [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 0x00380044 [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.934742] Hardware name: riscv-virtio,qemu (DT) [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 7fffe3a88160 [3.935316] gp : 91f30800 tp : 7fff9b83a780 t0 : 1000 [3.935869] t1 : 91f2da3c t2 : 0034e6b4 s0 : 7fff9ba28ae0 [3.936224] s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 7fff9ba28ae0 [3.936606] a2 : 00022560 a3 : 7fff a4 : [3.937030] a5 : 00380045 a6 : 000b3fa0 a7 : 001d [3.937443] s2 : 0001 s3 : 7fff9ba27d80 s4 : 0003 [3.937868] s5 : b3f9f2a0 s6 : s7 : 7fffe3a88160 [3.938261] s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 7fffe3a88178 [3.938681] s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : [3.939113] t5 : 7fff9b9ffa40 t6 : 7fff9ba00028 [3.939469] status: 00024020 badaddr: 00380044 cause: 000c [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 0x00380044 [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.952680] Hardware name: riscv-virtio,qemu (DT) [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 7fffea625160 [3.953236] gp : 74eb1800 tp : 7fff86426780 t0 : 1000 [3.953582] t1 : 74eaea3c t2 : 0034e6b4 s0 : 7fff86614ae0 [3.953936] s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 7fff86614ae0 [3.954302] a2 : 00022560 a3 : 7fff a4 : [3.954700] a5 : 00380045 a6 : 0009411b a7 : 001d [3.955114] s2 : 0001 s3 : 7fff86613d80 s4 : 0003 [3.955657] s5 : 9411a2a0 s6 : s7 : 7fffea625160 [3.956018] s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 7fffea625178 [3.956368] s11: 7fffea625188 t3 : 7fff86598be8 t4 : [3.956741] t5 : 7fff865eba40 t6 : 7fff865ec028 [3.957026] status: 00024020 badaddr: 00380044 cause: 000c Begin: Loading essential drivers ... [6.255484] raid6: int64x8 gen() 635 MB/s ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 07:42:51 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-riscv (Ubuntu) Importance: Undecided
[Kernel-packages] [Bug 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004
** 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/bugs/2038893 Title: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044 Status in linux-riscv package in Ubuntu: New Bug description: 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/qemu-riscv64_smode/uboot.elf -device virtio-net- device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio a crash was reported: Starting systemd-udevd version 253.5-1ubuntu6 [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044 [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.921064] Hardware name: riscv-virtio,qemu (DT) [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 7fffce174160 [3.921750] gp : 5fd56800 tp : 7fffade18780 t0 : 1000 [3.922110] t1 : 5fd53a3c t2 : 0034e6b4 s0 : 7fffae006ae0 [3.922422] s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 7fffae006ae0 [3.922751] a2 : 00022560 a3 : 7fff a4 : [3.923121] a5 : 00380045 a6 : 0007d436 a7 : 001d [3.923576] s2 : 0001 s3 : 7fffae005d80 s4 : 0003 [3.923913] s5 : 7d4352a0 s6 : s7 : 7fffce174160 [3.924251] s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 7fffce174178 [3.924585] s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : [3.924897] t5 : 7fffadfdda40 t6 : 7fffadfde028 [3.925090] status: 00024020 badaddr: 00380044 cause: 000c [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 0x00380044 [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.934742] Hardware name: riscv-virtio,qemu (DT) [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 7fffe3a88160 [3.935316] gp : 91f30800 tp : 7fff9b83a780 t0 : 1000 [3.935869] t1 : 91f2da3c t2 : 0034e6b4 s0 : 7fff9ba28ae0 [3.936224] s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 7fff9ba28ae0 [3.936606] a2 : 00022560 a3 : 7fff a4 : [3.937030] a5 : 00380045 a6 : 000b3fa0 a7 : 001d [3.937443] s2 : 0001 s3 : 7fff9ba27d80 s4 : 0003 [3.937868] s5 : b3f9f2a0 s6 : s7 : 7fffe3a88160 [3.938261] s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 7fffe3a88178 [3.938681] s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : [3.939113] t5 : 7fff9b9ffa40 t6 : 7fff9ba00028 [3.939469] status: 00024020 badaddr: 00380044 cause: 000c [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 0x00380044 [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.952680] Hardware name: riscv-virtio,qemu (DT) [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 7fffea625160 [3.953236] gp : 74eb1800 tp : 7fff86426780 t0 : 1000 [3.953582] t1 : 74eaea3c t2 : 0034e6b4 s0 : 7fff86614ae0 [3.953936] s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 7fff86614ae0 [3.954302] a2 : 00022560 a3 : 7fff a4 : [3.954700] a5 : 00380045 a6 : 0009411b a7 : 001d [3.955114] s2 : 0001 s3 : 7fff86613d80 s4 : 0003 [3.955657] s5 : 9411a2a0 s6 : s7 : 7fffea625160 [3.956018] s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 7fffea625178 [3.956368] s11: 7fffea625188 t3 : 7fff86598be8 t4 : [3.956741] t5 : 7fff865eba40 t6 : 7fff865ec028 [3.957026] status: 00024020 badaddr: 00380044 cause: 000c Begin: Loading essential drivers ... [6.255484] raid6: int64x8 gen() 635 MB/s ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0
[Kernel-packages] [Bug 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004
$ 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: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044 Status in linux-riscv package in Ubuntu: New Bug description: 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/qemu-riscv64_smode/uboot.elf -device virtio-net- device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio a crash was reported: Starting systemd-udevd version 253.5-1ubuntu6 [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044 [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.921064] Hardware name: riscv-virtio,qemu (DT) [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 7fffce174160 [3.921750] gp : 5fd56800 tp : 7fffade18780 t0 : 1000 [3.922110] t1 : 5fd53a3c t2 : 0034e6b4 s0 : 7fffae006ae0 [3.922422] s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 7fffae006ae0 [3.922751] a2 : 00022560 a3 : 7fff a4 : [3.923121] a5 : 00380045 a6 : 0007d436 a7 : 001d [3.923576] s2 : 0001 s3 : 7fffae005d80 s4 : 0003 [3.923913] s5 : 7d4352a0 s6 : s7 : 7fffce174160 [3.924251] s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 7fffce174178 [3.924585] s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : [3.924897] t5 : 7fffadfdda40 t6 : 7fffadfde028 [3.925090] status: 00024020 badaddr: 00380044 cause: 000c [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 0x00380044 [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.934742] Hardware name: riscv-virtio,qemu (DT) [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 7fffe3a88160 [3.935316] gp : 91f30800 tp : 7fff9b83a780 t0 : 1000 [3.935869] t1 : 91f2da3c t2 : 0034e6b4 s0 : 7fff9ba28ae0 [3.936224] s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 7fff9ba28ae0 [3.936606] a2 : 00022560 a3 : 7fff a4 : [3.937030] a5 : 00380045 a6 : 000b3fa0 a7 : 001d [3.937443] s2 : 0001 s3 : 7fff9ba27d80 s4 : 0003 [3.937868] s5 : b3f9f2a0 s6 : s7 : 7fffe3a88160 [3.938261] s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 7fffe3a88178 [3.938681] s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : [3.939113] t5 : 7fff9b9ffa40 t6 : 7fff9ba00028 [3.939469] status: 00024020 badaddr: 00380044 cause: 000c [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 0x00380044 [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.952680] Hardware name: riscv-virtio,qemu (DT) [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 7fffea625160 [3.953236] gp : 74eb1800 tp : 7fff86426780 t0 : 1000 [3.953582] t1 : 74eaea3c t2 : 0034e6b4 s0 : 7fff86614ae0 [3.953936] s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 7fff86614ae0 [3.954302] a2 : 00022560 a3 : 7fff a4 : [3.954700] a5 : 00380045 a6 : 0009411b a7 : 001d [3.955114] s2 : 0001 s3 : 7fff86613d80 s4 : 0003 [3.955657] s5 : 9411a2a0 s6 : s7 : 7fffea625160 [3.956018] s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 7fffea625178 [3.956368] s11: 7fffea625188 t3 : 7fff86598be8 t4 : [3.956741] t5 : 7fff865eba40 t6 : 7fff865ec028 [3.957026] status: 00024020 badaddr: 00380044 cause: 000c Begin: Loading essential drivers ... [6.255484] raid6: int64x8 gen() 635 MB/s ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64
[Kernel-packages] [Bug 2038920] [NEW] Nezahl D1: usb 1-1: device descriptor read/64, error -71
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/64, error -62 [ 4460.461621] usb 4-1: device descriptor read/64, error -62 [ 4460.953646] usb 4-1: device descriptor read/64, error -62 [ 4461.257626] usb 4-1: device descriptor read/64, error -62 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 12:20:40 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug cloud-image mantic riscv64 -- 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, error -71 Status in linux-riscv package in Ubuntu: New Bug description: 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/64, error -62 [ 4460.461621] usb 4-1: device descriptor read/64, error -62 [ 4460.953646] usb 4-1: device descriptor read/64, error -62 [ 4461.257626] usb 4-1: device descriptor read/64, error -62 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 12:20:40 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038920] Re: Nezahl D1: usb 1-1: device descriptor read/64, error -71
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, error -71 Status in linux-riscv package in Ubuntu: New Bug description: 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/64, error -62 [ 4460.461621] usb 4-1: device descriptor read/64, error -62 [ 4460.953646] usb 4-1: device descriptor read/64, error -62 [ 4461.257626] usb 4-1: device descriptor read/64, error -62 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 12:20:40 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038920] Re: Nezahl D1: usb 1-1: device descriptor read/64, error -71
** 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 descriptor read/64, error -71 [ 4460.157594] usb 4-1: device descriptor read/64, error -62 [ 4460.461621] usb 4-1: device descriptor read/64, error -62 [ 4460.953646] usb 4-1: device descriptor read/64, error -62 [ 4461.257626] usb 4-1: device descriptor read/64, error -62 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 12:20:40 2023 ProcEnviron: - LANG=C.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=vt220 +  LANG=C.UTF-8 +  PATH=(custom, no user) +  SHELL=/bin/bash +  TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) -- 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, error -71 Status in linux-riscv package in Ubuntu: New Bug description: On the Nezha D1 board USB does not work correctly. 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 descriptor read/64, error -71 [ 4460.157594] usb 4-1: device descriptor read/64, error -62 [ 4460.461621] usb 4-1: device descriptor read/64, error -62 [ 4460.953646] usb 4-1: device descriptor read/64, error -62 [ 4461.257626] usb 4-1: device descriptor read/64, error -62 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 12:20:40 2023 ProcEnviron:  LANG=C.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038928] [NEW] Unable to handle kernel paging request at virtual address ffffff8a012abe1a
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 handle kernel paging request at virtual address ffb4fffc [ 4050.426326] Oops [#1] [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 6.5.0-9-generic #9.1-Ubuntu [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.521997] ra : lookup_fast+0x36/0xfc [ 4050.525837] epc : 80315146 ra : 803042bc sp : ffc800a6bab0 [ 4050.533056] gp : 822602d8 tp : ffd8c56ea880 t0 : ffc800a6bce8 [ 4050.540279] t1 : t2 : 812002e8 s0 : ffc800a6bae0 [ 4050.547502] s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : ffc800a6bc10 m[ 4050.554810] a2 : ffc800a6bc44 a3 : 0001 a4 : 00015635 [ 4050.562033] a5 : 00015635 a6 : 00035238 a7 : [ 4050.569254] s2 : 0002 s3 : ffd8c9fd8a80 s4 : 002e [ 4050.576476] s5 : 0020 s6 : 0070 s7 : fff6 [ 4050.583697] s8 : 0002 s9 : ffd8ca244025 s10: ffc800a6bc00 [ 4050.590918] s11: 002f t3 : ffd8c9fd8a80 t4 : 000335238e2d [ 4050.598141] t5 : ffc800a6bc44 t6 : ffd8ca244021 [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 000d [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100 [ 4050.616858] [] walk_component+0x26/0x194 [ 4050.622348] [] link_path_walk.part.0.constprop.0+0x1c2/0x2c2 [ 4050.629575] [] path_parentat+0x48/0x96 [ 4050.634890] [] __filename_parentat+0x9e/0x188 [ 4050.640813] [] do_renameat2+0xc8/0x4e2 [ 4050.646128] [] sys_renameat2+0x5a/0x76 [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154 [ 4050.657018] [] ret_from_exception+0x0/0x64 [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) ffc7 [ 4050.670148] ---[ end trace ]--- [ 4050.670271] Unable to handle kernel paging request at virtual address 005dfffc [ 4050.670360] Unable to handle kernel paging request at virtual address ffb4fffc [ 4050.670368] Oops [#2] [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G D 6.5.0-9-generic #9.1-Ubuntu [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.670574] ra : lookup_fast+0x36/0xfc [ 4050.670582] epc : 80315146 ra : 803042bc sp : ffc80212bb70 [ 4050.670587] gp : 822602d8 tp : ffd8cb66d100 t0 : ffc80212bdb8 [ 4050.670591] t1 : t2 : 812002e8 s0 : ffc80212bba0 [ 4050.670595] s1 : ffc80212bcd0 a0 : ffd8c9fd8a80 a1 : ffc80212bce0 [ 4050.670600] a2 : ffc80212bd14 a3 : 0001 a4 : 00015635 [ 4050.670604] a5 : 00015635 a6 : 00035238 a7 : [ 4050.670608] s2 : 0002 s3 : ffd8c9fd8a80 s4 : 002e [ 4050.670612] s5 : 0
[Kernel-packages] [Bug 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004
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 code 0x1 at 0x00380044 Status in bcache-tools package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Bug description: 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/qemu-riscv64_smode/uboot.elf -device virtio-net- device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio a crash was reported: Starting systemd-udevd version 253.5-1ubuntu6 [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044 [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.921064] Hardware name: riscv-virtio,qemu (DT) [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 7fffce174160 [3.921750] gp : 5fd56800 tp : 7fffade18780 t0 : 1000 [3.922110] t1 : 5fd53a3c t2 : 0034e6b4 s0 : 7fffae006ae0 [3.922422] s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 7fffae006ae0 [3.922751] a2 : 00022560 a3 : 7fff a4 : [3.923121] a5 : 00380045 a6 : 0007d436 a7 : 001d [3.923576] s2 : 0001 s3 : 7fffae005d80 s4 : 0003 [3.923913] s5 : 7d4352a0 s6 : s7 : 7fffce174160 [3.924251] s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 7fffce174178 [3.924585] s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : [3.924897] t5 : 7fffadfdda40 t6 : 7fffadfde028 [3.925090] status: 00024020 badaddr: 00380044 cause: 000c [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 0x00380044 [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.934742] Hardware name: riscv-virtio,qemu (DT) [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 7fffe3a88160 [3.935316] gp : 91f30800 tp : 7fff9b83a780 t0 : 1000 [3.935869] t1 : 91f2da3c t2 : 0034e6b4 s0 : 7fff9ba28ae0 [3.936224] s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 7fff9ba28ae0 [3.936606] a2 : 00022560 a3 : 7fff a4 : [3.937030] a5 : 00380045 a6 : 000b3fa0 a7 : 001d [3.937443] s2 : 0001 s3 : 7fff9ba27d80 s4 : 0003 [3.937868] s5 : b3f9f2a0 s6 : s7 : 7fffe3a88160 [3.938261] s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 7fffe3a88178 [3.938681] s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : [3.939113] t5 : 7fff9b9ffa40 t6 : 7fff9ba00028 [3.939469] status: 00024020 badaddr: 00380044 cause: 000c [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 0x00380044 [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic #9.1-Ubuntu [3.952680] Hardware name: riscv-virtio,qemu (DT) [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 7fffea625160 [3.953236] gp : 74eb1800 tp : 7fff86426780 t0 : 1000 [3.953582] t1 : 74eaea3c t2 : 0034e6b4 s0 : 7fff86614ae0 [3.953936] s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 7fff86614ae0 [3.954302] a2 : 00022560 a3 : 7fff a4 : [3.954700] a5 : 00380045 a6 : 0009411b a7 : 001d [3.955114] s2 : 0001 s3 : 7fff86613d80 s4 : 0003 [3.955657] s5 : 9411a2a0 s6 : s7 : 7fffea625160 [3.956018] s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 7fffea625178 [3.956368] s11: 7fffea625188 t3 : 7fff86598be8 t4 : [3.956741] t5 : 7fff865eba40 t6 : 7fff865ec028 [3.957026] status: 00024020 badaddr: 00380044 cause: 000c Begin: Loading essential drivers ... [6.255484] raid6: int64x8 gen() 635 MB/s ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic ri
[Kernel-packages] [Bug 2038933] [NEW] sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY
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 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 14:42:06 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug cloud-image mantic riscv64 -- 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 Ubuntu: New Bug description: 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 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 14:42:06 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY
** 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/2038933 Title: sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY Status in linux-riscv package in Ubuntu: New Bug description: 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 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 14:42:06 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a
-- 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: New Bug description: 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 handle kernel paging request at virtual address ffb4fffc [ 4050.426326] Oops [#1] [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 6.5.0-9-generic #9.1-Ubuntu [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.521997] ra : lookup_fast+0x36/0xfc [ 4050.525837] epc : 80315146 ra : 803042bc sp : ffc800a6bab0 [ 4050.533056] gp : 822602d8 tp : ffd8c56ea880 t0 : ffc800a6bce8 [ 4050.540279] t1 : t2 : 812002e8 s0 : ffc800a6bae0 [ 4050.547502] s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : ffc800a6bc10 m[ 4050.554810] a2 : ffc800a6bc44 a3 : 0001 a4 : 00015635 [ 4050.562033] a5 : 00015635 a6 : 00035238 a7 : [ 4050.569254] s2 : 0002 s3 : ffd8c9fd8a80 s4 : 002e [ 4050.576476] s5 : 0020 s6 : 0070 s7 : fff6 [ 4050.583697] s8 : 0002 s9 : ffd8ca244025 s10: ffc800a6bc00 [ 4050.590918] s11: 002f t3 : ffd8c9fd8a80 t4 : 000335238e2d [ 4050.598141] t5 : ffc800a6bc44 t6 : ffd8ca244021 [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 000d [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100 [ 4050.616858] [] walk_component+0x26/0x194 [ 4050.622348] [] link_path_walk.part.0.constprop.0+0x1c2/0x2c2 [ 4050.629575] [] path_parentat+0x48/0x96 [ 4050.634890] [] __filename_parentat+0x9e/0x188 [ 4050.640813] [] do_renameat2+0xc8/0x4e2 [ 4050.646128] [] sys_renameat2+0x5a/0x76 [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154 [ 4050.657018] [] ret_from_exception+0x0/0x64 [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) ffc7 [ 4050.670148] ---[ end trace ]--- [ 4050.670271] Unable to handle kernel paging request at virtual address 005dfffc [ 4050.670360] Unable to handle kernel paging request at virtual address ffb4fffc [ 4050.670368] Oops [#2] [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G D 6.5.0-9-generic #9.1-Ubuntu [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.670574] ra : lookup_fast+0x36/0xfc [ 4050.670582] epc : 80315146 ra : 803042bc sp : ffc80212bb70 [ 4050.670587] gp : 822602d8 tp : ffd8cb66d100 t0 : ffc80212bdb8 [ 4050.670591] t1 : t2 :
[Kernel-packages] [Bug 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a
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 axp20x_pek pwm_starfive dw_axi_dmac_platform sfctemp uio_pdrv_genirq uio drm dm_multipath efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive stmmac_platform stmmac nvme xhci_pci axp20x_regulator xhci_pci_renesas nvme_core dw_mmc_starfive pcs_xpcs phylink nvme_common dw_mmc_pltfm clk_starfive_jh7110_aon clk_starfive_jh7110_isp clk_starfive_jh7110_vout pinctrl_starfive_jh7110_aon dw_mmc axp20x_i2c axp20x spi_cadence_quadspi jh7110_trng phy_jh7110_usb [ 201.548071] CPU: 0 PID: 612 Comm: systemd-network Not tainted 6.5.0-9-generic #9.1-Ubuntu [ 201.556251] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 201.561824] epc : __d_lookup_rcu+0x4a/0x100 [ 201.566024] ra : lookup_fast+0x36/0xfc [ 201.569870] epc : 80315146 ra : 803042bc sp : ffc800ecb8b0 [ 201.577091] gp : 822602d8 tp : ffd8c6f6d100 t0 : ffc800ecba58 [ 201.584320] t1 : t2 : 0008 s0 : ffc800ecb8e0 [ 201.591547] s1 : ffc800ecb970 a0 : ffd8c49b8000 a1 : ffc800ecb980 [ 201.598772] a2 : ffc800ecb9b4 a3 : 0001 a4 : 3b91a71338836970 [ 201.605996] a5 : 3b91a71338836970 a6 : 361d a7 : [ 201.613222] s2 : 0001 s3 : ffd8c49b8000 s4 : f000 [ 201.620444] s5 : 0001 s6 : ffc800ecbca8 s7 : [ 201.627666] s8 : ffd8c705ca00 s9 : 000a s10: 7fff [ 201.634887] s11: 003fc689f768 t3 : ffd8c49b8000 t4 : 00060361d211 [ 201.642109] t5 : ffc800ecb9b4 t6 : ffd8c24b102d [ 201.647420] status: 00020120 badaddr: ff933883696c cause: 000d [ 201.655337] [] __d_lookup_rcu+0x4a/0x100 [ 201.660834] [] walk_component+0x26/0x194 [ 201.666325] [] path_lookupat+0x76/0x196 [ 201.671730] [] filename_lookup+0x96/0x166 [ 201.677306] [] kern_path+0x38/0x60 [ 201.682274] [] unix_find_other+0x50/0x36a [ 201.687850] [] unix_dgram_sendmsg+0x43c/0x81a [ 201.693771] [] sock_sendmsg+0x4e/0x98 [ 201.699004] [] sys_sendmsg+0x1d8/0x20a [ 201.704664] [] ___sys_sendmsg+0x90/0xd6 [ 201.710066] [] __sys_sendmsg+0x84/0xd2 [ 201.715380] [] sys_sendmsg+0x1e/0x2c [ 201.720521] [] do_trap_ecall_u+0xd6/0x154 [ 201.726099] [] ret_from_exception+0x0/0x64 [ 201.731773] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) ffc7 [ 201.739422] Unable to handle kernel paging request at virtual address ffbf0099039c [ 201.739559] Unable to handle kernel paging request at virtual address 00678895ce42 [ 201.740238] ---[ end trace ]--- -- 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: New Bug description: 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 handle kernel paging request at virtual address ffb4fffc [ 4050.426326] Oops [#1] [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 6.5.0-9-generic #9.1-Ubuntu [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.521997] ra : lookup_fast+0x36/0xfc [ 4050.525837] epc : 80315146 ra : 803042bc sp : ffc800a6
[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY
** 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 Ubuntu: New Bug description: 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 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 14:42:06 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a
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 handle kernel paging request at virtual address ff8a012abe1a Status in linux-riscv package in Ubuntu: New Bug description: 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 handle kernel paging request at virtual address ffb4fffc [ 4050.426326] Oops [#1] [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 6.5.0-9-generic #9.1-Ubuntu [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.521997] ra : lookup_fast+0x36/0xfc [ 4050.525837] epc : 80315146 ra : 803042bc sp : ffc800a6bab0 [ 4050.533056] gp : 822602d8 tp : ffd8c56ea880 t0 : ffc800a6bce8 [ 4050.540279] t1 : t2 : 812002e8 s0 : ffc800a6bae0 [ 4050.547502] s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : ffc800a6bc10 m[ 4050.554810] a2 : ffc800a6bc44 a3 : 0001 a4 : 00015635 [ 4050.562033] a5 : 00015635 a6 : 00035238 a7 : [ 4050.569254] s2 : 0002 s3 : ffd8c9fd8a80 s4 : 002e [ 4050.576476] s5 : 0020 s6 : 0070 s7 : fff6 [ 4050.583697] s8 : 0002 s9 : ffd8ca244025 s10: ffc800a6bc00 [ 4050.590918] s11: 002f t3 : ffd8c9fd8a80 t4 : 000335238e2d [ 4050.598141] t5 : ffc800a6bc44 t6 : ffd8ca244021 [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 000d [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100 [ 4050.616858] [] walk_component+0x26/0x194 [ 4050.622348] [] link_path_walk.part.0.constprop.0+0x1c2/0x2c2 [ 4050.629575] [] path_parentat+0x48/0x96 [ 4050.634890] [] __filename_parentat+0x9e/0x188 [ 4050.640813] [] do_renameat2+0xc8/0x4e2 [ 4050.646128] [] sys_renameat2+0x5a/0x76 [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154 [ 4050.657018] [] ret_from_exception+0x0/0x64 [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) ffc7 [ 4050.670148] ---[ end trace ]--- [ 4050.670271] Unable to handle kernel paging request at virtual address 005dfffc [ 4050.670360] Unable to handle kernel paging request at virtual address ffb4fffc [ 4050.670368] Oops [#2] [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G D 6.5.0-9-generic #9.1-Ubuntu [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.670574] ra : lookup_fast+0x36/0xfc [ 4050.670582] epc : 80315146 ra : 803042bc sp : ffc80212bb70 [ 4050.670587] gp : 8
[Kernel-packages] [Bug 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a
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 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: New Bug description: 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 handle kernel paging request at virtual address ffb4fffc [ 4050.426326] Oops [#1] [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 6.5.0-9-generic #9.1-Ubuntu [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.521997] ra : lookup_fast+0x36/0xfc [ 4050.525837] epc : 80315146 ra : 803042bc sp : ffc800a6bab0 [ 4050.533056] gp : 822602d8 tp : ffd8c56ea880 t0 : ffc800a6bce8 [ 4050.540279] t1 : t2 : 812002e8 s0 : ffc800a6bae0 [ 4050.547502] s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : ffc800a6bc10 m[ 4050.554810] a2 : ffc800a6bc44 a3 : 0001 a4 : 00015635 [ 4050.562033] a5 : 00015635 a6 : 00035238 a7 : [ 4050.569254] s2 : 0002 s3 : ffd8c9fd8a80 s4 : 002e [ 4050.576476] s5 : 0020 s6 : 0070 s7 : fff6 [ 4050.583697] s8 : 0002 s9 : ffd8ca244025 s10: ffc800a6bc00 [ 4050.590918] s11: 002f t3 : ffd8c9fd8a80 t4 : 000335238e2d [ 4050.598141] t5 : ffc800a6bc44 t6 : ffd8ca244021 [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 000d [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100 [ 4050.616858] [] walk_component+0x26/0x194 [ 4050.622348] [] link_path_walk.part.0.constprop.0+0x1c2/0x2c2 [ 4050.629575] [] path_parentat+0x48/0x96 [ 4050.634890] [] __filename_parentat+0x9e/0x188 [ 4050.640813] [] do_renameat2+0xc8/0x4e2 [ 4050.646128] [] sys_renameat2+0x5a/0x76 [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154 [ 4050.657018] [] ret_from_exception+0x0/0x64 [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) ffc7 [ 4050.670148] ---[ end trace ]--- [ 4050.670271] Unable to handle kernel paging request at virtual address 005dfffc [ 4050.670360] Unable to handle kernel paging request at virtual address ffb4fffc [ 4050.670368] Oops [#2] [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G D 6.5.0-9-generic #9.1-Ubuntu [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.670574] ra : lookup_fast+0x36/0xfc [ 4050.670582] epc : 80315146 ra
[Kernel-packages] [Bug 2038920] Re: Nezha D1: usb 1-1: device descriptor read/64, error -71
** 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/bugs/2038920 Title: Nezha D1: usb 1-1: device descriptor read/64, error -71 Status in linux-riscv package in Ubuntu: New Bug description: On the Nezha D1 board USB does not work correctly. 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 descriptor read/64, error -71 [ 4460.157594] usb 4-1: device descriptor read/64, error -62 [ 4460.461621] usb 4-1: device descriptor read/64, error -62 [ 4460.953646] usb 4-1: device descriptor read/64, error -62 [ 4461.257626] usb 4-1: device descriptor read/64, error -62 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 12:20:40 2023 ProcEnviron:  LANG=C.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a
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 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: Invalid Bug description: 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 handle kernel paging request at virtual address ffb4fffc [ 4050.426326] Oops [#1] [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 6.5.0-9-generic #9.1-Ubuntu [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.521997] ra : lookup_fast+0x36/0xfc [ 4050.525837] epc : 80315146 ra : 803042bc sp : ffc800a6bab0 [ 4050.533056] gp : 822602d8 tp : ffd8c56ea880 t0 : ffc800a6bce8 [ 4050.540279] t1 : t2 : 812002e8 s0 : ffc800a6bae0 [ 4050.547502] s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : ffc800a6bc10 m[ 4050.554810] a2 : ffc800a6bc44 a3 : 0001 a4 : 00015635 [ 4050.562033] a5 : 00015635 a6 : 00035238 a7 : [ 4050.569254] s2 : 0002 s3 : ffd8c9fd8a80 s4 : 002e [ 4050.576476] s5 : 0020 s6 : 0070 s7 : fff6 [ 4050.583697] s8 : 0002 s9 : ffd8ca244025 s10: ffc800a6bc00 [ 4050.590918] s11: 002f t3 : ffd8c9fd8a80 t4 : 000335238e2d [ 4050.598141] t5 : ffc800a6bc44 t6 : ffd8ca244021 [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 000d [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100 [ 4050.616858] [] walk_component+0x26/0x194 [ 4050.622348] [] link_path_walk.part.0.constprop.0+0x1c2/0x2c2 [ 4050.629575] [] path_parentat+0x48/0x96 [ 4050.634890] [] __filename_parentat+0x9e/0x188 [ 4050.640813] [] do_renameat2+0xc8/0x4e2 [ 4050.646128] [] sys_renameat2+0x5a/0x76 [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154 [ 4050.657018] [] ret_from_exception+0x0/0x64 [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) ffc7 [ 4050.670148] ---[ end trace ]--- [ 4050.670271] Unable to handle kernel paging request at virtual address 005dfffc [ 4050.670360] Unable to handle kernel paging request at virtual address ffb4fffc [ 4050.670368] Oops [#2] [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G D 6.5.0-9-generic #9.1-Ubuntu [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT) [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100 [ 4050.670574] ra : lookup_fast+0x36/0xfc [ 4050.670582]
[Kernel-packages] [Bug 2039782] [NEW] Stalls on CPUs/tasks on VisionFive 2 with external GPU
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 not observed this behavior on StarFive VisionFive 2 1.3B boards without an external GPU. The U-Boot installed on SPI flash is https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb [ 93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 softirq=2431/2431 fqs=41 [ 93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 ncpus=4) [ 93.140996] Task dump for CPU 0: [ 93.149549] task:swapper/0 state:R running task stack:0 pid:0 ppid:0 flags:0x [ 93.164907] Call Trace: [ 93.172715] [] __schedule+0x27a/0x82e [ 93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200 [ 93.200202] rcu: Possible timer handling issue on cpu=0 timer-softirq=890 [ 93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0 [ 93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 93.243573] rcu: RCU grace-period kthread stack dump: [ 93.254522] task:rcu_sched state:R stack:0 pid:15ppid:2 flags:0x [ 93.268895] Call Trace: [ 93.277340] [] __schedule+0x27a/0x82e [ 93.288646] [] schedule+0x4e/0xde [ 93.299623] [] schedule_timeout+0x8c/0x15e [ 93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4 [ 93.323170] [] rcu_gp_kthread+0x11a/0x142 [ 93.334901] [] kthread+0xc4/0xe4 [ 93.345833] [] ret_from_fork+0xe/0x20 ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Attachment added: "boot.log.txt" https://bugs.launchpad.net/bugs/2039782/+attachment/5711125/+files/boot.log.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/bugs/2039782 Title: Stalls on CPUs/tasks on VisionFive 2 with external GPU Status in linux-riscv package in Ubuntu: New Bug description: 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 not observed this behavior on StarFive VisionFive 2 1.3B boards without an external GPU. The U-Boot installed on SPI flash is https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb [ 93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 softirq=2431/2431 fqs=41 [ 93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 ncpus=4) [ 93.140996] Task dump for CPU 0: [ 93.149549] task:swapper/0 state:R running task stack:0 pid:0 ppid:0 flags:0x [ 93.164907] Call Trace: [ 93.172715] [] __schedule+0x27a/0x82e [ 93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200 [ 93.200202] rcu: Possible timer handling issue on cpu=0 timer-softirq=890 [ 93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0 [ 93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 93.243573] rcu: RCU grace-period kthread stack dump: [ 93.254522] task:rcu_sched state:R stack:0 pid:15ppid:2 flags:0x [ 93.268895] Call Trace: [ 93.277340] [] __schedule+0x27a/0x82e [ 93.288646] [] schedule+0x4e/0xde [ 93.299623] [] schedule_timeout+0x8c/0x15e [ 93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4 [ 93.323170] [] rcu_gp_kthread+0x11a/0x142 [ 93.334901] [] kthread+0xc4/0xe4 [ 93.345833] [] ret_from_fork+0xe/0x20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2039782/+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 1989566] Re: [FFe] PolarFire Icicle Kit: enable PCIe support
@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 the code: [PATCH v9 0/22] Refactoring Microchip PCIe driver and add StarFive PCIe https://lore.kernel.org/linux-riscv/20231020104341.63157-1-minda.c...@starfivetech.com/ -- 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/1989566 Title: [FFe] PolarFire Icicle Kit: enable PCIe support Status in linux-riscv package in Ubuntu: Confirmed Bug description: The PolarFire Icicle Kit provides a PCIe slot. With our 5.19 kernel it is not usable. Please, add the following patches: # https://lore.kernel.org/linux-riscv/20220901133403.3392291-5-conor.doo...@microchip.com/ riscv: dts: microchip: add pci dma ranges for the icicle # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: move the mpfs' pci node to # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: update pci address # https://lore.kernel.org/linux-riscv/20220901133403.3392291-8-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: re-jig fabric peripheral # https://lore.kernel.org/linux-riscv/20220902142202.2437658-3-daire.mcnam...@microchip.com/ riscv: dts: microchip: add fabric address translation # https://lore.kernel.org/linux-riscv/20220902142202.2437658-4-daire.mcnam...@microchip.com/ PCI: microchip: add fabric address translation properties All patches are strictly restricted to the PolarFire Icicle Kit and have no impact on any other RISC-V boards that we support. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1989566/+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 1975592] Re: Enable Nezha board
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. They could even run a custom U-Boot. Please avoid linking the kernel upgrade to any assumptions about U-Boot. Best regards Heinrich -- 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/1975592 Title: Enable Nezha board Status in linux-allwinner package in Ubuntu: Fix Released Status in linux-riscv package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in u-boot-nezha package in Ubuntu: Confirmed Bug description: [Impact] integrate linux-allwinner patches into linux-riscv kernel [Test] * Newly built images should boot and work on both nezha and licheerv * Upgraded systems using old images should reboot and work on both nezha and licheerv * Once this migrates, mantic+ livecd-rootfs can be improved to use generic kernel [Implementation details] * linux[-image]-allwinner depends on new enough generic kernel with allwinner support pull request applied; and on an updated u-boot-nezha package * new enough u-boot-nezha package ensures that MMC driver is included in the initramfs, and triggers initramfs update at the end of the apt transaction * End result, nezha/licheerv systems switch from tracking allwinner kernel to tracking generic kernel with initrd that contains MMC driver which used to be built-in. [Regression potential] Ensure this new build of linux-riscv doesn't regress on existing supported systems (sifive & qemu) scope: linux-riscv https://lists.ubuntu.com/archives/kernel-team/2023-May/139655.html u-boot-nezha patch attached linux-meta-riscv patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/1975592/+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 2077731] [NEW] riscv64 EDK 2 crashes in KVM based emulation
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_VARS.fd RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) t0 = 0x083FFFB28t1 = 0x083238BC8 t2 = 0x0t3 = 0x0 t4 = 0x0t5 = 0x0 t6 = 0x0s0 = 0x083FFFBC0 s1 = 0x0s2 = 0x0 s3 = 0x0s4 = 0x0 s5 = 0x0s6 = 0x0 s7 = 0x0s8 = 0x0 s9 = 0x0 s10 = 0x0 s11 = 0x0a0 = 0x17E1DDD10 a1 = 0x00021a2 = 0x17E1B1A80 a3 = 0x00032a4 = 0x00021 a5 = 0x00021a6 = 0x0832391E0 a7 = 0x083FFFA64 zero = 0x0 ra = 0x17E0AFA08sp = 0x4 gp = 0x0tp = 0x0 sepc = 0x17E0B0824 sstatus = 0x20120 stval = 0x0D20787D3 QEMU: Terminated To reproduce the issue: Run a Noble RISC-V virtual machine as described in https://wiki.ubuntu.com/RISC-V/QEMU. sudo apt-get update sudo apt-get install qemu-efi-riscv64 qemu-system-misc cp /usr/share/qemu-efi-riscv64/RISCV_VIRT_*.fd . qemu-system-riscv64 \ -M virt,acpi=off -accel tcg -m 1024 \ -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_VARS.fd # In the EFI shell reset -s sudo modprobe kvm sudo qemu-system-riscv64 \ -M virt,acpi=off -accel kvm -m 1024 \ -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_VARS.fd # A crash occurs # RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) # Terminate emulation with ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: qemu-efi-riscv64 2024.02-2 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-generic 6.8.1 Uname: Linux 6.8.0-31-generic riscv64 ApportVersion: 2.28.1-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20240423 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Aug 23 13:10:55 2024 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: edk2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: edk2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-riscv (Ubuntu) Importance: Undecided Status: New ** Affects: edk2 (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-meta-riscv (Ubuntu Noble) Importance: Undecided Status: New ** Tags: apport-bug cloud-image noble riscv64 ** Package changed: edk2 (Ubuntu) => linux-meta-riscv (Ubuntu) ** Also affects: edk2 (Ubuntu) Importance: Undecided Status: New ** Also affects: edk2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-meta-riscv (Ubuntu Noble) Importance: Undecided Status: New ** Summary changed: - riscv64 EDK 2 crashes in KVM + riscv64 EDK 2 crashes in KVM based emulation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2077731 Title: riscv64 EDK 2 crashes in KVM based emulation Status in edk2 package in Ubuntu: New Status in linux-meta-riscv package in Ubuntu: New Status in edk2 source package in Noble: New Status in linux-meta-riscv source package in Noble: New Bug description: 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_VARS.fd RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) t0 = 0x083FFFB28t1 = 0x083238BC8 t2 = 0x0t3 = 0x0 t4 = 0x0t5 = 0x0 t6 = 0x0s0 = 0x083FFFBC0 s1 = 0x0s2 = 0x0 s3 = 0x0s4 = 0x000
[Kernel-packages] [Bug 2077731] Re: riscv64 EDK 2 crashes in KVM based emulation
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: 87732eb0 RA: 8773c092 TVAL: EPC: 80214eb0 RA: 8021e092 reloc adjusted Code: f517 0006 0513 7305 b721 9002 4505 8082 ( ) The last line can be disassembled with objcopy. See Linux' scripts/decodecode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2077731 Title: riscv64 EDK 2 crashes in KVM based emulation Status in edk2 package in Ubuntu: New Status in linux-meta-riscv package in Ubuntu: New Status in edk2 source package in Noble: New Status in linux-meta-riscv source package in Noble: New Bug description: 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_VARS.fd RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) t0 = 0x083FFFB28t1 = 0x083238BC8 t2 = 0x0t3 = 0x0 t4 = 0x0t5 = 0x0 t6 = 0x0s0 = 0x083FFFBC0 s1 = 0x0s2 = 0x0 s3 = 0x0s4 = 0x0 s5 = 0x0s6 = 0x0 s7 = 0x0s8 = 0x0 s9 = 0x0 s10 = 0x0 s11 = 0x0a0 = 0x17E1DDD10 a1 = 0x00021a2 = 0x17E1B1A80 a3 = 0x00032a4 = 0x00021 a5 = 0x00021a6 = 0x0832391E0 a7 = 0x083FFFA64 zero = 0x0 ra = 0x17E0AFA08sp = 0x4 gp = 0x0tp = 0x0 sepc = 0x17E0B0824 sstatus = 0x20120 stval = 0x0D20787D3 QEMU: Terminated To reproduce the issue: Run a Noble RISC-V virtual machine as described in https://wiki.ubuntu.com/RISC-V/QEMU. sudo apt-get update sudo apt-get install qemu-efi-riscv64 qemu-system-misc cp /usr/share/qemu-efi-riscv64/RISCV_VIRT_*.fd . qemu-system-riscv64 \ -M virt,acpi=off -accel tcg -m 1024 \ -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_VARS.fd # In the EFI shell reset -s sudo modprobe kvm sudo qemu-system-riscv64 \ -M virt,acpi=off -accel kvm -m 1024 \ -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_VARS.fd # A crash occurs # RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) # Terminate emulation with ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: qemu-efi-riscv64 2024.02-2 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-generic 6.8.1 Uname: Linux 6.8.0-31-generic riscv64 ApportVersion: 2.28.1-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20240423 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Aug 23 13:10:55 2024 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: edk2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2077731/+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 2077731] Re: riscv64 EDK 2 crashes in KVM based emulation
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 notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2077731 Title: riscv64 EDK 2 crashes in KVM based emulation Status in edk2 package in Ubuntu: New Status in linux-meta-riscv package in Ubuntu: New Status in edk2 source package in Noble: New Status in linux-meta-riscv source package in Noble: New Status in edk2 source package in Oracular: New Status in linux-meta-riscv source package in Oracular: New Bug description: 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_VARS.fd RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) t0 = 0x083FFFB28t1 = 0x083238BC8 t2 = 0x0t3 = 0x0 t4 = 0x0t5 = 0x0 t6 = 0x0s0 = 0x083FFFBC0 s1 = 0x0s2 = 0x0 s3 = 0x0s4 = 0x0 s5 = 0x0s6 = 0x0 s7 = 0x0s8 = 0x0 s9 = 0x0 s10 = 0x0 s11 = 0x0a0 = 0x17E1DDD10 a1 = 0x00021a2 = 0x17E1B1A80 a3 = 0x00032a4 = 0x00021 a5 = 0x00021a6 = 0x0832391E0 a7 = 0x083FFFA64 zero = 0x0 ra = 0x17E0AFA08sp = 0x4 gp = 0x0tp = 0x0 sepc = 0x17E0B0824 sstatus = 0x20120 stval = 0x0D20787D3 QEMU: Terminated To reproduce the issue: Run a Noble RISC-V virtual machine as described in https://wiki.ubuntu.com/RISC-V/QEMU. sudo apt-get update sudo apt-get install qemu-efi-riscv64 qemu-system-misc cp /usr/share/qemu-efi-riscv64/RISCV_VIRT_*.fd . qemu-system-riscv64 \ -M virt,acpi=off -accel tcg -m 1024 \ -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_VARS.fd # In the EFI shell reset -s sudo modprobe kvm sudo qemu-system-riscv64 \ -M virt,acpi=off -accel kvm -m 1024 \ -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_VARS.fd # A crash occurs # RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) # Terminate emulation with ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: qemu-efi-riscv64 2024.02-2 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-generic 6.8.1 Uname: Linux 6.8.0-31-generic riscv64 ApportVersion: 2.28.1-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20240423 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Aug 23 13:10:55 2024 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: edk2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2077731/+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 2077731] Re: riscv64 EDK 2 crashes in KVM based emulation
** 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. https://bugs.launchpad.net/bugs/2077731 Title: riscv64 EDK 2 crashes in KVM based emulation Status in edk2 package in Ubuntu: New Status in linux-meta-riscv package in Ubuntu: New Status in edk2 source package in Noble: New Status in linux-meta-riscv source package in Noble: New Status in edk2 source package in Oracular: New Status in linux-meta-riscv source package in Oracular: New Bug description: 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_VARS.fd RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) t0 = 0x083FFFB28t1 = 0x083238BC8 t2 = 0x0t3 = 0x0 t4 = 0x0t5 = 0x0 t6 = 0x0s0 = 0x083FFFBC0 s1 = 0x0s2 = 0x0 s3 = 0x0s4 = 0x0 s5 = 0x0s6 = 0x0 s7 = 0x0s8 = 0x0 s9 = 0x0 s10 = 0x0 s11 = 0x0a0 = 0x17E1DDD10 a1 = 0x00021a2 = 0x17E1B1A80 a3 = 0x00032a4 = 0x00021 a5 = 0x00021a6 = 0x0832391E0 a7 = 0x083FFFA64 zero = 0x0 ra = 0x17E0AFA08sp = 0x4 gp = 0x0tp = 0x0 sepc = 0x17E0B0824 sstatus = 0x20120 stval = 0x0D20787D3 QEMU: Terminated To reproduce the issue: Run a Noble RISC-V virtual machine as described in https://wiki.ubuntu.com/RISC-V/QEMU. sudo apt-get update sudo apt-get install qemu-efi-riscv64 qemu-system-misc cp /usr/share/qemu-efi-riscv64/RISCV_VIRT_*.fd . qemu-system-riscv64 \ -M virt,acpi=off -accel tcg -m 1024 \ -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_VARS.fd # In the EFI shell reset -s sudo modprobe kvm sudo qemu-system-riscv64 \ -M virt,acpi=off -accel kvm -m 1024 \ -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_VARS.fd # A crash occurs # RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) # Terminate emulation with ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: qemu-efi-riscv64 2024.02-2 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-generic 6.8.1 Uname: Linux 6.8.0-31-generic riscv64 ApportVersion: 2.28.1-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20240423 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Aug 23 13:10:55 2024 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: edk2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2077731/+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 2077731] Re: riscv64 EDK 2 crashes in KVM based emulation
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://bugs.launchpad.net/bugs/2077731 Title: riscv64 EDK 2 crashes in KVM based emulation Status in edk2 package in Ubuntu: New Status in linux-meta-riscv package in Ubuntu: New Status in edk2 source package in Noble: New Status in linux-meta-riscv source package in Noble: New Status in edk2 source package in Oracular: New Status in linux-meta-riscv source package in Oracular: New Bug description: 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_VARS.fd RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) t0 = 0x083FFFB28t1 = 0x083238BC8 t2 = 0x0t3 = 0x0 t4 = 0x0t5 = 0x0 t6 = 0x0s0 = 0x083FFFBC0 s1 = 0x0s2 = 0x0 s3 = 0x0s4 = 0x0 s5 = 0x0s6 = 0x0 s7 = 0x0s8 = 0x0 s9 = 0x0 s10 = 0x0 s11 = 0x0a0 = 0x17E1DDD10 a1 = 0x00021a2 = 0x17E1B1A80 a3 = 0x00032a4 = 0x00021 a5 = 0x00021a6 = 0x0832391E0 a7 = 0x083FFFA64 zero = 0x0 ra = 0x17E0AFA08sp = 0x4 gp = 0x0tp = 0x0 sepc = 0x17E0B0824 sstatus = 0x20120 stval = 0x0D20787D3 QEMU: Terminated To reproduce the issue: Run a Noble RISC-V virtual machine as described in https://wiki.ubuntu.com/RISC-V/QEMU. sudo apt-get update sudo apt-get install qemu-efi-riscv64 qemu-system-misc cp /usr/share/qemu-efi-riscv64/RISCV_VIRT_*.fd . qemu-system-riscv64 \ -M virt,acpi=off -accel tcg -m 1024 \ -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_VARS.fd # In the EFI shell reset -s sudo modprobe kvm sudo qemu-system-riscv64 \ -M virt,acpi=off -accel kvm -m 1024 \ -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_VARS.fd # A crash occurs # RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) # Terminate emulation with ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: qemu-efi-riscv64 2024.02-2 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-generic 6.8.1 Uname: Linux 6.8.0-31-generic riscv64 ApportVersion: 2.28.1-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20240423 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Aug 23 13:10:55 2024 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: edk2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2077731/+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 2060868] [NEW] Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected noble ** Tags added: apport-collected noble ** Description changed: 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/seq:zfsdt 2886 F pipewire + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 24.04 + InstallationDate: Installed on 2023-12-12 (120 days ago) + InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) + Lspci-vt: + -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) + -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] + -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter + MachineType: LENOVO 21BXCTO1WW + Package: linux (not installed) + ProcEnviron: + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + ProcFB: 0 msmdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 + ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 + RelatedPackageVersions: + linux-restricted-modules-6.5.0-1004-laptop N/A + linux-backports-modules-6.5.0-1004-laptop N/A + linux-firmware 20240318.git3b128b60-0ubuntu2 + Tags: noble + Uname: Linux 6.5.0-1004-laptop aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + acpidump: + + dmi.bios.date: 12/05/2023 + dmi.bios.release: 1.59 + dmi.bios.vendor: LENOVO + dmi.bios.version: N3HET87W (1.59 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 21BXCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: + SDK0T76463 WIN + ptal8 + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.ec.firmware.release: 1.23 + dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: + dmi.product.family: ThinkPad X
[Kernel-packages] [Bug 2060868] IwConfig.txt
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/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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Lspci.txt
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 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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] CurrentDmesg.txt
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/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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] AlsaInfo.txt
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/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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Lsusb.txt
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 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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Lsusb-t.txt
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/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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Lsusb-v.txt
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/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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] ProcInterrupts.txt
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.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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] ProcCpuinfo.txt
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/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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] ProcModules.txt
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/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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] ProcCpuinfoMinimal.txt
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.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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] WifiSyslog.txt
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 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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] RfKill.txt
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 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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] UdevDb.txt
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 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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
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 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: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-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 and 6.8.0-22-generic Status in linux package in Ubuntu: New Bug description: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2062548] Re: RISC-V: [drm] Display Core failed to initialize with v3.2.266!
** 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/bugs/2062548
Title:
RISC-V: [drm] Display Core failed to initialize with v3.2.266!
Status in linux-riscv package in Ubuntu:
New
Bug description:
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 works fine but that is using another firmware driver.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
Uname: Linux 6.8.0-20-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Apr 19 13:00:35 2024
InstallationDate: Installed on 2024-04-18 (1 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64
(20240418)
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+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 2062548] [NEW] RISC-V: [drm] Display Core failed to initialize with v3.2.266!
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 works fine but that is using another firmware driver.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
Uname: Linux 6.8.0-20-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Apr 19 13:00:35 2024
InstallationDate: Installed on 2024-04-18 (1 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64
(20240418)
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug noble riscv64
--
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/2062548
Title:
RISC-V: [drm] Display Core failed to initialize with v3.2.266!
Status in linux-riscv package in Ubuntu:
New
Bug description:
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 works fine but that is using another firmware driver.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
Uname: Linux 6.8.0-20-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Apr 19 13:00:35 2024
InstallationDate: Installed on 2024-04-18 (1 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64
(20240418)
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+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 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY
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@550 [0.141784] platform 550.hdmi: Fixed dependency cycle(s) with /soc/tcon-top@546 [0.151475] platform 550.hdmi: Fixed dependency cycle(s) with /connector [0.151769] platform connector: Fixed dependency cycle(s) with /soc/hdmi@550 [ 63.119552] sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY [ 63.287954] sun8i-dw-hdmi 550.hdmi: Detected HDMI TX controller v2.12a with HDCP (sun8i_dw_hdmi_phy) [ 63.298653] sun8i-dw-hdmi 550.hdmi: registered DesignWare HDMI I2C bus driver [ 63.299605] sun4i-drm display-engine: bound 550.hdmi (ops sun8i_dw_hdmi_ops [sun8i_drm_hdmi]) [ 72.732580] rc rc0: dw_hdmi as /devices/platform/soc/550.hdmi/rc/rc0 [ 72.733035] input: dw_hdmi as /devices/platform/soc/550.hdmi/rc/rc0/input1 -- 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 Ubuntu: Confirmed Bug description: 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 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 14:42:06 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2063300] [NEW] On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not detected
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, Driver=hub/4p, 480M |__ Port 002: Dev 009, If 0, Class=[unknown], Driver=dm9601, 12M |__ Port 004: Dev 010, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=musb-hdrc/1p, 480M $ dmesg | grep -i usb [0.200341] usbcore: registered new interface driver usbfs [0.200487] usbcore: registered new interface driver hub [0.200635] usbcore: registered new device driver usb [ 54.280232] ehci-platform 420.usb: EHCI Host Controller [ 54.280305] ehci-platform 420.usb: new USB bus registered, assigned bus number 1 [ 54.280729] ehci-platform 420.usb: irq 224, io mem 0x0420 [ 54.280897] ehci-platform 4101000.usb: EHCI Host Controller [ 54.280986] ehci-platform 4101000.usb: new USB bus registered, assigned bus number 2 [ 54.281606] ehci-platform 4101000.usb: irq 223, io mem 0x04101000 [ 54.300035] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00 [ 54.302412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08 [ 54.302448] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 54.302466] usb usb1: Product: EHCI Host Controller [ 54.302480] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd [ 54.302495] usb usb1: SerialNumber: 420.usb [ 54.312820] hub 1-0:1.0: USB hub found [ 54.321384] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00 [ 54.329391] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08 [ 54.329426] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 54.329444] usb usb2: Product: EHCI Host Controller [ 54.329459] usb usb2: Manufacturer: Linux 6.8.0-31-generic ehci_hcd [ 54.329474] usb usb2: SerialNumber: 4101000.usb [ 54.340294] hub 2-0:1.0: USB hub found [ 54.577549] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 54.767079] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.00 [ 54.767115] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 54.767133] usb 1-1: Product: USB2.0 HUB [ 54.769892] hub 1-1:1.0: USB hub found [ 55.201407] usb 1-1.2: new full-speed USB device number 3 using ehci-platform [ 55.429317] usb 1-1.2: device descriptor read/all, error -32 [ 55.641464] usb 1-1.2: new full-speed USB device number 4 using ehci-platform [ 55.709568] ohci-platform 4101400.usb: Generic Platform OHCI controller [ 55.709638] ohci-platform 4101400.usb: new USB bus registered, assigned bus number 3 [ 55.709960] ohci-platform 4101400.usb: irq 225, io mem 0x04101400 [ 55.746077] ohci-platform 4200400.usb: Generic Platform OHCI controller [ 55.746145] ohci-platform 4200400.usb: new USB bus registered, assigned bus number 4 [ 55.746450] ohci-platform 4200400.usb: irq 226, io mem 0x04200400 [ 55.794102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.08 [ 55.794138] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 55.794158] usb usb3: Product: Generic Platform OHCI controller [ 55.794173] usb usb3: Manufacturer: Linux 6.8.0-31-generic ohci_hcd [ 55.794189] usb usb3: SerialNumber: 4101400.usb [ 55.802158] hub 3-0:1.0: USB hub found [ 55.841520] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.08 [ 55.841556] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 55.841574] usb usb4: Product: Generic Platform OHCI controller [ 55.841590] usb usb4: Manufacturer: Linux 6.8.0-31-generic ohci_hcd [ 55.841605] usb usb4: SerialNumber: 4200400.usb [ 55.849788] hub 4-0:1.0: USB hub found [ 57.570642] usb_phy_generic usb_phy_generic.1.auto: dummy supplies not allowed for exclusive requests [ 57.572184] musb-hdrc musb-hdrc.2.auto: MUSB HDRC host driver [ 57.572253] musb-hdrc musb-hdrc.2.auto: new USB bus registered, assigned bus number 5 [ 57.650728] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08 [ 57.650766] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 57.650784] usb usb5: Product: MUSB HDRC host driver [ 57.650799] usb usb5: Manufacturer: Linux 6.8.0-31-generic musb-hcd [ 57.650814] usb usb5: SerialNumber: musb-hdrc.2.auto [ 57.711752] hub 5-0:1.0: USB hub found [ 61.089405] usb 1-1.2: device descriptor read/64, error -71 [ 66.477463] usb 1-1.2: device descriptor read/64, error -71
[Kernel-packages] [Bug 2063300] Re: On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not detected
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 detected Status in linux-riscv package in Ubuntu: New Bug description: 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, Driver=hub/4p, 480M |__ Port 002: Dev 009, If 0, Class=[unknown], Driver=dm9601, 12M |__ Port 004: Dev 010, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=musb-hdrc/1p, 480M $ dmesg | grep -i usb [0.200341] usbcore: registered new interface driver usbfs [0.200487] usbcore: registered new interface driver hub [0.200635] usbcore: registered new device driver usb [ 54.280232] ehci-platform 420.usb: EHCI Host Controller [ 54.280305] ehci-platform 420.usb: new USB bus registered, assigned bus number 1 [ 54.280729] ehci-platform 420.usb: irq 224, io mem 0x0420 [ 54.280897] ehci-platform 4101000.usb: EHCI Host Controller [ 54.280986] ehci-platform 4101000.usb: new USB bus registered, assigned bus number 2 [ 54.281606] ehci-platform 4101000.usb: irq 223, io mem 0x04101000 [ 54.300035] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00 [ 54.302412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08 [ 54.302448] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 54.302466] usb usb1: Product: EHCI Host Controller [ 54.302480] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd [ 54.302495] usb usb1: SerialNumber: 420.usb [ 54.312820] hub 1-0:1.0: USB hub found [ 54.321384] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00 [ 54.329391] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08 [ 54.329426] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 54.329444] usb usb2: Product: EHCI Host Controller [ 54.329459] usb usb2: Manufacturer: Linux 6.8.0-31-generic ehci_hcd [ 54.329474] usb usb2: SerialNumber: 4101000.usb [ 54.340294] hub 2-0:1.0: USB hub found [ 54.577549] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 54.767079] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.00 [ 54.767115] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 54.767133] usb 1-1: Product: USB2.0 HUB [ 54.769892] hub 1-1:1.0: USB hub found [ 55.201407] usb 1-1.2: new full-speed USB device number 3 using ehci-platform [ 55.429317] usb 1-1.2: device descriptor read/all, error -32 [ 55.641464] usb 1-1.2: new full-speed USB device number 4 using ehci-platform [ 55.709568] ohci-platform 4101400.usb: Generic Platform OHCI controller [ 55.709638] ohci-platform 4101400.usb: new USB bus registered, assigned bus number 3 [ 55.709960] ohci-platform 4101400.usb: irq 225, io mem 0x04101400 [ 55.746077] ohci-platform 4200400.usb: Generic Platform OHCI controller [ 55.746145] ohci-platform 4200400.usb: new USB bus registered, assigned bus number 4 [ 55.746450] ohci-platform 4200400.usb: irq 226, io mem 0x04200400 [ 55.794102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.08 [ 55.794138] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 55.794158] usb usb3: Product: Generic Platform OHCI controller [ 55.794173] usb usb3: Manufacturer: Linux 6.8.0-31-generic ohci_hcd [ 55.794189] usb usb3: SerialNumber: 4101400.usb [ 55.802158] hub 3-0:1.0: USB hub found [ 55.841520] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.08 [ 55.841556] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 55.841574] usb usb4: Product: Generic Platform OHCI controller [ 55.841590] usb usb4: Manufacturer: Linux 6.8.0-31-generic ohci_hcd [ 55.841605] usb usb4: SerialNumber: 4200400.usb [ 55.849788] hub 4-0:1.0: USB hub found [ 57.570642] usb_phy_generic usb_phy_generic.1.auto: dummy supplies not allowed for exclusive requests [ 57.572184] musb-hdrc musb-hdrc.2.auto: MUSB HDRC host driver [ 57.572253] musb-hdrc musb-hdrc.2.auto: new USB bus registered, assigned bus number 5 [ 57.650728] usb usb5: New USB device found
[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY
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 Title: sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY Status in linux-riscv package in Ubuntu: Confirmed Bug description: 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 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 14:42:06 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2063309] [NEW] RISC-V: nouveau 0000:05:00.0: timer: stalled at ffffffffffffffff
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-image-6.8.0-28-generic 6.8.0-28.28.1 ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1 Uname: Linux 6.8.0-28-generic riscv64 ApportVersion: 2.28.1-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20210714 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Wed Apr 24 09:43:12 2024 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug cloud-image noble riscv64 -- 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 Status in linux-riscv package in Ubuntu: New Bug description: 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-image-6.8.0-28-generic 6.8.0-28.28.1 ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1 Uname: Linux 6.8.0-28-generic riscv64 ApportVersion: 2.28.1-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20210714 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Wed Apr 24 09:43:12 2024 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2063309/+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 2063309] Re: RISC-V: nouveau 0000:05:00.0: timer: stalled at ffffffffffffffff
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 Status in linux-riscv package in Ubuntu: New Bug description: 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-image-6.8.0-28-generic 6.8.0-28.28.1 ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1 Uname: Linux 6.8.0-28-generic riscv64 ApportVersion: 2.28.1-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20210714 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Wed Apr 24 09:43:12 2024 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2063309/+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 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY
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 Alexandre wrote the tests it was explicitly foreseen to plug in HDMI after login. So this must have worked previously. -- 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 Ubuntu: Confirmed Bug description: 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 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20231010 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue Oct 10 14:42:06 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-riscv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
@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 defines the modules to be included in the initrd? -- 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: Confirmed Status in linux source package in Noble: Confirmed Bug description: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2054325] [NEW] nouveau 0000:05:00.0: timeout on HiFive SiFive Unmatched
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/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0x11a/0x12a [nouveau] [ +0.008579] Modules linked in: tls binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundc> [ +0.000245] CPU: 2 PID: 2028 Comm: kworker/2:3 Tainted: GW 6.5.0-17-generic #17.1.1~22.04.1-Ubuntu [ +0.11] Hardware name: SiFive HiFive Unmatched A00 (DT) [ +0.07] Workqueue: events drm_fb_helper_damage_work [drm_kms_helper] [ +0.000715] epc : g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006843] ra : g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006368] epc : 026becf8 ra : 026becf8 sp : ffc80172b6c0 [ +0.08] gp : 822603c8 tp : ffd89ae05100 t0 : 820bd738 [ +0.06] t1 : t2 : 2d2d2d2d2d2d2d2d s0 : ffc80172b720 [ +0.05] s1 : ffd887482000 a0 : a1 : [ +0.06] a2 : a3 : a4 : [ +0.06] a5 : a6 : a7 : [ +0.05] s2 : 0007 s3 : ffd89d6d19b8 s4 : 00020022 [ +0.06] s5 : 0046 s6 : 0046 s7 : [ +0.06] s8 : 1000 s9 : 1000 s10: ffc80172b9c8 [ +0.06] s11: ffd887144000 t3 : t4 : [ +0.06] t5 : t6 : ffc80172b4b8 [ +0.04] status: 00020100 badaddr: 0058 cause: 0003 [ +0.10] [] g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006810] [] nvkm_bar_flush+0x1a/0x2c [nouveau] [ +0.006619] [] nv50_instobj_release+0x34/0x90 [nouveau] [ +0.006681] [] gf100_vmm_pgt_mem+0x11a/0x1c0 [nouveau] [ +0.006721] [] nvkm_vmm_iter.constprop.0+0x37e/0x44e [nouveau] [ +0.006638] [] nvkm_vmm_ptes_get_map+0x36/0x98 [nouveau] [ +0.006891] [] nvkm_vmm_map_locked+0x190/0x2bc [nouveau] [ +0.006817] [] nvkm_vmm_map+0x46/0x7e [nouveau] [ +0.006676] [] nvkm_vram_map+0x68/0x98 [nouveau] [ +0.006690] [] gf100_mem_map+0x98/0x12c [nouveau] [ +0.006985] [] nvkm_umem_map+0x50/0xc4 [nouveau] [ +0.007003] [] nvkm_object_map+0x1e/0x42 [nouveau] [ +0.006670] [] nvkm_ioctl_map+0x76/0xf2 [nouveau] [ +0.007303] [] nvkm_ioctl+0xaa/0x208 [nouveau] [ +0.006766] [] nvkm_client_ioctl+0x18/0x26 [nouveau] [ +0.006833] [] nvif_object_map_handle+0x90/0xf6 [nouveau] [ +0.007200] [] nouveau_ttm_io_mem_reserve+0x13a/0x222 [nouveau] [ +0.007131] [] ttm_bo_vmap+0x82/0x120 [ttm] [ +0.000263] [] drm_gem_ttm_vmap+0x18/0x22 [drm_ttm_helper] [ +0.24] [] drm_gem_vmap+0x1e/0x40 [drm] [ +0.001963] [] drm_gem_vmap_unlocked+0x30/0x50 [drm] [ +0.000915] [] drm_client_buffer_vmap+0x26/0x44 [drm] [ +0.001034] [] drm_fbdev_generic_helper_fb_dirty+0xa2/0x190 [drm_kms_helper] [ +0.000717] [] drm_fb_helper_fb_dirty+0x86/0x174 [drm_kms_helper] [ +0.000286] [] drm_fb_helper_damage_work+0x1c/0x26 [drm_kms_helper] [ +0.000272] [] process_one_work+0x1f6/0x390 [ +0.24] [] worker_thread+0x8a/0x456 [ +0.11] [] kthread+0xc4/0xe4 [ +0.12] [] ret_from_fork+0xe/0x20 [ +0.14] ---[ end trace ]--- [ +0.133717] nouveau :05:00.0: timer: stalled at [ +0.007740] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17.1.1~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17.1.1~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic riscv64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Mon Feb 19 15:47:49 2024 SourcePackage: linux-riscv-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-riscv-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug jammy riscv64 uec-images -- 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 Title: nouveau :05:00.0: timeout on HiFive SiFive Unmatched Status in linux-riscv-6.5 package in Ubuntu: New Bug description: 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/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0x11a/0x12
[Kernel-packages] [Bug 2054325] Re: nouveau 0000:05:00.0: timeout on HiFive SiFive Unmatched
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 Title: nouveau :05:00.0: timeout on HiFive SiFive Unmatched Status in linux-riscv-6.5 package in Ubuntu: New Bug description: 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/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0x11a/0x12a [nouveau] [ +0.008579] Modules linked in: tls binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundc> [ +0.000245] CPU: 2 PID: 2028 Comm: kworker/2:3 Tainted: GW 6.5.0-17-generic #17.1.1~22.04.1-Ubuntu [ +0.11] Hardware name: SiFive HiFive Unmatched A00 (DT) [ +0.07] Workqueue: events drm_fb_helper_damage_work [drm_kms_helper] [ +0.000715] epc : g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006843] ra : g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006368] epc : 026becf8 ra : 026becf8 sp : ffc80172b6c0 [ +0.08] gp : 822603c8 tp : ffd89ae05100 t0 : 820bd738 [ +0.06] t1 : t2 : 2d2d2d2d2d2d2d2d s0 : ffc80172b720 [ +0.05] s1 : ffd887482000 a0 : a1 : [ +0.06] a2 : a3 : a4 : [ +0.06] a5 : a6 : a7 : [ +0.05] s2 : 0007 s3 : ffd89d6d19b8 s4 : 00020022 [ +0.06] s5 : 0046 s6 : 0046 s7 : [ +0.06] s8 : 1000 s9 : 1000 s10: ffc80172b9c8 [ +0.06] s11: ffd887144000 t3 : t4 : [ +0.06] t5 : t6 : ffc80172b4b8 [ +0.04] status: 00020100 badaddr: 0058 cause: 0003 [ +0.10] [] g84_bar_flush+0x11a/0x12a [nouveau] [ +0.006810] [] nvkm_bar_flush+0x1a/0x2c [nouveau] [ +0.006619] [] nv50_instobj_release+0x34/0x90 [nouveau] [ +0.006681] [] gf100_vmm_pgt_mem+0x11a/0x1c0 [nouveau] [ +0.006721] [] nvkm_vmm_iter.constprop.0+0x37e/0x44e [nouveau] [ +0.006638] [] nvkm_vmm_ptes_get_map+0x36/0x98 [nouveau] [ +0.006891] [] nvkm_vmm_map_locked+0x190/0x2bc [nouveau] [ +0.006817] [] nvkm_vmm_map+0x46/0x7e [nouveau] [ +0.006676] [] nvkm_vram_map+0x68/0x98 [nouveau] [ +0.006690] [] gf100_mem_map+0x98/0x12c [nouveau] [ +0.006985] [] nvkm_umem_map+0x50/0xc4 [nouveau] [ +0.007003] [] nvkm_object_map+0x1e/0x42 [nouveau] [ +0.006670] [] nvkm_ioctl_map+0x76/0xf2 [nouveau] [ +0.007303] [] nvkm_ioctl+0xaa/0x208 [nouveau] [ +0.006766] [] nvkm_client_ioctl+0x18/0x26 [nouveau] [ +0.006833] [] nvif_object_map_handle+0x90/0xf6 [nouveau] [ +0.007200] [] nouveau_ttm_io_mem_reserve+0x13a/0x222 [nouveau] [ +0.007131] [] ttm_bo_vmap+0x82/0x120 [ttm] [ +0.000263] [] drm_gem_ttm_vmap+0x18/0x22 [drm_ttm_helper] [ +0.24] [] drm_gem_vmap+0x1e/0x40 [drm] [ +0.001963] [] drm_gem_vmap_unlocked+0x30/0x50 [drm] [ +0.000915] [] drm_client_buffer_vmap+0x26/0x44 [drm] [ +0.001034] [] drm_fbdev_generic_helper_fb_dirty+0xa2/0x190 [drm_kms_helper] [ +0.000717] [] drm_fb_helper_fb_dirty+0x86/0x174 [drm_kms_helper] [ +0.000286] [] drm_fb_helper_damage_work+0x1c/0x26 [drm_kms_helper] [ +0.000272] [] process_one_work+0x1f6/0x390 [ +0.24] [] worker_thread+0x8a/0x456 [ +0.11] [] kthread+0xc4/0xe4 [ +0.12] [] ret_from_fork+0xe/0x20 [ +0.14] ---[ end trace ]--- [ +0.133717] nouveau :05:00.0: timer: stalled at [ +0.007740] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17.1.1~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17.1.1~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic riscv64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Mon Feb 19 15:47:49 2024 SourcePackage: linux-riscv-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-6.5/+bug/2054325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@l
[Kernel-packages] [Bug 2054814] [NEW] lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic
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, failing.
The "9pnet_virtio: no channels available for device config" messages occur
frequently in the kernel log and did not exist in kernels prior to 6.5.
Removing the 9pnet_virtio module does not resolve the issue.
Best regards
Heinrich
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Feb 23 12:28:11 2024
InstallationDate: Installed on 2023-12-04 (81 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 (20231204)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug noble riscv64
--
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 linux-riscv package in Ubuntu:
New
Bug description:
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, failing.
The "9pnet_virtio: no channels available for device config" messages occur
frequently in the kernel log and did not exist in kernels prior to 6.5.
Removing the 9pnet_virtio module does not resolve the issue.
Best regards
Heinrich
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Feb 23 12:28:11 2024
InstallationDate: Installed on 2023-12-04 (81 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2054814/+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 2054814] Re: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic
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 linux-riscv package in Ubuntu:
New
Bug description:
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, failing.
The "9pnet_virtio: no channels available for device config" messages occur
frequently in the kernel log and did not exist in kernels prior to 6.5.
Removing the 9pnet_virtio module does not resolve the issue.
Best regards
Heinrich
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Feb 23 12:28:11 2024
InstallationDate: Installed on 2023-12-04 (81 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2054814/+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 2054814] Re: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic
** 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.0-9-generic
Status in lxd-agent-loader package in Ubuntu:
New
Bug description:
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, failing.
The "9pnet_virtio: no channels available for device config" messages occur
frequently in the kernel log and did not exist in kernels prior to 6.5.
Removing the 9pnet_virtio module does not resolve the issue.
Best regards
Heinrich
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Feb 23 12:28:11 2024
InstallationDate: Installed on 2023-12-04 (81 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64
(20231204)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+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 2016881] Re: zfs-linux FTBFS for riscv64 on Focal
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 is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2016881 Title: zfs-linux FTBFS for riscv64 on Focal Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Won't Fix Status in zfs-linux source package in Focal: Won't Fix Bug description: [Impact] * riscv64 builds fail completely, so users on that architecture can't use ZFS. [Test Plan] * Build zfs-linux on target architecture. No test failure is expected. [Where problems could occur] * Test failures and bugs that are exclusive to RISCV64 might show up [Other Info] * Upstream introduced support riscv64 with 4254e407294b * Builds succeed on Jammy and newer, Focal is missing the enablement patch -- [Original Description] Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single patch missing: https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
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 and 6.8.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: 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/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 1861053] Re: fatrace doesn't trace on zfs filesystems
$ 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)
Status: New => Invalid
--
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/1861053
Title:
fatrace doesn't trace on zfs filesystems
Status in fatrace package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Invalid
Bug description:
Hello, fatrace in focal doesn't seem to work for me in focal.
Start fatrace in one terminal, and perform file operations in another
terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.
sarnold@millbarge:~$ sudo fatrace
[sudo] password for sarnold:
^Csarnold@millbarge:~$ sudo strace -yy fatrace
execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
brk(NULL) = 0x55c9a1947000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid
argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) =
0x7f3539b15000
close(3) = 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) =
3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
lseek(3, 64, SEEK_SET) = 64
read(3,
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
lseek(3, 848, SEEK_SET) = 848
read(3,
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
lseek(3, 880, SEEK_SET) = 880
read(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
68) = 68
fstat(3, {st_mode=S_IFREG|0755,
st_size=2025032, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f3539b13000
lseek(3, 64, SEEK_SET) = 64
read(3,
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
lseek(3, 848, SEEK_SET) = 848
read(3,
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
lseek(3, 880, SEEK_SET) = 880
read(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
68) = 68
mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE,
3, 0) = 0x7f3539922000
mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x25000) = 0x7f3539947000
mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE,
3, 0x19d000) = 0x7f3539abf000
mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x1e6000) = 0x7f3539b09000
mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
munmap(0x7f3539b15000, 71040) = 0
getpid()= 120700
fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) =
3
brk(NULL) = 0x55c9a1947000
brk(0x55c9a1968000) = 0x55c9a1968000
openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) =
4
fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) =
1024
access("sysfs", F_OK) = -1 ENOENT (No such file or
directory)
access("proc", F_OK)= -1 ENOENT (No such file or
directory)
access("udev", F_OK)= -1 ENOENT (No such file or
directory)
access("devpts", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("rpool/ROOT/ubuntu", F_OK) = -1 ENOENT (No such file or
directory)
access("securityfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("tmpfs", F_OK) = -1 ENOENT (No such file or
directory)
access("cgroup2", F_OK) = -1 ENOENT (No such file or
directory)
access("cgroup", F_OK) = -1 ENOENT (No such file or
directory)
access("pstore", F_OK) = -1 ENOENT (No such file or
directory)
access("efivarfs", F_OK)= -1 ENOENT (No such file or
directory)
read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) =
[Kernel-packages] [Bug 1967889] Re: Raise CONFIG_NR_CPUS
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, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1958374] [NEW] riscv: Improve support for the SiFive Unmathed board
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 the tmp451 with its power supply
Fixes the following probe warning:
lm90 0-004c: Looking up vcc-supply from device tree
lm90 0-004c: Looking up vcc-supply property in node
/soc/i2c@1003/temperature-sensor@4c failed
lm90 0-004c: supply vcc not found, using dummy regulator
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ad931d9b3b2e21586de8e6b34346d0a30c13721d
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:41 2021 +
riscv: dts: sifive unmatched: Fix regulator for board rev3
The existing values are rejected by the da9063 regulator driver, as they
are unachievable with the declared chip setup (non-merged vcore and bmem
are unable to provide the declared curent).
Fix voltages to match rev3 schematics, which also matches their boot-up
configuration within the chip's available precision.
Declare bcore1/bcore2 and bmem/bio as merged.
Set ldo09 and ldo10 as always-on as their consumers are not declared but
exist.
Drop ldo current limits as there is no current limit feature for these
regulators in the DA9063. Fixes warnings like:
DA9063_LDO3: Operation of current configuration missing
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit cd29cc8ad2540a4f9a0a3e174394d39e648ef941
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:39 2021 +
riscv: dts: sifive unmatched: Expose the PMIC sub-functions
These sub-functions are available in the chip revision on this board, so
expose them.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 8120393b74b31bbaf293f59896de6b0d50febc48
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:38 2021 +
riscv: dts: sifive unmatched: Expose the board ID eeprom
Mark it as read-only as it is factory-programmed with identifying
information, and no executable nor configuration:
- eth MAC address
- board model (PCB version, BoM version)
- board serial number
Accidental modification would cause misidentification which could brick
the board, so marking read-only seem like both a safe and non-constraining
choice.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ea81b91e4e256b0bb75d47ad3a5c230b2171a005
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:37 2021 +
riscv: dts: sifive unmatched: Name gpio lines
Follow the pin descriptions given in the version 3 of the board schematics.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 298d03c2d7f1b5daacb6d4f4053fd3d677d67087
Author: Bin Meng
Date: Wed Jun 16 15:46:45 2021 +0800
riscv: dts: unmatched: Add gpio card detect to mmc-spi-slot
Per HiFive Unmatched schematics, the card detect signal of the
micro SD card is connected to gpio pin #15, which should be
reflected in the DT via the property, as described in
Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt.
[1]
https://sifive.cdn.prismic.io/sifive/6a06d6c0-6e66-49b5-8e9e-e68ce76f4192_hifive-unmatched-schematics-v3.pdf
Signed-off-by: Bin Meng
Fixes: d573b5558abb ("riscv: dts: add initial board data for the SiFive
HiFive Unmatched")
Cc: sta...@vger.kernel.org
Signed-off-by: Palmer Dabbelt
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Tags: riscv64
** Package changed: linux-meta (Ubuntu) => linux-riscv (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1958374
Title:
riscv: Improve support for the SiFive Unmathed board
Status in linux-riscv package in Ubuntu:
New
Bug description:
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 the tmp451 with its power supply
Fixes the following probe warning:
lm90 0-004c: Looking up vcc-supply from device tree
lm90 0-004c: Looking up vcc-supply property in node
/soc/i2c@1003/temperature-sensor@4c failed
lm90 0-004c: supply vcc not found, using dummy regulator
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ad931d9b3b2e21586de8e6b34346d0a30c13721d
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:41 2021 +
riscv: dts: sifive unmatched: Fix r
[Kernel-packages] [Bug 1958374] Re: riscv: Improve support for the SiFive Unmatched board
** 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/1958374
Title:
riscv: Improve support for the SiFive Unmatched board
Status in linux-riscv package in Ubuntu:
New
Bug description:
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 the tmp451 with its power supply
Fixes the following probe warning:
lm90 0-004c: Looking up vcc-supply from device tree
lm90 0-004c: Looking up vcc-supply property in node
/soc/i2c@1003/temperature-sensor@4c failed
lm90 0-004c: supply vcc not found, using dummy regulator
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ad931d9b3b2e21586de8e6b34346d0a30c13721d
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:41 2021 +
riscv: dts: sifive unmatched: Fix regulator for board rev3
The existing values are rejected by the da9063 regulator driver, as they
are unachievable with the declared chip setup (non-merged vcore and bmem
are unable to provide the declared curent).
Fix voltages to match rev3 schematics, which also matches their boot-up
configuration within the chip's available precision.
Declare bcore1/bcore2 and bmem/bio as merged.
Set ldo09 and ldo10 as always-on as their consumers are not declared but
exist.
Drop ldo current limits as there is no current limit feature for these
regulators in the DA9063. Fixes warnings like:
DA9063_LDO3: Operation of current configuration missing
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit cd29cc8ad2540a4f9a0a3e174394d39e648ef941
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:39 2021 +
riscv: dts: sifive unmatched: Expose the PMIC sub-functions
These sub-functions are available in the chip revision on this board, so
expose them.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 8120393b74b31bbaf293f59896de6b0d50febc48
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:38 2021 +
riscv: dts: sifive unmatched: Expose the board ID eeprom
Mark it as read-only as it is factory-programmed with identifying
information, and no executable nor configuration:
- eth MAC address
- board model (PCB version, BoM version)
- board serial number
Accidental modification would cause misidentification which could brick
the board, so marking read-only seem like both a safe and non-constraining
choice.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ea81b91e4e256b0bb75d47ad3a5c230b2171a005
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:37 2021 +
riscv: dts: sifive unmatched: Name gpio lines
Follow the pin descriptions given in the version 3 of the board
schematics.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 298d03c2d7f1b5daacb6d4f4053fd3d677d67087
Author: Bin Meng
Date: Wed Jun 16 15:46:45 2021 +0800
riscv: dts: unmatched: Add gpio card detect to mmc-spi-slot
Per HiFive Unmatched schematics, the card detect signal of the
micro SD card is connected to gpio pin #15, which should be
reflected in the DT via the property, as described in
Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt.
[1]
https://sifive.cdn.prismic.io/sifive/6a06d6c0-6e66-49b5-8e9e-e68ce76f4192_hifive-unmatched-schematics-v3.pdf
Signed-off-by: Bin Meng
Fixes: d573b5558abb ("riscv: dts: add initial board data for the SiFive
HiFive Unmatched")
Cc: sta...@vger.kernel.org
Signed-off-by: Palmer Dabbelt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1958374/+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 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Also makes some systems unbootable if they display prompts
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 are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Also makes some systems unbootable if they display prompts Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+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 1966978] [NEW] microchip/microchip-mpfs-icicle-kit.dtb missing
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 to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1966978 Title: microchip/microchip-mpfs-icicle-kit.dtb missing Status in linux-riscv package in Ubuntu: New Bug description: Please, add microchip/microchip-mpfs-icicle-kit.dtb to the list of created device-trees. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1966978/+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] [NEW] rcu_sched detected stalls on CPUs/tasks
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: [ 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 ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy riscv64 ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1967130/+attachment/5574771/+files/kern.log -- 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
** 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/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
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 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 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1967130/+attachment/5574772/+files/Dependencies.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/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
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 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 1967889] [NEW] Raise CONFIG_NR_CPUS
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: 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/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
** 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 Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in grub2-unsigned package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
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.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in grub2-unsigned package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
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: LoadFile2 initrd loading protocol installed net/net.c:1819: grub_net_fini_hw() net/drivers/efi/efinet.c:232: efi_net close_card loader/efi/linux.c:141: Installed/updated FDT configuration table @ 0x0 loader/efi/linux.c:191: linux command line: 'BOOT_IMAGE=/casper/vmlinuz efi=debug earlyprintk url=https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/jammy-live-serv er-arm64.iso' loader/efi/peimage.c:215: PE-COFF header checked loader/efi/peimage.c:282: sections loaded loader/efi/peimage.c:493: no relocations loader/efi/peimage.c:709: Executing image loaded at 0xf364 Entry point 0xf55473c8 Size 0x02d9 EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Generating empty DTB loader/efi/linux.c:348: Providing initrd via LOAD_FILE2_PROTOCOL net/net.c:1685: fs_read_real() name: /casper/initrd net/drivers/efi/efinet.c:169: efi_net open_card net/drivers/efi/efinet.c:75: Timeout: limit_time 50680, new_time 50681 error: couldn't send network packet. -- 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 Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
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 ExitBootServices(). -- 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 Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
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.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: New Status in grub2-signed package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1964335] [NEW] Excessive size of kernel modules on RISC-V
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 matches what we see on the other architectures. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 -- 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 Status in linux-riscv package in Ubuntu: New Bug description: 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 matches what we see on the other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+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 1964335] Re: Excessive size of kernel modules on RISC-V - modules unstripped
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 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 - modules unstripped Status in linux-riscv package in Ubuntu: New Bug description: 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 matches what we see on the other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+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 1964335] Re: Excessive size of kernel modules on RISC-V - modules unstripped
** 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 - modules unstripped Status in linux-riscv package in Ubuntu: Confirmed Bug description: 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 matches what we see on the other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+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
