Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266339AbUAHUs6 (ORCPT ); Thu, 8 Jan 2004 15:48:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266340AbUAHUs6 (ORCPT ); Thu, 8 Jan 2004 15:48:58 -0500 Received: from fw.osdl.org ([65.172.181.6]:31928 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S266339AbUAHUs5 (ORCPT ); Thu, 8 Jan 2004 15:48:57 -0500 Date: Thu, 8 Jan 2004 12:50:08 -0800 From: Andrew Morton To: Torrey Hoffman Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: 2.6.1-rc2-mm1 Message-Id: <20040108125008.228dd6fe.akpm@osdl.org> In-Reply-To: <1073594191.1618.13.camel@moria.arnor.net> References: <20040107232831.13261f76.akpm@osdl.org> <1073593346.1618.3.camel@moria.arnor.net> <1073594191.1618.13.camel@moria.arnor.net> X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1582 Lines: 35 Torrey Hoffman wrote: > > ... And another kernel error about two minutes later than the ones > below. This happened while starting up my X desktop and apps. The > gnome-notification-applet failed to start, and Mozilla doesn't appear > start up properly for me in rc2-mm1. However, Evolution is sending and > receiving mail ok... > > I'll reboot to -rc2-vanilla and see if I can reproduce the problem > there. (same .config was used on both -rc2-vanilla and -rc2-mm1) > > Jan 8 12:18:27 moria kernel: <3>Debug: sleeping function called from > invalid context at mm/page_alloc.c:550 > Jan 8 12:18:27 moria kernel: in_atomic():1, irqs_disabled():0 > Jan 8 12:18:27 moria kernel: Call Trace: > Jan 8 12:18:27 moria kernel: [] __might_sleep+0xab/0xc9 > Jan 8 12:18:27 moria kernel: [] __alloc_pages+0x341/0x346 > Jan 8 12:18:27 moria kernel: [] pte_alloc_one+0x20/0x56 > Jan 8 12:18:27 moria kernel: [] pte_alloc_map+0x4e/0x111 > Jan 8 12:18:27 moria kernel: [] > filemap_populate_nonblock+0x2a1/0x2ce Yes, this one's a locking problem in the new filemap code. I'm not sure why people are seeing oopses in the poll code - I hope networking didn't break. Oh well, it looks like 2.6.1-rc2-mm1 is a dud. I'll drop a few things and do rc3-mm1 tonight. - 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/