linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Catalin Marinas <catalin.marinas@arm.com>, cki-project@redhat.com
Cc: will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for for-kernelci (6.10.0-rc5, arm-next, 59ed70ca)
Date: Sat, 29 Jun 2024 10:36:26 +0200	[thread overview]
Message-ID: <87jzi8xi0l.ffs@tglx> (raw)
In-Reply-To: <Zn810pr-Zaa4PHa9@arm.com>

On Fri, Jun 28 2024 at 23:14, Catalin Marinas wrote:
> On Fri, Jun 28, 2024 at 09:53:01PM -0000, cki-project@redhat.com wrote:
>> Hi, we tested your kernel and here are the results:
>> 
>>     Overall result: FAILED
>>              Merge: OK
>>            Compile: OK
>>               Test: FAILED (Did not boot)
>> 
>> 
>> Kernel information:
>>     Commit message: Merge remote-tracking branch 'tglx/devmsi-arm' into for-kernelci
>> 
>> You can find all the details about the test run at
>>     https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1353028391
>> 
>> One or more kernel builds failed:
>>     Builds that are failing to boot:
>>          aarch64 - https://datawarehouse.cki-project.org/kcidb/builds/redhat:1353028391-aarch64-kernel
>
> I did not check the logs and I probably won't have time until Monday but
> it might be related to the tlgx/devmsi-arm branch (I'm seeing boot
> failures under KVM on TX2). Cc'ing Thomas as well.

Yes it is. Looks like PCI interrupts are not delivered


      reply	other threads:[~2024-06-29  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 21:53 ❌ FAIL: Test report for for-kernelci (6.10.0-rc5, arm-next, 59ed70ca) cki-project
2024-06-28 22:14 ` Catalin Marinas
2024-06-29  8:36   ` Thomas Gleixner [this message]

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=87jzi8xi0l.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).