Re: MMCCAM hang

From: Emmanuel Vadot <manu_at_bidouilliste.com>
Date: Wed, 10 Jan 2024 11:35:44 UTC
On Wed, 10 Jan 2024 11:17:04 +0000 (UTC)
"Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> wrote:

> 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.

 You can't :)

> 
> > 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


-- 
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>