From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, kvm@vger.kernel.org
Subject: Re: linux-next boots then hangs...
Date: Tue, 7 Jun 2016 17:14:57 +0200 [thread overview]
Message-ID: <cface69a-ce21-3faf-bca9-267ddf05237a@intel.com> (raw)
In-Reply-To: <CAOg9mSRYcD9+P+914WY5_iLUWb4ZwXnQ02avtM3vV5+LiWsrXQ@mail.gmail.com>
On 6/7/2016 5:08 PM, Mike Marshall wrote:
> 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...
I see.
I think I'll need to drop the latest ACPICA changes from linux-next then.
Let me try to do that and please test linux-next again tomorrow.
Thanks,
Rafael
> On Tue, Jun 7, 2016 at 10:55 AM, Rafael J. Wysocki
> <rafael.j.wysocki@intel.com> 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
>>
next prev parent reply other threads:[~2016-06-07 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 20:56 linux-next boots then hangs Mike Marshall
2016-06-06 23:51 ` Paolo Bonzini
2016-06-07 9:38 ` Mike Marshall
2016-06-07 9:50 ` Paolo Bonzini
2016-06-07 14:55 ` Rafael J. Wysocki
2016-06-07 15:08 ` Mike Marshall
2016-06-07 15:14 ` Rafael J. Wysocki [this message]
2016-06-07 18:58 ` Mike Marshall
2016-06-08 16:18 ` Mike Marshall
2016-06-09 23:40 ` Rafael J. Wysocki
2016-06-10 11:49 ` Mike Marshall
2016-06-10 16:46 ` Martin Brandenburg
2016-06-12 1:01 ` Zheng, Lv
2016-06-12 1:40 ` Zheng, Lv
2016-06-13 10:13 ` Mike Marshall
2016-06-13 22:54 ` Zheng, Lv
2016-06-14 8:20 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cface69a-ce21-3faf-bca9-267ddf05237a@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=hubcap@omnibond.com \
--cc=kvm@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox