Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754154AbZFGOUW (ORCPT ); Sun, 7 Jun 2009 10:20:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752659AbZFGOUL (ORCPT ); Sun, 7 Jun 2009 10:20:11 -0400 Received: from mx2.redhat.com ([66.187.237.31]:54990 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753208AbZFGOUJ (ORCPT ); Sun, 7 Jun 2009 10:20:09 -0400 Message-ID: <4A2BCC6F.8090004@redhat.com> Date: Sun, 07 Jun 2009 10:19:27 -0400 From: Rik van Riel Organization: Red Hat, Inc User-Agent: Thunderbird 2.0.0.17 (X11/20080915) MIME-Version: 1.0 To: Pekka Enberg CC: Larry Finger , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Johannes Berg , Andrew Morton , KOSAKI Motohiro , KAMEZAWA Hiroyuki , hugh@veritas.com Subject: Re: [Bug #13319] Page allocation failures with b43 and p54usb References: <4A2BBC30.2030300@lwfinger.net> <84144f020906070640rf5ab14nbf66d3ca7c97675f@mail.gmail.com> In-Reply-To: <84144f020906070640rf5ab14nbf66d3ca7c97675f@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2327 Lines: 51 Pekka Enberg wrote: > Hi Larry, > > On Sun, Jun 7, 2009 at 4:10 PM, Larry Finger wrote: >> Rafael J. Wysocki wrote: >>> This message has been generated automatically as a part of a report >>> of recent regressions. >>> >>> The following bug entry is on the current list of known regressions >>> from 2.6.29. Please verify if it still should be listed and let me know >>> (either way). >>> >>> >>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13319 >>> Subject : Page allocation failures with b43 and p54usb >>> Submitter : Larry Finger >>> Date : 2009-04-29 21:01 (40 days old) >>> References : http://marc.info/?l=linux-kernel&m=124103897101088&w=4 >>> Handled-By : Johannes Berg >> This bug is extremely difficult to pin down. I cannot reproduce it at >> will. The system has to be up for a long time, which is difficult with >> testing the late RC's of 2.6.30 and the code in wireless-testing so >> that new bugs don't end up in 2.6.31-RCX. That said, it still was in >> 2.6.30-RC6 and I'm not aware of any changes since that would fix it. >> >> My operating kernel is patched with additional diagnostics to help me >> understand why a kmalloc request for a buffer of 1390 bytes suddenly >> ends up as an O(1) request. Unfortunately, I don't have any answers. > > Looking at the out-of-memory trace, there's still memory available but > the pskb_expand_head() allocation is GFP_ATOMIC so there's not much > the page allocator can do here. The amount of memory consumed by > inactive_file is pretty high so maybe the problem is related to the > recent mm/vmscan.c changes. Lets copy some more mm developers and see > if they can help out. That is a very strange trace. The Mem-Info indicates that the system has more than enough memory free, and also enough memory in higher-order free blocks. This would indicate a bug somewhere in the page allocator - this memory should have been given to this allocation request. -- All rights reversed. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/