From: Pavel Roskin <proski@gnu.org>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: rt2800usb: memory corruption?
Date: Sat, 01 Aug 2009 20:21:54 -0400 [thread overview]
Message-ID: <1249172514.3043.7.camel@ct> (raw)
In-Reply-To: <1249124154.8236.5.camel@marge.simson.net>
On Sat, 2009-08-01 at 12:55 +0200, Mike Galbraith wrote:
> Enabled slub/pagealloc debugging. First down/rmmod said...
I suggest that you try kmemcheck. It's very slow, but it finds memory
problems when they occur, not when it's too late.
You may want to disable kmemleak and framebuffer support and make sure
that X doesn't start, at it will be too slow. Slub debugging might
conflict with kmemcheck, so it's better to disable it.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-08-02 0:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 9:22 [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today Mike Galbraith
2009-07-30 9:29 ` Johannes Berg
2009-07-30 9:44 ` Mike Galbraith
2009-07-30 9:55 ` Johannes Berg
2009-07-30 10:05 ` Mike Galbraith
2009-07-30 12:11 ` [rt2800 doesn't authenticate (wpapsk/tkip)] " Mike Galbraith
2009-08-01 5:25 ` rt2800usb: memory corruption? Mike Galbraith
2009-08-01 10:55 ` Mike Galbraith
2009-08-02 0:21 ` Pavel Roskin [this message]
2009-08-02 5:16 ` Mike Galbraith
2009-08-02 6:29 ` Mike Galbraith
2009-08-02 6:47 ` Mike Galbraith
2009-08-06 10:12 ` Pavel Roskin
2009-07-30 10:06 ` [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today Luis Correia
2009-07-30 13:17 ` Bartlomiej Zolnierkiewicz
2009-07-30 16:52 ` Ivo van Doorn
2009-07-30 17:09 ` Mike Galbraith
2009-07-30 17:11 ` Johannes Berg
2009-07-30 17:26 ` Greg KH
2009-07-30 18:04 ` Dan Williams
2009-07-30 18:13 ` Greg KH
2009-08-02 9:10 ` Peter Teoh
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=1249172514.3043.7.camel@ct \
--to=proski@gnu.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).