Bug 1949334
Summary: | Fedora installation fails on an amberwing with btrfs | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Whalen <pwhalen> | ||||
Component: | kernel | Assignee: | fedora-kernel-btrfs | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 34 | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, bugzilla, davide, efuller, hdegoede, jarodwilson, jbastian, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, msalter, pbrobinson, pbunyan, ptalbert, steved | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | aarch64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2022-06-07 21:08:08 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Paul Whalen
2021-04-14 03:00:35 UTC
Created attachment 1771731 [details]
journalctl
Adding the BTRFS maintainers I'm digging into this, gonna take me a minute to get an arm virt guest and cross compiling working. (In reply to Josef Bacik from comment #3) > I'm digging into this, gonna take me a minute to get an arm virt guest and > cross compiling working. I've only seen this while testing on the Amberwing, other hardware and virt work as expected. Just a random observation: as old as it is, Amberwing still has a knack for turning up mm/barrier/tlb related issues. Not seeing this during Rawhide testing with 5.14 RC's. Unfortunately, hit this again today while testing Fedora 35. [ 440.089768] Internal error: Oops: 96000004 [#1] SMP [ 440.093685] Modules linked in: vfat fat rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver xfs libfc scsi_transport_fc scsi_dh_rdac scsi_dh_emc scsi_dh_alua acpi_ipmi ipmi_ssif ipmi_devintf ipmi_msghandler cppc_cpufreq drm fuse zram overlay loop nfsv3 nfs_acl nfs lockd grace fscache netfs rpcrdma rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_iser ib_umad rdma_cm ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core rfkill crct10dif_ce mlx5_core ghash_ce sbsa_gwdt at803x mlxfw psample qcom_rng ahci_platform qcom_emac sdhci_acpi sdhci hdma hdma_mgmt xhci_plat_hcd i2c_qup sunrpc lrw dm_crypt trusted asn1_encoder tee dm_round_robin dm_multipath linear raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 squashfs cramfs be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi aes_neon_bs [ 440.174674] CPU: 40 PID: 1527 Comm: kworker/u92:7 Not tainted 5.14.0-0.rc7.54.fc35.aarch64 #1 [ 440.183180] Hardware name: WIWYNN Qualcomm Centriq 2400 Reference Evaluation Platform CV90-LA115-P11/Qualcomm Centriq 2400 Customer Reference Board, BIOS [ 440.196982] Workqueue: btrfs-delalloc btrfs_work_helper [ 440.202191] pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 440.208179] pc : submit_compressed_extents+0x38/0x3d0 [ 440.213214] lr : async_cow_submit+0x6c/0xc0 [ 440.217381] sp : ffff80001665bc20 [ 440.220680] x29: ffff80001665bc30 x28: 0000000000000000 x27: ffffc2db26391000 [ 440.227797] x26: fffffffffffffdd0 x25: dead000000000100 x24: ffff5e514a086408 [ 440.234915] x23: 0000000000000000 x22: 0000000000000000 x21: ffff5e5149dcf200 [ 440.242034] x20: ffff5e514a086408 x19: ffff5e514a086448 x18: 0000000000000001 [ 440.249152] x17: ffff5e5212a06abd x16: 0000000000000006 x15: 58b7bdf0f78aee0a [ 440.256270] x14: bb5977f05d2587b6 x13: 0000000000000020 x12: ffff5e6833f998c0 [ 440.263388] x11: ffffc2db263ab500 x10: 0000000000000000 x9 : ffffc2db24b8216c [ 440.270506] x8 : 0000000000000001 x7 : ffffc2db263ab521 x6 : 0000000000000000 [ 440.277624] x5 : 0000000000000000 x4 : ffff5e5173cb3518 x3 : 0000000000000000 [ 440.284742] x2 : ffff5e5173cb32e8 x1 : ffff5e514a086430 x0 : ffff5e514a086430 [ 440.291861] Call trace: [ 440.294292] submit_compressed_extents+0x38/0x3d0 [ 440.298978] async_cow_submit+0x6c/0xc0 [ 440.302798] run_ordered_work+0xc8/0x280 [ 440.306704] btrfs_work_helper+0x98/0x250 [ 440.310697] process_one_work+0x1f0/0x4ac [ 440.314690] worker_thread+0x188/0x504 [ 440.318423] kthread+0x110/0x114 [ 440.321634] ret_from_fork+0x10/0x18 [ 440.325195] Code: a9056bf9 f8428437 f9401400 d108c2fa (f9400356) [ 440.331271] ---[ end trace 7d10bc4e24ab0123 ]--- Still seeing this while testing Fedora 35(5.14.10-300.fc35.aarch64), moving to btrfs-kernel. I've been compiling the kernel for about 6 hours, with about 1 hour of package installation concurrently. And no crash. This is in Vexxhost aarch64 openstack vm, bug 2011928. I have kdump setup there, so I can get a kernel core dump to developers, but without a crash I can't do that. And in your case it's happening so early that you can't install to have a chance of setting up kdump :\ Any chance you can use a ready to go raw.xz image? The catch though is kdump needs kernel debuginfo which is almost 700M download and altogether might be 3.5G to install which almost certainly trigger the crash before you get it all setup. Maybe the thing to do is go backward to Fedora 34 with an older kernel, and setup a 5.14.x kernel+debuginfo with all the kdump tools and kernel.org git source. Then reboot into the new kernel and hopefully capture a vmcore. This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed. |