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;
MIME-Version: 1.0
References: <CAD2CkAWjS8=kKwEEN4cgVNjyFORUibzEiCUA-X+SMtbo0JoMmA@mail.gmail.com>
 <d8434a1a-b813-958f-69d7-34007faa49b7@deltatee.com> <CAD2CkAV8fWVPdtoxzf5w-q_411Zw_Rwm1QGuz3-Li7eFXehktw@mail.gmail.com>
 <3747d7c3-0cb1-c9b7-8eb8-4d0b167e03fb@deltatee.com>
In-Reply-To: <3747d7c3-0cb1-c9b7-8eb8-4d0b167e03fb@deltatee.com>
From:   Marshall Midden <marshallmidden@gmail.com>
Date:   Wed, 27 Oct 2021 12:44:22 -0500
Message-ID: <CAD2CkAVvgZU_nFYyjhg6ArNjgxfRvzGbVo0WPHf5+NyaVASJzg@mail.gmail.com>
Subject: Re: v5.15-rc7 AMD no kernel dump, spews "scsi_dma_map failed: request
 for 36 bytes!"
To:     Logan Gunthorpe <logang@deltatee.com>
Cc:     joro@8bytes.org, will@kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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


On Wed, Oct 27, 2021 at 12:24 PM Logan Gunthorpe <logang@deltatee.com> wrote:
>
>
>
>
> 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