I'm one of the original reporters and testers of that problem/fix... my current problem started after that... I've tested next-20160607 and 4.7.0-rc2-00004-g3613a62 (Linus' tree of the moment) so far today... Linus' tree is still OK (because it has 7f9bef9) and linux-next is still busted (for me). I'll keep on bisecting using the suggestions that Paolo sent... -Mike On Tue, Jun 7, 2016 at 10:55 AM, Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> wrote: > On 6/6/2016 10:56 PM, Mike Marshall wrote: >> >> Greetings... >> >> Please keep my email in the loop on this, I'm only subscribed >> to fs-devel... >> >> Linux-next fails to boot properly for me, but Linux 4.7-rc2 from >> Linus' tree boots fine. >> >> I got started bisecting next-20160603 last Friday, but didn't get done. >> >> git bisect start '64289ca' '7f9bef9' >> >> I picked 7f9bef9 as the good commit to start with because I knew >> I needed 7f9bef9 or else my QEMU-KVM would crash. Before I started >> the bisection, I verified that 7f9bef9 was indeed good by checking >> out a branch from next-20160603 with 7f9bef9 as the HEAD and >> building it: git checkout -b gas 7f9bef9 >> >> Today I got next-20160606 and checked to see if the same failure >> occurred - it did. So I continued with the bisection of next-20160603. >> >> I arrived at 407aa3ff6f54ea2be7959639d664ae5183e2e9f8 as the bad commit. >> >> >> 407aa3f is a rather complex commit... there is a problem with it, >> but I'm not sure what to do next... both 7f9bef9 and 407aa3f are >> related to ACPICA... > > > It looks like this commit > > https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/commit/?h=acpica-fixes&id=7f9bef9debafcb767d00efb177d0f2edd4940eab > > should fix the problem for you. > > Thanks, > Rafael > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
