Date: Sun, 15 Apr 2018 10:53:56 -0700 From: Stanislav Sedov <stas@freebsd.org> To: Udit agarwal <dev.madaari@gmail.com> Cc: freebsd-arm@freebsd.org, Russell Haley <russ.haley@gmail.com> Subject: Re: kernel panic while building SDIO driver Message-ID: <EB523BC3-316D-4907-8238-AF9E15F59DD7@freebsd.org> In-Reply-To: <CAM0bxh9OUK%2BJOuxig6EsiaCB6ke5=MJPab=2EHZ23QyvXN_a6A@mail.gmail.com> References: <CAM0bxh9OUK%2BJOuxig6EsiaCB6ke5=MJPab=2EHZ23QyvXN_a6A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Apr 15, 2018, at 8:01 AM, Udit agarwal <dev.madaari@gmail.com> wrote: >=20 > Hi, > I have been trying to build the kernel (for BBB) invoking SDIO driver from= > FreeBSD latest src tree using BEAGLEBONE-MMCCAM kernconf file(Yes, I added= > that file manually). I seems like the kernel panics due to sleep > lock(complete logs: > https://gist.github.com/madaari/4779d75e7f1ab88369318a40cb026d9b ) >=20 > mmc_dev_async(async_code=3D0x20, path_id=3D1, target_id=3D0, lun_id=3D0 > Got AC_PATH_REGISTERED -- whatever... > mmc_dev_async(async_code=3D0x20, path_id=3D1, target_id=3Dffffffff, > lun_id=3Dffffffff > usbus0: 480Mbps High Speed USB v2.0 > usbus1: 480Mbps High Speed USB v2.0 > (noperiph:sdhci_slot0:0:-1:ffffffff): XPT_SCAN_{BUS,TGT,LUN} > Kernel page fault with the following non-sleepable locks held: > exclusive sleep mutex CAM device lock (CAM device lock) r =3D 0 (0xc30e146= 4) > lock2 > stack backtrace: > Fatal kernel mode data abort: 'Translation Fault (L1)' on read > trapframe: 0xd0dc0ac0 > FSR=3D00000005, FAR=3D00000010, spsr=3D60000013 > r0 =3D00000061, r1 =3D00000188, r2 =3Dd0dc0a8c, r3 =3D60000013 > r4 =3Dc30e0000, r5 =3Dc30dec40, r6 =3D00000000, r7 =3Dd0dc0b68 > r8 =3Dc086f528, r9 =3Dc068f050, r10=3D00000000, r11=3Dd0dc0d10 > r12=3D00000062, ssp=3Dd0dc0b50, slr=3Dc002b77c, pc =3Dc002b5c0 > [ thread pid 4 tid 100048 ] > Stopped at mmc_action+0x94: ldr r6, [r6, #0x010] > db> >=20 > Any idea how to resolve this? >=20 It actually panicked on read fault (see L1 translation failure) on trying to= read the address which isn=E2=80=99t mapped. =46rom the obstruction printe= d, it appears to be r6, which is 0x0 =E2=80=94 most likely a NULL pointer de= reference in the code. What is at mmc_action+0x95 in your kernel? -- Stas=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EB523BC3-316D-4907-8238-AF9E15F59DD7>