Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750900AbVKRT32 (ORCPT ); Fri, 18 Nov 2005 14:29:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750906AbVKRT31 (ORCPT ); Fri, 18 Nov 2005 14:29:27 -0500 Received: from gold.veritas.com ([143.127.12.110]:7274 "EHLO gold.veritas.com") by vger.kernel.org with ESMTP id S1750892AbVKRT31 (ORCPT ); Fri, 18 Nov 2005 14:29:27 -0500 Date: Fri, 18 Nov 2005 19:28:09 +0000 (GMT) From: Hugh Dickins X-X-Sender: hugh@goblin.wat.veritas.com To: Marc Koschewski cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.15-rc1-mm2 unsusable on DELL Inspiron 8200, 2.6.15-rc1 works fine In-Reply-To: <20051118182910.GJ6640@stiffy.osknowledge.org> Message-ID: References: <20051118182910.GJ6640@stiffy.osknowledge.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 18 Nov 2005 19:29:26.0862 (UTC) FILETIME=[6371B6E0:01C5EC76] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2284 Lines: 45 On Fri, 18 Nov 2005, Marc Koschewski wrote: > > I didn't manage to read all the archive yet That should only keep you busy for a year or two! > and I'm new to the list > anyways. I wanted to report that 2.6.15-rc1-mm2 is unusable in an X > enviroment due to the mouse pointer hanging, jumping or not even working > at all. The behaviour occurs randomly. Many thanks for the report. It looks from the messages at the end as if this is a manifestation of my PageReserved "Bad page states" that 2.6.15-rc1-mm2 was particularly put out to check for. Unfortunately your logging system is cutting out the most important info (perhaps because that's marked KERN_EMERG and the stack trace is not): I get lost in these logging setups myself so can't tell you what to do to correct it: but maybe running "dmesg" will give the full output. However, I've got four other reporters (though you're the first to mention the mouse), and hope to be able to work it out from their info, so don't worry if you can't track down the full Bad page state messages. Thanks, Hugh > Nov 18 13:05:12 stiffy kernel: [bad_page+134/318] bad_page+0x86/0x13e > Nov 18 13:05:12 stiffy kernel: [free_hot_cold_page+66/285] free_hot_cold_page+0x42/0x11d > Nov 18 13:05:13 stiffy kernel: [do_gettimeofday+20/188] do_gettimeofday+0x14/0xbc > Nov 18 13:05:13 stiffy kernel: [zap_pte_range+305/719] zap_pte_range+0x131/0x2cf > Nov 18 13:05:13 stiffy kernel: [unmap_page_range+236/273] unmap_page_range+0xec/0x111 > Nov 18 13:05:13 stiffy kernel: [unmap_vmas+193/476] unmap_vmas+0xc1/0x1dc > Nov 18 13:05:13 stiffy kernel: [unmap_region+150/289] unmap_region+0x96/0x121 > Nov 18 13:05:13 stiffy kernel: [do_munmap+235/300] do_munmap+0xeb/0x12c > Nov 18 13:05:13 stiffy kernel: [sys_munmap+62/88] sys_munmap+0x3e/0x58 > Nov 18 13:05:13 stiffy kernel: [syscall_call+7/11] syscall_call+0x7/0xb > Nov 18 13:05:14 stiffy kernel: [bad_page+134/318] bad_page+0x86/0x13e > Nov 18 13:05:14 stiffy kernel: [free_hot_cold_page+66/285] free_hot_cold_page+0x42/0x11d > .... - 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/