From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Thorsten Leemhuis
<regressions-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Ard Biesheuvel
<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: 4.9-rc1 boot regression, ambiguous bisect result
Date: Mon, 31 Oct 2016 09:38:29 +0000 [thread overview]
Message-ID: <20161031093829.GA8845@codeblueprint.co.uk> (raw)
In-Reply-To: <CAPcyv4gNyUMU+r-N-qa6ZrF0zG2AuirR0NqVRu40jAgNqc5MNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sun, 30 Oct, at 08:59:58AM, Dan Williams wrote:
> On Sun, Oct 30, 2016 at 5:08 AM, Thorsten Leemhuis
> <regressions-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org> wrote:
> > JFYI: I added this report to the list of regressions for Linux 4.9. I'll
> > watch this thread for further updates on this issue to document progress
> > in my weekly reports. Please let me know via regressions-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org
> > in case the discussion moves to a different place (bugzilla or another
> > mail thread for example). tia!
> >
> > Current status (afaics) in my report: This looks stuck. Or was is
> > discussed (or even fixed) somewhere else?
>
> Thanks, and no, not fixed yet. I've not found the time to run the
> experiments Matt needs, but a colleague has offered to look into it.
Of course, if you are willing to help with debugging, Thorsten, it
would be much appreciated and this bug might get fixed sooner.
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
LKML <linux-kernel@vger.kernel.org>,
linux-efi@vger.kernel.org, Peter Jones <pjones@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: 4.9-rc1 boot regression, ambiguous bisect result
Date: Mon, 31 Oct 2016 09:38:29 +0000 [thread overview]
Message-ID: <20161031093829.GA8845@codeblueprint.co.uk> (raw)
In-Reply-To: <CAPcyv4gNyUMU+r-N-qa6ZrF0zG2AuirR0NqVRu40jAgNqc5MNw@mail.gmail.com>
On Sun, 30 Oct, at 08:59:58AM, Dan Williams wrote:
> On Sun, Oct 30, 2016 at 5:08 AM, Thorsten Leemhuis
> <regressions@leemhuis.info> wrote:
> > JFYI: I added this report to the list of regressions for Linux 4.9. I'll
> > watch this thread for further updates on this issue to document progress
> > in my weekly reports. Please let me know via regressions@leemhuis.info
> > in case the discussion moves to a different place (bugzilla or another
> > mail thread for example). tia!
> >
> > Current status (afaics) in my report: This looks stuck. Or was is
> > discussed (or even fixed) somewhere else?
>
> Thanks, and no, not fixed yet. I've not found the time to run the
> experiments Matt needs, but a colleague has offered to look into it.
Of course, if you are willing to help with debugging, Thorsten, it
would be much appreciated and this bug might get fixed sooner.
next prev parent reply other threads:[~2016-10-31 9:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 4:04 4.9-rc1 boot regression, ambiguous bisect result Dan Williams
2016-10-20 4:04 ` Dan Williams
2016-10-20 6:24 ` Ingo Molnar
2016-10-20 12:29 ` Matt Fleming
[not found] ` <20161020122931.GD19876-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-10-20 15:22 ` Dan Williams
2016-10-20 15:22 ` Dan Williams
[not found] ` <CAPcyv4hT+yQvnQzfb49FP-+vVaVKHTYEj1EjNd9Xvu0Wr8T+Bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-20 19:37 ` Dan Williams
2016-10-20 19:37 ` Dan Williams
2016-10-21 7:00 ` Ingo Molnar
2016-10-21 18:20 ` Dan Williams
[not found] ` <CAPcyv4gE0wtoR3Yxh6axiQpPE2MvDgGW=JLEz9b7OMSBQZ_HDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-21 15:41 ` Matt Fleming
2016-10-21 15:41 ` Matt Fleming
[not found] ` <20161021154129.GH27807-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-10-21 20:20 ` Matt Fleming
2016-10-21 20:20 ` Matt Fleming
[not found] ` <20161021202022.GI27807-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-10-21 23:20 ` Dan Williams
2016-10-21 23:20 ` Dan Williams
[not found] ` <CAPcyv4jkVcBwecxwt1P+p-fMSuen9B9xHEVf0BjM5uJZ4_jAdw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-30 12:08 ` Thorsten Leemhuis
2016-10-30 12:08 ` Thorsten Leemhuis
[not found] ` <4a73a7d8-599c-eb25-0f78-d921a16bb56f-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org>
2016-10-30 15:59 ` Dan Williams
2016-10-30 15:59 ` Dan Williams
[not found] ` <CAPcyv4gNyUMU+r-N-qa6ZrF0zG2AuirR0NqVRu40jAgNqc5MNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-31 9:38 ` Matt Fleming [this message]
2016-10-31 9:38 ` Matt Fleming
2016-11-03 0:41 ` Neri, Ricardo
2016-11-03 5:18 ` Dan Williams
2016-11-03 5:18 ` Dan Williams
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=20161031093829.GA8845@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=regressions-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.