From: Logan Gunthorpe <logang@deltatee.com>
To: Marshall Midden <marshallmidden@gmail.com>
Cc: joro@8bytes.org, will@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: v5.15-rc7 AMD no kernel dump, spews "scsi_dma_map failed: request for 36 bytes!"
Date: Wed, 27 Oct 2021 11:45:41 -0600 [thread overview]
Message-ID: <31cb0f0d-93d1-d017-ec9f-1405ce97fa30@deltatee.com> (raw)
In-Reply-To: <CAD2CkAVvgZU_nFYyjhg6ArNjgxfRvzGbVo0WPHf5+NyaVASJzg@mail.gmail.com>
On 2021-10-27 11:44 a.m., Marshall Midden wrote:
> Try number 2 with plain text definitely selected.
>
> Forgot to cut and paste -- interruption occurred. The
> "vmcore-dmesg-incomplete.txt" (this file is created before the vmcore
> is taken, and then later in the process, the vmcore-dmesg.txt file is
> created).
>
> AMD machine after taking dump and rebooting:
> /media/parsecdata/crash/127.0.0.1-2021-10-27-12:06:53:
> -rw------- 1 root root 5410206160 Oct 27 12:06 vmcore
> -rw-r--r-- 1 root root 0 Oct 27 12:06 vmcore-dmesg-incomplete.txt
>
> Intel machine:
> /media/parsecdata/crash/127.0.0.1-2021-10-27-12:12:33:
> -rw------- 1 root root 5482529464 Oct 27 12:12 vmcore
> -rw-r--r-- 1 root root 236525 Oct 27 12:12 vmcore-dmesg.txt
>
Ah, so some kind of issue with the testing infrastructure you are using?
Not something we need to be concerned about.
Logan
prev parent reply other threads:[~2021-10-27 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 16:08 Marshall Midden
2021-10-27 16:41 ` Logan Gunthorpe
2021-10-27 17:21 ` Marshall Midden
2021-10-27 17:24 ` Logan Gunthorpe
2021-10-27 17:44 ` Marshall Midden
2021-10-27 17:45 ` Logan Gunthorpe [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=31cb0f0d-93d1-d017-ec9f-1405ce97fa30@deltatee.com \
--to=logang@deltatee.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marshallmidden@gmail.com \
--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
all inboxes | Powered by JetHome®