Launchpad has imported 16 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=197047.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-09-26T20:58:32+00:00 russianneuromancer wrote: Created attachment 258613 dmesg with Linux 4.13.3 On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci0000:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/0 ------------------------------------------------------------------------ On 2017-09-26T21:02:55+00:00 russianneuromancer wrote: > Sometimes events rate fall from two hundred to one hundred for shorts period > of time Correction: here I talk about events coming especially from INT343A, not total events rate. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/1 ------------------------------------------------------------------------ On 2017-09-26T21:05:08+00:00 russianneuromancer wrote: Sorry, another correction, just to be sure: > Sometimes events rate fall from two hundred to one hundred for shorts period > of time Here I talk about events coming especially from *INT3432*, not total events rate. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/2 ------------------------------------------------------------------------ On 2017-10-03T05:33:13+00:00 kai.heng.feng wrote: Can you do a bisect between 4.9.45 and 4.9.46? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/7 ------------------------------------------------------------------------ On 2017-12-18T03:07:10+00:00 rui.zhang wrote: since there are not too many changes between 4.9.45 and 4.9.46, please do git bisect to find out which commit introduces the problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/8 ------------------------------------------------------------------------ On 2017-12-18T11:59:28+00:00 russianneuromancer wrote: > Can you do a bisect between 4.9.45 and 4.9.46? > since there are not too many changes between 4.9.45 and 4.9.46, please do git > bisect to find out which commit introduces the problem. Thanks for advice! I'll try to do so, as soon as it will be possible. (There is some issues with hardware I usually use for building kernels.) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/9 ------------------------------------------------------------------------ On 2018-01-15T03:44:13+00:00 rui.zhang wrote: any updates? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/10 ------------------------------------------------------------------------ On 2018-01-15T11:35:19+00:00 russianneuromancer wrote: Not yet, as issues mentioned above remain unresolved, so I still can't rebuild kernel. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/11 ------------------------------------------------------------------------ On 2018-02-06T16:41:06+00:00 russianneuromancer wrote: Hardware I usually use for building kernels is operational again, so I hope to do git bisect between 4.9.45 and 4.9.46 in next couple of weeks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/12 ------------------------------------------------------------------------ On 2018-04-02T01:28:48+00:00 rui.zhang wrote: ping ... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/13 ------------------------------------------------------------------------ On 2018-04-03T15:19:16+00:00 russianneuromancer wrote: Hello! Albeit I started it with (unexpected for me) delay and doing it slow (due to age of hardware I using for building kernel) bisect is in progress right now. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/14 ------------------------------------------------------------------------ On 2018-04-10T09:55:49+00:00 russianneuromancer wrote: On every step I done testing three times but unfortunately commit I come to seems like doesn't make any sense for this issue: 5f81b1f51b9cfcbfbe7a1abea09962c91bf485e7 is the first bad commit commit 5f81b1f51b9cfcbfbe7a1abea09962c91bf485e7 Author: Florian Westphal <f...@strlen.de> Date: Fri Jul 7 13:07:17 2017 +0200 netfilter: nat: fix src map lookup commit 97772bcd56efa21d9d8976db6f205574ea602f51 upstream. When doing initial conversion to rhashtable I replaced the bucket walk with a single rhashtable_lookup_fast(). ... I will re-done bisect doing ten tests on every step this time. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/15 ------------------------------------------------------------------------ On 2018-05-07T06:02:13+00:00 rui.zhang wrote: so I suppose we will have some update about the bisect? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/16 ------------------------------------------------------------------------ On 2018-05-07T11:15:31+00:00 russianneuromancer wrote: Yes, with additional tests I find that assumption about Linux 4.9.45 was wrong - 4.9.45 is affected too. Blame commit seems like somewhere between 4.9.0-4.9.8. (Sorry for slow progress on this, hardware for building is old and slow, and every test takes much more time now.) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/17 ------------------------------------------------------------------------ On 2018-05-30T04:41:59+00:00 rui.zhang wrote: any updates? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/18 ------------------------------------------------------------------------ On 2018-06-09T20:22:44+00:00 russianneuromancer wrote: As I proceed with bisect (due to various reasons now I have to build inside virtual machine instead of bare metal hardware, so this slow down building by few times) I have difficulties with determining what build have to be marked as good, and what build have to be marked as bad. For example, with 4.9.44 I seen issue reproduced couple of times, but most of the time it doesn't happen with this release. With 4.9.3 issue seems like doesn't happen at all, but if I boot 4.17.0 and then reboot to 4.9.3 - it's there. With 4.9.8 it's seems like the same, but I can't be 100% sure, as situation could be the similar to 4.9.44, where issue is rare but happen sometimes. But with 4.9.46 issue happen every time. In your opinion, do I need to chase for commit that makes issue reproduced on every boot in 100% of attempts, or it's better to search for commit that makes issue reproduced at least once? Should I care about reboots from affected kernel into unaffected, like in 4.17.0->4.9.3 or it's possible that newer kernel somehow put hardware into failed state which makes issue happen on unaffected kernels too? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719795/comments/19 ** Changed in: linux Status: Unknown => Incomplete ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
