Additional info: reporter: libreport-2.7.1 WARNING: CPU: 3 PID: 822 at drivers/i2c/busses/i2c-designware-core.c:280 i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core] Modules linked in: i2c_designware_platform(+) i2c_designware_core tpm_tis(+) tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt rtsx_pci_sdmmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel 8021q garp amdgpu stp llc mrp i2c_algo_bit drm_kms_helper serio_raw tg3 ttm ptp pps_core rtsx_pci drm fjes i2c_hid hid_lenovo CPU: 3 PID: 822 Comm: systemd-udevd Not tainted 4.7.0-0.rc4.git1.1.fc25.x86_64 #1 Hardware name: HP HP EliteBook 745 G3/807E, BIOS N73 Ver. 01.08 01/28/2016 0000000000000286 00000000cbbcde03 ffff88042ab2f9f8 ffffffff81458a95 0000000000000000 0000000000000000 ffff88042ab2fa38 ffffffff810ac40b 000001182bf8d810 ffff88009a62f028 0000000000000000 000000000000012c Call Trace: [<ffffffff81458a95>] dump_stack+0x86/0xc1 [<ffffffff810ac40b>] __warn+0xcb/0xf0 [<ffffffff810ac53d>] warn_slowpath_null+0x1d/0x20 [<ffffffffc03f3091>] i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core] [<ffffffffc03f3321>] i2c_dw_init+0x111/0x430 [i2c_designware_core] [<ffffffffc03f4069>] i2c_dw_probe+0x39/0x1d0 [i2c_designware_core] [<ffffffffc039b4a2>] dw_i2c_plat_probe+0x1e2/0x420 [i2c_designware_platform] [<ffffffff815c7bdb>] platform_drv_probe+0x3b/0xa0 [<ffffffff815c14f0>] ? devices_kset_move_last+0x60/0x90 [<ffffffff815c563c>] driver_probe_device+0x22c/0x440 [<ffffffff815c5925>] __driver_attach+0xd5/0x100 [<ffffffff815c5850>] ? driver_probe_device+0x440/0x440 [<ffffffff815c2e83>] bus_for_each_dev+0x73/0xc0 [<ffffffff815c4d0e>] driver_attach+0x1e/0x20 [<ffffffff815c4736>] bus_add_driver+0x1c6/0x290 [<ffffffffc03a0000>] ? 0xffffffffc03a0000 [<ffffffff815c65f0>] driver_register+0x60/0xe0 [<ffffffffc03a0000>] ? 0xffffffffc03a0000 [<ffffffff815c7b56>] __platform_driver_register+0x36/0x40 [<ffffffffc03a0017>] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform] [<ffffffff81002190>] do_one_initcall+0x50/0x180 [<ffffffff8112b095>] ? rcu_read_lock_sched_held+0x45/0x80 [<ffffffff812680ec>] ? kmem_cache_alloc_trace+0x2ac/0x310 [<ffffffff811f0a2d>] ? do_init_module+0x27/0x1da [<ffffffff811f0a65>] do_init_module+0x5f/0x1da [<ffffffff811577fd>] load_module+0x21cd/0x2960 [<ffffffff81154250>] ? __symbol_put+0x70/0x70 [<ffffffff81153250>] ? show_coresize+0x30/0x30 [<ffffffff81037a09>] ? sched_clock+0x9/0x10 [<ffffffff810e8057>] ? sched_clock_cpu+0xa7/0xc0 [<ffffffff81158102>] SYSC_init_module+0x172/0x1b0 [<ffffffff8115826e>] SyS_init_module+0xe/0x10 [<ffffffff81003fe7>] do_syscall_64+0x67/0x190 [<ffffffff818d8a7f>] entry_SYSCALL64_slow_path+0x25/0x25 Potential duplicate: bug 1322761
Created attachment 1175957 [details] File: dmesg
*********** 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 24 kernel bugs. Fedora 24 has now been rebased to 4.7.4-200.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 25, and are still experiencing this issue, please change the version to Fedora 25. 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 4 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.
ok