canonical-ubuntu-qa team mailing list archive

[Launchpad Bug Tracker <2042388@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package linux-starfive - 6.5.0-1005.6

---------------
linux-starfive (6.5.0-1005.6) mantic; urgency=medium

  * mantic/linux-starfive: 6.5.0-1005.6 -proposed tracker (LP: #2041535)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] resync update-dkms-versions helper
    - debian/dkms-versions -- update from kernel-versions (main/2023.10.30)

  * disable shiftfs (LP: #2038522)
    - [Config] starfive: disable shiftfs

  * context test in ubuntu_stress_smoke_test failed with M-6.5 riscv / starfive
    instances (LP: #2042388)
    - riscv: signal: fix sigaltstack frame size checking

  [ Ubuntu: 6.5.0-14.14 ]

  * mantic/linux: 6.5.0-14.14 -proposed tracker (LP: #2042660)
  * Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC
    (LP: #2042850)
    - drm/ast: Add BMC virtual connector
  * arm64 atomic issues cause disk corruption (LP: #2042573)
    - locking/atomic: scripts: fix fallback ifdeffery
  * Packaging resync (LP: #1786013)
    - [Packaging] update annotations scripts

  [ Ubuntu: 6.5.0-12.12 ]

  * mantic/linux: 6.5.0-12.12 -proposed tracker (LP: #2041536)
  * Packaging resync (LP: #1786013)
    - [Packaging] update annotations scripts
    - [Packaging] update helper scripts
    - debian/dkms-versions -- update from kernel-versions (main/2023.10.30)
  * CVE-2023-5633
    - drm/vmwgfx: Keep a gem reference to user bos in surfaces
  * CVE-2023-5345
    - fs/smb/client: Reset password pointer to NULL
  * CVE-2023-39189
    - netfilter: nfnetlink_osf: avoid OOB read
  * CVE-2023-4244
    - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction
  * apparmor restricts read access of user namespace mediation sysctls to root
    (LP: #2040194)
    - SAUCE: apparmor: open userns related sysctl so lxc can check if restriction
      are in place
  * AppArmor spams kernel log with assert when auditing (LP: #2040192)
    - SAUCE: apparmor: fix request field from a prompt reply that denies all
      access
  * apparmor notification files verification (LP: #2040250)
    - SAUCE: apparmor: fix notification header size
  * apparmor oops when racing to retrieve a notification (LP: #2040245)
    - SAUCE: apparmor: fix oops when racing to retrieve notification
  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
    (LP: #2039575)
    - net/smc: Fix pos miscalculation in statistics
  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Meteor
      Lake
    - SAUCE: platform/x86: int3472: Add handshake GPIO function
  * CVE-2023-45898
    - ext4: fix slab-use-after-free in ext4_es_insert_extent()
  * CVE-2023-31085
    - ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-5717
    - perf: Disallow mis-matched inherited group reads
  * CVE-2023-5178
    - nvmet-tcp: Fix a possible UAF in queue intialization setup
  * CVE-2023-5158
    - vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()
  * CVE-2023-5090
    - x86: KVM: SVM: always update the x2avic msr interception
  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
    (LP: #2033406)
    - [Packaging] Make WWAN driver loadable modules
  * Unable to power off the system with MTL CPU (LP: #2039405)
    - Revert "x86/smp: Put CPUs into INIT on shutdown if possible"
  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
    - [Packaging] Make linux-tools-common depend on hwdata
  * drop all references to is_rust_module.sh in kernels >= 6.5 (LP: #2038611)
    - [Packaging] drop references to is_rust_module.sh
  * disable shiftfs (LP: #2038522)
    - SAUCE: ceph: enable unsafe idmapped mounts by default
    - [Config] disable shiftfs
  * Infinite systemd loop when power off the machine with multiple MD RAIDs
    (LP: #2036184)
    - md: Put the right device in md_seq_next
  * [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and
    PCIE peripherals (LP: #2036587)
    - [Config] Enable CONFIG_MTK_IOMMU on arm64
  * Realtek 8852CE WiFi 6E country code udpates (LP: #2037273)
    - wifi: rtw89: regd: update regulatory map to R64-R43
  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
    - misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
      probe
  * CVE-2023-42754
    - ipv4: fix null-deref in ipv4_link_failure
  * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root
    images (LP: #2019040)
    - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y
  * Fix RCU warning on AMD laptops (LP: #2036377)
    - power: supply: core: Use blocking_notifier_call_chain to avoid RCU complaint
  * allow io_uring to be disabled in runtime (LP: #2035116)
    - io_uring: add a sysctl to disable io_uring system-wide
  * Fix unstable audio at low levels on Thinkpad P1G4 (LP: #2037077)
    - ALSA: hda/realtek - ALC287 I2S speaker platform support

 -- Emil Renner Berthing <emil.renner.berthing@xxxxxxxxxxxxx>  Thu, 23
Nov 2023 14:58:08 +0100

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2042388

Title:
  context test in ubuntu_stress_smoke_test failed with M-6.5 riscv /
  starfive instances

Status in ubuntu-kernel-tests:
  New
Status in glibc package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux-starfive package in Ubuntu:
  Invalid
Status in glibc source package in Mantic:
  Invalid
Status in linux-riscv source package in Mantic:
  Fix Released
Status in linux-starfive source package in Mantic:
  Fix Released

Bug description:
  This issue can be found from the very beginning of these two kernels
  * mantic/linux-starfive/6.5.0-1001.2
  * mantic/linux-riscv/6.5.0-7.7.2

  Test failed with:
   context STARTING
   context RETURNED 2
   context FAILED
   stress-ng: debug: [12644] invoked with './stress-ng -v -t 5 --context 4 --context-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root'
   stress-ng: debug: [12644] stress-ng 0.16.05 gaea6f3306f46
   stress-ng: debug: [12644] system: Linux mantic-starfive-riscv64 6.5.0-1001-starfive #2-Ubuntu SMP Fri Oct  6 12:08:59 UTC 2023 riscv64, gcc 13.2.0, glibc 2.38
   stress-ng: debug: [12644] RAM total: 7.7G, RAM free: 6.6G, swap free: 1024.0M
   stress-ng: debug: [12644] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext2 (4617314 blocks available)
   stress-ng: debug: [12644] 8 processors online, 8 processors configured
   stress-ng: info:  [12644] setting to a 5 secs run per stressor 
   stress-ng: debug: [12644] cache allocate: using defaults, cannot determine cache level details
   stress-ng: debug: [12644] cache allocate: shared cache buffer size: 2048K
   stress-ng: info:  [12644] dispatching hogs: 4 context
   stress-ng: debug: [12644] starting stressors
   stress-ng: debug: [12644] 4 stressors started
   stress-ng: debug: [12645] context: [12645] started (instance 0 on CPU 2)
   stress-ng: debug: [12647] context: [12647] started (instance 2 on CPU 5)
   stress-ng: debug: [12648] context: [12648] started (instance 3 on CPU 7)
   stress-ng: debug: [12646] context: [12646] started (instance 1 on CPU 4)
   stress-ng: debug: [12644] context: [12645] terminated on signal: 11 (Segmentation fault)
   stress-ng: debug: [12644] context: [12645] terminated (success)
   stress-ng: debug: [12644] context: [12646] terminated on signal: 11 (Segmentation fault)
   stress-ng: debug: [12644] context: [12646] terminated (success)
   stress-ng: debug: [12644] context: [12647] terminated on signal: 11 (Segmentation fault)
   stress-ng: debug: [12644] context: [12647] terminated (success)
   stress-ng: debug: [12644] context: [12648] terminated on signal: 11 (Segmentation fault)
   stress-ng: debug: [12644] context: [12648] terminated (success)
   stress-ng: warn:  [12644] metrics-check: all bogo-op counters are zero, data may be incorrect
   stress-ng: debug: [12644] metrics-check: all stressor metrics validated and sane 
   stress-ng: info:  [12644] skipped: 0
   stress-ng: info:  [12644] passed: 4: context (4)
   stress-ng: info:  [12644] failed: 0
   stress-ng: info:  [12644] metrics untrustworthy: 0 
   stress-ng: info:  [12644] unsuccessful run completed in 9.98 secs

  Looks like the tests have passed. But marked as failed with a non-zero
  return code.

  Tested with stress-ng V0.16.05 and V0.17.00, they all failed with the
  same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2042388/+subscriptions