All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: hch@lst.de
Cc: Tianyu.Lan@microsoft.com, iommu@lists.linux.dev,
	linux-doc@vger.kernel.org, lkp@intel.com, lkp@lists.01.org,
	ltykernel@gmail.com, oliver.sang@intel.com
Subject: Re: [EXTERNAL] [swiotlb] 44d89f2248: Kernel_panic-not_syncing:swiotlb_init_remap:nslabs=#too_small
Date: Wed, 13 Jul 2022 17:11:34 +0100	[thread overview]
Message-ID: <20220713161133.1707380-1-conor@kernel.org> (raw)
In-Reply-To: <20220713060246.GA13497@lst.de>

FWIW, I hit this on a PolarFire SoC.
Was relieved to see that it was not another wacky edge case like my
last run-in with swiotlb issues! If you could CC me on the fix that'd
be great.

Thanks,
Conor.

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: lkp@lists.01.org
Subject: Re: [EXTERNAL] [swiotlb] 44d89f2248: Kernel_panic-not_syncing:swiotlb_init_remap:nslabs=#too_small
Date: Wed, 13 Jul 2022 17:11:34 +0100	[thread overview]
Message-ID: <20220713161133.1707380-1-conor@kernel.org> (raw)
In-Reply-To: <20220713060246.GA13497@lst.de>

[-- Attachment #1: Type: text/plain, Size: 206 bytes --]

FWIW, I hit this on a PolarFire SoC.
Was relieved to see that it was not another wacky edge case like my
last run-in with swiotlb issues! If you could CC me on the fix that'd
be great.

Thanks,
Conor.

  reply	other threads:[~2022-07-13 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13  3:08 [swiotlb] 44d89f2248: Kernel_panic-not_syncing:swiotlb_init_remap:nslabs=#too_small kernel test robot
2022-07-13  3:08 ` kernel test robot
2022-07-13  5:58 ` [EXTERNAL] " Tianyu Lan
2022-07-13  5:58   ` Tianyu Lan
2022-07-13  6:02   ` Christoph Hellwig
2022-07-13  6:02     ` Christoph Hellwig
2022-07-13 16:11     ` Conor Dooley [this message]
2022-07-13 16:11       ` Conor Dooley

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=20220713161133.1707380-1-conor@kernel.org \
    --to=conor@kernel.org \
    --cc=Tianyu.Lan@microsoft.com \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=ltykernel@gmail.com \
    --cc=oliver.sang@intel.com \
    /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.