-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Kalle Valo schrieb: > What about N800 or is this reproducible only on 770? Unfortunately, I couldn't test this because I only have a 770... > What are your WLAN settings? Is this related to some particular > settings, like WPA for instance? I don't use WPA but I experienced it both without any encryption and with my WEP network. The fact that already scanning for networks causes the problem makes me think that it doesn't depend much on special settings... Also, the address stays the same in all cases. > How long does it take you to see the corruption with memtester? With test sizes of about 24 MB, chances seem to be very good to catch the bad bytes. In other words, usually if I run memtester 24 after booting and still without WLAN, everything is ok. As soon as I click on "Choose connection..." and scanning starts, I see FAILURE messages from memtester. I don't have to wait for it. If they don't show up, it means memtester didn't get the corrupted bytes. Then it usually helps to start it again with a little bigger size. Also, when I shut down the WLAN connection, the errors immediately stop. If you have more questions, let me know. I'll also file my bug report soon. Best regards, Tilman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG6Fz09ZPu6Yae8lkRAhzKAKCny84mXBOxMoB5zxaa+7JGZ5XGkQCfW3l3 VmAD+N97YUAtnAfGpZqJG2Q= =OJRe -----END PGP SIGNATURE-----
