[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Changed in: crash (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.10.2 --- crash (7.2.8-1ubuntu1.20.10.2) groovy; urgency=medium * Fix FTBFS (LP: #1931435): - d/p/0004-Fix-for-an-ARM64-gcc-10-compilation-error.-Without-t.patch crash (7.2.8-1ubuntu1.20.10.1) groovy; urgency=medium * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275): - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch -- Ioanna Alifieraki Thu, 10 Jun 2021 16:07:41 + -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.04.1 --- crash (7.2.8-1ubuntu1.20.04.1) focal; urgency=medium * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275): - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch -- Ioanna Alifieraki Thu, 15 Apr 2021 12:33:46 +0300 ** Changed in: crash (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug was fixed in the package crash - 7.2.8-1ubuntu0.18.04.2 --- crash (7.2.8-1ubuntu0.18.04.2) bionic; urgency=medium * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275): - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch -- Ioanna Alifieraki Wed, 14 Apr 2021 18:41:40 +0300 ** Changed in: crash (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: crash (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Brian, 7.2.8-1ubuntu1.20.10.2 fix addresses the issue. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
The arm64 build failure on groovy is due to a commit missning regarding gdb. See bug https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435. On riscv64 it seems it never built successfully and the failure is irrelevant to the patch. See bug https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
We're still waiting on verification for Groovy - the kernel task was verified, but the groovy build of crash has not been verified yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Apologies for not getting back to this earlier, it looks like the verification was already done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Apologies for not getting back to this earlier, it looks like the verification was already done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug was fixed in the package linux - 5.8.0-55.62 --- linux (5.8.0-55.62) groovy; urgency=medium * groovy/linux: 5.8.0-55.62 -proposed tracker (LP: #1930379) * [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64 (LP: #1929925) - SAUCE: KVM: arm64: Assign kvm_ipa_limit linux (5.8.0-54.61) groovy; urgency=medium * groovy/linux: 5.8.0-54.61 -proposed tracker (LP: #1927592) * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * netfilter: x_tables: fix compat match/target pad out-of-bound write (LP: #1927682) - netfilter: x_tables: fix compat match/target pad out-of-bound write * Groovy update: upstream stable patchset 2021-05-04 (LP: #1927150) - mt76: fix tx skb error handling in mt76_dma_tx_queue_skb - net: fec: ptp: avoid register access when ipg clock is disabled - powerpc/4xx: Fix build errors from mfdcr() - atm: eni: dont release is never initialized - atm: lanai: dont run lanai_dev_close if not open - Revert "r8152: adjust the settings about MAC clock speed down for RTL8153" - ALSA: hda: ignore invalid NHLT table - ixgbe: Fix memleak in ixgbe_configure_clsu32 - scsi: ufs: ufs-qcom: Disable interrupt in reset path - blk-cgroup: Fix the recursive blkg rwstat - net: tehuti: fix error return code in bdx_probe() - net: intel: iavf: fix error return code of iavf_init_get_resources() - sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count - cifs: ask for more credit on async read/write code paths - gfs2: fix use-after-free in trans_drain - cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev - gpiolib: acpi: Add missing IRQF_ONESHOT - nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default - NFS: Correct size calculation for create reply length - net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch() - net: wan: fix error return code of uhdlc_init() - net: davicom: Use platform_get_irq_optional() - net: enetc: set MAC RX FIFO to recommended value - atm: uPD98402: fix incorrect allocation - atm: idt77252: fix null-ptr-dereference - cifs: change noisy error message to FYI - irqchip/ingenic: Add support for the JZ4760 - kbuild: add image_name to no-sync-config-targets - kbuild: dummy-tools: fix inverted tests for gcc - umem: fix error return code in mm_pci_probe() - sparc64: Fix opcode filtering in handling of no fault loads - habanalabs: Call put_pid() when releasing control device - staging: rtl8192e: fix kconfig dependency on CRYPTO - u64_stats,lockdep: Fix u64_stats_init() vs lockdep - regulator: qcom-rpmh: Correct the pmic5_hfsmps515 buck - block: Fix REQ_OP_ZONE_RESET_ALL handling - drm/amd/display: Revert dram_clock_change_latency for DCN2.1 - drm/amdgpu: fb BO should be ttm_bo_type_device - drm/radeon: fix AGP dependency - nvme: add NVME_REQ_CANCELLED flag in nvme_cancel_request() - nvme-fc: set NVME_REQ_CANCELLED in nvme_fc_terminate_exchange() - nvme-fc: return NVME_SC_HOST_ABORTED_CMD when a command has been aborted - nvme-rdma: Fix a use after free in nvmet_rdma_write_data_done - nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a Samsung PM1725a - nfs: we don't support removing system.nfs4_acl - block: Suppress uevent for hidden device when removed - ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls - ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign - netsec: restore phy power state after controller reset - platform/x86: intel-vbtn: Stop reporting SW_DOCK events - psample: Fix user API breakage - z3fold: prevent reclaim/free race for headless pages - squashfs: fix inode lookup sanity checks - squashfs: fix xattr id and id lookup sanity checks - hugetlb_cgroup: fix imbalanced css_get and css_put pair for shared mappings - kasan: fix per-page tags for non-page_alloc pages - gcov: fix clang-11+ support - ACPI: video: Add missing callback back for Sony VPCEH3U1E - ACPICA: Always create namespace nodes using acpi_ns_create_node() - arm64: dts: ls1046a: mark crypto engine dma coherent - arm64: dts: ls1012a: mark crypto engine dma coherent - arm64: dts: ls1043a: mark crypto engine dma coherent - ARM: dts: at91: sam9x60: fix mux-mask for PA7 so it can be set to A, B and C - ARM: dts: at91: sam9x60: fix mux-mask to match product's datasheet - ARM: dts: at91-sama5d27_som1: fix phy address to 7 - integrity: double check iint_cache was initialized - drm/amd/pm: workaround for audio noise issue - drm/i915: Fix the GT fence revocation runtime PM logic - dm verity: fix
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
* linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
* Enable CIFS GCM256 (LP: #1921916)
- smb3: add defines for new crypto algorithms
- smb3.1.1: add new module load parm require_gcm_256
- smb3.1.1: add new module load parm enable_gcm_256
- smb3.1.1: print warning if server does not support requested encryption
type
- smb3.1.1: rename nonces used for GCM and CCM encryption
- smb3.1.1: set gcm256 when requested
- cifs: Adjust key sizes and key generation routines for AES256 encryption
* locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184)
- locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
* [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink
(LP: #1925452)
- net/mlx5: Fix HW spec violation configuring uplink
* Focal update: v5.4.114 upstream stable release (LP: #1926493)
- Revert "scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure"
- Revert "scsi: qla2xxx: Fix stuck login session using prli_pend_timer"
- scsi: qla2xxx: Dual FCP-NVMe target port support
- scsi: qla2xxx: Fix device connect issues in P2P configuration
- scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure
- scsi: qla2xxx: Add a shadow variable to hold disc_state history of fcport
- scsi: qla2xxx: Fix stuck login session using prli_pend_timer
- scsi: qla2xxx: Fix fabric scan hang
- net/sctp: fix race condition in sctp_destroy_sock
- Input: nspire-keypad - enable interrupts only when opened
- gpio: sysfs: Obey valid_mask
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- arc: kernel: Return -EFAULT if copy_to_user() fails
- ASoC: max98373: Added 30ms turn on/off time delay
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ARM: omap1: fix building with clang IAS
- drm/msm: Fix a5xx/a6xx timestamps
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: forbid monitor for add llsec key
- net: ieee802154: forbid monitor for del llsec key
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: forbid monitor for del llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: forbid monitor for del llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- virt_wifi: Return micros for BSS TSF values
- Input: s6sy761 - fix coordinate read bit shift
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- dm verity fec: fix misaligned RS roots IO
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- vfio/pci: Add missing range check in vfio_pci_mmap
- riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
- netfilter: bridge: add pre_exit hooks for ebtable unregistration
- netfilter: arp_tables: add pre_exit hook for table unregister
- net: macb: fix the restore of cmp registers
- netfilter: nft_limit: avoid possible divide error in nft_limit_init
- net: davicom: Fix regulator not turned off on failed probe
- net: sit: Unregister catch-all devices
- net: ip6_tunnel: Unregister catch-all devices
- i40e: fix the panic when running bpf in xdpdrv mode
- ibmvnic: avoid calling napi_disable() twice
- ibmvnic: remove duplicate napi_schedule call in do_reset function
- ibmvnic: remove duplicate napi_schedule call in open function
- gro:
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Verification for F and B done. On G build fails, I'll look into it and update the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
#VERIFICATION BIONIC - crash part Installed crash from -proposed, triggered a crash and opened dump with crash. Crash opens dump successfully. ~# crash usr/lib/debug/boot/vmlinux-5.4.0-1049-aws /var/crash/202106021531/dump.202106021531 crash 7.2.8 Copyright (C) 2002-2020 Red Hat, Inc. crash> ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
#VERIFICATION FOCAL - crash part Installed crash from -proposed, triggered a crash and opened dump with crash. Crash opens dump successfully. # crash usr/lib/debug/boot/vmlinux-5.4.0-1049-aws /var/crash/202106021329/dump.202106021329 crash 7.2.8 Copyright (C) 2002-2020 Red Hat, Inc. crash> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Changed in: crash (Ubuntu Bionic) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: crash (Ubuntu Focal) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: crash (Ubuntu Groovy) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Hello Ali, or anyone else affected, Accepted crash into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: crash (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags removed: verification-done-focal ** Tags added: verification-needed-focal ** Changed in: crash (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Hello Ali, or anyone else affected, Accepted crash into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: crash (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Tags removed: verification-done-groovy ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
#VERIFICATION GROOVY - kernel part Installed kernel from -proposed, triggered a crash and opened dump with crash. Crash opens dump successfully (patched version of crash required with commit from description). # crash usr/lib/debug/boot/vmlinux-5.8.0-1034-aws /var/crash/202105182030/dump.202105182030 crash 7.2.8 Copyright (C) 2002-2020 Red Hat, Inc. crash> ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
#VERIFICATION FOCAL - kernel part Installed kernel from -proposed, triggered a crash and opened dump with crash. Crash opens dump successfully (patched version of crash required with commit from description). # crash usr/lib/debug/boot/vmlinux-5.4.0-1049-aws /var/crash/202105181907/dump.202105181907 crash 7.2.8 Copyright (C) 2002-2020 Red Hat, Inc. ... crash> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
uploaded to b/f/g, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug is awaiting verification that the 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- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. 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: verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug is awaiting verification that the 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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Merge proposal linked: https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401229 ** Merge proposal linked: https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401230 ** Merge proposal linked: https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401231 ** Merge proposal linked: https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401232 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Changed in: crash (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Also affects: crash (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: crash (Ubuntu Bionic) Status: New => Confirmed ** Description changed: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ + + Series affected : + + Kenrel : + This affects Focal (5.4 kernel) and Groovy (5.8 kernel). + Hirsute already contains the commit and kernels prior to 5.3 are not affected. + + Crash : + The commit is already in Hirsute. + Groovy, Focal and Bionic are affected. + In case of Bionic the bug appears only if 5.4 hwe kernel is used. + [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. - [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Focal kernel : Patch submitted https://lists.ubuntu.com/archives/kernel-team/2021-April/119287.html Groovy kernel : Patch submitted https://lists.ubuntu.com/archives/kernel-team/2021-April/119288.html ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: crash (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: crash (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: crash (Ubuntu Groovy) Status: New => Confirmed ** Changed in: crash (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: crash (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: crash (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Also affects: crash-installer Importance: Undecided Status: New ** No longer affects: crash-installer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Description changed: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 - arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo - + arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 - arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ - + arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL + [Where problems could occur] - [Where problems could occur] + Kernel patch : + + The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation + and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. + Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. + + Crash patch : + + This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. + The regression potential is small and any problem would regard reading this variable. + [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Description changed: + [Impact] + On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL - This bug/change in crash provides a workaround for 5.4+ - https://github.com/crash-utility/crash/issues/52 kernels. + This bug has been addressed upstream and needed patches both in crash + and kernel. + + Kernel patch : + + commit bbdbc11804ff0b4130e7550113b452e96a74d16e + Author: Bhupesh Sharma + Date: Thu May 14 00:22:37 2020 +0530 + arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo + + + Crash patch : + + commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 + Author: Bhupesh Sharma + Date: Tue Jul 14 01:14:49 2020 +0530 + + arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ + + + [Test Case] + + On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. + It will fail with : + crash: cannot determine VA_BITS_ACTUAL + + + [Where problems could occur] + + [Other] + + Workaround : + This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
** Changed in: crash (Ubuntu) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: crash (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
