Description of problem: boot ssytem on a new machine (acer aspire E 15) Additional info: reporter: libreport-2.7.2 WARNING: CPU: 1 PID: 799 at drivers/i2c/busses/i2c-designware-core.c:280 i2c_dw_clk_rate+0x3a/0x50 [i2c_designware_core]() Modules linked in: pcc_cpufreq(-) i2c_designware_platform(+) acpi_cpufreq tpm_crb(+) tpm_tis i2c_designware_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt rtsx_pci_sdmmc amdkfd mmc_core amd_iommu_v2 amdgpu crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel i2c_algo_bit drm_kms_helper serio_raw ttm 8021q uas garp stp drm llc usb_storage mrp r8169 rtsx_pci mii fjes i2c_hid CPU: 1 PID: 799 Comm: systemd-udevd Not tainted 4.5.5-300.fc24.x86_64 #1 Hardware name: Acer Aspire E5-553G/Wasp_BR, BIOS V1.05 05/12/2016 0000000000000286 000000007b3de59a ffff88040b62ba38 ffffffff813d35af 0000000000000000 ffffffffa029d080 ffff88040b62ba70 ffffffff810a5f12 ffff88040be15028 0000000000000000 000000000000012c 000000000000012c Call Trace: [<ffffffff813d35af>] dump_stack+0x63/0x84 [<ffffffff810a5f12>] warn_slowpath_common+0x82/0xc0 [<ffffffff810a605a>] warn_slowpath_null+0x1a/0x20 [<ffffffffa029b08a>] i2c_dw_clk_rate+0x3a/0x50 [i2c_designware_core] [<ffffffffa029b2dd>] i2c_dw_init+0xed/0x360 [i2c_designware_core] [<ffffffffa029b59e>] i2c_dw_probe+0x4e/0x170 [i2c_designware_core] [<ffffffffa0344481>] dw_i2c_plat_probe+0x1d1/0x410 [i2c_designware_platform] [<ffffffff8151597b>] platform_drv_probe+0x3b/0xa0 [<ffffffff8150f850>] ? devices_kset_move_last+0x50/0x90 [<ffffffff8151381c>] driver_probe_device+0x22c/0x440 [<ffffffff81513ab4>] __driver_attach+0x84/0x90 [<ffffffff81513a30>] ? driver_probe_device+0x440/0x440 [<ffffffff8151114c>] bus_for_each_dev+0x6c/0xc0 [<ffffffff81512f0e>] driver_attach+0x1e/0x20 [<ffffffff81512953>] bus_add_driver+0x1c3/0x280 [<ffffffffa0349000>] ? 0xffffffffa0349000 [<ffffffff81514380>] driver_register+0x60/0xe0 [<ffffffff815158f6>] __platform_driver_register+0x36/0x40 [<ffffffffa0349017>] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform] [<ffffffff81002123>] do_one_initcall+0xb3/0x1f0 [<ffffffff8121ab12>] ? kmem_cache_alloc_trace+0x182/0x1d0 [<ffffffff811b0c8c>] ? do_init_module+0x27/0x1d8 [<ffffffff811b0cc4>] do_init_module+0x5f/0x1d8 [<ffffffff8112d4c6>] load_module+0x1fd6/0x2790 [<ffffffff81129dc0>] ? __symbol_put+0x60/0x60 [<ffffffff8112ddc9>] SYSC_init_module+0x149/0x190 [<ffffffff8112defe>] SyS_init_module+0xe/0x10 [<ffffffff817cecee>] entry_SYSCALL_64_fastpath+0x12/0x6d
Created attachment 1200667 [details] File: dmesg
4.5.5 is no longer supported on F24. Please update your kernel and reopen if you can recreate on the latest stable update.
the problem is still present in 4.7.3-200. bug reporting tool reported the first instance which was right after installation. it'd help if either there was a live image with more recent kernel or fix the bug reporting tool to not merge bugs from different kernel versions. anyway the new dmesg trace is: [ 16.961668] ------------[ cut here ]------------ [ 16.961677] WARNING: CPU: 0 PID: 768 at drivers/i2c/busses/i2c-designware-core.c:280 i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core] [ 16.961678] Modules linked in: i2c_designware_platform(+) tpm_tis i2c_designware_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt amdkfd amd_iommu_v2 amdgpu rtsx_pci_sdmmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel i2c_algo_bit drm_kms_helper serio_raw 8021q ttm garp stp llc mrp drm r8169 rtsx_pci mii fjes i2c_hid i2c_dev [ 16.961703] CPU: 0 PID: 768 Comm: systemd-udevd Not tainted 4.7.3-200.fc24.x86_64 #1 [ 16.961705] Hardware name: Acer Aspire E5-553G/Wasp_BR, BIOS V1.05 05/12/2016 [ 16.961707] 0000000000000286 00000000ddc132f0 ffff88040a1ef9f8 ffffffffb33d961f [ 16.961710] 0000000000000000 0000000000000000 ffff88040a1efa38 ffffffffb309faab [ 16.961712] 00000118b348b081 ffff8800bd643828 0000000000000000 000000000000012c [ 16.961715] Call Trace: [ 16.961723] [<ffffffffb33d961f>] dump_stack+0x63/0x84 [ 16.961727] [<ffffffffb309faab>] __warn+0xcb/0xf0 [ 16.961730] [<ffffffffb309fbdd>] warn_slowpath_null+0x1d/0x20 [ 16.961733] [<ffffffffc0616091>] i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core] [ 16.961735] [<ffffffffc0616321>] i2c_dw_init+0x111/0x430 [i2c_designware_core] [ 16.961738] [<ffffffffc0617019>] i2c_dw_probe+0x39/0x1d0 [i2c_designware_core] [ 16.961742] [<ffffffffc06914a2>] dw_i2c_plat_probe+0x1e2/0x420 [i2c_designware_platform] [ 16.961746] [<ffffffffb3523e9b>] platform_drv_probe+0x3b/0xa0 [ 16.961749] [<ffffffffb351dcc0>] ? devices_kset_move_last+0x50/0x90 [ 16.961751] [<ffffffffb3521c8c>] driver_probe_device+0x22c/0x440 [ 16.961753] [<ffffffffb3521f71>] __driver_attach+0xd1/0xf0 [ 16.961755] [<ffffffffb3521ea0>] ? driver_probe_device+0x440/0x440 [ 16.961757] [<ffffffffb351f5bc>] bus_for_each_dev+0x6c/0xc0 [ 16.961759] [<ffffffffb352137e>] driver_attach+0x1e/0x20 [ 16.961761] [<ffffffffb3520dc3>] bus_add_driver+0x1c3/0x280 [ 16.961763] [<ffffffffc06a2000>] ? 0xffffffffc06a2000 [ 16.961765] [<ffffffffb35228c0>] driver_register+0x60/0xe0 [ 16.961767] [<ffffffffc06a2000>] ? 0xffffffffc06a2000 [ 16.961769] [<ffffffffb3523e16>] __platform_driver_register+0x36/0x40 [ 16.961772] [<ffffffffc06a2017>] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform] [ 16.961774] [<ffffffffb3002190>] do_one_initcall+0x50/0x180 [ 16.961778] [<ffffffffb321eeb2>] ? kmem_cache_alloc_trace+0x182/0x1d0 [ 16.961781] [<ffffffffb31b342b>] ? do_init_module+0x27/0x1d8 [ 16.961783] [<ffffffffb31b3463>] do_init_module+0x5f/0x1d8 [ 16.961787] [<ffffffffb312a786>] load_module+0x1fe6/0x27e0 [ 16.961789] [<ffffffffb3127650>] ? __symbol_put+0x60/0x60 [ 16.961792] [<ffffffffb312b0ce>] SYSC_init_module+0x14e/0x190 [ 16.961795] [<ffffffffb312b23e>] SyS_init_module+0xe/0x10 [ 16.961797] [<ffffffffb3003d52>] do_syscall_64+0x62/0x110 [ 16.961801] [<ffffffffb37eb921>] entry_SYSCALL64_slow_path+0x25/0x25 [ 16.961803] ---[ end trace ff713d9a76d3aeb3 ]--- [ 16.963504] i2c_hid i2c-ELAN0501:00: Failed to get GPIO interrupt I think this problem causes the touchpad to not work.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.