On Fri, 2002-09-06 at 01:48, Andrew Morton wrote: > > I've seen this on 6 diffrent machines (master.kernel.org is one of > > them). I have a fileserver here that hits this all the time, sometimes > > as much as a few times a day. > > > > What have you seen? I doubt if it's a memory leak - they tend to > be preceded by a very obvious swapstorm. > > It seems that you have boxes which lock up, and we have no more info > than that. > > If the machine remains pingable then yes, it may be a VM deadlock/livelock. > We'd need to know the kernel version, system description, and a SYSRQ-T > trace passed through ksymoops would be helpful. They lock up, they respond to ping and accept connections. But nothing responds in userspace. You can switch consoles and sysrq works but otherwise they are unresponsive to keyboard input. No kernelmessages or anything and no heavy swapout storms before lockup. The fileserver is running 2.4.19-pre8-xfs (I've seen it with vanilla 2.4.19 aswell on other machines), Athlon 1600+, 256MB ram, 1+ TB disk (IDE). I can't seem to find my traces right now but I know they included references to empty_zero_page, I'll see if I can get a new trace next time. Upgraded to 2.4.19-xfs with kdb yesterday, maybe that will give some more info. I've seen the same thing on my workstation (2.4.19 with ext3) a few times, the last time it happened was when I switched tabs in galeon. -- /Martin Never argue with an idiot. They drag you down to their level, then beat you with experience.
This is a digitally signed message part