KernelCI discussions
 help / color / mirror / Atom feed
From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: Hans de Goede <hdegoede@redhat.com>, Mark Brown <broonie@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-pci@vger.kernel.org,
	"kernelci@groups.io" <kernelci@groups.io>,
	"kernelci-results@groups.io" <kernelci-results@groups.io>
Subject: Re: next/master bisection: baseline.login on asus-C523NA-A20057-coral
Date: Mon, 4 Apr 2022 20:44:41 +0100	[thread overview]
Message-ID: <28ee7ff8-5b21-9154-74e9-efd59da4a498@collabora.com> (raw)
In-Reply-To: <28699579-8384-ff3b-5662-fb56d8ced766@collabora.com>

+kernelci

On 29/03/2022 19:44, Guillaume Tucker wrote:
> On 28/03/2022 13:54, Hans de Goede wrote:
>> Hi,
>>
>> On 3/24/22 23:19, Mark Brown wrote:
>>> On Thu, Mar 24, 2022 at 09:34:30PM +0100, Hans de Goede wrote:
>>>
>>>> Mark, if one of use writes a test patch, can you get that Asus machine to boot a
>>>> kernel build from next + the test patch ?
>>>
>>> I can't directly unfortunately as the board is in Collabora's lab but
>>> Guillaume (who's already CCed) ought to be able to, and I can generally
>>> prod and try to get that done.
>>
>> Ok, Guillaume, can you try a kernel with commit 5949965ec9340cfc0e65f7d8a576b660b26e2535
>> ("x86/PCI: Preserve host bridge windows completely covered by E820") + the 
>> attached patch added on top a try on the asus-C523NA-A20057-coral machine please
>> and see if that makes it boot again ?
> 
> Sorry I've been busy with a conference.  Sure, will put that
> through KernelCI tomorrow and let you know the outcome.

Well the issue seems to have been fixed on mainline, unless it's
intermittent.  In any case, next-20220404 is booting fine:

  https://linux.kernelci.org/test/plan/id/624aed811a5acd09adae071e/

Last time it was seen to fail was next-20220330:

  https://linux.kernelci.org/test/plan/id/62442f68e30d6f89a4ae06b7/


Ironically, the KernelCI staging linux-next job with the patches
mentioned in your previous email applied is now failing:

  https://staging.kernelci.org/test/plan/id/624b2d3b923f532dc305f4c7/

The kernel branch being used is:

  https://github.com/kernelci/linux/commits/staging-next


I haven't checked the logs or investigated any further, this is
just a quick summary based on the boot test results.

Please let us know if we should drop these patches or try
anything else.  I'll be on holiday for the rest of the week but
others can pick things up if needed.

Thanks,
Guillaume

       reply	other threads:[~2022-04-04 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <623c13ec.1c69fb81.8cbdb.5a7a@mx.google.com>
     [not found] ` <Yjyv03JsetIsTJxN@sirena.org.uk>
     [not found]   ` <4e9fca2f-0af1-3684-6c97-4c35befd5019@redhat.com>
     [not found]     ` <Yjzua8Wye/3DHBKx@sirena.org.uk>
     [not found]       ` <f8e96f8a-c19c-6acd-2f54-688924f491e8@redhat.com>
     [not found]         ` <28699579-8384-ff3b-5662-fb56d8ced766@collabora.com>
2022-04-04 19:44           ` Guillaume Tucker [this message]
2022-04-05  8:13             ` next/master bisection: baseline.login on asus-C523NA-A20057-coral Hans de Goede
2022-04-05 17:57             ` Bjorn Helgaas
     [not found]           ` <16E2C910B4947F17.5433@groups.io>
2022-04-04 19:48             ` Guillaume Tucker
     [not found] <20220405235315.GA101393@bhelgaas>
     [not found] ` <20220406185931.GA165754@bhelgaas>
     [not found]   ` <Yk3r9uhIHmNumtxi@sirena.org.uk>
2022-04-06 20:11     ` Guillaume Tucker
2022-04-07 15:17       ` Denys Fedoryshchenko

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=28ee7ff8-5b21-9154-74e9-efd59da4a498@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=kernelci-results@groups.io \
    --cc=kernelci@groups.io \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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