rt2870 (staging kernel driver) crashes fatally

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

Hello,

I am experiencing the documented crash after intense usage of the wi-fi device.

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

iQEcBAEBAgAGBQJLjiDOAAoJEON28As9epPAacQH/igJUCDKGDLzTnZhllzpR6yn jl7BusfXbpxwBUT6SYB4UQ8RobapmJCGpmcYMlbFTOnXRTK2WmiPrcbORqSBgZJV MZM8kvNoF9fJOg4Yr7mvwaMAaDBhYTPJFaCDcbHeLL06Sg1XLkiCaWnAQNk7IyVp cbVa031vh3lDrRJi7Xbcb2FLU7gxaKU9jc3dQcLWuBzu+Yte+Wn0ymbsVFDKFxQi 3ZObIaIVS3AQDS1seSielPfW3igP9blB05+S6XagGMsrolEE+yXG1SmAmk8+v7dl XHIOQCE51yPwjFQ5ExcM3slCPBUEczEupEj/Urngck8FXnJ8jIHD/AA8z6rIhEI= =Kees
-----END PGP SIGNATURE-----

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 )

Quoted 10 lines

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.

Quoted 3 lines

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.

Quoted 10 lines · Hin-Tak Leung

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.

Quoted 3 lines

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.

Quoted 15 lines · Hin-Tak Leung

Quoted 13 lines

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 )

Quoted 3 lines

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: [email protected]

Ivo

-------- Original Message --------
Subject: Re: rt2870 (staging kernel driver) crashes fatally
From: Ivo van Doorn <[email protected]>
To: Larry Finger <[email protected]>
Date: Fri Mar 05 2010 17:22:41 GMT+0100 (CET)

Quoted 16 lines · Larry Finger

Quoted 15 lines · Hin-Tak Leung

Quoted 13 lines

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 )

Quoted 7 lines

Quoted 3 lines

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: [email protected]

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.

Quoted 22 lines · Daniele C.

-------- Original Message  --------
Subject: Re: rt2870 (staging kernel driver) crashes fatally
From: Ivo van Doorn <[email protected]>
To: Larry Finger <[email protected]>
Date: Fri Mar 05 2010 17:22:41 GMT+0100 (CET)

Quoted 16 lines · Larry Finger

Quoted 15 lines · Hin-Tak Leung

Quoted 13 lines

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 )

Quoted 8 lines

Quoted 7 lines

Quoted 3 lines

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: [email protected]

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.

Your mail wasn't refused for the rt2x00-users mailinglist, we have a filter that prevents non-subscribed members from sending mails to it. Luis and myself are administrating the list, so your mails were approoved, but we forgot to press the button to allow all your mails to the list to be accepted. :)

Quoted 1 line

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.

Good luck. :)

Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Well,

to set the record straight I did reply privately to tell that staging isn't our business.

But my fault was not to point out the correct mailing list for staging.

I hope that my apology is accepted.

Luis Correia

Quoted 46 lines · Ivo van Doorn

Quoted 22 lines · Daniele C.

-------- Original Message --------
Subject: Re: rt2870 (staging kernel driver) crashes fatally
From: Ivo van Doorn <[email protected]>
To: Larry Finger <[email protected]>
Date: Fri Mar 05 2010 17:22:41 GMT+0100 (CET)

Quoted 16 lines · Larry Finger

Quoted 15 lines · Hin-Tak Leung

Quoted 13 lines

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 )

Quoted 8 lines

Quoted 7 lines

Quoted 3 lines

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: [email protected]

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.

Your mail wasn't refused for the rt2x00-users mailinglist, we have a filter that prevents non-subscribed members from sending mails to it. Luis and myself are administrating the list, so your mails were approoved, but we forgot to press the button to allow all your mails to the list to be accepted. :)

Quoted 1 line

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.

Good luck. :)

Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

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 )

On Wed, Mar 3, 2010 at 8:41 AM, Daniele C.
<[email protected]> wrote:
Hello,

I am experiencing the documented crash after intense usage of the wi-fi device.

Best regards,

Quoted 1 line