I'd like to perform a kernel bisect to identify the commit that introduced this regression. We first need to identify the last good kernel and the first bad kernel.
It might be good to first test the latest mainline kernel to see if this bug is already fixed upstream. Can you test v4.14-rc5 to see if it resolves this bug? It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5/ ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Status: New => Triaged ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Zesty) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723785 Title: 'cat /sys/class/power_supply/BAT0/capacity' hangs indefinitely (Dell XPS15, Ubuntu 17.04 w/kernel 4.10.0-37-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723785/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
