From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Daniele C." <legolas558@users.sourceforge.net>
Cc: Hin-Tak Leung <hintak.leung@gmail.com>,
users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org
Subject: Re: rt2870 (staging kernel driver) crashes fatally
Date: Wed, 03 Mar 2010 20:35:43 -0600 [thread overview]
Message-ID: <4B8F1C7F.7050305@lwfinger.net> (raw)
In-Reply-To: <3ace41891003031814r73d3b615x99d29e9cad1fd9c4@mail.gmail.com>
On 03/03/2010 08:14 PM, Hin-Tak Leung wrote:
> You appear to have two issues - (1) the driver doesn't
> hibernate/resume well, (2) there is some bad memory leak which causes
> your system to run out of memory.
>
> You did not mention issue (1) - that you were hibernating and resuming
> (and expecting it to work, which it does not). For the latter, you
> probably need to track down where the memory is leaking in the driver,
> which is probably easier than tracking down the hibernate/resume
> issue.
>
> Good luck with tracking down the memory leak. (you do understand that
> staging drivers are DIY - i.e. you try it only if you are willing to
> look into fixing it yourself - I hope )
By generating your own kernel with MEMLEAK enabled, you should be able to see
which data blob is being leaked. If you post that info, someone on this list
should be able to help you find the cause.
Larry
next prev parent reply other threads:[~2010-03-04 2:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 8:41 rt2870 (staging kernel driver) crashes fatally Daniele C.
2010-03-04 2:14 ` Hin-Tak Leung
2010-03-04 2:35 ` Larry Finger [this message]
2010-03-04 10:44 ` Daniele C.
2010-03-05 16:22 ` Ivo van Doorn
2010-03-05 20:13 ` Daniele C.
2010-03-05 20:21 ` Ivo van Doorn
2010-03-05 20:24 ` Luis Correia
2010-03-05 20:32 ` Daniele C.
2010-03-04 10:13 ` Daniele C.
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=4B8F1C7F.7050305@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=hintak.leung@gmail.com \
--cc=legolas558@users.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.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).