linux-kernel - Re: v5.15-rc7 AMD no kernel dump, spews "scsi_dma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 27 Oct 2021 12:44:22 -0500
From:   Marshall Midden <marshallmidden@...il.com>
To:     Logan Gunthorpe <logang@...tatee.com>
Cc:     joro@...tes.org, will@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: v5.15-rc7 AMD no kernel dump, spews "scsi_dma_map failed: request
 for 36 bytes!"

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@...tatee.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