From nobody Wed Jan 10 11:17:04 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 4T94yN4tT3z56hT2 for ; Wed, 10 Jan 2024 11:17:16 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T94yN1nCqz4NN6 for ; Wed, 10 Jan 2024 11:17:15 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; none Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 7B4C18D4A228; Wed, 10 Jan 2024 11:17:07 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id B94DC2D029D8; Wed, 10 Jan 2024 11:17:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id 9QvzIpB05luo; Wed, 10 Jan 2024 11:17:05 +0000 (UTC) Received: from strong-aiccu0.sbone.de (strong-aiccu0.sbone.de [IPv6:fde9:577b:c1a9:f491::2]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 923C12D029D7; Wed, 10 Jan 2024 11:17:05 +0000 (UTC) Date: Wed, 10 Jan 2024 11:17:04 +0000 (UTC) From: "Bjoern A. Zeeb" To: Warner Losh cc: "freebsd-arm@freebsd.org" Subject: Re: MMCCAM hang In-Reply-To: Message-ID: 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-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 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: multipart/mixed; boundary="1098556516-66325157-1704885425=:2837" X-Rspamd-Queue-Id: 4T94yN1nCqz4NN6 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:24940, ipnet:2a01:4f8::/32, country:DE] This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1098556516-66325157-1704885425=:2837 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 9 Jan 2024, Warner Losh wrote: > That makes sense. The threads you posted showed several blocked on IO while > sdhci was resetting. That's going to keep any I/O from happening. I guess > 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 wrong > 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=1 > > we'll probe the device (which for FDT checks the compat settings) and then > never call attach, but instead print a message saying it is disabled. Ah, hadn't thought so far; one too many steps. > 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. fdt rm fdt mkprop 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. > 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 >> > -- Bjoern A. Zeeb r15:7 --1098556516-66325157-1704885425=:2837--