Bug #2013232 “Enable StarFive VisionFive 2 board” : Bugs : linux-riscv package : Ubuntu

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-04-11:

#1

Download full text (11.6 KiB)

This bug was fixed in the package linux-riscv - 6.2.0-19.19.1

---------------
linux-riscv (6.2.0-19.19.1) lunar; urgency=medium

* lunar/linux-riscv: 6.2.0-19.19.1 -proposed tracker (LP: #2013348)

  * Enable StarFive VisionFive 2 board (LP: #2013232)
    - net: phy: motorcomm: change the phy id of yt8521 and yt8531s to lowercase
    - dt-bindings: net: Add Motorcomm yt8xxx ethernet phy
    - net: phy: Add BIT macro for Motorcomm yt8521/yt8531 gigabit ethernet phy
    - net: phy: Add dts support for Motorcomm yt8521 gigabit ethernet phy
    - net: phy: Add dts support for Motorcomm yt8531s gigabit ethernet phy
    - net: phy: Add driver for Motorcomm yt8531 gigabit ethernet phy
    - net: phy: motorcomm: uninitialized variables in yt8531_link_change_notify()
    - dt-bindings: pinctrl: Add StarFive JH7110 sys pinctrl
    - dt-bindings: pinctrl: Add StarFive JH7110 aon pinctrl
    - pinctrl: starfive: Add StarFive JH7110 sys controller driver
    - pinctrl: starfive: Add StarFive JH7110 aon controller driver
    - dt-bindings: mmc: Add StarFive MMC module
    - mmc: starfive: Add sdio/emmc driver support
    - dt-bindings: riscv: Add StarFive JH7110 SoC and VisionFive 2 board
    - dt-bindings: riscv: correct starfive visionfive 2 compatibles
    - dt-bindings: sifive,ccache0: Support StarFive JH7110 SoC
    - soc: sifive: ccache: Add StarFive JH7110 support
    - RISC-V: introduce ARCH_FOO kconfig aliases for SOC_FOO symbols
    - SAUCE: clk: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE
    - SAUCE: clk: starfive: Factor out common JH7100 and JH7110 code
    - SAUCE: clk: starfive: Rename clk-starfive-jh7100.h to clk-starfive-jh71x0.h
    - SAUCE: clk: starfive: Rename "jh7100" to "jh71x0" for the common code
    - SAUCE: reset: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE
    - SAUCE: reset: Create subdirectory for StarFive drivers
    - SAUCE: reset: starfive: Factor out common JH71X0 reset code
    - SAUCE: reset: starfive: Extract the common JH71X0 reset code
    - SAUCE: reset: starfive: Rename "jh7100" to "jh71x0" for the common code
    - SAUCE: reset: starfive: jh71x0: Use 32bit I/O on 32bit registers
    - SAUCE: dt-bindings: clock: Add StarFive JH7110 system clock and reset
      generator
    - SAUCE: dt-bindings: clock: Add StarFive JH7110 always-on clock and reset
      generator
    - SAUCE: clk: starfive: Add StarFive JH7110 system clock driver
    - SAUCE: clk: starfive: Add StarFive JH7110 always-on clock driver
    - SAUCE: reset: starfive: Add StarFive JH7110 reset driver
    - SAUCE: dt-bindings: timer: Add StarFive JH7110 clint
    - SAUCE: dt-bindings: interrupt-controller: Add StarFive JH7110 plic
    - SAUCE: dt-bindings: riscv: Add SiFive S7 compatible
    - SAUCE: riscv: dts: starfive: Add initial StarFive JH7110 device tree
    - SAUCE: riscv: dts: starfive: Add StarFive JH7110 pin function definitions
    - SAUCE: riscv: dts: starfive: Add StarFive JH7110 VisionFive 2 board device
      tree
    - SAUCE: dt-bindings: syscon: Add StarFive syscon doc
    - SAUCE: mmc: starfive: Add initialization of prev_err
    - SAUCE: riscv: dts: starfive: Add mmc node
    - SAUCE: dt-bindings: net: snps,dwmac: Add dw...

This bug was fixed in the package linux-riscv - 6.2.0-19.19.1

---------------
linux-riscv (6.2.0-19.19.1) lunar; urgency=medium

* lunar/linux-riscv: 6.2.0-19.19.1 -proposed tracker (LP: #2013348)

* Enable StarFive VisionFive 2 board (LP: #2013232)
    - net: phy: motorcomm: change the phy id of yt8521 and yt8531s to lowercase
    - dt-bindings: net: Add Motorcomm yt8xxx ethernet phy
    - net: phy: Add BIT macro for Motorcomm yt8521/yt8531 gigabit ethernet phy
    - net: phy: Add dts support for Motorcomm yt8521 gigabit ethernet phy
    - net: phy: Add dts support for Motorcomm yt8531s gigabit ethernet phy
    - net: phy: Add driver for Motorcomm yt8531 gigabit ethernet phy
    - net: phy: motorcomm: uninitialized variables in yt8531_link_change_notify()
    - dt-bindings: pinctrl: Add StarFive JH7110 sys pinctrl
    - dt-bindings: pinctrl: Add StarFive JH7110 aon pinctrl
    - pinctrl: starfive: Add StarFive JH7110 sys controller driver
    - pinctrl: starfive: Add StarFive JH7110 aon controller driver
    - dt-bindings: mmc: Add StarFive MMC module
    - mmc: starfive: Add sdio/emmc driver support
    - dt-bindings: riscv: Add StarFive JH7110 SoC and VisionFive 2 board
    - dt-bindings: riscv: correct starfive visionfive 2 compatibles
    - dt-bindings: sifive,ccache0: Support StarFive JH7110 SoC
    - soc: sifive: ccache: Add StarFive JH7110 support
    - RISC-V: introduce ARCH_FOO kconfig aliases for SOC_FOO symbols
    - SAUCE: clk: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE
    - SAUCE: clk: starfive: Factor out common JH7100 and JH7110 code
    - SAUCE: clk: starfive: Rename clk-starfive-jh7100.h to clk-starfive-jh71x0.h
    - SAUCE: clk: starfive: Rename "jh7100" to "jh71x0" for the common code
    - SAUCE: reset: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE
    - SAUCE: reset: Create subdirectory for StarFive drivers
    - SAUCE: reset: starfive: Factor out common JH71X0 reset code
    - SAUCE: reset: starfive: Extract the common JH71X0 reset code
    - SAUCE: reset: starfive: Rename "jh7100" to "jh71x0" for the common code
    - SAUCE: reset: starfive: jh71x0: Use 32bit I/O on 32bit registers
    - SAUCE: dt-bindings: clock: Add StarFive JH7110 system clock and reset
      generator
    - SAUCE: dt-bindings: clock: Add StarFive JH7110 always-on clock and reset
      generator
    - SAUCE: clk: starfive: Add StarFive JH7110 system clock driver
    - SAUCE: clk: starfive: Add StarFive JH7110 always-on clock driver
    - SAUCE: reset: starfive: Add StarFive JH7110 reset driver
    - SAUCE: dt-bindings: timer: Add StarFive JH7110 clint
    - SAUCE: dt-bindings: interrupt-controller: Add StarFive JH7110 plic
    - SAUCE: dt-bindings: riscv: Add SiFive S7 compatible
    - SAUCE: riscv: dts: starfive: Add initial StarFive JH7110 device tree
    - SAUCE: riscv: dts: starfive: Add StarFive JH7110 pin function definitions
    - SAUCE: riscv: dts: starfive: Add StarFive JH7110 VisionFive 2 board device
      tree
    - SAUCE: dt-bindings: syscon: Add StarFive syscon doc
    - SAUCE: mmc: starfive: Add initialization of prev_err
    - SAUCE: riscv: dts: starfive: Add mmc node
    - SAUCE: dt-bindings: net: snps,dwmac: Add dwmac-5.20 version
    - SAUCE: net: stmmac: platform: Add snps,dwmac-5.20 IP compatible string
    - SAUCE: dt-bindings: net: snps,dwmac: Add 'ahb' reset/reset-name
    - SAUCE: dt-bindings: net: Add support StarFive dwmac
    - SAUCE: net: stmmac: Add glue layer for StarFive JH7110 SoC
    - SAUCE: net: stmmac: starfive_dmac: Add phy interface settings
    - SAUCE: riscv: dts: starfive: jh7110: Add ethernet device nodes
    - SAUCE: riscv: dts: starfive: visionfive 2: Add configuration of gmac and phy
    - SAUCE: riscv: dts: starfive: Add VisionFive 2 reserved memory node
    - [Config] updateconfigs for VisionFive 2 patches
    - [Config] Enable CONFIG_SERIAL_8250_DW for riscv64

* Packaging resync (LP: #1786013)
    - [Packaging] update Ubuntu.md
    - [Packaging] update update.conf

[ Ubuntu: 6.2.0-19.19 ]

* lunar/linux: 6.2.0-19.19 -proposed tracker (LP: #2012488)
  * Neuter signing tarballs (LP: #2012776)
    - [Packaging] neuter the signing tarball
  * LSM stacking and AppArmor refresh for 6.2 kernel (LP: #2012136)
    - Revert "UBUNTU: [Config] define CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS"
    - Revert "UBUNTU: SAUCE: apparmor: add user namespace creation mediation"
    - Revert "UBUNTU: SAUCE: apparmor: Add fine grained mediation of posix
      mqueues"
    - Revert "UBUNTU: SAUCE: Revert "apparmor: make __aa_path_perm() static""
    - Revert "UBUNTU: SAUCE: LSM: Specify which LSM to display (using struct cred
      as input)"
    - Revert "UBUNTU: SAUCE: apparmor: Fix build error, make sk parameter const"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in smk_netlbl_mls()"
    - Revert "UBUNTU: SAUCE: LSM: change ima_read_file() to use lsmblob"
    - Revert "UBUNTU: SAUCE: apparmor: rename kzfree() to kfree_sensitive()"
    - Revert "UBUNTU: SAUCE: AppArmor: Remove the exclusive flag"
    - Revert "UBUNTU: SAUCE: LSM: Add /proc attr entry for full LSM context"
    - Revert "UBUNTU: SAUCE: Audit: Fix incorrect static inline function
      declration."
    - Revert "UBUNTU: SAUCE: Audit: Fix for missing NULL check"
    - Revert "UBUNTU: SAUCE: Audit: Add a new record for multiple object LSM
      attributes"
    - Revert "UBUNTU: SAUCE: Audit: Add new record for multiple process LSM
      attributes"
    - Revert "UBUNTU: SAUCE: NET: Store LSM netlabel data in a lsmblob"
    - Revert "UBUNTU: SAUCE: LSM: security_secid_to_secctx in netlink netfilter"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmcontext in security_inode_getsecctx"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmcontext in security_secid_to_secctx"
    - Revert "UBUNTU: SAUCE: LSM: Ensure the correct LSM context releaser"
    - Revert "UBUNTU: SAUCE: LSM: Specify which LSM to display"
    - Revert "UBUNTU: SAUCE: IMA: Change internal interfaces to use lsmblobs"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_cred_getsecid"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_inode_getsecid"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_task_getsecid"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_ipc_getsecid"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_secid_to_secctx"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_secctx_to_secid"
    - Revert "UBUNTU: SAUCE: net: Prepare UDS for security module stacking"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_kernel_act_as"
    - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_audit_rule_match"
    - Revert "UBUNTU: SAUCE: LSM: Create and manage the lsmblob data structure."
    - Revert "UBUNTU: SAUCE: LSM: Infrastructure management of the sock security"
    - Revert "UBUNTU: SAUCE: apparmor: LSM stacking: switch from SK_CTX() to
      aa_sock()"
    - Revert "UBUNTU: SAUCE: apparmor: rename aa_sock() to aa_unix_sk()"
    - Revert "UBUNTU: SAUCE: apparmor: disable showing the mode as part of a secid
      to secctx"
    - Revert "UBUNTU: SAUCE: apparmor: fix use after free in sk_peer_label"
    - Revert "UBUNTU: SAUCE: apparmor: af_unix mediation"
    - Revert "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x
      net rules"
    - Revert "UBUNTU: SAUCE: apparmor: add/use fns to print hash string hex value"
    - SAUCE: apparmor: rename SK_CTX() to aa_sock and make it an inline fn
    - SAUCE: apparmor: Add sysctls for additional controls of unpriv userns
      restrictions
    - SAUCE: Stacking v38: LSM: Identify modules by more than name
    - SAUCE: Stacking v38: LSM: Add an LSM identifier for external use
    - SAUCE: Stacking v38: LSM: Identify the process attributes for each module
    - SAUCE: Stacking v38: LSM: Maintain a table of LSM attribute data
    - SAUCE: Stacking v38: proc: Use lsmids instead of lsm names for attrs
    - SAUCE: Stacking v38: integrity: disassociate ima_filter_rule from
      security_audit_rule
    - SAUCE: Stacking v38: LSM: Infrastructure management of the sock security
    - SAUCE: Stacking v38: LSM: Add the lsmblob data structure.
    - SAUCE: Stacking v38: LSM: provide lsm name and id slot mappings
    - SAUCE: Stacking v38: IMA: avoid label collisions with stacked LSMs
    - SAUCE: Stacking v38: LSM: Use lsmblob in security_audit_rule_match
    - SAUCE: Stacking v38: LSM: Use lsmblob in security_kernel_act_as
    - SAUCE: Stacking v38: LSM: Use lsmblob in security_secctx_to_secid
    - SAUCE: Stacking v38: LSM: Use lsmblob in security_secid_to_secctx
    - SAUCE: Stacking v38: LSM: Use lsmblob in security_ipc_getsecid
    - SAUCE: Stacking v38: LSM: Use lsmblob in security_current_getsecid
    - SAUCE: Stacking v38: LSM: Use lsmblob in security_inode_getsecid
    - SAUCE: Stacking v38: LSM: Use lsmblob in security_cred_getsecid
    - SAUCE: Stacking v38: LSM: Specify which LSM to display
    - SAUCE: Stacking v38: LSM: Ensure the correct LSM context releaser
    - SAUCE: Stacking v38: LSM: Use lsmcontext in security_secid_to_secctx
    - SAUCE: Stacking v38: LSM: Use lsmcontext in security_inode_getsecctx
    - SAUCE: Stacking v38: Use lsmcontext in security_dentry_init_security
    - SAUCE: Stacking v38: LSM: security_secid_to_secctx in netlink netfilter
    - SAUCE: Stacking v38: NET: Store LSM netlabel data in a lsmblob
    - SAUCE: Stacking v38: binder: Pass LSM identifier for confirmation
    - SAUCE: Stacking v38: LSM: security_secid_to_secctx module selection
    - SAUCE: Stacking v38: Audit: Keep multiple LSM data in audit_names
    - SAUCE: Stacking v38: Audit: Create audit_stamp structure
    - SAUCE: Stacking v38: LSM: Add a function to report multiple LSMs
    - SAUCE: Stacking v38: Audit: Allow multiple records in an audit_buffer
    - SAUCE: Stacking v38: Audit: Add record for multiple task security contexts
    - SAUCE: Stacking v38: audit: multiple subject lsm values for netlabel
    - SAUCE: Stacking v38: Audit: Add record for multiple object contexts
    - SAUCE: Stacking v38: netlabel: Use a struct lsmblob in audit data
    - SAUCE: Stacking v38: LSM: Removed scaffolding function lsmcontext_init
    - SAUCE: Stacking v38: AppArmor: Remove the exclusive flag
    - SAUCE: apparmor: combine common_audit_data and apparmor_audit_data
    - SAUCE: apparmor: setup slab cache for audit data
    - SAUCE: apparmor: rename audit_data->label to audit_data->subj_label
    - SAUCE: apparmor: pass cred through to audit info.
    - SAUCE: apparmor: Improve debug print infrastructure
    - SAUCE: apparmor: add the ability for profiles to have a learning cache
    - SAUCE: apparmor: enable userspace upcall for mediation
    - SAUCE: apparmor: cache buffers on percpu list if there is lock contention
    - SAUCE: apparmor: fix policy_compat permission remap with extended
      permissions
    - SAUCE: apparmor: advertise availability of exended perms
    - [Config] define CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS
  * kinetic: apply new apparmor and LSM stacking patch set (LP: #1989983) // LSM
    stacking and AppArmor refresh for 6.2 kernel (LP: #2012136)
    - SAUCE: apparmor: add/use fns to print hash string hex value
    - SAUCE: apparmor: patch to provide compatibility with v2.x net rules
    - SAUCE: apparmor: add user namespace creation mediation
    - SAUCE: apparmor: af_unix mediation
    - SAUCE: apparmor: Add fine grained mediation of posix mqueues
  * devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute
    (KeyError: 'flavour') (LP: #1937133)
    - selftests: net: devlink_port_split.py: skip test if no suitable device
      available
  * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
    - NFS: Correct timing for assigning access cache timestamp

-- Dimitri John Ledkov <dimitri.ledkov@canonical.com>  Thu, 30 Mar 2023 18:14:32 +0100

Changed in linux-riscv (Ubuntu):
status:	New → Fix Released

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-07-27:

#2

This bug is awaiting verification that the linux-starfive/6.2.0-1002.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-lunar-linux-starfive verification-needed-lunar

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-10-24:

#3

This bug is awaiting verification that the linux-azure-6.5/6.5.0-1007.7~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-done-jammy-linux-azure-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-failed-jammy-linux-azure-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-azure-6.5-v2 verification-needed-jammy-linux-azure-6.5

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-10-24:

#4

This bug is awaiting verification that the linux-aws-6.5/6.5.0-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-aws-6.5-v2 verification-needed-jammy-linux-aws-6.5

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-05-06:

#5

This bug is awaiting verification that the linux/6.8.0-32.32 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux' to 'verification-done-noble-linux'. If the problem still exists, change the tag 'verification-needed-noble-linux' to 'verification-failed-noble-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-05-14:

#6

This bug is awaiting verification that the linux-nvidia-6.8/6.8.0-1006.6~22.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#7

This bug is awaiting verification that the linux-azure/6.8.0-1008.8 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure' to 'verification-done-noble-linux-azure'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure' to 'verification-failed-noble-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-azure-v2 verification-needed-noble-linux-azure

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#8

This bug is awaiting verification that the linux-gke/6.8.0-1004.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-gke' to 'verification-done-noble-linux-gke'. If the problem still exists, change the tag 'verification-needed-noble-linux-gke' to 'verification-failed-noble-linux-gke'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-gke-v2 verification-needed-noble-linux-gke

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#9

This bug is awaiting verification that the linux-gcp/6.8.0-1008.9 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-gcp' to 'verification-done-noble-linux-gcp'. If the problem still exists, change the tag 'verification-needed-noble-linux-gcp' to 'verification-failed-noble-linux-gcp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-gcp-v2 verification-needed-noble-linux-gcp

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#10

This bug is awaiting verification that the linux-aws/6.8.0-1009.9 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-aws' to 'verification-done-noble-linux-aws'. If the problem still exists, change the tag 'verification-needed-noble-linux-aws' to 'verification-failed-noble-linux-aws'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-aws-v2 verification-needed-noble-linux-aws

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#11

This bug is awaiting verification that the linux-intel/6.8.0-1005.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-intel' to 'verification-done-noble-linux-intel'. If the problem still exists, change the tag 'verification-needed-noble-linux-intel' to 'verification-failed-noble-linux-intel'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-intel-v2 verification-needed-noble-linux-intel

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#12

This bug is awaiting verification that the linux-ibm/6.8.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-ibm' to 'verification-done-noble-linux-ibm'. If the problem still exists, change the tag 'verification-needed-noble-linux-ibm' to 'verification-failed-noble-linux-ibm'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-ibm-v2 verification-needed-noble-linux-ibm

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#13

This bug is awaiting verification that the linux-nvidia/6.8.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia' to 'verification-done-noble-linux-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia' to 'verification-failed-noble-linux-nvidia'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-nvidia-v2 verification-needed-noble-linux-nvidia

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#14

This bug is awaiting verification that the linux-oem-6.8/6.8.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-oem-6.8' to 'verification-done-noble-linux-oem-6.8'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.8' to 'verification-failed-noble-linux-oem-6.8'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-oem-6.8-v2 verification-needed-noble-linux-oem-6.8

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#15

This bug is awaiting verification that the linux-riscv/6.8.0-35.35.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-riscv' to 'verification-done-noble-linux-riscv'. If the problem still exists, change the tag 'verification-needed-noble-linux-riscv' to 'verification-failed-noble-linux-riscv'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-riscv-v2 verification-needed-noble-linux-riscv

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#16

This bug is awaiting verification that the linux-raspi-realtime/6.8.0-2004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-raspi-realtime' to 'verification-done-noble-linux-raspi-realtime'. If the problem still exists, change the tag 'verification-needed-noble-linux-raspi-realtime' to 'verification-failed-noble-linux-raspi-realtime'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-raspi-realtime-v2 verification-needed-noble-linux-raspi-realtime

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-03:

#17

This bug is awaiting verification that the linux-lowlatency/6.8.0-35.35.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-lowlatency' to 'verification-done-noble-linux-lowlatency'. If the problem still exists, change the tag 'verification-needed-noble-linux-lowlatency' to 'verification-failed-noble-linux-lowlatency'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-lowlatency-v2 verification-needed-noble-linux-lowlatency

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-06:

#18

This bug is awaiting verification that the linux-oracle/6.8.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-oracle' to 'verification-done-noble-linux-oracle'. If the problem still exists, change the tag 'verification-needed-noble-linux-oracle' to 'verification-failed-noble-linux-oracle'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-oracle-v2 verification-needed-noble-linux-oracle

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-06-10:

#19

This bug is awaiting verification that the linux-ibm-gt/6.8.0-1004.5 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-ibm-gt' to 'verification-done-noble-linux-ibm-gt'. If the problem still exists, change the tag 'verification-needed-noble-linux-ibm-gt' to 'verification-failed-noble-linux-ibm-gt'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-ibm-gt-v2 verification-needed-noble-linux-ibm-gt

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-07-08:

#20

This bug is awaiting verification that the linux-lowlatency-hwe-6.8/6.8.0-38.38.1~22.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency-hwe-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy-linux-lowlatency-hwe-6.8'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-07-22:

#21

This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-linux-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-fips' to 'verification-failed-noble-linux-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-noble-linux-fips-v2 verification-needed-noble-linux-fips

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#22

This bug is awaiting verification that the linux-riscv-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8

Ubuntu
linux-riscv package

Enable StarFive VisionFive 2 board

Bug Description

Other bug subscribers

Remote bug watches

Ubuntulinux-riscv package

Enable StarFive VisionFive 2 board

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
linux-riscv package