Date: Thu, 13 May 2021 15:26:45 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: Henri Hennebert <hlh@restart.be>, Marc Veldman <marc@bumblingdork.com> Cc: freebsd-current@freebsd.org Subject: Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way! Message-ID: <f64d7043-f12e-c43a-9f59-666d3a46589b@FreeBSD.org> In-Reply-To: <4f396c9f-2e35-fa02-f313-a6a664836673@restart.be> References: <a7363387-c53f-d6c0-acc0-be9081590ea1@FreeBSD.org> <740cd7a0-3faf-7a56-80f7-dbb9bdacb55b@FreeBSD.org> <37122994-8172-b943-2602-fd1b4e9af78a@FreeBSD.org> <CALH631k8ek0UEB8LUv04YQg%2BzZUafUO2W4hcHBXqrTWDdDp7mg@mail.gmail.com> <20210512122747.51d2f574@laptop.domain> <1e23c1de-7529-0be9-c4ec-83d17b2b6bac@restart.be> <e49c4a5e-d567-522b-c60c-59faa054c807@FreeBSD.org> <20210512133456.57f374f4@ernst.home> <b72d8b9d-8cfd-84a7-59b2-c5a2b33416e7@FreeBSD.org> <20210512141130.755ae361@ernst.home> <D9843F30-308D-4F9F-A229-05639346564A@bumblingdork.com> <9f0abf48-ed13-bff3-5687-fca0d57195d8@restart.be> <C4E25C70-25BA-4BEB-83F0-D77279B2B94A@bumblingdork.com> <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>
index | next in thread | previous in thread | raw e-mail
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 Serebryakovhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f64d7043-f12e-c43a-9f59-666d3a46589b>