From mboxrd@z Thu Jan 1 00:00:00 1970 From: Romit Dasgupta Subject: Re: Memory allocations in .suspend became very unreliable Date: Fri, 15 Jan 2010 15:54:27 +0530 Message-ID: <4B50425B.4050605@ti.com> References: <1263549544.3112.10.camel@maxim-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1263549544.3112.10.camel@maxim-laptop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Maxim Levitsky Cc: linux-pm List-Id: linux-pm@vger.kernel.org Maxim Levitsky wrote: > Hi, > > I know that this is very controversial, because here I want to describe > a problem in a proprietary driver that happens now in 2.6.33-rc3 > I am taking about nvidia driver. > > Some time ago I did very long hibernate test and found no errors after > more that 200 cycles. > > Now I update to 2.6.33 and notice that system will hand when nvidia > driver allocates memory is their .suspend functions. > This could fail in 2.6.32 if I would run many memory hungry > applications, but now this happens with most of memory free. > > I added some printks to function used to allocate memory in nvidia > driver and found out that contrary to my belief, they don't allocate > much memory there. Hello Maxim, Do you hit the error early if you reduce your memory (by passing 'mem= ' bootargs)? The hibernation routine allocates memory for creating its own bitmaps, so I was wondering if it is really a memory issue or bug in the nvidia driver. Thanks, -Romit