Date: Fri, 29 Oct 2021 12:34:48 -0600 From: Ian Lepore <ian@freebsd.org> To: kamalpr@gmail.com, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: bug in mmc driver Message-ID: <22fb38d9b6cda8baec08713159bb65afcc8cd418.camel@freebsd.org> In-Reply-To: <CAK=yUG%2Bu9K3=9yHKeabBkyKx%2B6=mGy3_cKXaJeTa75OQ%2BbTJYg@mail.gmail.com> References: <CAK=yUG%2Bu9K3=9yHKeabBkyKx%2B6=mGy3_cKXaJeTa75OQ%2BbTJYg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2021-10-29 at 10:02 +0530, Kamal R. Prasad wrote:
> hello,
>
> if i run a stress test on a freebsd system booted from a micron mmc
> device, and run a script which in a loop opens the same mmc device in
> read-only mode, it causes a problem in acquiring the bus and panics
> the box. both the stress test and a script to open the mmc device in
> read only mode are in user space and so kernel should not have
> panic'ed. Pl see stack trace from our freebsd derived os.
>
> thanks
> -kamal
> --------------
>
> panic: mmc: host bridge didn't serialize us.
>
> [...]
>
This indicates a problem in the low-level mmc/sd controller ("host
bridge") driver. You didn't say anything about what hardware is in
use; I have no idea what driver to look at.
-- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22fb38d9b6cda8baec08713159bb65afcc8cd418.camel>