linux-kernel - Re: Crash on reducing the kernel mem.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100903140041.GA16223@kroah.com>
Date:	Fri, 3 Sep 2010 07:00:41 -0700
From:	Greg KH <greg@...ah.com>
To:	Prabhu Chawandi <prabhu.chavandi@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	kernelnewbies@...linux.org
Subject: Re: Crash on reducing the kernel mem.

On Fri, Sep 03, 2010 at 12:04:09PM +0530, Prabhu Chawandi wrote:
> Hi all,
> 
>  I am using MIPS processor, with 256 MB RAM. currently I am using 128
> M for drivers and 128 M for Kernel. I tried to allocate more memory
> for Drivers,
> surprisingly I got crash when I reduced kernel memory to 110 M. My
> debugging took me to USB controller, which was not reset in
> bootloader.
> 
> I am not having any clue, why it didnt crash with 128 M ? How reducing
> memory  for kernel bringing it up ?

Perhaps your drivers really needed that much memory.  How are you
"splitting" memory up between drivers and the kernel when the drivers
and kernel all share the same memory areas?

good luck,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/