Re: glibc 2.1 is now on master in my homedir
> This isn't the problem. modprobe is locking up. Whenever a module is
> autoloaded, the system locks up. The last thing modprobe does is:
>
> SYS_66(
>
> Which should be a 'vfork()'. I'm not entirely sure what is going
> wrong here. In the kernel vfork calls exactly the same code as fork
> (although the entry code is different in sparc64). I would suspect a
> kernel problem, but the older version of libc works.
sparc32 vfork has been broken until very recently. It should be fixed
in the cvs tree.
Anton
Reply to: