Re: Oops in MMC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"ext Premi, Sanjeev" <premi@xxxxxx> writes:

> Hi,
>
> I was trying to mount the filesystem from MMC card on OMAP3EVM.
> Came across this oops.
>
> However, when I boot via ramdisk/NFS and mount /dev/mmcblk0p2; there is no oops.
>
> Anything missing in the configuration?
>
> Here is my snapshot menuconfig:
>    --- MMC/SD/SDIO card support
>    *** MMC/SD/SDIO Card Drivers ***
>     <*>   MMC block device driver
>     [*]     Use bounce buffer for simple hosts
>     <*>   TI OMAP High Speed Multimedia Card Interface support
>
> Also:
> # git-show --pretty=oneline
> 5019ed843f3208482c64043e4052e89b3d5462a0 sync isp1301_omap with mainlne
>
> Best regards,
> Sanjeev
>
> Mounting NFS filesystems:  [  OK  ]
> Mounting other filesystems:  [  OK  ]
> Starting system logger: <1>Unhandled fault: external abort on non-linefetch (0x1808) at 0xd809c104
> Unhandled fault: external abort on non-linefetch (0x1808) at
> 0xd809c104

This indicates that the driver is trying to access OMAP HSMMC module
registers while the module has it's clocks disabled. So probably there
is bug in HSMMC driver clock handling or in clockfw.

-- 
Jouni Högander

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux