From owner-freebsd-emulation@FreeBSD.ORG Fri Oct 15 18:31:37 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CFB5106566C for ; Fri, 15 Oct 2010 18:31:37 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id 56FA58FC1C for ; Fri, 15 Oct 2010 18:31:36 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id A93181E00834; Fri, 15 Oct 2010 20:31:35 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.4/8.14.3) with ESMTP id o9FILsAp041965; Fri, 15 Oct 2010 20:21:54 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.4/8.14.3/Submit) id o9FILsrm041963; Fri, 15 Oct 2010 20:21:54 +0200 (CEST) (envelope-from nox) Date: Fri, 15 Oct 2010 20:21:54 +0200 (CEST) From: Juergen Lock Message-Id: <201010151821.o9FILsrm041963@triton8.kn-bremen.de> To: arundel@freebsd.org X-Newsgroups: local.list.freebsd.emulation In-Reply-To: <20101014184626.GA1961@freebsd.org> Organization: home Cc: freebsd-emulation@freebsd.org Subject: Re: reduce 'unknown op 265' message storm X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2010 18:31:37 -0000 In article <20101014184626.GA1961@freebsd.org> 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