A question regarding the memory errors

Hi all,

I have a question about the memory errors. My system is based on a ARM920T chip with Linux running on it. When I used mtest command in u-boot, I can find there is some error bytes:
Mem error @ 0x33EFFB6C: found 33F00000, expected FF0400C0

Mem error @ 0x33EFFB70: found 33EFFB6C, expected FF0400BF

Mem error @ 0x33EFFB74: found 33EFFB6C, expected FF0400BE

Mem error @ 0x33EFFB78: found FF0400BE, expected FF0400BD

I would like to know how the system will handle these bytes, will them lead to corruption?

I found that TEXT_BASE in my system is defined as 0x33f80000. So the u-boot data should be placed backward from 0x33f80000. But every time when I use mtest to test memory from 0x33f00000 to 0x33f7ffff, the u-boot will die. So it seems that this portion of data is used by u-boot. But I am now sure how u-boot uses this part.

HI all,
I read through the code in uboot and found out that the error happens in IRQ area. The ram structure is as following:

0x33f80000--TEXT_BASE
------------CFG_MALLOC_LEN(512K)
0x33f00000
------------GBL_DATA(128)
0x33efff80
------------IRQ(4K)
0x33efef80
------------FIQ(4K)
0x33efdf80
------------12 bytes
0x33efdf74 SP

According to the above structure, things seems to be easier. But data in the stack is supposed to be very fragile; however, when I use mtest to change the data in the stack, u-boot seems to be working fine. This is really tricky. Is this stack area not used uboot?