From owner-freebsd-current@freebsd.org Fri May 7 13:59:39 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3A28762EC35 for ; Fri, 7 May 2021 13:59:39 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4FcBs715nbz4dfT for ; Fri, 7 May 2021 13:59:39 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 2400062EC34; Fri, 7 May 2021 13:59:39 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 23CAC62EB3E for ; Fri, 7 May 2021 13:59:39 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FcBs70XrSz4dTG; Fri, 7 May 2021 13:59:39 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: lev/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id DEF8A5C74; Fri, 7 May 2021 13:59:38 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.134.16] (unknown [94.19.224.8]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 253163D7F; Fri, 7 May 2021 16:59:36 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way! To: gljennjohn@gmail.com Cc: current@freebsd.org, jsm@FreeBSD.org, hlh@restart.be References: <740cd7a0-3faf-7a56-80f7-dbb9bdacb55b@FreeBSD.org> <37122994-8172-b943-2602-fd1b4e9af78a@FreeBSD.org> <20210507132215.2469c296@ernst.home> From: Lev Serebryakov Organization: FreeBSD Message-ID: <755d0029-bea6-3a43-c0c2-184349d88054@FreeBSD.org> Date: Fri, 7 May 2021 16:59:35 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <20210507132215.2469c296@ernst.home> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 May 2021 13:59:39 -0000 On 07.05.2021 16:22, Gary Jennejohn wrote: >>>> Looks like there is problem with rtsx driver! >>> Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem! >>> >>> And console on these crashes is totally dead, and disks are not >>> detected yet, so I can not look at structures in memory and/or >>> dump core. >> >> 13.0-RELEASE installation media crashes in same way if SD reader is >> enabled in BIOS. >> > > I see that rtsx was added to GENERIC. Might have been premature. > > The only thing I can recommend is to install with the SD card reader > disabled in the BIOS. Yep, it works. Not only install, but booting of installed system too — any GENERIC kernel panics, even new, built by hands from latest sources. > It may be the case that rtsx still works even if the card reader is > disabled in the BIOS. That's the first thing I would try out. Nope, it doesn't work (and I don't need it on this Laptop, to be honest). If SD reader is disabled in BIOS, it isn't detected at all. > If that fails then generate a kernel with rtsx as a module rather than > it being hard coded into the kernel. > > You could then re-enable the SD card reader in the BIOS and load the > module to check whether the SD card reader works or causes a panic > when the moduke is loaded. This approach might make it possible to > get a crash dump if a problem occurs. Ok, I'll try this, good idea. BTW, I've got hints that it it rtsx-related only after ~40 crashes, as most of stack traces don't have rtsx in them and are very generic. Looks like rtsx mangle kernel memory and it crashes in other places/kernel threads. -- // Lev Serebryakov