On Fri, 15 Dec 2006 15:35:00 -0600 Michal Sabala <[EMAIL PROTECTED]> wrote:
> On 2006/12/15 at 14:42:08 Andrew Morton <[EMAIL PROTECTED]> wrote > > On Fri, 15 Dec 2006 11:50:30 -0600 > > Michal Sabala <[EMAIL PROTECTED]> wrote: > > > > > On 2006/12/15 at 10:24:15 Trond Myklebust <[EMAIL PROTECTED]> wrote > > > > On Thu, 2006-12-14 at 20:30 -0600, Michal Sabala wrote: > > > > > > > > > > `cat /proc/*PID*/wchan` for all hanging processes contains page_sync. > > > > > > > > Have you tried an 'echo t >/proc/sysrq-trigger' on a client with one of > > > > these hanging processes? If so, what does the output look like? > > > > > > Hello Trond, > > > > > > Below is the sysrq trace output for XFree86 which entered the > > > uninterruptible sleep state on the P4 machine with nfs /home. Please > > > note that XFree86 does not have any files open in /home - as reported by > > > `lsof`. Below, I also listed the output of vmstat. > > > > We'd need to see the trace of all D-state processes, please. Xfree86 might > > just be a victim of a deadlock elsewhere. However there is a problem here.. > > Hi Andrew, > > In most cases only a single process enters the D-state, this time it was > XFree, but I've seen gimp, firefox, gconfd and bash. Once or twice I did > see two or three processes ending up in uninterruptible sleep, but I > suspect they entered this state at different test-mmap.c runs (I left > test-mmap.c running in a bash loop and checked the system after a few > hours). OK, useful info, thanks. > Would it be beneficial to keep running test-mmap.c on this machine until > two or more processes end up in D-state? I can leave this machine > running test-mmap.c over the weekend. No, that's OK. The next step should be for a kernel wrangler to get in there with your testcase. It could well be that lock_page-inside-lock_page thing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
