From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 9 15:24:19 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 017511065676 for ; Sun, 9 Mar 2008 15:24:19 +0000 (UTC) (envelope-from mitchell@wyatt672earp.force9.co.uk) Received: from pih-relay08.plus.net (pih-relay08.plus.net [212.159.14.134]) by mx1.freebsd.org (Postfix) with ESMTP id B43A28FC1C for ; Sun, 9 Mar 2008 15:24:18 +0000 (UTC) (envelope-from mitchell@wyatt672earp.force9.co.uk) Received: from [81.174.213.123] (helo=81-174-213-123.pth-as6.dial.plus.net) by pih-relay08.plus.net with esmtp (Exim) id 1JYN0V-0005vz-If for freebsd-hackers@freebsd.org; Sun, 09 Mar 2008 15:00:12 +0000 From: Frank Mitchell To: freebsd-hackers@freebsd.org Date: Sun, 9 Mar 2008 14:41:30 +0000 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200803091441.30157.mitchell@wyatt672earp.force9.co.uk> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Plusnet-Relay: 0bf135d1bbe34951f0789c8d119a108a Subject: Bugs On 64-Bit Version 6.3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2008 15:24:19 -0000 MOUNTING EXT2FS: I dual-boot with OpenSUSE, sharing data on an Ext2 Partition. The machine is an AMD Sempron with SATA Hard Disk. After installing FreeBSD 64-bit for AMD, I suddenly got problems with mount_ext2fs. Thus: "mount_ext2fs /dev/ad4s2 /mnt" , with various options can yield: "Operation not permitted" "kldload: unsupported file type" I haven't noticed a pattern yet, but I discovered a simple solution: "umount /mnt" Which can work without complaining when I didn't know anything was mounted, like immediately after reboot. MEMORY LOCKING: Recompiling my root-privileged program, I get a System Call failure for: mlockall(MCL_CURRENT); errno says: "Resource temporarily unavailable" But mlock(); works. BIOS TIME SETTING: System Time keeps getting set back, typically by 5 minutes plus. I can't see another explanation yet except my new FreeBSD Installation. Faictz Ce Que Vouldras: Frank Mitchell.