On Sat, May 25, 2013 at 3:25 AM, Yuanhan Liu
wrote:
> Firstly, your patch works and feel free to add:
> Tested-by: Yuanhan Liu
ok, will resend it in complete form.
>
> While, your patch fixes this issue on source side. I thought that
> before, too. But I think it's better to fix it on
On Sat, May 25, 2013 at 12:31:43AM -0700, Yinghai Lu wrote:
> On Fri, May 24, 2013 at 9:30 PM, Yuanhan Liu
> wrote:
> > Commit 8d57470d introduced a kernel panic while setting mem=2G at
> > boot time, and commit c9b3234a6 turns the the kernel panic to hang.
> >
> > While, the reason is the same: t
On Fri, May 24, 2013 at 9:30 PM, Yuanhan Liu
wrote:
> Commit 8d57470d introduced a kernel panic while setting mem=2G at
> boot time, and commit c9b3234a6 turns the the kernel panic to hang.
>
> While, the reason is the same: the are accessing a BAD address; I mean
> the mapping is broken.
>
> Here
Commit 8d57470d introduced a kernel panic while setting mem=2G at
boot time, and commit c9b3234a6 turns the the kernel panic to hang.
While, the reason is the same: the are accessing a BAD address; I mean
the mapping is broken.
Here is a mem mapping range dumped at boot time:
[mem 0x-
4 matches
Mail list logo