From: Christoph Hellwig <hch@lst.de>
To: Conor.Dooley@microchip.com
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org, hch@lst.de,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: linux-next: Tree for May 3
Date: Mon, 9 May 2022 16:11:22 +0200 [thread overview]
Message-ID: <20220509141122.GA14555@lst.de> (raw)
In-Reply-To: <9a424be9-380f-f99c-4126-25a00eba0271@microchip.com>
On Mon, May 09, 2022 at 01:33:07PM +0000, Conor.Dooley@microchip.com wrote:
> @Christoph, I know /nothing/ about swiotlb, so if you have any
> suggestions for debugging that you would like me to try, let me
> know please.
Hi Conor,
sorry for dropping this on the flor. I was at LSF/MM least week and
my plan to go through my backlog today didn't go to plan as I unepectedly
spent half the day at doctors appointments.
The commit looks like a somewhat unusual culprit for a boot failure,
so any chance you could do another manual verifiation pass where
you checkout 6424e31b1c05 and then the commit before it (i.e. as
git checkout 6424e31b1c05^) to make sure it really is this commits?
Some of the commits around it just seems like more likely culprits to
me, so I'd like to really be 100% sure here. In the meantime I'll
look through the patch. Also you don't happen to have earlycon support
on this plaform to see if there are any interesting messages on the
serial console?
next prev parent reply other threads:[~2022-05-09 14:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 7:29 linux-next: Tree for May 3 Stephen Rothwell
2022-05-04 8:32 ` Conor.Dooley
2022-05-09 13:33 ` Conor.Dooley
2022-05-09 14:11 ` Christoph Hellwig [this message]
2022-05-09 14:39 ` Conor.Dooley
2022-05-10 11:20 ` Conor.Dooley
2022-05-11 6:22 ` Christoph Hellwig
2022-05-11 6:44 ` Conor.Dooley
2022-05-11 6:48 ` Christoph Hellwig
2022-05-11 10:10 ` Conor.Dooley
2022-05-11 12:37 ` Christoph Hellwig
2022-05-11 14:08 ` Mike Rapoport
2022-05-11 14:10 ` Christoph Hellwig
2022-05-11 14:37 ` Mike Rapoport
2022-05-11 14:40 ` Christoph Hellwig
2022-05-13 7:55 ` Conor.Dooley
2022-05-14 12:18 ` Geert Uytterhoeven
2022-05-16 9:47 ` Conor.Dooley
-- strict thread matches above, loose matches on Subject: below --
2024-05-03 7:17 Stephen Rothwell
2021-05-03 2:59 Stephen Rothwell
2019-05-03 10:00 Stephen Rothwell
2018-05-03 5:13 Stephen Rothwell
2017-05-03 5:54 Stephen Rothwell
2016-05-03 9:37 Stephen Rothwell
2013-05-03 4:10 Stephen Rothwell
2012-05-03 6:38 Stephen Rothwell
2011-05-03 5:47 Stephen Rothwell
2010-05-03 5:16 Stephen Rothwell
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=20220509141122.GA14555@lst.de \
--to=hch@lst.de \
--cc=Conor.Dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).