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:24:49 -0600 [thread overview]
Message-ID: <3747d7c3-0cb1-c9b7-8eb8-4d0b167e03fb@deltatee.com> (raw)
In-Reply-To: <CAD2CkAV8fWVPdtoxzf5w-q_411Zw_Rwm1QGuz3-Li7eFXehktw@mail.gmail.com>
On 2021-10-27 11:21 a.m., Marshall Midden wrote:
> Yes, the spewing of messages stopped. Kernel crash dump taking is now
> occurring. Patch applied to v5.15-rc7.
> Reworded: THANKS! Patch works!
>
> Dunno why the dmesg isn't right, but at least there is a core image!
> [I updated makedumpfs for v5.15-rc4 -- applying a bunch of cifs/smb,
> qlogic, etc. patches and was getting ready for new kernel release in a
> few weeks -- couldn't debug a cifs crash. :) Down the rabbit hole...
> ;) ]
> Intel machine booted, etc. and it has a dmesg correct. *sigh* I don't
> think "I" need to worry about that. Someone else can report it.
What do you mean the dmesg isn't "right"? What are you seeing and what
are you expecting? What is it that someone else will be reporting with
Intel machine having a "correct" dmesg?
Logan
next prev parent reply other threads:[~2021-10-27 17:24 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 [this message]
2021-10-27 17:44 ` Marshall Midden
2021-10-27 17:45 ` Logan Gunthorpe
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=3747d7c3-0cb1-c9b7-8eb8-4d0b167e03fb@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®