From nobody Wed Jan 10 11:35:44 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T95My0qNkz56kFd for ; Wed, 10 Jan 2024 11:35:58 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T95Mx4gh6z4Pyx for ; Wed, 10 Jan 2024 11:35:57 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1704886550; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9V6JeJKXXSK/uZUc2o4/d0hyH1DWXu2L0KsaO+Ln9ZA=; b=md9PgzqgojIHcj44FGPNzUpeoXWbsEh5iUKJXVzdb1OuRJvwuH8EYGrRHY+Uk1PGVrSudc L09g+4uFdaOEiPHLwGvEV5Q5moMPQpfoef/QDrZcdnTuBIFQr/zJ+IrtKFUrnkBBdcqFHO Wd4oNbjYMnoQrYmPSopyYIg4S5+mYJU= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 84d5690b (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 10 Jan 2024 11:35:50 +0000 (UTC) Date: Wed, 10 Jan 2024 12:35:44 +0100 From: Emmanuel Vadot To: "Bjoern A. Zeeb" Cc: Warner Losh , "freebsd-arm@freebsd.org" Subject: Re: MMCCAM hang Message-Id: <20240110123544.af40b71f72a512c61fddf1f2@bidouilliste.com> In-Reply-To: References: <49DE81A1-7DF5-48BF-A334-961A73B91E53@gmail.com> <20240109114822.522d91fea8cf170af4d895b7@bidouilliste.com> <5299p2p7-4r17-7o65-3569-o4pn3pq8r597@yvfgf.mnoonqbm.arg> <084r150q-076r-9rpn-89p2-87osq1p82orp@yvfgf.mnoonqbm.arg> <4759s3r7-4no5-777q-8r01-4192909p2sp4@yvfgf.mnoonqbm.arg> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4T95Mx4gh6z4Pyx X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] On Wed, 10 Jan 2024 11:17:04 +0000 (UTC) "Bjoern A. Zeeb" wrote: > On Tue, 9 Jan 2024, Warner Losh wrote: >=20 > > That makes sense. The threads you posted showed several blocked on IO w= hile > > sdhci was resetting. That's going to keep any I/O from happening. I gue= ss > > I'm not surprised it's the wrong quirks... Many years ago when I was > > playing with a new, somewhat buggy SDHCI PCIe add-in card having the wr= ong > > quirks would cause super weird behavior. In my case, it was an infinite > > stream of interrupts... > > > > You should be able to disable the FreeBSD device like any other FreeBSD > > device > > > > hint.sdhci.0.disabled=3D1 > > > > we'll probe the device (which for FDT checks the compat settings) and t= hen > > never call attach, but instead print a message saying it is disabled. >=20 > Ah, hadn't thought so far; one too many steps. >=20 > > One can also create an overlay that sets its status to something other = than > > okay, but that's quite a bit trickier and can't be done on the fly from= the > > boot loader. >=20 > fdt rm > fdt mkprop >=20 > can do that to toggle state from okay to disabled. But once it is > disabled at run-time how can you enable it again (that was kind-of my > original question) because fdt disabled the device is not created. You can't :) >=20 > > Warner > > > > On Tue, Jan 9, 2024, 1:57?PM Bjoern A. Zeeb > > wrote: > > > >> On Tue, 9 Jan 2024, Bjoern A. Zeeb wrote: > >> > >> Problem was in sdhci for the specific chipset; wrong quirk/errata > >> information. > >> > >> I'll put a patch up in Phab the next days. > >> > >> -- > >> Bjoern A. Zeeb r15= :7 > >> > > >=20 > --=20 > Bjoern A. Zeeb r15:7 --=20 Emmanuel Vadot