From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Odd NFS related SIGBUS (& possible fix) Date: Fri, 01 Oct 2010 16:01:30 +1000 Message-ID: <1285912890.2463.71.camel@pasglop> References: <1285734825.14081.87.camel@pasglop> <1285912667.2463.68.camel@pasglop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Trond Myklebust , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Al Viro , linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Nick Piggin Return-path: In-Reply-To: <1285912667.2463.68.camel@pasglop> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 2010-10-01 at 15:57 +1000, Benjamin Herrenschmidt wrote: > I actually just reproduced the lockup on x86_64 with 4 CPUs using > mmapstress01 -p 5 -t 1.3 -f 4096. > > So the trick is to mount /tmp over nfs (so that the mmap'ed file ends up > on nfs) and run mmapstress01 as above. Then try ctrl-C it. > > I'll do a bz for that one. > > I'm now going to try going back kernel versions to see if I can also > reproduce the SIGBUS or other timing issues. So on x86 I didn't get a backtrace, but the VGA console was still responsive somewhat, and I saw mmapstress01 there using 100% CPU and unresponsive to kill -9 (stays in state R). Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html