All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniele C." <legolas558@users.sourceforge.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	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: Fri, 05 Mar 2010 21:13:50 +0100	[thread overview]
Message-ID: <4B9165FE.1080502@users.sourceforge.net> (raw)
In-Reply-To: <201003051722.42437.IvDoorn@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -------- Original Message  --------
Subject: Re: rt2870 (staging kernel driver) crashes fatally
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Date: Fri Mar 05 2010 17:22:41 GMT+0100 (CET)

> On Thursday 04 March 2010, Larry Finger wrote:
>> 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.
> 
> Actually the rt2x00-users list is not intended for the Ralink staging drivers.
> You have to use the staging mailing list: devel@driverdev.osuosl.org
> 
Yes, they refused my message but didn't tell anything about the staging mailing list which I couldn't find either and I am now reading from you. Many thanks for pointing this out.

I am now running with MEMLEAK enabled, as soon as I will make a new "hammering session" I'll grab the debug data and post another message.

Best regards,
- --
  Daniele

> Ivo
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLkWX+AAoJEON28As9epPAI9AH/j6nspsStdgsO4AigPVlQRrb
tc7VOTmv+EwuydntCERrlFGx20sNYfKcBtyt7WHg3TWQnMr7ISgCK4fB+YDvWExb
gS4+4n7u6AgDMPkrL3tr4PBvCFQJksGPh8epaB9InRv8JnBTmhwv287Ng7PiXY6h
P0YYmcxIgQ2F9BPA5PHJ3+Y2PqIQl+2cur95rp3Q7EUESwyHSeDqQnC1l9k50FsM
M6tGyTMBYUZDHEncdu6wpDipfnTQ9gUD0j4XUlfmRhVmedJ4DTknySMOup1dgNPz
Y1UMYhyvjkibeAEcep2KAShMwEfapyUf01gaGMsRxecvexQwC1YsekGJ1/pbCBs=
=6LbC
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-03-05 20:14 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
2010-03-04 10:44     ` Daniele C.
2010-03-05 16:22     ` Ivo van Doorn
2010-03-05 20:13       ` Daniele C. [this message]
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=4B9165FE.1080502@users.sourceforge.net \
    --to=legolas558@users.sourceforge.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=hintak.leung@gmail.com \
    --cc=ivdoorn@gmail.com \
    --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 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.