Date: Wed, 10 Jan 2024 11:17:04 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: MMCCAM hang Message-ID: <qr8p64r0-70ns-s604-72o9-no1r23q1p45n@yvfgf.mnoonqbm.arg> In-Reply-To: <CANCZdfp2B9SPtuLPPWoivPe=VE9Sg%2Bc=Tc-tKc7sN-=mTVa7gw@mail.gmail.com> References: <nsors8o2-25pn-pr36-7rp6-3rp47psp7q69@yvfgf.mnoonqbm.arg> <CANCZdfrVyap71Q1=q8FJ8X9Fe2Wpj4tC8GQH0VHmgGrmerYwQQ@mail.gmail.com> <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> <CANCZdfp2B9SPtuLPPWoivPe=VE9Sg%2Bc=Tc-tKc7sN-=mTVa7gw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <bzeeb-lists@lists.zabbadoz.net> > 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?qr8p64r0-70ns-s604-72o9-no1r23q1p45n>