Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758174Ab0DWQlN (ORCPT ); Fri, 23 Apr 2010 12:41:13 -0400 Received: from mail.deathmatch.net ([72.66.92.28]:1792 "EHLO mail.deathmatch.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758052Ab0DWQlL (ORCPT ); Fri, 23 Apr 2010 12:41:11 -0400 Date: Fri, 23 Apr 2010 12:37:03 -0400 From: me@bobcopeland.com To: "John W. Linville" Cc: Pedro Francisco , linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, mickflemm@gmail.com Subject: Re: ath5k misbehaving affecting other kernel parts unrelated? Message-ID: <20100423163703.GB11112@hash.localnet> References: <201004230806.13628.pedrogfrancisco@gmail.com> <20100423134823.GB5004@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100423134823.GB5004@tuxdriver.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 668 Lines: 16 On Fri, Apr 23, 2010 at 09:48:23AM -0400, John W. Linville wrote: > > a) is it "normal"? I thought modules were somewhat isolated these days. > > b) any advices for debugging? I've yet to have two oopses that are similar.... Advice for debugging: turn on slub/slab debug options, and possibly kmemcheck. kmemcheck was very helpful for me last time I had such a corruption issue. -- Bob Copeland %% www.bobcopeland.com -- 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/