On Sat, Apr 6, 2019 at 2:47 AM Palmer Dabbelt wrote:
>
> On Thu, 04 Apr 2019 23:01:11 PDT (-0700), a...@brainfault.org wrote:
> > On Fri, Apr 5, 2019 at 11:24 AM Christoph Hellwig
> > wrote:
> >>
> >> On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote:
> >> > The Maximum Physical Memory
On Thu, 04 Apr 2019 23:01:11 PDT (-0700), a...@brainfault.org wrote:
On Fri, Apr 5, 2019 at 11:24 AM Christoph Hellwig wrote:
On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote:
> The Maximum Physical Memory 2GiB option for 64bit systems is currently
> broken because kernel hangs at bo
On Fri, Apr 5, 2019 at 11:24 AM Christoph Hellwig wrote:
>
> On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote:
> > The Maximum Physical Memory 2GiB option for 64bit systems is currently
> > broken because kernel hangs at boot-time when this option is enabled
> > and the underlying system
On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote:
> The Maximum Physical Memory 2GiB option for 64bit systems is currently
> broken because kernel hangs at boot-time when this option is enabled
> and the underlying system has more than 2GiB memory.
>
> This issue can be easily reproduced
The Maximum Physical Memory 2GiB option for 64bit systems is currently
broken because kernel hangs at boot-time when this option is enabled
and the underlying system has more than 2GiB memory.
This issue can be easily reproduced on SiFive Unleashed board where
we have 8GiB of memory.
This patch f
5 matches
Mail list logo
