In article <[email protected]> you write:
>
>--ZPt4rx8FFjLCG7dd
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>
>hi there,
Hi! :)
>
>i see a lot of these warnings:
>
>'linux_sys_futex: unknown op 265'
>
>although there is no support in the linuxulator for opcode 256
>(FUTEX_CLOCK_REALTIME) it is possible to handle some of these cases earlier.
>
>FUTEX_CLOCK_REALTIME can be used to tell linux to use CLOCK_REALTIME instead of
>CLOCK_MONOTONIC. FUTEX_CLOCK_REALTIME however must only be set, if either
>FUTEX_WAIT_BITSET or FUTEX_WAIT_REQUEUE_PI are set too. if that's not the case
>we can die with -ENOSYS right at the beginning.
Hmm looks like that's not enough to fix kern/148076, i.e. emerge...
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/148076
This is procstat -k of the hanging emerge process:
PID TID COMM TDNAME KSTACK
41734 100450 python2.6 - mi_switch sleepq_catch_signals
sleepq_wait_sig _cv_wait_sig tty_wait tty_drain ttydev_leave ttydev_close
devfs_close vn_close vn_closefile devfs_close_f _fdrop closef kern_close
ia32_syscall Xint0x80_syscall
(Disclaimer: I applied the patch on 8.1 and just reloaded linux.ko,
maybe head has other fixes that are also needed here.)
Cheers,
Juergen
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "[email protected]"
