From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762851AbYDVJyc (ORCPT ); Tue, 22 Apr 2008 05:54:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757661AbYDVJyU (ORCPT ); Tue, 22 Apr 2008 05:54:20 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:49656 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755549AbYDVJyT (ORCPT ); Tue, 22 Apr 2008 05:54:19 -0400 Date: Tue, 22 Apr 2008 11:53:15 +0200 From: Ingo Molnar To: Jiri Slaby Cc: Linus Torvalds , "Rafael J. Wysocki" , paulmck@linux.vnet.ibm.com, David Miller , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, linux-ext4@vger.kernel.org, herbert@gondor.apana.org.au, Zdenek Kabelac Subject: Re: 2.6.25-git2: BUG: unable to handle kernel paging request at ffffffffffffffff Message-ID: <20080422095315.GA28014@elte.hu> References: <480D1CF1.7010300@gmail.com> <480D208A.9050909@gmail.com> <200804220254.45251.rjw@sisk.pl> <480DB493.6080004@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <480DB493.6080004@gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Jiri Slaby wrote: >> What do you do to trigger this? Any particular load? Is it still just >> doing suspend/resume, or do you have something else that you are >> playing with? > > Yesterday I did 2 suspend/resumes after 1 hour of uptime and ran > git-status for a fraction of a second until it was killed. So I can > perfectly reproduce it when I suspend, resume and produce some io > load. I guess it's time to bisect 2.6.25-rc8-mm2 as I'm able to > reproduce it the best and haven't seen that bug in -rc8-mm1 for over > week of suspending and working. the most dangerous x86 change we added was the PAT stuff. Does it influence the crashes in any way if you boot with 'nopat' or if you disable CONFIG_X86_PAT=y into the .config? the other area was the DMA ops change - that should be rather trivial on 64-bit though. Ingo