Description of problem: Touchscreen not working (Lenovo 510-14AST) dmesg reveals error probing i2c bus. Version-Release number of selected component (if applicable): Fedora (4.8.15-300.fc25.x86_64) 25 (Workstation Edition) How reproducible: Every boot Actual results: No touchscreen. No sign of touchscreen device in lsusb, lshw, lspci, cat /proc/bus/input/devices, cat /dev/input/event[0-10] (while touching screen). Expected results: Additional info: 13.926885] ------------[ cut here ]------------ [ 13.926891] WARNING: CPU: 1 PID: 624 at drivers/i2c/busses/i2c-designware-cor e.c:280 i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core] [ 13.926892] Modules linked in: i2c_designware_platform(+) rfkill wmi i2c_desi gnware_core soundcore video tpm_crb shpchp acpi_cpufreq tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc amdkfd amd_iommu_v2 amdgpu rtsx_pci _sdmmc mmc_core i2c_algo_bit drm_kms_helper crc32c_intel ttm 8021q garp serio_ra w stp llc mrp drm rtsx_pci r8169 fjes i2c_hid mii [ 13.926910] CPU: 1 PID: 624 Comm: systemd-udevd Not tainted 4.8.15-300.fc25.x 86_64 #1 [ 13.926911] Hardware name: LENOVO 80S9/Lenovo YOGA 510-14AST, BIOS 1RCN26WW(V 1.06) 09/10/2016 [ 13.926912] 0000000000000286 00000000f2198a1b ffff9cba72bd7a08 ffffffffa63e5e1d [ 13.926915] 0000000000000000 0000000000000000 ffff9cba72bd7a48 ffffffffa60a0e8b [ 13.926916] 00000118a6499c8a ffff9cba6fc8d028 0000000000000000 000000000000012c [ 13.926918] Call Trace: [ 13.926924] [<ffffffffa63e5e1d>] dump_stack+0x63/0x86 [ 13.926927] [<ffffffffa60a0e8b>] __warn+0xcb/0xf0 [ 13.926929] [<ffffffffa60a0fbd>] warn_slowpath_null+0x1d/0x20 [ 13.926931] [<ffffffffc0696091>] i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core] [ 13.926932] [<ffffffffc0696321>] i2c_dw_init+0x111/0x470 [i2c_designware_core] [ 13.926934] [<ffffffffc0697049>] i2c_dw_probe+0x39/0x1d0 [i2c_designware_core] [ 13.926936] [<ffffffffc06a84a2>] dw_i2c_plat_probe+0x1e2/0x420 [i2c_designware_platform] [ 13.926939] [<ffffffffa6530adb>] platform_drv_probe+0x3b/0xa0 [ 13.926941] [<ffffffffa652a9bc>] ? devices_kset_move_last+0x4c/0x90 [ 13.926943] [<ffffffffa652e903>] driver_probe_device+0x223/0x430 [ 13.926945] [<ffffffffa652ebef>] __driver_attach+0xdf/0xf0 [ 13.926946] [<ffffffffa652eb10>] ? driver_probe_device+0x430/0x430 [ 13.926947] [<ffffffffa652c28c>] bus_for_each_dev+0x6c/0xc0 [ 13.926949] [<ffffffffa652e00e>] driver_attach+0x1e/0x20 [ 13.926950] [<ffffffffa652da20>] bus_add_driver+0x170/0x270 [ 13.926951] [<ffffffffc06b3000>] ? 0xffffffffc06b3000 [ 13.926952] [<ffffffffa652f510>] driver_register+0x60/0xe0 [ 13.926953] [<ffffffffc06b3000>] ? 0xffffffffc06b3000 [ 13.926954] [<ffffffffa6530a56>] __platform_driver_register+0x36/0x40 [ 13.926956] [<ffffffffc06b3017>] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform] [ 13.926958] [<ffffffffa6002190>] do_one_initcall+0x50/0x180 [ 13.926960] [<ffffffffa6205fa1>] ? __vunmap+0x81/0xd0 [ 13.926962] [<ffffffffa62263e9>] ? kmem_cache_alloc_trace+0x159/0x1b0 [ 13.926963] [<ffffffffa61b6966>] ? do_init_module+0x27/0x1ef [ 13.926964] [<ffffffffa61b699e>] do_init_module+0x5f/0x1ef [ 13.926966] [<ffffffffa612cde0>] load_module+0x2170/0x29d0 [ 13.926967] [<ffffffffa6129b00>] ? __symbol_put+0x60/0x60 [ 13.926969] [<ffffffffa612d7b3>] SYSC_init_module+0x173/0x190 [ 13.926971] [<ffffffffa612d8ee>] SyS_init_module+0xe/0x10 [ 13.926972] [<ffffffffa6003c57>] do_syscall_64+0x67/0x160 [ 13.926975] [<ffffffffa6803c21>] entry_SYSCALL64_slow_path+0x25/0x25 [ 13.926983] ---[ end trace a79f8ef34c11d600 ]--- Possibly related to / same as Bug 1375756
*********** 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 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. 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.
After applying the updates, /etc/fedora-release tells me I am still on 25, but the kernel version is now 4.9.4-201. I am still seeing the same message in startup (slightly different line numbers): [ 14.708249] ------------[ cut here ]------------ [ 14.708257] WARNING: CPU: 1 PID: 625 at drivers/i2c/busses/i2c-designware-core.c:293 i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core] [ 14.708259] Modules linked in: i2c_designware_platform(+) shpchp i2c_designware_core tpm_crb snd soundcore video acpi_cpufreq tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc amdkfd amd_iommu_v2 amdgpu rtsx_pci_sdmmc mmc_core crc32c_intel serio_raw 8021q garp i2c_algo_bit stp llc drm_kms_helper mrp ttm drm r8169 fjes i2c_hid mii rtsx_pci i2c_dev [ 14.708282] CPU: 1 PID: 625 Comm: systemd-udevd Not tainted 4.9.4-201.fc25.x86_64 #1 [ 14.708283] Hardware name: LENOVO 80S9/Lenovo YOGA 510-14AST, BIOS 1RCN26WW(V1.06) 09/10/2016 [ 14.708285] ffffb8e0013bba10 ffffffff893f3ddd 0000000000000000 0000000000000 000 [ 14.708287] ffffb8e0013bba50 ffffffff890a202b 00000125013bba70 ffff956eb0cb1828 [ 14.708289] 0000000000000000 0000000000000000 000000000000012c 0000000000ffffad [ 14.708291] Call Trace: [ 14.708297] [<ffffffff893f3ddd>] dump_stack+0x63/0x86 [ 14.708299] [<ffffffff890a202b>] __warn+0xcb/0xf0 [ 14.708301] [<ffffffff890a215d>] warn_slowpath_null+0x1d/0x20 [ 14.708303] [<ffffffffc06450e1>] i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core] [ 14.708305] [<ffffffffc0645ec9>] i2c_dw_init+0x2f9/0x610 [i2c_designware_core] [ 14.708307] [<ffffffffc06466f9>] i2c_dw_probe+0x39/0x940 [i2c_designware_core] ... If it helps: the touchscreen works with the default driver and no startup errors relating to i2c when I boot up in Ubuntu 14.04.5 (kernel version around 3.15) but in Ubuntu 161.0 (4.8 kernel) I get i2c errors and no touchscreen.
*********** 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 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. 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.