From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756270Ab0KOMiu (ORCPT ); Mon, 15 Nov 2010 07:38:50 -0500 Received: from smtp-out-139.synserver.de ([212.40.180.139]:1044 "EHLO smtp-out-139.synserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751098Ab0KOMit (ORCPT ); Mon, 15 Nov 2010 07:38:49 -0500 X-SynServer-TrustedSrc: 1 X-SynServer-AuthUser: markus@trippelsdorf.de X-SynServer-PPID: 12775 Date: Mon, 15 Nov 2010 13:38:46 +0100 From: Markus Trippelsdorf To: Christoph Lameter Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: BUG: Bad page state in process (current git) Message-ID: <20101115123846.GA30047@arch.trippelsdorf.de> References: <20101110152519.GA1626@arch.trippelsdorf.de> <20101110154057.GA2191@arch.trippelsdorf.de> <20101112122003.GA1572@arch.trippelsdorf.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101112122003.GA1572@arch.trippelsdorf.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2010.11.12 at 13:20 +0100, Markus Trippelsdorf wrote: > On 2010.11.10 at 15:46 -0600, Christoph Lameter wrote: > > On Wed, 10 Nov 2010, Markus Trippelsdorf wrote: > > > > > I found this in my dmesg: > > > ACPI: Local APIC address 0xfee00000 > > > [ffffea0000000000-ffffea0003ffffff] PMD -> [ffff8800d0000000-ffff8800d39fffff] on node 0 > > > > That only shows you how the memmap was virtually mapped. > > Yes. Fortunately the BUG is gone since I pulled the upcoming drm fixes No. I happend again today (with those fixes already applied): BUG: Bad page state in process knode pfn:7f0a8 page:ffffea0001bca4c0 count:0 mapcount:0 mapping: (null) index:0x0 page flags: 0x4000000000000008(uptodate) Pid: 18310, comm: knode Not tainted 2.6.37-rc1-00549-gae712bf-dirty #16 Call Trace: [] ? bad_page+0x92/0xe0 [] ? get_page_from_freelist+0x4b0/0x570 [] ? apic_timer_interrupt+0xe/0x20 [] ? __alloc_pages_nodemask+0x113/0x6b0 [] ? file_read_actor+0xc4/0x190 [] ? generic_file_aio_read+0x560/0x6b0 [] ? handle_mm_fault+0x6bd/0x970 [] ? do_page_fault+0x120/0x410 [] ? do_brk+0x275/0x360 [] ? page_fault+0x1f/0x30 Disabling lock debugging due to kernel taint -- Markus From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with ESMTP id 459348D0017 for ; Mon, 15 Nov 2010 07:38:50 -0500 (EST) Date: Mon, 15 Nov 2010 13:38:46 +0100 From: Markus Trippelsdorf Subject: Re: BUG: Bad page state in process (current git) Message-ID: <20101115123846.GA30047@arch.trippelsdorf.de> References: <20101110152519.GA1626@arch.trippelsdorf.de> <20101110154057.GA2191@arch.trippelsdorf.de> <20101112122003.GA1572@arch.trippelsdorf.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101112122003.GA1572@arch.trippelsdorf.de> Sender: owner-linux-mm@kvack.org To: Christoph Lameter Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org List-ID: On 2010.11.12 at 13:20 +0100, Markus Trippelsdorf wrote: > On 2010.11.10 at 15:46 -0600, Christoph Lameter wrote: > > On Wed, 10 Nov 2010, Markus Trippelsdorf wrote: > > > > > I found this in my dmesg: > > > ACPI: Local APIC address 0xfee00000 > > > [ffffea0000000000-ffffea0003ffffff] PMD -> [ffff8800d0000000-ffff8800d39fffff] on node 0 > > > > That only shows you how the memmap was virtually mapped. > > Yes. Fortunately the BUG is gone since I pulled the upcoming drm fixes No. I happend again today (with those fixes already applied): BUG: Bad page state in process knode pfn:7f0a8 page:ffffea0001bca4c0 count:0 mapcount:0 mapping: (null) index:0x0 page flags: 0x4000000000000008(uptodate) Pid: 18310, comm: knode Not tainted 2.6.37-rc1-00549-gae712bf-dirty #16 Call Trace: [] ? bad_page+0x92/0xe0 [] ? get_page_from_freelist+0x4b0/0x570 [] ? apic_timer_interrupt+0xe/0x20 [] ? __alloc_pages_nodemask+0x113/0x6b0 [] ? file_read_actor+0xc4/0x190 [] ? generic_file_aio_read+0x560/0x6b0 [] ? handle_mm_fault+0x6bd/0x970 [] ? do_page_fault+0x120/0x410 [] ? do_brk+0x275/0x360 [] ? page_fault+0x1f/0x30 Disabling lock debugging due to kernel taint -- Markus -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org