Re: AMD64 Machine hardlocks when using memset

[Denis Vlasenko <vda@ilport.com.ua>]

On Thursday 31 March 2005 07:38, Robert Hancock wrote:
> Philip Lawatsch wrote:
> > Hi,
> > 
> > 
> > I do have a very strange problem:
> > 
> > If I memset a ~1meg buffer some thousand times (in the userspace) it
> > will hardlock my machine.
> 
> I thought that this must be impossible, but I tried it on my machine 
> which is very similar (Asus A8N-SLI, Athlon 64 3500+, 2GB RAM) and to my 
> surprise it breaks on mine too with kernel 2.6.11. I tested using the 
> program below. After about a minute or so of this, the machine either 
> locked hard or rebooted spontaneously. When it locked, there was no oops 
> message, the NMI watchdog was not triggered and there was no response to 
>   SysRq commands. (I tested it with and without the NVIDIA module loaded.)
> 
> This seems pretty terrible, a perfectly legal program running as a 
> normal user is hard-locking the machine. Anyone have any suggestions to 
> debug this? Also, can somebody else on an x86_64 try and duplicate this?
> 
> #include <stdio.h>
> #include <stdlib.h>
> #include <string.h>
> 
> int main( int argc, char* argv[] )
> {
> 	char* test = malloc(512*1024*1024);
> 	int i;
> 	for( i=0; i<1000000; i++ )
> 	{
> 		memset( test, 0, 512*1024*1024);
> 	}
> 	free(test);
> 	return 0;
> }

This reminds me on VIA northbridge problem when BIOS enabled
a feature which was experimental and turned out to be buggy.
Was causing oopses ONLY on K7 optimized kernels because
of movntq stores used. They seem to put an awful lot of writes
on the bus.
--
vda

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/