From: "Daniele C." <legolas558@users.sourceforge.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Hin-Tak Leung <hintak.leung@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: rt2870 (staging kernel driver) crashes fatally
Date: Thu, 04 Mar 2010 11:44:32 +0100 [thread overview]
Message-ID: <4B8F8F10.5040404@users.sourceforge.net> (raw)
In-Reply-To: <4B8F1C7F.7050305@lwfinger.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -------- Original Message --------
Subject: Re: rt2870 (staging kernel driver) crashes fatally
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Daniele C. <legolas558@users.sourceforge.net>
Date: Thu Mar 04 2010 03:35:43 GMT+0100 (CET)
> 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.
>
I will enable this feature so that next time it happens I will have such information.
However looks like bug is not triggering unless I first do a resume.
Thank you both for reviewing my logs and for the pointers.
Best regards,
- --
Daniele C.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJLj48QAAoJEON28As9epPAqfIH/AktbatFnxAt6peijPxz64PV
jElSTuDYaieRRjKfoTQCVZoiSsf4f4sPAiqBR4E30zX7u9nWqqbaTIxLJjeC74Nr
fqfoFS2QBg8Ow5pLhs/pXUKR4c7g/x/QIQ7fzCAOUj/enirni2f6n9Gc8Tf8O1Mo
ejKXqqKeKPsnlNoBXtnB3ihE5sVp7O2PJZvxV3GCRy5KEmoIivPkrd3U4Lsc2pZG
86LOolgilto6I73/bdoU0CffiKyTENwpyJTMy1VFjqwOWLLn9ukuFbfyBd00Oo3W
uYX/SSCnouAKeAG0LzzTZMaYKOGkqJQzVLv/B0nhlcrrlk+xzWBNe04fxHamVo8=
=8q9G
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-04 10:45 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. [this message]
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=4B8F8F10.5040404@users.sourceforge.net \
--to=legolas558@users.sourceforge.net \
--cc=Larry.Finger@lwfinger.net \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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.