Re: problem with 114 sched.* changes (not the gcc one)

Meelis Roos (mroos@tartu.cyber.ee)
Thu, 6 Aug 1998 14:34:16 +0300

MR> amd and mount -t autofs hang. Also any umount (and probably also mount)
MR> hangs after this. The processes are in D state. No wchan nowadays :(
MR> No entries appear in /proc/mounts for these mounts.

I did some further investigation.
autofs in not faulty :) - it hangs only after amd has ben run.
The first program that causes the problem is amd. After this every
mount operation hangs.

So i straced amd. Yes, it's the mount syscall that hangs:
mount("roos:(pid456)", 0x806cc28, "nfs", 0xc0ed0000, 0xbffff1dc) = -1 ENOSYS (Function not implemented)
mount("roos:(pid456)", 0x806cc28, "nfs", 0xc0ed0000, 0xbffff1dc) = -1 ENOSYS (Function not implemented)
mount("roos:(pid456)", 0x806cc28, "nfs", 0xc0ed0000, 0xbffff1dc) = -1 ENOSYS (Function not implemented)
mount("roos:(pid456)", 0x806cc28, "nfs", 0xc0ed0000, 0xbffff1dc) = -1 ENOSYS (Function not implemented)
mount("roos:(pid456)", 0x806cc28, "nfs", 0xc0ed0000, 0xbffff1dc

Also, when stracing it I discovered that when nfs modules had been loaded
befor, it worked. Did some more tests - yes, the same. It hangs without nfs
(not sure if 100%) and doesn't hang when nfs is loaded or compiled into
the kernel.

Why does it retry the same syscall 5 times when it gets an error?
And why does the hang happen only on the 5th time?
And how is is all related to sched.c changes in 114?

-- 
Meelis Roos (mroos@tartu.cyber.ee)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html