gt;>>> OF: fdt: Machine model: Edimax NS-2502
> > >>>>> Memory policy: Data cache writeback
> > >>>>> Zone ranges:
> > >>>>> Normal [mem 0x-0x07ff]
> > >>>>>
t;> CPU: FA526 [66015261] revision 1 (ARMv4), cr=397f
> >>>>> CPU: VIVT data cache, VIVT instruction cache
> >>>>> OF: fdt: Machine model: Edimax NS-2502
> >>>>> Memory policy: Data cache writeback
> >>>>> Zone ranges:
> >
0007ff]
crashkernel reservation failed - No suitable area found.
Built 1 zonelists, mobility grouping on. Total pages: 32512
Kernel command line: console=ttyS0,19200n8 ip=dhcp crashkernel=8M
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
Inode-cache hash table entries: 8192
;> Zone ranges:
> >>> Normal [mem 0x-0x07ff]
> >>> HighMem empty
> >>> Movable zone start for each node
> >>> Early memory node ranges
> >>> node 0: [mem 0x-0x07ff]
>
Mem empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x-0x07ff]
Initmem setup node 0 [mem 0x-0x07ff]
crashkernel reservation failed - No suitable area found.
Built 1 zonelists, mobility grouping on. Total pa
> > Memory policy: Data cache writeback
> > Zone ranges:
> >Normal [mem 0x-0x07ff]
> >HighMem empty
> > Movable zone start for each node
> > Early memory node ranges
> > node 0: [mem 0x00000000-0x000007ff]
&g
0007ff]
Initmem setup node 0 [mem 0x-0x07ff]
crashkernel reservation failed - No suitable area found.
Built 1 zonelists, mobility grouping on. Total pages: 32512
Kernel command line: console=ttyS0,19200n8 ip=dhcp crashkernel=8M
Dentry cache hash table entries: 16384
ode ranges
node 0: [mem 0x-0x07ff]
Initmem setup node 0 [mem 0x-0x07ff]
crashkernel reservation failed - No suitable
On 01/24/2013 09:07 AM, Vivek Goyal wrote:
>>
>> Is there a kernel/kexec-tools patch to address this problem in kernel 3.x
>> yet? Also, according to Takashi Iwa wrote, "the problem does not happen
>> always. However, once this happens, it continues to happen" :-(
>> Yes, yes, it drove me completel
system started
> to fail reserving the requested memory, even after I set it back to 512M:
> crashkernel reservation failed - No suitable area found
>
> Is there a kernel/kexec-tools patch to address this problem in kernel 3.x
> yet? Also, according to Takashi Iwa wrote, &qu
failed - No suitable area found
Is there a kernel/kexec-tools patch to address this problem in kernel 3.x
yet? Also, according to Takashi Iwa wrote, "the problem does not happen
always. However, once this happens, it continues to happen" :-(
Yes, yes, it drove me completely crazy trying to
11 matches
Mail list logo