From owner-freebsd-current@freebsd.org Thu May 13 12:40:36 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 B651063F04B for ; Thu, 13 May 2021 12:40:36 +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 4Fgrq84hYHz4rDQ; Thu, 13 May 2021 12:40:36 +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 7A2D8961A; Thu, 13 May 2021 12:40:36 +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 A58D64878; Thu, 13 May 2021 15:40:34 +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: Henri Hennebert , Marc Veldman Cc: 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> <20210512141130.755ae361@ernst.home> <9f0abf48-ed13-bff3-5687-fca0d57195d8@restart.be> <8d4e076b-9ecd-aef2-0ee8-73519bb9d939@FreeBSD.org> <8d2be5f2-4144-082e-4237-0dac0c4b37e6@restart.be> <6798878a-c499-d78d-e96d-d744513cb80d@restart.be> From: Lev Serebryakov Organization: FreeBSD Message-ID: Date: Thu, 13 May 2021 15:40:34 +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: <6798878a-c499-d78d-e96d-d744513cb80d@restart.be> 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: Thu, 13 May 2021 12:40:36 -0000 On 13.05.2021 15:13, Henri Hennebert via freebsd-current wrote: >>>>> I’m not sure if this is an interesting data point or not, >>>>> but a warm boot without the card inserted succeeds after >>>>> a cold boot with the card inserted. >>>> >>>>   It could explain, why my tests with "same code path" gave different results! >>>> >>> With a "cold" boot and without a card inserted did you see something like: >>> >>> rtsx0: <2.0c Realtek ... >>> rtsx0: Card present >>> mmc0: on rtsx0 >>> rtsx0: Interrupt card inserted/removed >>> rtsx0: Card absent >>   When it panics, it panics before rtsx0 prints something in my case. >> > Does iwm0 / mmc0 is shown during boot? > > can you try a verbose boot (boot -s) do you mean "boot -v"? :) It runs very fast, and there are not so much lines on the screen (is it possible to change screen reoslution before loading i915kms?) Ok, now I've recorded cold boot without SD, without verbose, with my phone (yes, screenshots by photocamera, I fell so low!) and I was wrong, there is rtsx0: rtsx0: <2.0c .....> rtsx0: Card present mmc0: on rtsx0 rtsx0: Interrupt card inserted/removed rtsx0: Card absent ... PANIC! (without rtsx0 in stacktrace, again it is run_interrupt_driven_config_hooks()). > if you can't see the verbose output which is too fast on the display: > try a boot -p Oooops, keyboard is unresponsive after first pause and I can not unpause output :-( Looks like another bug of early boot — EFI boot can not access keywboard before it is detected as `atkbd` (keyboard in loader works!) -- // Lev Serebryakov