From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262170AbUE2BQa (ORCPT ); Fri, 28 May 2004 21:16:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262794AbUE2BQa (ORCPT ); Fri, 28 May 2004 21:16:30 -0400 Received: from potato.cts.ucla.edu ([149.142.36.49]:14265 "EHLO potato.cts.ucla.edu") by vger.kernel.org with ESMTP id S262170AbUE2BQ2 (ORCPT ); Fri, 28 May 2004 21:16:28 -0400 Date: Fri, 28 May 2004 18:16:22 -0700 (PDT) From: Chris Stromsoe To: Dave Kleikamp cc: linux-kernel , Marcelo Tosatti Subject: Re: oops, 2.4.26 and jfs In-Reply-To: <1085776292.13846.18.camel@shaggy.austin.ibm.com> Message-ID: References: <1085776292.13846.18.camel@shaggy.austin.ibm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 28 May 2004, Dave Kleikamp wrote: > On Fri, 2004-05-28 at 15:15, Chris Stromsoe wrote: > > This morning during a cron run while doing a find across /, I got the > > following oops. > > The oops is fixed in 2.4.27-pre3 with the patch: > http://linux.bkbits.net:8080/linux-2.4/cset@1.1359.20.3 > > jfs still may give you problems if 0-order allocations are failing, but > it's not supposed to trap. Thanks, patch applied. Aside from that: > May 26 06:28:10 begonia kernel: __alloc_pages: 0-order allocation failed > (gfp=0x1f0/0) I'm curious about why 0-order allocations would fail. From everything I've read (google searching for the error message), that indicates an out of memory condition, which shouldn't be the case. The box in question has 4Gb of physical ram (512Mb is used as tmpfs) and 9Gb of swap. When the oops happened, no swap was in use. Physical ram was pretty much filled, but no swap at all. OOM_KILLER is not enabled. There's nothing especially exotic in the box. It does a lot of network traffic (eepro100) and a lot of disk traffic (aic7xxx). The morning cron jobs had just kicked off. Two of them do "find /" -- I believe that the second one was running when it happened. -Chris