From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760625AbYDYJK4 (ORCPT ); Fri, 25 Apr 2008 05:10:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758267AbYDYJKq (ORCPT ); Fri, 25 Apr 2008 05:10:46 -0400 Received: from fg-out-1718.google.com ([72.14.220.155]:40975 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758086AbYDYJKp (ORCPT ); Fri, 25 Apr 2008 05:10:45 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=cA3nIzFhaWNaNsZVe/dp+Y/f/0UHGeYQZsGQEU8j/rtm9R17D6Evra7bOhQbppPocw2vsPMghh1Rd96g6LlqkATnGfkS2LxYWnjO8GxFJo00r1VsTawM+hqvdTcpenrCIUz0dk8yLPw6hiDNHFsVYPwHoi17vJGgRz/Epn1Tkkw= Message-ID: <4812108D.6020103@gmail.com> Date: Fri, 25 Apr 2008 19:10:37 +0200 From: Jiri Slaby User-Agent: Thunderbird 2.0.0.12 (X11/20080213) MIME-Version: 1.0 To: Linus Torvalds CC: Zdenek Kabelac , Ingo Molnar , "Rafael J. Wysocki" , paulmck@linux.vnet.ibm.com, David Miller , Linux Kernel Mailing List , Andrew Morton , linux-ext4@vger.kernel.org, herbert@gondor.apana.org.au, Pekka Enberg , Christoph Lameter Subject: Re: 2.6.25-git2: BUG: unable to handle kernel paging request at ffffffffffffffff References: <480D1CF1.7010300@gmail.com> <480D208A.9050909@gmail.com> <200804220254.45251.rjw@sisk.pl> <480DB493.6080004@gmail.com> <20080422095315.GA28014@elte.hu> <4811090A.9030809@gmail.com> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/25/2008 12:41 AM, Linus Torvalds wrote: > Also, it does seem like you can re-create this at will in ways that others > can not. Could you try to bisect it a bit? Right now we have no real clue > what it is all about, except that it seems to be related to suspend/resume > and there are some indications that it's about networking (and _perhaps_ > wireless in particular). Yes! I'm able to reproduce it 90%! We can exclude X, 80211 and so ath5k too (I removed them from /lib/modules, so they won't ever load). I set the water mark at 1700 megabytes to allocate by the testing programs, so that it eats almost all free available memory. Then, I wait to "alloced 1" and then pm-suspend on second console. After resume, it spits out the corruption. I'm going to bisect it, will be back in few hours ;).