On Sun, Apr 26, 2020 at 12:33:42AM +0200, Stephen Berman wrote: > > I guess I should report this to the kernel bug list? I searched that > list for power-off issues and found only one report after the above > commit, and it seems to be a different issue. It is rather surprising > that my machine seems to be the only one with this problem. > > Steve Berman
I was going to suggest you might try reverting that commit from linus's current tree, and/or from current stable (i.e. save the commit and then try patch -R if in the stable source), but it might not revert cleanly. I suppose that linus's current tree (close to 5.7-rc3) ought to be reasonably good, but YMMV. I guess that pedantically that means testing current (and/or current 5.6 stable) without the revert, to prove the problem is still there, and then reverting to prove the problem is fixed - or else reporting that it doesn't revert cleanly. At a minimum, I guess reverting it from the version you first identified as 'bad' (5.2 ? I've trimmed too much) and proving that the revert solves the problem. iThen maybe just post to the three people who signed off on that commit, with a Cc: to lkml ([email protected]), summarising the problem (and your hardware) and giving the commit you identified, with your detailed bisection results. Good luck! ĸen -- He could send for Ptraci, his favourite handmaiden. She was special. Her singing always cheered him up. Life seemed so much brighter when she stopped. -- Pyramids -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
