From owner-freebsd-current@freebsd.org Thu May 13 12:26:47 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 48B1663E62F for ; Thu, 13 May 2021 12:26:47 +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 4FgrWC1TP8z4qR3; Thu, 13 May 2021 12:26:47 +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 0A3A98E3E; Thu, 13 May 2021 12:26:47 +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 7A9A54870; Thu, 13 May 2021 15:26:45 +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> <664e1728-8c8c-0967-81a9-f7b6e047ddb7@restart.be> <2C68D31D-B24E-44B3-AF80-D215C1D1A56E@bumblingdork.com> <261e5e3b-6522-2bca-a689-16e5abcd8f8e@restart.be> <33D1DC7E-ECFA-4BA1-B0DE-FD7ADA2AB127@bumblingdork.com> <4f396c9f-2e35-fa02-f313-a6a664836673@restart.be> From: Lev Serebryakov Organization: FreeBSD Message-ID: Date: Thu, 13 May 2021 15:26:45 +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: <4f396c9f-2e35-fa02-f313-a6a664836673@restart.be> 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: Thu, 13 May 2021 12:26:47 -0000 On 13.05.2021 15:06, Henri Hennebert via freebsd-current wrote: > Just what I was thinking: in this case the card status is found correctly without an interrupt. > > In the "cold" case an interrupt change the card present/absent status, a taskqueue is scheduled. I am digging there... It could explain, why in my case it crashes in different threads. And sometimes in strlen() in stacktrace which contains rtsx functions! -- // Lev Serebryakov