From owner-freebsd-current@freebsd.org Wed May 12 13:45:02 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 69E7263F02D for ; Wed, 12 May 2021 13:45:02 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 4FgGHy2XnSz4ctH; Wed, 12 May 2021 13:45:02 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) (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 301882D8D6; Wed, 12 May 2021 13:45:02 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [IPv6:2001:470:923f:1:a9a4:7e74:328f:b59] (unknown [IPv6:2001:470:923f:1:a9a4:7e74:328f:b59]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 0FB3A4668; Wed, 12 May 2021 16:44:59 +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: Henri Hennebert , freebsd-current@freebsd.org References: <740cd7a0-3faf-7a56-80f7-dbb9bdacb55b@FreeBSD.org> <37122994-8172-b943-2602-fd1b4e9af78a@FreeBSD.org> <20210512122747.51d2f574@laptop.domain> <1e23c1de-7529-0be9-c4ec-83d17b2b6bac@restart.be> <20210512133456.57f374f4@ernst.home> From: Lev Serebryakov Organization: FreeBSD Message-ID: Date: Wed, 12 May 2021 16:44:59 +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: <20210512133456.57f374f4@ernst.home> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Wed, 12 May 2021 13:45:02 -0000 On 12.05.2021 16:34, Gary Jennejohn wrote: > Is sysctl debug.debugger_on_panic set to 1? You should automatically > land in ddb if that is set. I suppose it is, since you posted some > back trace in an earlier mail. It also seems to be the default, at > least in my FreeBSD-14 kernel. I see ddb report about panic, but it's all. Keyboard doesn't work, and panic occurs before any disks are detected, so there is no space for crash dump. > AFAIK ddb has a command to generate a crash dump. But I can't easily > check that :( Yep, but console is dead & there are no disks for crash dump at this stage. > It seems like there's a major bug when no SD card is inserted and the > driver is in the kernel. And a timing problem when a card is in the > slot at boot time. > > Good to know that the module still works. Yep, smoke tests for module (without inversion!) pass: I could mount R/W SD card with release image, mount FS, read and write files, unmount FS and eject card without panics and errors. I didn't try any high-load tests, though. > > Difficult to debug without your laptop model in the hands of a developer. It is "pretty common" (but old) Lenovo ThinkPad T540p. I could provide remote access to it, but it will not help for such low-level and early panic :-( -- // Lev Serebryakov