From owner-freebsd-hackers Tue Nov 14 06:25:14 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA02261 for hackers-outgoing; Tue, 14 Nov 1995 06:25:14 -0800 Received: from cls.net (freeside.cls.de [192.129.50.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id GAA02248 for ; Tue, 14 Nov 1995 06:25:11 -0800 Received: by mail.cls.net (Smail3.1.29.1) from allegro.lemis.de (192.109.197.134) with smtp id ; Tue, 14 Nov 95 14:24 GMT From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Reply-To: grog@lemis.de (Greg Lehey) Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id PAA03522; Tue, 14 Nov 1995 15:18:21 +0100 Message-Id: <199511141418.PAA03522@allegro.lemis.de> Subject: Can't NFS mount with latest -current To: phk@critter.tfs.com Date: Tue, 14 Nov 1995 15:18:21 +0100 (MET) Cc: hackers@freebsd.org (FreeBSD Hackers) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 766 Sender: owner-hackers@freebsd.org Precedence: bulk I've just installed the latest -current, and can't perform NFS mounts. mount_nfs aborts as the result of an error ENOMEM: 187 mount_nfs CALL __sysctl(0xefbfd670,0x2,0xefbfd714,0xefbfd678,0,0) 187 mount_nfs RET __sysctl -1 errno 12 Cannot allocate memory 187 mount_nfs CALL sigprocmask(0x3,0xffffffdf) 187 mount_nfs RET sigprocmask 0 187 mount_nfs CALL getpid 187 mount_nfs RET getpid 187/0xbb 187 mount_nfs CALL kill(0xbb,0x6) 187 mount_nfs PSIG SIGIOT SIG_DFL 187 mount_nfs NAMI "mount_nfs.core" I've traced this back to /usr/src/kern/kern_sysctl.c, but haven't got round to finding out why it dies (it's difficult without an editor and a debugger :-) It looks as if you've seen problems in this area before, though. Greg