Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
To:     Marshall Midden <marshallmidden@gmail.com>
Cc:     joro@8bytes.org, will@kernel.org, linux-kernel@vger.kernel.org
References: <CAD2CkAWjS8=kKwEEN4cgVNjyFORUibzEiCUA-X+SMtbo0JoMmA@mail.gmail.com>
 <d8434a1a-b813-958f-69d7-34007faa49b7@deltatee.com>
 <CAD2CkAV8fWVPdtoxzf5w-q_411Zw_Rwm1QGuz3-Li7eFXehktw@mail.gmail.com>
From:   Logan Gunthorpe <logang@deltatee.com>
Message-ID: <3747d7c3-0cb1-c9b7-8eb8-4d0b167e03fb@deltatee.com>
Date:   Wed, 27 Oct 2021 11:24:49 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <CAD2CkAV8fWVPdtoxzf5w-q_411Zw_Rwm1QGuz3-Li7eFXehktw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-CA
Content-Transfer-Encoding: 7bit
Subject: Re: v5.15-rc7 AMD no kernel dump, spews "scsi_dma_map failed: request
 for 36 bytes!"
Precedence: bulk


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