Athlon possible fixes
Quoted 7 lines · Alan Cox
Quoted 6 lines
Quoted 4 lines
There really needs to be a hardware fix... this doesn't stop some application having it's owne optimised code from breaking on some hardware (think games and similation software perhaps).
prefetch is virtually addresses. An application would need access to
/dev/mem
Quoted 1 line
Quoted 1 line
or similar. So the only folks I think it might actually bite are the
Xserver
Quoted 3 lines
Quoted 1 line
people.
Prefetch bugs in hardware have biten Linux/68k as early as '94; a GVP
SCSI
Quoted 3 lines
HBA on the Amiga may touch areas beyond the last valid RAM address when
doing DMA to the last page. Being a burned child from that time
Linux/MIPS
Quoted 3 lines
didn't use the last RAM page just to be on the safe side.
Ralf
I use Duron 750 MHz and has experienced a strange X11 server error. (The motherboard is Gigabyte 7IXE4 and uses AMD 751 and 756 chipsets.)
If I follow a certain steps accessing a web page using netscape, the X11 server crashes reliably. (The server is for ATI rage 128. Xfree86 3.3.6.)
After recompiling the X11 server with debug flag to C compiler, I figured that the X11 server crashes in a bitblt copy againt its backing up store . (I forgot what the proper X11 terminology, but this is where the image data is saved for quick re-display, etc.. You can build an image in a memory buffer and then simply copy it onto screen memory, etc..)
I was a little skeptical to think that the X11 server code has such a bug for SVGA 16bits color server today, and yet was still wondering if
the code might want to access non-allocated area due to some optimized accessing pattern or something.
(Long time ago, I had a similar bug on a dedicated bitblt instruction for a workstation: the bitblt instruction could access outside the boundary of malloc-ed area
since it tries to access as many words as possible if there is a chance to use
long word access. In doing so, the CPU could
step outside sbrk() limit and VM access error condition was generated. Since this access violation occured inside the CPU firmware and not visible to outside, it was very hard to track. Eventually, I figured out
the problem, and always allocated enough trailing area for bitmap storage
just in case the CPU tried to access a few word outside the limit.
Now, back to DuronAthlon problem:
I wasn't following this Athlong bug discussion in depth, thinking it has something to do with VIA chipset alone.
But can the same problem manifest on AMD 751 chipset? That would explain this mysterious X11 server crash beatifully :-)
Happy Hacking,
ci
Quoted 3 lines
I was a little skeptical to think that the X11 server code has such a bug for SVGA 16bits color server today, and yet was still wondering if
Corner cases could exist. If you can replicate it the X folks will be most interested I suspect.
Quoted 4 lines
But can the same problem manifest on AMD 751 chipset? That would explain this mysterious X11 server crash beatifully :-)
The X server doesnt use prefetch instructions...