Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756674AbYGaK3Y (ORCPT ); Thu, 31 Jul 2008 06:29:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753529AbYGaK3O (ORCPT ); Thu, 31 Jul 2008 06:29:14 -0400 Received: from rv-out-0506.google.com ([209.85.198.237]:11934 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753218AbYGaK3N (ORCPT ); Thu, 31 Jul 2008 06:29:13 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=SxaZo114NU8GiAHstZRk/g8LASU5fJUsJgMOviOsyRTC48SI+5luN+10Ujgq/oHsD2 Ywmk6LLAUSwqhcbVTnSDjdrGQpWIArdFZGroxEKkwMuyK2rWtgT6xwup0upy3RlkZvLQ /40jW5+pgUquUByuE4AKCaGSoXLZZbX/yuZhI= Message-ID: <1ba2fa240807310329v7256b7dcteffec3d419eb204d@mail.gmail.com> Date: Thu, 31 Jul 2008 13:29:12 +0300 From: "Tomas Winkler" To: "Pekka Enberg" Subject: Re: [BUG] wireless : cpu stuck for 61s Cc: "Andrew Morton" , "Dave Young" , "Johannes Berg" , linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org In-Reply-To: <1217497994.7813.184.camel@penberg-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080729055731.GA3265@darkstar> <1217334724.10489.47.camel@johannes.berg> <20080730020820.8bcc00e2.akpm@linux-foundation.org> <20080730031047.54e13e2d.akpm@linux-foundation.org> <20080730195637.2197a82d.akpm@linux-foundation.org> <1ba2fa240807310250kd2df7bfxa3591cf78e68f8dc@mail.gmail.com> <1217497994.7813.184.camel@penberg-laptop> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1117 Lines: 24 On Thu, Jul 31, 2008 at 12:53 PM, Pekka Enberg wrote: > On Thu, 2008-07-31 at 12:50 +0300, Tomas Winkler wrote: >> > There's ath5k in the stack trace but that, of course, doesn't >> > automatically mean it's at fault here. It could have been just the poor >> > bastard who was the next to allocate 4 KB with kmalloc() noticing the >> > corruption. >> > >> > Hope this helps! >> >> I've seen something similar with fragmentation code in iwl4965 but I >> can reproduce it only when using SLAB. With SLUB it didn't shown up. >> Does anyone know what is difference between SLAB and SLUB in this context.? > > Do you have CONFIG_SLUB_DEBUG_ON enabled? (Note: if you only have > CONFIG_SLUB_DEBUG enabled, then you need to enable debugging at run-time > by passing slub_debug to kernel command line.) Yes sure I've done that with slub_debug=FZPU Tomas -- 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/