On Wed, 20 May 2020 at 11:02, Valdis Klētnieks wrote:
>
> On Wed, 20 May 2020 10:26:50 +0530, Pintu Agarwal said:
> > I know it is weird to manually arrive a MemTotal from the values of meminfo.
> > But I am actually looking for general formula.
>
> You missed the point - the "general formula" has
On Wed, 20 May 2020 10:26:50 +0530, Pintu Agarwal said:
> I know it is weird to manually arrive a MemTotal from the values of meminfo.
> But I am actually looking for general formula.
You missed the point - the "general formula" has probably changed over the
years.
> With this I could arrive to
On Wed, 20 May 2020 at 09:31, Valdis Klētnieks wrote:
>
> On Tue, 19 May 2020 22:33:15 +0530, Pintu Agarwal said:
>
> > > Below are some data taken from a small embedded arm32 device with 512MB
> > > RAM:
> > >
> >
> > Sorry, I forgot to mention the kernel version. Here it is 3.18 Kernel
>
> That
On Tue, 19 May 2020 22:33:15 +0530, Pintu Agarwal said:
> > Below are some data taken from a small embedded arm32 device with 512MB RAM:
> >
>
> Sorry, I forgot to mention the kernel version. Here it is 3.18 Kernel
That's a kernel from 2014. You don't seriously expect us to remember how
all thos
On Mon, 18 May 2020 at 23:27, Pintu Agarwal wrote:
>
> Hi,
>
> I was just trying to manually calculate the total memory available in
> a system to match up the MemTotal shown in /proc/meminfo
> I know "free -m" command will give the vary high level usage, but I
> wanted to breakdown the MemTotal n
Hi ,
kdump need 2 kernel primary and secondary. Primary will be panicked, then
secondary will do capture coredump.
In boot loader/ kernel command line specify crashkernel=256MB or more,
ensure secondary kernel is small in size so that it can be boot within this
memory, oom should not happen.
Pri
