Bug 1225671
Summary: | [abrt] WARNING: CPU: 0 PID: 78 at mm/backing-dev.c:372 bdi_unregister+0x3a/0x50() | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jim Simmons <simmonsjw> | ||||
Component: | kernel | Assignee: | fedora-kernel-block | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 22 | CC: | amk, ejfowler, gansalmon, ifoolb, itamar, jhoward, jmoyer, jonathan, jwright2, kernel-maint, leo, madhu.chinakonda, marcel, mchehab, nexusfc, pgsellmann, v.ronnen | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/48ad480dffc5e89b5c5fc431491400ce8670e699 | ||||||
Whiteboard: | abrt_hash:9a3ee63ffd60a8f2d80e82d011902bfc9bac6cd3 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-07-19 14:18:19 UTC | Type: | --- | ||||
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
Jim Simmons
2015-05-28 00:37:56 UTC
Created attachment 1030851 [details]
File: dmesg
Description of problem: trying to install F22 on a x86_64 machine deleted all partitions on target disk invoke 'install to disk' Version-Release number of selected component: kernel Additional info: reporter: libreport-2.5.1 cmdline: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-22-3 ro rd.live.image quiet rhgb kernel: 4.0.4-301.fc22.x86_64 runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 1 PID: 1996 at mm/backing-dev.c:372 bdi_unregister+0x3a/0x50() Modules linked in: iscsi_ibft iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sha256_ssse3 dm_crypt vfat fat dm_round_robin dm_multipath raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid0 bnep bluetooth fuse nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ebtable_broute bridge ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw snd_hda_codec_hdmi intel_rapl iosf_mbi x86_pkg_temp_thermal raid1 coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel snd_hda_intel snd_hda_controller snd_hda_codec kvm iTCO_wdt iTCO_vendor_support eeepc_wmi asus_wmi sparse_keymap rfkill snd_hwdep snd_seq snd_seq_device i2c_i801 sb_edac snd_pcm edac_core serio_raw lpc_ich mfd_core shpchp snd_timer snd mei_me soundcore mei nfsd auth_rpcgss nfs_acl lockd grace isofs squashfs 8021q garp stp llc mrp nouveau mxm_wmi video crct10dif_pclmul crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel ttm e1000e firewire_ohci igb drm uas firewire_core usb_storage crc_itu_t dca ptp pps_core i2c_algo_bit wmi scsi_dh_rdac scsi_dh_emc scsi_dh_alua sunrpc loop CPU: 1 PID: 1996 Comm: kworker/1:4 Not tainted 4.0.4-301.fc22.x86_64 #1 Hardware name: System manufacturer System Product Name/SABERTOOTH X79, BIOS 4801 07/25/2014 Workqueue: md_misc mddev_delayed_delete 0000000000000000 00000000e2ebc1d7 ffff8807cb2afcb8 ffffffff81782644 0000000000000000 0000000000000000 ffff8807cb2afcf8 ffffffff8109c66a 0000000000000000 ffff880805009800 0000000000000000 0000000000000000 Call Trace: [<ffffffff81782644>] dump_stack+0x45/0x57 [<ffffffff8109c66a>] warn_slowpath_common+0x8a/0xc0 [<ffffffff8109c79a>] warn_slowpath_null+0x1a/0x20 [<ffffffff811c0a4a>] bdi_unregister+0x3a/0x50 [<ffffffff8137f5c1>] del_gendisk+0x131/0x240 [<ffffffff815e6853>] md_free+0x43/0x60 [<ffffffff8139e44a>] kobject_release+0x7a/0x1c0 [<ffffffff8139e2f5>] kobject_put+0x35/0x70 [<ffffffff815e4794>] mddev_delayed_delete+0x34/0x40 [<ffffffff810b596b>] process_one_work+0x1bb/0x410 [<ffffffff810b5c13>] worker_thread+0x53/0x470 [<ffffffff810b5bc0>] ? process_one_work+0x410/0x410 [<ffffffff810bb678>] kthread+0xd8/0xf0 [<ffffffff810bb5a0>] ? kthread_worker_fn+0x180/0x180 [<ffffffff81788bd8>] ret_from_fork+0x58/0x90 [<ffffffff810bb5a0>] ? kthread_worker_fn+0x180/0x180 Same problem here. Fedora 21 2 disks raid 1 lvm Boot live media, select install to disk. Looks as if this has never been tested on physical machines. Are tests, if any, only conducted on virtual machines? Is there a work around or new spin of media? With the final F22 Workstation installation image (x86, 64 bit) I've the same problem for my existing F21 installation based on regular software RAID-1 (md*). When I boot the Workstation image (USB stick) and select "Install to Harddisk", first some mysterious crash occurs (Oops...) but eventually the Installer starts up. Unfortunately, when selecting the destination devices, no software RAID devices (md*) from my existing F21 installation will show up. So there's nothing I can install F22 on. There's no hardware-based RAID involved or any motherboard RAID functions. Works fine with the Server Image. Looks similar to bug #1225184 Description of problem: Booted Fedora 22 x86 Workstation DVD (freshly burned from .iso). Used menu "Troubleshoot"->"Check media and boot Fedora". Media check OK; booted OS and brought up GUI. Chose "Install to Hard Disk". Received on-screen message "Oops. Something has failed." and asked me to send in the report. Rest of OS continued to work, allowing me to send in this report from the failing machine. Hardware is a NetGear ReadyNAS 6-disk box with so-called "Flame-6" motherboard. Version-Release number of selected component: kernel Additional info: reporter: libreport-2.5.1 cmdline: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-i686-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 rd.live.check kernel: 4.0.4-301.fc22.i686 runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 0 PID: 741 at mm/backing-dev.c:372 bdi_unregister+0x38/0x50() Modules linked in: iscsi_ibft iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt dm_round_robin dm_multipath raid10 raid0 vfat fat bnep bluetooth rfkill fuse nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ebtable_broute bridge ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw coretemp kvm_intel kvm raid456 async_raid6_recov async_memcpy async_pq async_xor xor snd_hda_intel snd_hda_controller snd_hda_codec serio_raw gpio_ich async_tx raid6_pq ppdev raid1 iTCO_wdt iTCO_vendor_support snd_hwdep snd_seq snd_seq_device snd_pcm parport_pc parport snd_timer snd lpc_ich soundcore i2c_i801 acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace isofs squashfs i915 uas 8021q garp stp llc video mrp i2c_algo_bit usb_storage drm_kms_helper sky2 drm scsi_dh_rdac scsi_dh_emc scsi_dh_alua sunrpc loop CPU: 0 PID: 741 Comm: kworker/0:5 Not tainted 4.0.4-301.fc22.i686 #1 Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014 07/26/2010 Workqueue: md_misc mddev_delayed_delete c0d1b947 b7b28f4f 00000000 dc5efe20 c0a71a6e 00000000 dc5efe50 c0458127 c0c34ff4 00000000 000002e5 c0c4c348 00000174 c05567b8 c05567b8 e69e7000 00000000 e69e7064 dc5efe60 c0458232 00000009 00000000 dc5efe68 c05567b8 Call Trace: [<c0a71a6e>] dump_stack+0x41/0x52 [<c0458127>] warn_slowpath_common+0x87/0xc0 [<c05567b8>] ? bdi_unregister+0x38/0x50 [<c05567b8>] ? bdi_unregister+0x38/0x50 [<c0458232>] warn_slowpath_null+0x22/0x30 [<c05567b8>] bdi_unregister+0x38/0x50 [<c06cf500>] del_gendisk+0x100/0x1f0 [<c08f7499>] md_free+0x39/0x50 [<c06eaaeb>] kobject_release+0x7b/0x200 [<c06ea9bd>] kobject_put+0x2d/0x60 [<c06eaa5d>] ? kobject_del+0x2d/0x40 [<c08f5719>] mddev_delayed_delete+0x29/0x30 [<c046d415>] process_one_work+0x145/0x370 [<c046d679>] worker_thread+0x39/0x410 [<c046d640>] ? process_one_work+0x370/0x370 [<c0472116>] kthread+0xa6/0xc0 [<c0a76f81>] ret_from_kernel_thread+0x21/0x30 [<c0472070>] ? kthread_worker_fn+0x130/0x130 (In reply to v.ronnen from comment #3) > Same problem here. > Fedora 21 > 2 disks raid 1 lvm > > Boot live media, select install to disk. > Looks as if this has never been tested on physical machines. > Are tests, if any, only conducted on virtual machines? > > Is there a work around or new spin of media? This bug can be reproduced on a VirtualBox with fc21 and two disk in raid1 Conclusion NO test was done nor on real hardware, nor on virtual hardware. Effectively it is IMPOSSIBLE to install fc22 nor via live nor via net media. FC22 is released too soon. Installers did not reach pre alpha quality. I believe this issue is addressed in 4.1-rc7. If we could spin install media with that kernel, we would know for sure. (In reply to Jeffrey Moyer from comment #7) > I believe this issue is addressed in 4.1-rc7. If we could spin install > media with that kernel, we would know for sure. The rawhide nightlies are probably the only media that will contain the patch until F23 Alpha is released. If I'm not mistaken though, this should be fixed in the 4.0.5 update as I backported the patch via bug 1226621 Don't know about LVM, but for installation of Fedora 22 to existing MDRAID volumes, the F22 Server (!) image can be used as a workaround. For some reason the F22 Server edition doesn't trigger that bug and MDRAID volumes are properly detected. After the installation is done, there are no issues with MDRAID. Seems to be a bug for only the F22 Workstation/Live image. With the F22 Server ISO, a Minimal Installation can be performed, and after the system is ready, use dnf to install the "Fedora Workstation" packages group. The resulting system comes pretty close to an installation from the (broken) F22 Workstation/Live image. There's a difference of about 100 packages to a real F22 Workstation/Live installation but nothing dramatic. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those. The crashes have gone, but Fedora 23 (official) Live image still doesn't recognize Software RAID devices properly, so installation fails. Fedora 22 + 23 are both not suitable for systems with Software RAID. Has the support for Software RAID been dropped officially? Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |