Am Fri, 15 May 2009 12:05:47 -0400 schrieb John Baldwin <j...@freebsd.org>:
> > (kgdb) x/i 0xffffffff805bbc66 > > 0xffffffff805bbc66 <rt_maskedcopy+6>: movzbl (%rdx),%edx > > Hmm, your %rdx is garbage. :( > > rdx 0xef3fdf377db53afa -1207000745686779142 > > That should at least be > > 0xffffff.......... > > Looks like r9 and r14 have the same odd value. Normally I would see > a more obvious breakage such as one of the 'f' nibbles being set to > '0' or 'e', etc. You could try looking for that odd pointer value in > the route structure or as arguments to other functions in the stack > trace to see if you can find a corrupted data structure. Hi John, I've been testing RAM for 2 hours in user space with 3 parallel processes of sysutils/memtest. What can I say? I just got this in second loop of memtest: Loop 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 : testing 59FAILURE: 0xaaaaaaaaaaaaaaaa != 0x400300007007 at offset 0x007dc608. FAILURE: 0x5555555555555555 != 0xf0000070ef00007 at offset 0x007dc609. FAILURE: 0xaaaaaaaaaaaaaaaa != 0x00004003 at offset 0x007dc60a. FAILURE: 0x5555555555555555 != 0x00004002 at offset 0x007dc60b. FAILURE: 0xaaaaaaaaaaaaaaaa != 0xffffffff807cb4e0 at offset 0x007dc60c. FAILURE: 0x5555555555555555 != 0x00000000 at offset 0x007dc60d. FAILURE: 0xaaaaaaaaaaaaaaaa != 0x000002fa at offset 0x007dc60e. FAILURE: 0x5555555555555555 != 0x00000000 at offset 0x007dc60f. Bit Spread : ok Bit Flip : setting 35^C I think this is obvious enough. Thank you for your patience with me. This was a good hint. I would have never thought of a RAM defect. -- Martin _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
