Hide Forgot
Description of problem: Booted the system normally Additional info: reporter: libreport-2.7.2 WARNING: CPU: 3 PID: 499 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 sysfs: cannot create duplicate filename '/bus/i2c/devices/i2c-DUAL250E:00' Modules linked in: snd_timer acpi_thermal_rel int340x_thermal_zone intel_soc_dts_iosf snd acpi_cpufreq(-) rfkill_gpio i2c_designware_platform(+) soundcore tpm_tis i2c_designware_core tpm rfkill spi_pxa2xx_platform pwm_lpss_platform pwm_lpss nfsd auth_rpcgss nfs_acl lockd grace sunrpc i915 mmc_block crc32c_intel i2c_algo_bit drm_kms_helper 8021q serio_raw garp stp llc drm mrp r8169 mii video fjes i2c_hid sdhci_acpi sdhci rtsx_usb_sdmmc mmc_core rtsx_usb CPU: 3 PID: 499 Comm: systemd-udevd Not tainted 4.7.4-200.fc24.x86_64 #1 Hardware name: LENOVO 80M0/Mini, BIOS C0CN25WW 04/21/2015 0000000000000286 00000000ce4d434d ffff8800764bb6d8 ffffffffa13d994f ffff8800764bb728 0000000000000000 ffff8800764bb718 ffffffffa109faab 0000001f3f81d000 ffff88003f81d000 ffff880072490110 ffff88007902a348 Call Trace: [<ffffffffa13d994f>] dump_stack+0x63/0x84 [<ffffffffa109faab>] __warn+0xcb/0xf0 [<ffffffffa109fb2f>] warn_slowpath_fmt+0x5f/0x80 [<ffffffffa12caa42>] sysfs_warn_dup+0x62/0x80 [<ffffffffa12cadc7>] sysfs_do_create_link_sd.isra.2+0x97/0xb0 [<ffffffffa12cae05>] sysfs_create_link+0x25/0x40 [<ffffffffa1520c3d>] bus_add_device+0x10d/0x1f0 [<ffffffffa151e97d>] device_add+0x43d/0x670 [<ffffffffa151ebca>] device_register+0x1a/0x20 [<ffffffffa163a996>] i2c_new_device+0x196/0x240 [<ffffffffa163afd8>] acpi_i2c_add_device+0x1a8/0x210 [<ffffffffa148b09b>] acpi_ns_walk_namespace+0xe8/0x19d [<ffffffffa163ae30>] ? i2c_sysfs_new_device+0x270/0x270 [<ffffffffa163ae30>] ? i2c_sysfs_new_device+0x270/0x270 [<ffffffffa148b5de>] acpi_walk_namespace+0xa0/0xd5 [<ffffffffa163b6f9>] i2c_register_adapter+0x349/0x4e0 [<ffffffffa163b8ea>] i2c_add_adapter+0x5a/0x70 [<ffffffffa163b980>] i2c_add_numbered_adapter+0x80/0x90 [<ffffffffc04b20f8>] i2c_dw_probe+0x118/0x1d0 [i2c_designware_core] [<ffffffffc02784a2>] dw_i2c_plat_probe+0x1e2/0x420 [i2c_designware_platform] [<ffffffffa15241cb>] platform_drv_probe+0x3b/0xa0 [<ffffffffa151dff0>] ? devices_kset_move_last+0x50/0x90 [<ffffffffa1521fbc>] driver_probe_device+0x22c/0x440 [<ffffffffa15222a1>] __driver_attach+0xd1/0xf0 [<ffffffffa15221d0>] ? driver_probe_device+0x440/0x440 [<ffffffffa151f8ec>] bus_for_each_dev+0x6c/0xc0 [<ffffffffa15216ae>] driver_attach+0x1e/0x20 [<ffffffffa15210f3>] bus_add_driver+0x1c3/0x280 [<ffffffffc041a000>] ? 0xffffffffc041a000 [<ffffffffa1522bf0>] driver_register+0x60/0xe0 [<ffffffffc041a000>] ? 0xffffffffc041a000 [<ffffffffa1524146>] __platform_driver_register+0x36/0x40 [<ffffffffc041a017>] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform] [<ffffffffa1002190>] do_one_initcall+0x50/0x180 [<ffffffffa11ff0b1>] ? __vunmap+0x81/0xd0 [<ffffffffa121ef22>] ? kmem_cache_alloc_trace+0x182/0x1d0 [<ffffffffa11b349b>] ? do_init_module+0x27/0x1d8 [<ffffffffa11b34d3>] do_init_module+0x5f/0x1d8 [<ffffffffa112a7f6>] load_module+0x1fe6/0x27e0 [<ffffffffa11276c0>] ? __symbol_put+0x60/0x60 [<ffffffffa112b13e>] SYSC_init_module+0x14e/0x190 [<ffffffffa112b2ae>] SyS_init_module+0xe/0x10 [<ffffffffa1003d52>] do_syscall_64+0x62/0x110 [<ffffffffa17eb921>] entry_SYSCALL64_slow_path+0x25/0x25
Created attachment 1202184 [details] File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are 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 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. 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 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 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.