Re: mmccam -> no more cards/sdio but "mmcprobe"
- Reply: Warner Losh : "Re: mmccam -> no more cards/sdio but "mmcprobe""
- In reply to: Bjoern A. Zeeb: "Re: mmccam -> no more cards/sdio but "mmcprobe""
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 21 Jul 2025 17:38:55 UTC
So, We're getting through the 'reset' and 'identify' states in the state machine and entering the 'power off' state. And then progressing no further. So we get into the 'done' routine, but don't progress to sending the get ocr command. That's why we still have the probe routine. We're not setting the probe into INVALID state, so we should be calling xpt_schedule() to do the next single step of this process at the end of mmc_done(), but that doesn't trigger a new call to mmc_start(). I did some CAM cleanups that shouldn't have broken this, but might have (low probability, but with cam you never know, especially in the single step phase we do to do the probing). I'll check those out. Maybe it's easy. Warner On Mon, Jul 21, 2025 at 7:15 AM Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote: > > On Sun, 20 Jul 2025, Warner Losh wrote: > > > On Sun, Jul 20, 2025, 7:20 PM Warner Losh <imp@bsdimp.com> wrote: > > > >> > >> > >> On Sun, Jul 20, 2025, 5:24 PM Warner Losh <imp@bsdimp.com> wrote: > >> > >>> > >>> > >>> On Sun, Jul 20, 2025, 5:19 PM Bjoern A. Zeeb < > >>> bzeeb-lists@lists.zabbadoz.net> wrote: > >>> > >>>> Hi, > >>>> > >>>> I've updated one of my trees to main after a longer while and I am > >>>> confused that I no longer see and SD card or SDIO (this is netbooted): > >>>> > >>>> # sysctl kern.features.mmccam > >>>> kern.features.mmccam: 1 > >>>> > >>>> # camcontrol devlist -v > >>>> scbus0 on dw_mmc_sim0 bus 0: > >>>> <> at scbus0 target 0 lun 0 (mmcprobe0) > >>>> scbus1 on dw_mmc_sim1 bus 0: > >>>> <> at scbus1 target 0 lun 0 (mmcprobe1) > >>>> scbus-1 on xpt0 bus 0: > >>>> <> at scbus-1 target -1 lun ffffffff > >>>> (xpt0) > >>>> > >>>> Where to start looking? > >>>> > >>> > >>> So those probes are put there to evaluate devices that were found. If > >>> they remain, then that never finished. Most likely never started. > >>> > >>> What hardware is this on? > >>> > >> > >> Thanks for the debug... > >> > >> As luck would have it, I just installed on emmc system (x86). I'm building > >> mmccam kernel now. > >> > > > > I can confirm this result. When was your last update? There was also > > sleeping on a non-sleepable lock witness warning... > > The locking issue I think I posted a while a ago. > > I cannot say which kernel last worked there; that was likely from 2024. > > I found an arm64 MMCCAM kernel from around 2025-03-18/26 which works on > the LS1088. Seems the last commit from main on that branch was > 12bff22669cf . > > # camcontrol devlist -v > scbus0 on sdhci_slot0 bus 0: > <SDHC FD4Q5 3.0 SN 7D9E55CA MFG 05/2022 > at scbus0 target 0 lun 0 (pass0,sdda0) > ... > > In either case the nvme does work by the way. It's just mmccam it seems > which does not. > > -- > Bjoern A. Zeeb r15:7