All of lore.kernel.org
 help / color / mirror / Atom feed
From: me@bobcopeland.com
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Pedro Francisco <pedrogfrancisco@gmail.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	mickflemm@gmail.com
Subject: Re: ath5k misbehaving affecting other kernel parts unrelated?
Date: Fri, 23 Apr 2010 12:37:03 -0400	[thread overview]
Message-ID: <20100423163703.GB11112@hash.localnet> (raw)
In-Reply-To: <20100423134823.GB5004@tuxdriver.com>

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


  reply	other threads:[~2010-04-23 16:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23  7:06 ath5k misbehaving affecting other kernel parts unrelated? Pedro Francisco
2010-04-23 13:48 ` John W. Linville
2010-04-23 16:37   ` me [this message]
2010-04-23 16:43     ` Maciej Żenczykowski
2010-04-24  8:59       ` Pedro Francisco
2010-04-24  8:56     ` Pedro Francisco
2010-04-24 12:05       ` me
2010-04-24 12:09       ` Vegard Nossum
2010-04-24 17:28         ` Pedro Francisco
2010-04-25 19:22           ` me
2010-04-25 20:29             ` Jiri Slaby
2010-04-25 21:24               ` Pedro Francisco
2010-04-27 11:04                 ` Pedro Francisco
2010-04-28 21:52           ` Pedro Francisco
2010-04-29  7:17             ` Vegard Nossum
2010-04-29 10:25               ` Pedro Francisco
2010-04-23 19:13 ` Dan Carpenter
2010-04-24  9:27   ` Pedro Francisco
2010-04-24 12:13     ` Dan Carpenter
2010-04-24 13:13       ` Pedro Francisco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100423163703.GB11112@hash.localnet \
    --to=me@bobcopeland.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mickflemm@gmail.com \
    --cc=pedrogfrancisco@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.