Description of problem: During startup of Fedora 20 on Fujitsu RX300 S6 (Xeon 56XX series, 5520 Mainboard) system udevd gets tainted because of duplicate filenames Version-Release number of selected component (if applicable): Tested with Kernel 3.14.8 and 3.16.2 How reproducible: 100% Steps to Reproduce: start system Actual results: dmesg shows: [ 8.591343] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0 [ 8.696312] pps_core: LinuxPPS API ver. 1 registered [ 8.696315] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti> [ 8.721727] ------------[ cut here ]------------ [ 8.721740] WARNING: CPU: 5 PID: 449 at fs/sysfs/dir.c:52 sysfs_warn_dup+0x86/0xa0() [ 8.721743] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host6/target6:0:6/6:0:6:0/enclosure/6:0:6:0/ArrayDevice03' [ 8.721745] Modules linked in: ses(+) enclosure pps_core kvm crct10dif_pclmul ipmi_si(+) ipmi_msghandler dca shpchp iTCO_wdt iTCO_vendor_support lpc_ich mfd_core crc32_pclmul crc32c_intel i7core_edac edac_core ghash_clmulni_intel microcode i2c_i801 nfsd auth_rpcgss nfs_acl lockd acpi_power_meter acpi_cpufreq sunrpc dm_multipath 8021q garp mrp tun bridge stp llc bonding ib_umad ib_ipoib ib_cm mlx4_ib ib_sa i2c_algo_bit drm_kms_helper ttm drm i2c_core megaraid_sas mlx4_core ib_mad ib_core ib_addr dummy [ 8.721785] CPU: 5 PID: 449 Comm: systemd-udevd Tainted: G I 3.14.8-200.fc20.x86_64 #1 [ 8.721787] Hardware name: FUJITSU PRIMERGY RX300 S6 /D2619, BIOS 6.00 Rev. 1.13.2619.N1 01/19/2012 [ 8.721789] 0000000000000000 000000000f17b3b4 ffff881978d81990 ffffffff816f0502 [ 8.721793] ffff881978d819d8 ffff881978d819c8 ffffffff8108a1cd ffff880d747e5000 [ 8.721796] ffff880d747e5000 ffff881975d52690 ffff881975c6cdf0 0000000000000004 [ 8.721800] Call Trace: [ 8.721809] [<ffffffff816f0502>] dump_stack+0x45/0x56 [ 8.721816] [<ffffffff8108a1cd>] warn_slowpath_common+0x7d/0xa0 [ 8.721819] [<ffffffff8108a24c>] warn_slowpath_fmt+0x5c/0x80 [ 8.721822] [<ffffffff81263d66>] sysfs_warn_dup+0x86/0xa0 [ 8.721825] [<ffffffff81263e0e>] sysfs_create_dir_ns+0x8e/0xa0 [ 8.721831] [<ffffffff81356fc0>] kobject_add_internal+0xc0/0x3f0 [ 8.721834] [<ffffffff813577b5>] kobject_add+0x75/0xd0 [ 8.721840] [<ffffffff81462583>] ? device_private_init+0x23/0x80 [ 8.721843] [<ffffffff81462705>] device_add+0x125/0x630 [ 8.721846] [<ffffffff81462c2a>] device_register+0x1a/0x20 [ 8.721850] [<ffffffffa02db696>] enclosure_component_register+0xb6/0x100 [enclosure] [ 8.721854] [<ffffffffa029c91d>] ses_enclosure_data_process+0x27d/0x370 [ses] [ 8.721857] [<ffffffffa029d07d>] ses_intf_add+0x44d/0x4fc [ses] [ 8.721860] [<ffffffff81466ab9>] class_interface_register+0xa9/0x100 [ 8.721864] [<ffffffffa0005000>] ? 0xffffffffa0004fff [ 8.721868] [<ffffffff814920f6>] scsi_register_interface+0x16/0x20 [ 8.721872] [<ffffffffa0005013>] ses_init+0x13/0x1000 [ses] [ 8.721874] [<ffffffffa0005000>] ? 0xffffffffa0004fff [ 8.721879] [<ffffffff8100216a>] do_one_initcall+0xfa/0x1b0 [ 8.721884] [<ffffffff8105a953>] ? set_memory_nx+0x43/0x50 [ 8.721890] [<ffffffff81105c17>] load_module+0x1e37/0x25d0 [ 8.721893] [<ffffffff811012b0>] ? store_uevent+0x70/0x70 [ 8.721899] [<ffffffff811efa30>] ? kernel_read+0x50/0x80 [ 8.721902] [<ffffffff81106566>] SyS_finit_module+0xa6/0xd0 [ 8.721908] [<ffffffff817008e9>] system_call_fastpath+0x16/0x1b [ 8.721909] ---[ end trace 3ee315892ccc5432 ]--- [ 8.721911] ------------[ cut here ]------------ Expected results: No error shown, kernel not tainted Additional info: Error is repeated once per CPU/thread. In our case 16 times.
After digging for the reason of this all I found an older thread that was about the same topic: https://lists.debian.org/debian-kernel/2012/06/msg01069.html I'm willing to test and give feedback about the mentioned patch. Is this the right bugzilla to track the progress? If not whom should I contact?
*********** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.