--- In nslu2-linux@
>
> Hello,
> On a second NSLU2 I installed SlugOS 4.8 beta. When I try to login, after entering the password PuTTY says: "Server unexpectedly closed network connection".
> Next action was to connect a HyperTerminal to the serial link ttyS0 (115200 baud 8N1). The last lines in the boot log are:
> INIT: Entering runlevel: 3
> Data CRC cee07dfc != calculated CRC ae2900a4 for node at 0042f66c
> Starting OpenBSD Secure Shell server: sshd
> done.
>
> OpenEmbedded Linux LKG300DB0 ttyS0
>
> SlugOS 4.8-beta LKG300DB0 ttyS0
>
> LKG300DB0 login:
>
> A logread showed:
> Feb 20 14:15:27 (none) user.warn kernel: Data CRC cee07dfc != calculated CRC ae2
> 900a4 for node at 0042f66c (dez. 4.388.460, RAM)
>
> Hence, I assume it could be a RAM failure.
>
> Does anybody know how to do a RAM test?
>
> Regards, Rudolf
> p.s. Going back to UNSLUng 6.10 did work, but I wanted to have SlugOS 4.8.
>
I found a RAM test program: memtester. I checked 21 MB of RAM: all OK
How can I find that CRC error?
Regards, Rudolf
Console output of the RAM test:
root@LKG300DB0:
The authenticity of host '192.168.17.
RSA key fingerprint is 6:2a:8b:49:3c:
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.17.
rudi@192.168.
memtester 100% 10KB 10.4KB/s 00:00
root@LKG300DB0:
total used free shared buffers
Mem: 30376 9140 21236 0 0
Swap: 0 0 0
Total: 30376 9140 21236
root@LKG300DB0:
memtester version 4.0.6 (32-bit)
Copyright (C) 2006 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).
pagesize is 4096
pagesizemask is 0xfffff000
want 21MB (22020096 bytes)
got 21MB (22020096 bytes), trying mlock ...locked.
Loop 1/2:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok
Saturday, February 20, 2010
[nslu2-linux] Re: NSLU2 RAM failure?
__._,_.___
.
__,_._,___
No comments:
Post a Comment