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 for Android: free password hash cracker in your pocket

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

Message-ID: <3747d7c3-0cb1-c9b7-8eb8-4d0b167e03fb@deltatee.com>
Date:   Wed, 27 Oct 2021 11:24:49 -0600
From:   Logan Gunthorpe <logang@...tatee.com>
To:     Marshall Midden <marshallmidden@...il.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!"




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