From: "Daniele C." <legolas558@users.sourceforge.net>
To: 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:13:10 +0100 [thread overview]
Message-ID: <4B8F87B6.9060901@users.sourceforge.net> (raw)
In-Reply-To: <3ace41891003031814r73d3b615x99d29e9cad1fd9c4@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -------- Original Message --------
Subject: Re: rt2870 (staging kernel driver) crashes fatally
From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Daniele C. <legolas558@users.sourceforge.net>
Date: Thu Mar 04 2010 03:14:38 GMT+0100 (CET)
> 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.
>
Sorry I thought that hibernation/resume was supported.
> 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 )
>
I wish I were that good, but I'll try.
Best regards,
- --
Daniele
> On Wed, Mar 3, 2010 at 8:41 AM, Daniele C.
> <legolas558@users.sourceforge.net> wrote:
> Hello,
>
> I am experiencing the documented crash after intense usage of the wi-fi device.
>
> Best regards,
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJLj4e2AAoJEON28As9epPA/+4H/jDpF8Y8FIzJ9UlDOD4yuVNb
yeRgoJW4h1fnL5atZ66Ku+5EehOsKYQEjQDa3Apwl+g1RXFPenbIm4+A/mJQ4INu
7/wIgQIGRh9mPLmRw1+ylMExBbGSm/v4yp4oUj1ZygLGbiBgV2iQMxbmYPQoCdNt
Rf6lvj20Sz0cfVZWvAw+9HfpMRHYYzQ2UgJkdl4iMaJyNIHhAHCgtMsC/00SGsCn
Wi9iQDtw4O5BbhGPx99J4OipBg0LfAihsOdzgxfv8/jNB9z6OwS4hudmwyHc4PHF
B+ZyEnEJfD3CL8qyaknHZXC18QV0NfnrM1P0NBU/E+WTlFuooywBOG+EWDRmF9E=
=NLMu
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-03-04 10:13 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.
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. [this message]
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=4B8F87B6.9060901@users.sourceforge.net \
--to=legolas558@users.sourceforge.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.