| Summary: | sys-kernel/gentoo-sources: I2C pointing device fails after resume | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Victor Bessonov <unb0rnster> |
| Component: | Current packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | tb |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugzilla.redhat.com/show_bug.cgi?id=1431375 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info output
dmesg output Kernel config Kernel config 4.11.3 |
||
please attach the .config and the all the dmesg Created attachment 474710 [details]
dmesg output
Created attachment 474712 [details]
Kernel config
Created attachment 474714 [details]
Kernel config 4.11.3
Done. The only problem-my kernel is semi-mute. Tried running 4.11.3, result is the same. Reverted to 4.10.17 could you try git bisecting the problem ? https://wiki.gentoo.org/wiki/Kernel_git-bisect (In reply to Victor Bessonov from comment #5) > Done. The only problem-my kernel is semi-mute. what means by semi-mute ? is not showing debug informations? > Tried running 4.11.3, result is the same. Reverted to 4.10.17 please bisect the kernel if you can Sorry, had no time to do bisecting. Found this bug in Red Hat Bugzilla. They seem to have some progress. https://bugzilla.redhat.com/show_bug.cgi?id=1431375 would be nice to know if is solved in most recent kernel. looks like they fixed with patch https://patchwork.kernel.org/patch/9858267/ but i cannot reproduce it as now 4.13 and 4.12 as been dropped |
Created attachment 472762 [details] emerge --info output After updating to 4.11 gentoo-sources a new error appeared. After waking up the laptop, Synaptics I2C pointing device stops working, journalctl gives an error: kernel: dpm_run_callback(): i2c_hid_resume+0x0/0xd0 returns -11 kernel: PM: Device i2c-SYNA2B22:00 failed to resume async: error -11 Reverting to 4.10.16 resolves this.