Hi Geert-san,
> From: Geert Uytterhoeven, Sent: Wednesday, October 2, 2019 5:32 PM
>
> Hi Shimoda-san, Wolfram,
>
> On Wed, Oct 2, 2019 at 10:26 AM Yoshihiro Shimoda
> <yoshihiro.shimoda.uh@xxxxxxxxxxx> wrote:
> > > From: Wolfram Sang, Sent: Wednesday, October 2, 2019 5:16 PM
> > <snip>
> > > Tested on a R-Car H2: it does make the error message go away and the
> > > MMCIF device acts normal during boot. Can't enter userspace currently
> > > with v5.4-rc1 but this is unrelated to this patch and MMCIF. Looks like a
> > > configuration thing on my side, so I will still give:
> >
> > I also should have reported this though, my environment (R-Car H2 + NFS +
> > buildroot on v5.4-rc1 with shmobile_defconfig) also has a similar issue
> > like the following:
> >
> > [ 3.573488] VFS: Mounted root (nfs filesystem) on device 0:16.
> > [ 3.579869] devtmpfs: mounted
> > [ 3.588014] Freeing unused kernel memory: 1024K
> > [ 3.651771] Run /sbin/init as init process
> > Starting syslogd: OK
> > Starting klogd: OK
> > Initializing random number generator... [ 4.073629] random: dd: uninitialized urandom read (512 bytes read)
> > urandom start: failed.
> > done.
> > Starting network: ip: OVERRUN: Bad address
> > ip: OVERRUN: Bad address
> > ip: OVERRUN: Bad address
>
> Please cherry-pick the top commit from renesas-devel:
> 6e47c841329eb9b0 ("ARM: fix __get_user_check() in case uaccess_* calls
> are not inlined")
Thank you for the information. This commit could fix the issue on my environment.
Best regards,
Yoshihiro Shimoda
