From owner-freebsd-stable@FreeBSD.ORG Sun Jul 20 11:32:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A082F37B401 for ; Sun, 20 Jul 2003 11:32:00 -0700 (PDT) Received: from hobbes.biaix.org (86.Red-213-97-212.pooles.rima-tde.net [213.97.212.86]) by mx1.FreeBSD.org (Postfix) with SMTP id 802CD43FA3 for ; Sun, 20 Jul 2003 11:31:58 -0700 (PDT) (envelope-from joan@iaeste-catalunya.upc.es) Received: (qmail 91076 invoked from network); 20 Jul 2003 18:25:20 -0000 Received: from peque.biaix.org (HELO iaeste-catalunya.upc.es) (192.168.124.3) by 0 with SMTP; 20 Jul 2003 18:25:20 -0000 Message-ID: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> Date: Sun, 20 Jul 2003 20:27:00 +0200 From: Joan Picanyol i Puig User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; ca; rv:1.3) Gecko/20030312 X-Accept-Language: ca-es MIME-Version: 1.0 Followup-To: freebsd-stable@freebsd.org,joan@iaeste-catalunya.upc.es To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: mismatching vinum configurations X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jul 2003 18:32:00 -0000 Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic way to recover the data? Most of the data is mirrored over da0 & da1, but I can't start any of the mirrored volumes (I get 'Drive is down') What should I do to access the mirrored volumes? tks -- pica From owner-freebsd-stable@FreeBSD.ORG Sun Jul 20 13:07:28 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D9BC37B404 for ; Sun, 20 Jul 2003 13:07:28 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64DF543FB1 for ; Sun, 20 Jul 2003 13:07:27 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6KK7QwO001012; Sun, 20 Jul 2003 13:07:26 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6KK7QZU013315; Sun, 20 Jul 2003 13:07:26 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h6KK7Q73013314; Sun, 20 Jul 2003 13:07:26 -0700 (PDT) (envelope-from marcel) Date: Sun, 20 Jul 2003 13:07:26 -0700 From: Marcel Moolenaar To: Joan Picanyol i Puig Message-ID: <20030720200726.GB13216@dhcp01.pn.xcllnt.net> References: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> User-Agent: Mutt/1.5.4i cc: freebsd-stable@freebsd.org Subject: Re: mismatching vinum configurations X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jul 2003 20:07:28 -0000 On Sun, Jul 20, 2003 at 08:27:00PM +0200, Joan Picanyol i Puig wrote: > Hi, > > I had a power failure, and the on-disk configuration for vinum went > bizarre. The logs read from disks are at http://biaix.org/pk/debug/ > (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously > wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead > drive? Can I force vinum to use the other's drive configuration? What's > the less traumatic way to recover the data? I had the same problem twice. Also a power failure. There was no way I could fix it without trauma. I had to do the following (and I'm not joking about the reboots): WARNING: do not follow the steps below if you're not entirely sure what you're doing unless you already have nothing to lose... 1. Nuke the complete configuration, but make sure you know exactly what it was. 2. Reconfigure vinum from scratch in exactly the same way it was before. 3. Reboot the machine. I got kernel panics trying to recover my vinum volumes and that only made matters worse (it always can). 4a.For mirrored volumes you should be able to mark one drive as up, and mark the other(s) as empty (ie manually set the state). This forces a complete resync. Let it finish and reboot the machine afterwards. 4b.For RAID5 volumes you manually have to mark all disks as up and rebuild the parity. After that it's probably good to reboot the machine avoid kernel panics. Reboot twice if you're paranoid. Verify that the parity is ok! 5. fsck(8). 6. Drink lot's of alcoholic beverages to recover yourself after you verified you recovered vinum. 7. Reboot yourself. FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-stable@FreeBSD.ORG Sun Jul 20 13:48:17 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE6DA37B401 for ; Sun, 20 Jul 2003 13:48:17 -0700 (PDT) Received: from hog.ivil.org (as5-4-8.far.s.bonet.se [217.215.110.193]) by mx1.FreeBSD.org (Postfix) with SMTP id E2AF643FBD for ; Sun, 20 Jul 2003 13:48:15 -0700 (PDT) (envelope-from tobias@ivil.org) Received: (qmail 4323 invoked from network); 20 Jul 2003 20:50:54 -0000 Received: from unknown (HELO ivil.org) (192.168.0.2) by as5-4-8.far.s.bonet.se with SMTP; 20 Jul 2003 20:50:54 -0000 Message-ID: <3F1B000E.5090107@ivil.org> Date: Sun, 20 Jul 2003 22:48:14 +0200 From: Tobias Larsson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <3F15050C.6050404@ivil.org> <20030716122914.P27866@carver.gumbysoft.com> <3F172523.5090301@ivil.org> <20030718140040.U46097@carver.gumbysoft.com> In-Reply-To: <20030718140040.U46097@carver.gumbysoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: Compiling problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jul 2003 20:48:18 -0000 No strange things in the logs. I tried supping to CURRENT aswell - same make buildworld problem. :-( Do you have any more ideas? I don't want to do a complete reinstall. //Tobias ===> share/termcap gzip -cn /usr/src/share/termcap/termcap.5 > termcap.5.gz TERM=dumb TERMCAP=dumb: ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder Incomplete termcap entry *** Error code 1 Stop in /usr/src/share/termcap. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Doug White wrote: >On Fri, 18 Jul 2003, Tobias Larsson wrote: > > > >>Hi, >> >>The same problem is still there, even after deleting the whole /usr/src >>and resupping :-( >> >>MD5 (/usr/src/share/termcap/termcap.src) = 9301473e4dcf275418c1c88a8894c9a2 >> >>Any more ideas? >> >> > >Are you getting any SIGBUS or SIGSEGV warnings in your logs? Something is >certainly different with your system than everyone else's... > > > > From owner-freebsd-stable@FreeBSD.ORG Sun Jul 20 18:05:45 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A64C137B401 for ; Sun, 20 Jul 2003 18:05:45 -0700 (PDT) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id D261B43F3F for ; Sun, 20 Jul 2003 18:05:43 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id B9292526A9; Mon, 21 Jul 2003 10:35:41 +0930 (CST) Date: Mon, 21 Jul 2003 10:35:41 +0930 From: Greg 'groggy' Lehey To: Joan Picanyol i Puig Message-ID: <20030721010541.GE11810@wantadilla.lemis.com> References: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rErXCrER28iYcLtG" Content-Disposition: inline In-Reply-To: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-stable@freebsd.org Subject: Re: mismatching vinum configurations X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 01:05:45 -0000 --rErXCrER28iYcLtG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sunday, 20 July 2003 at 20:27:00 +0200, Joan Picanyol i Puig wrote: > Hi, > > I had a power failure, and the on-disk configuration for vinum went > bizarre. The logs read from disks are at http://biaix.org/pk/debug/ > (log.$DEVICE files).=20 They're not much help, and a lot of the files are inaccessible. The output of 'vinum dumpconfig' would be easier. > The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty > sure the others are ok. Is this a 'virtually' dead drive? It's not a hardware problem, if that's what you mean. > Can I force vinum to use the other's drive configuration? Yes. > What's the less traumatic way to recover the data? I've never tried this, but a thing you could do is: vinum -> setdaemon 4 (turn off config updates) vinum -> read /dev/ad0s1d (or another drive with valid config) vinum -> start This could bring back your entire configuration. If anything goes wrong, it's not serious, because the config updates are turned off. Why do you have two drives on each SCSI disk? > Most of the data is mirrored over da0 & da1, but I can't start any of > the mirrored volumes (I get 'Drive is down') What should I do to access > the mirrored volumes? If 'start' above doesn't work, you can try running a Vinum config file like: drive barracuda device /dev/da0s1f Let me know how it works out. Greg -- See complete headers for address and phone numbers --rErXCrER28iYcLtG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/GzxlIubykFB6QiMRAgssAJ9t8Q2TCqjdgCyscifKU13igrkw0gCdHsfV 4bYj7jiFOk6nZ3051JP84Bk= =6s90 -----END PGP SIGNATURE----- --rErXCrER28iYcLtG-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 20 23:03:53 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DB2C37B401; Sun, 20 Jul 2003 23:03:53 -0700 (PDT) Received: from triangle.rtp.FreeBSD.Org (triangle.rtp.FreeBSD.org [192.58.184.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id C72C743F75; Sun, 20 Jul 2003 23:03:52 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from triangle.rtp.FreeBSD.Org (localhost [127.0.0.1]) h6L63q27060857; Mon, 21 Jul 2003 02:03:52 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by triangle.rtp.FreeBSD.Org (8.12.9/8.12.9/Submit) id h6L63pvL060856; Mon, 21 Jul 2003 06:03:51 GMT Date: Mon, 21 Jul 2003 06:03:51 GMT Message-Id: <200307210603.h6L63pvL060856@triangle.rtp.FreeBSD.Org> X-Authentication-Warning: triangle.rtp.FreeBSD.Org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: stable@freebsd.org, i386@freebsd.org Precedence: bulk Subject: [-STABLE tinderbox] failure on i386/pc98 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 06:03:53 -0000 TB --- 2003-07-21 05:27:28 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-07-21 05:27:28 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-07-21 05:33:30 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/RELENG_4/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-07-21 06:02:33 - building generic kernel TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Jul 21 06:02:33 GMT 2003 [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/../include -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -mpreferred-stack-boundary=2 /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/kern/tty_tty.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/../include -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -mpreferred-stack-boundary=2 /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/kern/uipc_accf.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/../include -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -mpreferred-stack-boundary=2 /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/kern/uipc_domain.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/../include -I/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -mpreferred-stack-boundary=2 /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/kern/uipc_mbuf.c /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/kern/uipc_mbuf.c: In function `m_clreflimit': /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/kern/uipc_mbuf.c:1624: `m_clreflimithits' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/kern/uipc_mbuf.c:1624: (Each undeclared identifier is reported only once /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/kern/uipc_mbuf.c:1624: for each function it appears in.) *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/RELENG_4/i386/pc98/src. TB --- 2003-07-21 06:03:51 - /usr/bin/make returned exit code 1 TB --- 2003-07-21 06:03:51 - ERROR: failed to build generic kernel TB --- 2003-07-21 06:03:51 - tinderbox aborted From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 02:18:06 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0DC537B401 for ; Mon, 21 Jul 2003 02:18:06 -0700 (PDT) Received: from mail.spod.org (opal.spod.org [195.92.99.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C95E43FBD for ; Mon, 21 Jul 2003 02:18:06 -0700 (PDT) (envelope-from yann@spod.org) Received: from yann by mail.spod.org with local (Exim 3.36 #1) id 19eWo0-0007D4-00 for freebsd-stable@freebsd.org; Mon, 21 Jul 2003 10:18:04 +0100 Date: Mon, 21 Jul 2003 10:18:04 +0100 From: Yann Golanski To: freebsd-stable@freebsd.org Message-ID: <20030721091804.GA27424@kierun.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . User-Agent: Mutt/1.5.4i Sender: Yann Golanski Subject: Mozilla port. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 09:18:07 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have a very strange problem with Mozilla since I updated it to the latest stable. The font used on the menus are rendered extermly badly such as lots of white spaces between the letters, large blocky font. The font option does not seem to change any of those fonts which makes me think it maybe something to do with X11. However, none of the other things I use have any font issues... Any idea what's wrong? --=20 yann@kierun.org -=3D*=3D- www.kierun.= org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/G6/K91FwBp3iYxgRAuS9AKCSEqKsGLL4QW3h2AiwKrF79Bg/oQCdHqmD hVdo7pyWl8xLwzWna8ZlcV4= =XXeX -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 02:22:45 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9561F37B401 for ; Mon, 21 Jul 2003 02:22:45 -0700 (PDT) Received: from morpheus.webteckies.org (node123e0.a2000.nl [24.132.35.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D7E943FAF for ; Mon, 21 Jul 2003 02:22:44 -0700 (PDT) (envelope-from freebsd-stable@webteckies.org) Received: from ghost.lan.webteckies.org (ghost.lan.webteckies.org [192.168.1.10]) by morpheus.webteckies.org (Postfix) with ESMTP id 91F8A107D0; Mon, 21 Jul 2003 11:22:18 +0200 (CEST) From: Melvyn Sopacua Organization: WebTeckies.org To: Yann Golanski , freebsd-stable@freebsd.org Date: Mon, 21 Jul 2003 11:22:34 +0200 User-Agent: KMail/1.5.2 References: <20030721091804.GA27424@kierun.org> In-Reply-To: <20030721091804.GA27424@kierun.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307211122.34292.freebsd-stable@webteckies.org> Subject: Re: Mozilla port. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 09:22:45 -0000 On Monday 21 July 2003 11:18, Yann Golanski wrote: [ .. ] > The font used on the menus are rendered extermly badly > such as lots of white spaces between the letters, large blocky font. [ ... ] > Any idea what's wrong? From: /usr/ports/www/mozilla/Makefile: .if !defined(WITHOUT_XFT) LIB_DEPENDS+= Xft.2:${PORTSDIR}/x11-fonts/Xft .if exists(${X11BASE}/lib/X11/fonts/mozilla/fonts.dir) BROKEN= Mozilla and Xft2 render the mozilla-fonts \ illegibly. Please remove the mozilla-fonts package. .endif .endif -- Melvyn ======================================================= FreeBSD ghost.lan.webteckies.org 4.8-STABLE FreeBSD 4.8-STABLE #0: Sat Jul 5 18:39:46 CEST 2003 root@ghost.lan.webteckies.org:/usr/obj/usr/src/sys/GHOST i386 ======================================================= From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 02:23:18 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D221437B401 for ; Mon, 21 Jul 2003 02:23:18 -0700 (PDT) Received: from vivaldi.meteo.fr (vivaldi.meteo.fr [137.129.28.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0FC843FAF for ; Mon, 21 Jul 2003 02:23:16 -0700 (PDT) (envelope-from igor.pokrovsky@cnrm.meteo.fr) Received: from cti825.cnrm.meteo.fr (localhost.meteo.fr [127.0.0.1]) JAA03900 for ; Mon, 21 Jul 2003 09:22:57 GMT Received: from xdata.cnrm.meteo.fr (xdata.cnrm.meteo.fr [137.129.150.2]) LAA05826; Mon, 21 Jul 2003 11:22:53 +0200 (METDST) Received: from exmatis1.cnrm.meteo.fr (exmatis1.cnrm.meteo.fr [137.129.157.46]) by xdata.cnrm.meteo.fr with ESMTP (8.9.3 (PHNE_24419)/8.7.1) id LAA17775; Mon, 21 Jul 2003 11:24:04 +0200 (METDST) Received: from exmatis1.cnrm.meteo.fr (localhost [127.0.0.1]) h6L9JwhB017739; Mon, 21 Jul 2003 11:19:58 +0200 (CEST) (envelope-from pokrovsi@exmatis1.cnrm.meteo.fr) Received: (from pokrovsi@localhost) by exmatis1.cnrm.meteo.fr (8.12.9/8.12.9/Submit) id h6L9JwfP017738; Mon, 21 Jul 2003 11:19:58 +0200 (CEST) Date: Mon, 21 Jul 2003 11:19:58 +0200 From: Igor Pokrovsky To: Yann Golanski Message-ID: <20030721091958.GA17706@exmatis1.cnrm.meteo.fr> Mail-Followup-To: Igor Pokrovsky , Yann Golanski , freebsd-stable@freebsd.org References: <20030721091804.GA27424@kierun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030721091804.GA27424@kierun.org> User-Agent: Mutt/1.4.1i X-Accept-Language: ru X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (cti825/CNRM) Organization: METEO FRANCE(CNRM) cc: freebsd-stable@freebsd.org Subject: Re: Mozilla port. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Igor Pokrovsky List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 09:23:19 -0000 On Mon, Jul 21, 2003 at 10:18:04AM +0100, Yann Golanski wrote: > > I have a very strange problem with Mozilla since I updated it to the > latest stable. The font used on the menus are rendered extermly badly > such as lots of white spaces between the letters, large blocky font. > The font option does not seem to change any of those fonts which makes > me think it maybe something to do with X11. However, none of the other > things I use have any font issues... > > Any idea what's wrong? Try upgrading fontconfig to 2.2.90_3 (latest). -- Igor From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 02:35:53 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B21B37B401 for ; Mon, 21 Jul 2003 02:35:53 -0700 (PDT) Received: from mail.spod.org (opal.spod.org [195.92.99.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6146943FAF for ; Mon, 21 Jul 2003 02:35:52 -0700 (PDT) (envelope-from yann@spod.org) Received: from yann by mail.spod.org with local (Exim 3.36 #1) id 19eX5C-0007WX-00; Mon, 21 Jul 2003 10:35:50 +0100 Date: Mon, 21 Jul 2003 10:35:50 +0100 From: Yann Golanski To: Igor Pokrovsky , freebsd-stable@freebsd.org Message-ID: <20030721093550.GA28396@kierun.org> References: <20030721091804.GA27424@kierun.org> <20030721091958.GA17706@exmatis1.cnrm.meteo.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <20030721091958.GA17706@exmatis1.cnrm.meteo.fr> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . User-Agent: Mutt/1.5.4i Sender: Yann Golanski Subject: Re: Mozilla port. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 09:35:53 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Igor Pokrovsky on Mon, Jul 21, 2003 at 11:19:58 +0200 > > Any idea what's wrong? >=20 > Try upgrading fontconfig to 2.2.90_3 (latest). And this fixed it. I hate it when this happens and I try to fix something BEFORE running my daily portupgrade. Many thanks indeed. --=20 yann@kierun.org -=3D*=3D- www.kierun.= org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/G7P191FwBp3iYxgRAs+SAKCwDjxbn9RHzeoF09CZlM0BVJGzKwCaA9iC 5PSM/MzwQkVbw59KOnXm9xM= =C0U/ -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 12:29:53 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 776C937B404 for ; Mon, 21 Jul 2003 12:29:53 -0700 (PDT) Received: from electricrain.com (electricrain.com [64.71.143.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE63743F75 for ; Mon, 21 Jul 2003 12:29:52 -0700 (PDT) (envelope-from fuzzy@electricrain.com) Received: (qmail 21822 invoked by uid 540); 21 Jul 2003 19:29:52 -0000 Date: Mon, 21 Jul 2003 12:29:52 -0700 From: Chris Doherty To: freebsd-stable@freebsd.org Message-ID: <20030721192952.GE23226@zot.electricrain.com> References: <3F19C78A.7030008@mac.com> <20030719233535.GF77396@sunbay.com> <3F19D8D3.1040401@mac.com> <87vftyoy91.fsf@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87vftyoy91.fsf@inf.enst.fr> User-Agent: Mutt/1.4i X-Operating-System: XEmacs X-Koan: mu. Organization: The Inside Foundation Subject: Re: A patch to man to handle "man.1"... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: chris-freebsd@randomcamel.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 19:29:53 -0000 On Sun, Jul 20, 2003 at 02:08:58AM +0200, Samuel Tardieu said: > >>>>> "Chuck" == Chuck Swiger writes: > > Chuck> Thanks for this example. However, if you try the patch, you'll > Chuck> discover that this case also works properly: > > It works only by chance. If ld-elf.so.1 was in section 2 for example, > your patch would prevent it from being found as the section is forced > to 1. > > Sam seems pretty simple: 1) first check to see if there's a manpage for the literal argument (e.g. "ld-elf.so.1") 2) if that fails, treat the trailing digit as a section specifier--i.e. look for "ld-elf.so" in section 1. 3) if that also fails, report that not only was there a "ld-elf.so.1" in any section, but there was also no "ld-elf.so" in section 1. does that cover all cases? seems like this is a useful syntax to add on--anything to make man(7) more usable is a good thing IMO. :-) chris ------------------------------- Chris Doherty chris [at] randomcamel.net "I think," said Christopher Robin, "that we ought to eat all our provisions now, so we won't have so much to carry." -- A. A. Milne ------------------------------- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 12:57:43 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C211B37B401 for ; Mon, 21 Jul 2003 12:57:43 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3CA943F85 for ; Mon, 21 Jul 2003 12:57:42 -0700 (PDT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19egkT-0005nZ-00 for ; Mon, 21 Jul 2003 21:55:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19egjH-0005hp-00 for ; Mon, 21 Jul 2003 21:53:51 +0200 From: Samuel Tardieu Date: Mon, 21 Jul 2003 21:47:54 +0200 Organization: Avian Carrier & Friends Lines: 15 Message-ID: <87el0j1x1x.fsf@inf.enst.fr> References: <3F19C78A.7030008@mac.com> <20030719233535.GF77396@sunbay.com> <3F19D8D3.1040401@mac.com> <87vftyoy91.fsf@inf.enst.fr> <20030721192952.GE23226@zot.electricrain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org Mail-Copies-To: sam@rfc1149.net User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.5 (cauliflower, i386--freebsd) Cancel-Lock: sha1:YyT8H7zhAlF+v1CM/MNybrKKV68= X-Leafnode-NNTP-Posting-Host: 127.0.0.1 Sender: news Subject: Re: A patch to man to handle "man.1"... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 19:57:44 -0000 >>>>> "Chris" == Chris Doherty writes: Chris> does that cover all cases? seems like this is a useful syntax Chris> to add on--anything to make man(7) more usable is a good thing Chris> IMO. :-) It may cover all the cases, but I'm still undecided whether it makes things simpler or not :-) After all, it's the very same number of characters to type and complexity to add (your first implementation looked ok but had an hidden flaw, wouldn't your second have one as well?). Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 13:21:04 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32BBD37B401 for ; Mon, 21 Jul 2003 13:21:04 -0700 (PDT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FBAC43FAF for ; Mon, 21 Jul 2003 13:21:03 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by out006.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030721202102.LVVG16647.out006.verizon.net@mac.com>; Mon, 21 Jul 2003 15:21:02 -0500 Message-ID: <3F1C4B2A.7090107@mac.com> Date: Mon, 21 Jul 2003 16:20:58 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: chris-freebsd@randomcamel.net References: <3F19C78A.7030008@mac.com> <20030719233535.GF77396@sunbay.com> <3F19D8D3.1040401@mac.com> <87vftyoy91.fsf@inf.enst.fr> <20030721192952.GE23226@zot.electricrain.com> In-Reply-To: <20030721192952.GE23226@zot.electricrain.com> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [141.149.47.46] at Mon, 21 Jul 2003 15:21:02 -0500 cc: freebsd-stable@freebsd.org Subject: Re: A patch to man to handle "man.1"... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 20:21:04 -0000 Chris Doherty wrote: [ ... ] > seems pretty simple: > > 1) first check to see if there's a manpage for the literal argument > (e.g. "ld-elf.so.1") > > 2) if that fails, treat the trailing digit as a section > specifier--i.e. look for "ld-elf.so" in section 1. > > 3) if that also fails, report that not only was there a "ld-elf.so.1" in > any section, but there was also no "ld-elf.so" in section 1. > > does that cover all cases? seems like this is a useful syntax to add > on--anything to make man(7) more usable is a good thing IMO. :-) Thanks for the vote in favor of the proposed syntax, as well as for your thoughts about an implementation that would remain backwards compatible. The only difficulty is that I would probably choose to re-write 'man' from scratch rather than try to make non-localized/extensive changes to the existing code. This can be explained simply, even: the function is_section() has side effects and changes some global variable named 'longsec' which relates to the 'shortsec' variable seen in my patch in ways that I don't want to understand further. :-) On the other hand, are there any other implementations of 'man' around? I seem to recall something called 'polaris' which implemented browsable links between manpages (similar to GNU info pages, come to think of it)...? -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 13:32:15 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A50437B401 for ; Mon, 21 Jul 2003 13:32:15 -0700 (PDT) Received: from snoopy.pacific.net.au (snoopy.pacific.net.au [61.8.0.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CA0D43F85 for ; Mon, 21 Jul 2003 13:32:14 -0700 (PDT) (envelope-from memetical@yahoo.com.au) Received: from sunny.pacific.net.au (sunny.pacific.net.au [203.2.228.40]) h6LKWCiI021312 for ; Tue, 22 Jul 2003 06:32:12 +1000 Received: from wisma.pacific.net.au (wisma.pacific.net.au [210.23.129.72]) by sunny.pacific.net.au with ESMTP id h6LKWCQg021350 for ; Tue, 22 Jul 2003 06:32:12 +1000 (EST) Received: from zhadum.dnsalias.net (dyn153.syd7.homedsl.pacific.net.au [202.7.78.153]) by wisma.pacific.net.au (8.12.9/8.12.9) with ESMTP id h6LKWB8E025030 for ; Tue, 22 Jul 2003 06:32:11 +1000 (EST) Received: from psi.starfleet.org.au (psi.starfleet.org.au [172.16.0.3]) by arthur.starfleet.org.au (Postfix) with ESMTP id 4F6879438 for ; Tue, 22 Jul 2003 06:32:11 +1000 (EST) Received: by psi.starfleet.org.au (Postfix, from userid 1000) id 8EF7C6ECCC; Tue, 22 Jul 2003 06:32:10 +1000 (EST) Date: Tue, 22 Jul 2003 06:32:09 +1000 From: Rudolph Pereira To: freebsd-stable@FreeBSD.ORG Message-ID: <20030721203209.GO1414@starfleet.org.au> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <006601c29cab$ec3a9c80$0100000a@D9NLZD0J> <20021205234945.GA70487@tassie.net.au> <1039133969.1728.25.camel@chowder.gsoft.com.au> <20021206011334.GB70929@tassie.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021206011334.GB70929@tassie.net.au> User-Agent: Mutt/1.4.1i Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 20:32:16 -0000 Just to drag this thread on a bit further ... I've been looking into these little boxes, thinking I could use one as a firewall/gateway. My one requirement is that it would need to have two PCI slots (one can be low-profile), and although I've seen PCI riser cards that can give me two slots, they've been rare, and cases that are suitable (i.e have the space, and back panels are compatible) even rarer (I've yet to find one). Does anyone know of any such cases (it'd be even better if they're available in au)? thanks From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 14:34:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1F8137B409 for ; Mon, 21 Jul 2003 14:34:00 -0700 (PDT) Received: from pop018.verizon.net (pop018pub.verizon.net [206.46.170.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59F2543FB1 for ; Mon, 21 Jul 2003 14:33:59 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by pop018.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030721213358.KAYZ11703.pop018.verizon.net@mac.com> for ; Mon, 21 Jul 2003 16:33:58 -0500 Message-ID: <3F1C5C42.2090207@mac.com> Date: Mon, 21 Jul 2003 17:33:54 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <3F19C78A.7030008@mac.com> <20030719233535.GF77396@sunbay.com> <3F19D8D3.1040401@mac.com> <87vftyoy91.fsf@inf.enst.fr> <20030721192952.GE23226@zot.electricrain.com> <87el0j1x1x.fsf@inf.enst.fr> In-Reply-To: <87el0j1x1x.fsf@inf.enst.fr> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [141.149.47.46] at Mon, 21 Jul 2003 16:33:58 -0500 Subject: Re: A patch to man to handle "man.1"... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 21:34:01 -0000 Samuel Tardieu wrote: [ ... ] > It may cover all the cases, but I'm still undecided whether it makes > things simpler or not :-) After all, it's the very same number of > characters to type and complexity to add (your first implementation > looked ok but had an hidden flaw, wouldn't your second have one as > well?). Thanks for your feedback, Sam. You've raised several points which I will attempt to address. First, any change to 'man' probably will be expected to be 100% backwards-compatible with the behavior of the existing command, at least as a controllable default. Yes? OK. -- Most people, particularly novices, are going to type "man foo" without any section number. People often don't realize that there _are_ several 'versions' of a manpage, or different manpages of the same basename in different sections. Until you show them, such people don't even realize that "man 2 sync" and "man 8 sync" display different things. The following use case helps address such problems. Type "man sync" then and get: 7-shot% man sync sync.2 sync.8 syncer.4 syncok.3 ...displayed, with additional s cycling through the list of items. Whether shell completion saves typing is less important than whether it can aid comprehension. [This is in response to your comment vis-a-vis "simpler".] -- I acknowledge the point that my patch would make "man foo.1" not work if there was a foo.1.2 manpage in section two. [ It is at least arguable that manpage authors should be able to use any basename they want, although life is much less confusing if one restricts basenames to not have a period in them. More to the point, such manpages exist, so...moot. ] On the other hand, the suggestion made by Chris appears to address the concern of retaining the prior behavior for this case. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 14:59:31 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E71B37B407 for ; Mon, 21 Jul 2003 14:59:31 -0700 (PDT) Received: from ocortes.net1.nerim.net (ocortes.net1.nerim.net [213.41.136.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C68943F3F for ; Mon, 21 Jul 2003 14:59:30 -0700 (PDT) (envelope-from olive@deep-ocean.org) Received: from [192.168.0.23] (syrenna.deep-ocean.local [192.168.0.23]) by ocortes.net1.nerim.net (Postfix) with ESMTP id 7CC335EF02 for ; Mon, 21 Jul 2003 23:52:20 +0200 (CEST) From: Olivier Cortes To: Mailing-List FreeBSD Stable Content-Type: text/plain Message-Id: <1058824474.20464.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 21 Jul 2003 23:54:35 +0200 Content-Transfer-Encoding: 7bit Subject: portupgrade -PP needs glasses ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 21:59:31 -0000 does anybody have the same problem as I have : (running CURRENT, but the problem occurs on STABLE too) latest portupgrade, ports cvsuped today. fully reproductible with any package... am i missing something ? i hope yes... portinstall -PP teTeX ---> Checking the availability of the latest package of 'print/teTeX' ---> Fetching the package(s) for 'teTeX-2.0.2_2' (print/teTeX) ---> Fetching teTeX-2.0.2_2 Receiving /var/tmp/teTeX-2.0.2_2.tbz (55422581 bytes): 100% (ETA 00:00) 55422581 bytes transferred in 925.5 seconds (58.48 kBps) ---> Downloaded as teTeX-2.0.2_2.tbz ---> Identifying the package /var/tmp/teTeX-2.0.2_2.tbz ---> Saved as /usr/ports/packages/All/teTeX-2.0.2_2.tbz ** Could not fetch the latest version '2.0.2_2' ** The package of 'print/teTeX' is not found. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! print/teTeX (package not found) why doesn't portupgrade see it has the good package ???? this bug has been here for a long time. now that i don't have much compile time, i try to get binary packages, but that doesn't seem to work. correct me if i'm doing something wrong. Olivier From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 15:12:25 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00B7537B401 for ; Mon, 21 Jul 2003 15:12:25 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-67-119-53-152.dsl.lsan03.pacbell.net [67.119.53.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4482D43F75 for ; Mon, 21 Jul 2003 15:12:24 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id B9EEE66E8C; Mon, 21 Jul 2003 15:12:23 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 8FB8DC0D; Mon, 21 Jul 2003 15:12:23 -0700 (PDT) Date: Mon, 21 Jul 2003 15:12:23 -0700 From: Kris Kennaway To: Olivier Cortes Message-ID: <20030721221223.GA688@rot13.obsecurity.org> References: <1058824474.20464.4.camel@localhost> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <1058824474.20464.4.camel@localhost> User-Agent: Mutt/1.4.1i cc: Mailing-List FreeBSD Stable Subject: Re: portupgrade -PP needs glasses ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 22:12:25 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 21, 2003 at 11:54:35PM +0200, Olivier Cortes wrote: > does anybody have the same problem as I have : > (running CURRENT, but the problem occurs on STABLE too) > latest portupgrade, ports cvsuped today. > fully reproductible with any package... > am i missing something ? i hope yes... Have you reported the problem to the portupgrade author? Kris --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/HGVHWry0BWjoQKURAgdcAJ9Yq/KzPIPDpvU1VouHNLFn07j8OwCfcyTu 9pRyYv7yldbGVmfui1dq7PY= =P8gn -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 17:02:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C9A737B401 for ; Mon, 21 Jul 2003 17:02:50 -0700 (PDT) Received: from util.inch.com (ns.inch.com [216.223.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3047743FA3 for ; Mon, 21 Jul 2003 17:02:49 -0700 (PDT) (envelope-from spork@inch.com) Received: from shell.inch.com (www.inch.com [216.223.192.20]) h6M02lJu060623; Mon, 21 Jul 2003 20:02:47 -0400 (EDT) (envelope-from spork@inch.com) Received: from shell.inch.com (localhost [127.0.0.1]) by shell.inch.com (8.12.8p1/8.12.8) with ESMTP id h6M02lSM024525; Mon, 21 Jul 2003 20:02:47 -0400 (EDT) (envelope-from spork@inch.com) Received: from localhost (spork@localhost)h6M02lIA024522; Mon, 21 Jul 2003 20:02:47 -0400 (EDT) X-Authentication-Warning: shell.inch.com: spork owned process doing -bs Date: Mon, 21 Jul 2003 20:02:47 -0400 (EDT) From: Charles Sprickman To: Rudolph Pereira In-Reply-To: <20030721203209.GO1414@starfleet.org.au> Message-ID: <20030721195854.P20962@shell.inch.com> References: <006601c29cab$ec3a9c80$0100000a@D9NLZD0J> <20021205234945.GA70487@tassie.net.au> <20021206011334.GB70929@tassie.net.au> <20030721203209.GO1414@starfleet.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 00:02:50 -0000 On Tue, 22 Jul 2003, Rudolph Pereira wrote: > Just to drag this thread on a bit further ... > > I've been looking into these little boxes, thinking I could use one as a > firewall/gateway. My one requirement is that it would need to have two > PCI slots (one can be low-profile), and although I've seen PCI riser > cards that can give me two slots, they've been rare, And all the dual or triple slot ones I've seen also have an edge connector that goes into another PCI slot on the mainboard, so I don't know that they would even work. > and cases that are suitable (i.e have the space, and back panels are > compatible) even rarer (I've yet to find one). Does anyone know of any > such cases (it'd be even better if they're available in au)? No, but if you find something, please post! I've been searching for something that is nice and small yet has more power than say a Soekris box and can handle more than one or two ethernet cards. Isn't there also another mini form factor? I see that places like Iron Systems and other rack-mount outlets have some boxes that aren't mini-itx, but are still only 14" deep (about the size of an old Cisco 25xx router)... It also seems the built-in ethernet on the Via boards is not the best either... Charles > thanks > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 17:49:47 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9E1F37B401 for ; Mon, 21 Jul 2003 17:49:47 -0700 (PDT) Received: from updegrove.net (12-246-251-12.client.attbi.com [12.246.251.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 37E1C43FB1 for ; Mon, 21 Jul 2003 17:49:47 -0700 (PDT) (envelope-from freebsdstable@updegrove.net) Received: (qmail 34539 invoked from network); 22 Jul 2003 00:50:53 -0000 Received: from adsl-64-166-46-11.dsl.scrm01.pacbell.net (HELO updegrove.net) (64.166.46.11) by updegrove.net with SMTP; 22 Jul 2003 00:50:53 -0000 Message-ID: <3F1C8A82.6030804@updegrove.net> Date: Mon, 21 Jul 2003 17:51:14 -0700 From: Rick Updegrove User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: LH3 SMP hangs for no apparent reason X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 00:49:48 -0000 Hi, I have been having a fairly serious problem with an HP Netserver LH3 that seems to hang for no apparent reason. This happens when the machine is under load and it also happens when it is simply idle. When this "hang" occurs I can no longer SSH to the box. I can ping it and port scan it and it appears to be "alive" but it won't load web pages or process mail etc. When I physically access the box there are NO error messages, warnings or anything on the monitor and when I attempt to log on, I enter any username or root and hit enter and it just sits there forever. I try Ctrl + ALT + F2 and I have the same problem on another tty. When I power off and then log on, I am unable to find any evidence of what is causing this problem in any system logs. I am wondering if is because I uncomment the 2 lines needed for SMP support, and rebuilt 4.8-STABLE FreeBSD and boot to that kernel. I do this because I would like to use both CPUs. I suppose I could do that and then run it and see if that is in fact the cause but that would not really get me any close to using both CPUs which is of course my ultimate goal. I am about out of ideas here, what should I do first? Thanks! Rick Up P.S. Some hopefully useful info can be found here: dmesg @ http://12.246.251.12/dmesg.txt SMP kernel config file @ http://12.246.251.12/SMP.txt var/log/messages @ http://12.246.251.12/messages.txt I am running qmail + vpopmail + procmail under a very light load 1000 messages per 24 hours right now and apache with almost no load at all, just me reading documentation etc. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 20:30:24 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DAB237B401 for ; Mon, 21 Jul 2003 20:30:24 -0700 (PDT) Received: from eden.barryp.org (host-150-32-220-24.midco.net [24.220.32.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id B774C43F75 for ; Mon, 21 Jul 2003 20:30:23 -0700 (PDT) (envelope-from bp@barryp.org) Received: from localhost ([127.0.0.1] helo=barryp.org) by eden.barryp.org with esmtp (Exim 4.20) id 19enr1-0001Zv-Gx for freebsd-stable@freebsd.org; Mon, 21 Jul 2003 22:30:19 -0500 Message-ID: <3F1CAFCA.4070209@barryp.org> Date: Mon, 21 Jul 2003 22:30:18 -0500 From: Barry Pederson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030704 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <006601c29cab$ec3a9c80$0100000a@D9NLZD0J> <20021205234945.GA70487@tassie.net.au> <20021206011334.GB70929@tassie.net.au> <20030721203209.GO1414@starfleet.org.au> <20030721195854.P20962@shell.inch.com> In-Reply-To: <20030721195854.P20962@shell.inch.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-7.9 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MOZILLA_UA autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 03:30:24 -0000 Charles Sprickman wrote: > On Tue, 22 Jul 2003, Rudolph Pereira wrote: > > >>Just to drag this thread on a bit further ... >> >>I've been looking into these little boxes, thinking I could use one as a >>firewall/gateway. My one requirement is that it would need to have two >>PCI slots (one can be low-profile), and although I've seen PCI riser >>cards that can give me two slots, they've been rare, > No, but if you find something, please post! I've been searching for > something that is nice and small yet has more power than say a Soekris box > and can handle more than one or two ethernet cards. Another way to go is stick a multi-port ethernet card in the mini-itx's single PCI slot. You can find dual Intel Pro/100 cards on eBay for around $30 - I've got one stuck into an EPIA board running FreeBSD 4.8, runs great as a firewall. Just have to make sure your case can take a regular-sized PCI card, and not just the low-profiles ones. Barry From owner-freebsd-stable@FreeBSD.ORG Tue Jul 22 02:17:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31E0C37B401 for ; Tue, 22 Jul 2003 02:17:27 -0700 (PDT) Received: from hobbes.biaix.org (86.Red-213-97-212.pooles.rima-tde.net [213.97.212.86]) by mx1.FreeBSD.org (Postfix) with SMTP id 5458743F75 for ; Tue, 22 Jul 2003 02:17:25 -0700 (PDT) (envelope-from joan@iaeste-catalunya.upc.es) Received: (qmail 7232 invoked from network); 22 Jul 2003 09:10:38 -0000 Received: from peque.biaix.org (HELO iaeste-catalunya.upc.es) (192.168.124.3) by 0 with SMTP; 22 Jul 2003 09:10:38 -0000 Message-ID: <3F1CFFFF.2090202@iaeste-catalunya.upc.es> Date: Tue, 22 Jul 2003 11:12:31 +0200 From: Joan Picanyol i Puig User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; ca; rv:1.3) Gecko/20030312 X-Accept-Language: ca-es MIME-Version: 1.0 Followup-To: freebsd-stable@freebsd.org,joan@iaeste-catalunya.upc.es To: freebsd-stable@FreeBSD.org References: <3F1ADEF4.3040306@iaeste-catalunya.upc.es> <20030721010541.GE11810@wantadilla.lemis.com> In-Reply-To: <20030721010541.GE11810@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: mismatching vinum configurations X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 09:17:27 -0000 En/na Greg 'groggy' Lehey ha escrit: >>What's the less traumatic way to recover the data? > I've never tried this, but a thing you could do is: > > vinum -> setdaemon 4 (turn off config updates) > vinum -> read /dev/ad0s1d (or another drive with valid config) > vinum -> start This (followed by two reboots) has worked. The reason I didn't think it was ok is that I got a wired output from 'vinum list' (wrong number of drives, *invalid* still there), how is it suposed to be useful if is not a faithful report of vinum's state? Is there another way to get the same information? tks -- pica From owner-freebsd-stable@FreeBSD.ORG Tue Jul 22 04:20:12 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5163537B401 for ; Tue, 22 Jul 2003 04:20:12 -0700 (PDT) Received: from gateway.webize.com.au (gateway.webize.com.au [203.17.1.92]) by mx1.FreeBSD.org (Postfix) with SMTP id 69ADD43F75 for ; Tue, 22 Jul 2003 04:20:09 -0700 (PDT) (envelope-from bsdmn@webize.com.au) Received: (qmail 2852 invoked from network); 22 Jul 2003 11:13:37 -0000 Received: from unknown (HELO cmlaptop) (192.168.100.51) by 192.168.100.50 with SMTP; 22 Jul 2003 11:13:37 -0000 From: "Carl Morley" To: "'Rudolph Pereira'" , Date: Tue, 22 Jul 2003 21:19:47 +1000 Message-ID: <000601c35043$2dda2d90$3364a8c0@cmlaptop> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: <20030721203209.GO1414@starfleet.org.au> Subject: RE: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 11:20:12 -0000 See bottom of email for CLM's comments; > -----Original Message----- > From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- > stable@freebsd.org] On Behalf Of Rudolph Pereira > Sent: Tuesday, 22 July 2003 06:32 > To: freebsd-stable@FreeBSD.ORG > Subject: Re: Via EPIA Mini-ITX motherboard > > Just to drag this thread on a bit further ... No worries, I have found it a useful thread. > > I've been looking into these little boxes, thinking I could use one as a > firewall/gateway. My one requirement is that it would need to have two > PCI slots (one can be low-profile), and although I've seen PCI riser > cards that can give me two slots, they've been rare, and cases that are > suitable (i.e have the space, and back panels are compatible) > even rarer (I've yet to find one). Does anyone know of any such > cases (it'd be even better if they're available in au)? And they can be got - www.traverse.com.au, speak to a bloke by the name of Guy Ellis. > > thanks No probs, but be warned about the vr0 cards. The CPU/chipset is great, and who cares about sound and video for routing - plus they look bloody great. I only wish they came with something other than the Rhine chipset NIC's..... Cheers, Carl. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Jul 22 06:16:09 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B375737B404 for ; Tue, 22 Jul 2003 06:16:09 -0700 (PDT) Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6679243F93 for ; Tue, 22 Jul 2003 06:16:06 -0700 (PDT) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (dialup-1.aaa.net.au [203.14.230.66]) by posgate.acis.com.au (8.12.7/8.12.7) with ESMTP id h6MDFuMM019711; Tue, 22 Jul 2003 23:15:57 +1000 Received: from bullseye.apana.org.au (localhost.apana.org.au [127.0.0.1]) h6MDHSWO003366; Tue, 22 Jul 2003 23:17:31 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Received: from localhost (andymac@localhost)h6MBTeea003264; Tue, 22 Jul 2003 21:29:40 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Tue, 22 Jul 2003 21:29:40 +1000 (EST) From: Andrew MacIntyre To: Rudolph Pereira In-Reply-To: <20030721203209.GO1414@starfleet.org.au> Message-ID: <20030722212600.V3219@bullseye.apana.org.au> References: <006601c29cab$ec3a9c80$0100000a@D9NLZD0J> <20021205234945.GA70487@tassie.net.au> <20021206011334.GB70929@tassie.net.au> <20030721203209.GO1414@starfleet.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang) cc: freebsd-stable@freebsd.org Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 13:16:10 -0000 On Tue, 22 Jul 2003, Rudolph Pereira wrote: > I've been looking into these little boxes, thinking I could use one as a > firewall/gateway. My one requirement is that it would need to have two > PCI slots (one can be low-profile), and although I've seen PCI riser > cards that can give me two slots, they've been rare, and cases that are > suitable (i.e have the space, and back panels are compatible) > even rarer (I've yet to find one). Does anyone know of any such > cases (it'd be even better if they're available in au)? I don't know whether it would meet your requirements, let alone be readily available, but last time I looked at VIA's site (www.viavpsd.com) it listed a MicroATX version of the EPIA-M board (don't remember the model #) with the CLE266 chipset and 3 PCI slots. Regards, Andrew. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia From owner-freebsd-stable@FreeBSD.ORG Tue Jul 22 10:13:15 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4D6E37B401 for ; Tue, 22 Jul 2003 10:13:15 -0700 (PDT) Received: from updegrove.net (12-246-251-12.client.attbi.com [12.246.251.12]) by mx1.FreeBSD.org (Postfix) with SMTP id E3CFD43F3F for ; Tue, 22 Jul 2003 10:13:14 -0700 (PDT) (envelope-from freebsdstable@updegrove.net) Received: (qmail 41506 invoked from network); 22 Jul 2003 17:14:25 -0000 Received: from adsl-64-166-46-11.dsl.scrm01.pacbell.net (HELO updegrove.net) (64.166.46.11) by updegrove.net with SMTP; 22 Jul 2003 17:14:25 -0000 Message-ID: <3F1D7108.2010300@updegrove.net> Date: Tue, 22 Jul 2003 10:14:48 -0700 From: Rick Updegrove User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG References: <3F1C8A82.6030804@updegrove.net> In-Reply-To: <3F1C8A82.6030804@updegrove.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: LH3 SMP hangs for no apparent reason X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 17:13:16 -0000 Sean wrote: >Go into the BIOS, change IRQ routing from "Smart" to "Static" (or whatever >the opposite of Smart is); I had problems with LH3s losing the interrupts >for the onboard LSI RAID card, and locking up in the driver until I did >that. The Intel cards we added also lost interrupts occasionally, though >they were more graceful about it. I went into the BIOS and selected: Configuration -> PCI Slot Devices -> PCI IRQ Locking -> Routing Algorithm [Smart] Ok I changed Routing Algorithm [Smart] to [Fixed] and got a scary warning about data loss etc. but I hit Yes and saved as prompted and rebooted. >We've now got several LH3s, an LH4 and an LH6000 all running under >load. Ok hopefully I will have this LH3 "fixed" as well : ) Thanks for the help. P.S. I have been looking at mailing list archives where the following was mentioned... Is this going to be a problem? Could this be causing my current problem? < snip from dmesg @ http://12.246.251.12/dmesg.txt > APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 From owner-freebsd-stable@FreeBSD.ORG Tue Jul 22 15:19:44 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D0ED37B401 for ; Tue, 22 Jul 2003 15:19:44 -0700 (PDT) Received: from gw01.mail.saunalahti.fi (gw01.mail.saunalahti.fi [195.197.172.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D69743FBD for ; Tue, 22 Jul 2003 15:19:43 -0700 (PDT) (envelope-from djv@pop.mbnet.fi) Received: from tuomon-atte (MCIII.dsl.saunalahti.fi [62.142.243.203]) by gw01.mail.saunalahti.fi (Postfix) with ESMTP id 7F9EB143CEA; Wed, 23 Jul 2003 01:19:41 +0300 (EEST) To: Charles Sprickman References: <006601c29cab$ec3a9c80$0100000a@D9NLZD0J> <20021205234945.GA70487@tassie.net.au> <20021206011334.GB70929@tassie.net.au> <20030721203209.GO1414@starfleet.org.au> <20030721195854.P20962@shell.inch.com> Message-ID: Content-Type: text/plain; charset=iso-8859-15; format=flowed From: Tuomo Latto MIME-Version: 1.0 Date: Wed, 23 Jul 2003 01:19:49 +0300 In-Reply-To: <20030721195854.P20962@shell.inch.com> User-Agent: Opera7.11/Win32 M2 build 2887 cc: "freebsd-stable@freebsd.org" Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: djv@mbnet.fi List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 22:19:44 -0000 On Mon, 21 Jul 2003 20:02:47 -0400 (EDT), Charles Sprickman wrote: ... >> compatible) even rarer (I've yet to find one). Does anyone know of any >> such cases (it'd be even better if they're available in au)? > > No, but if you find something, please post! I've been searching for > something that is nice and small yet has more power than say a Soekris > box > and can handle more than one or two ethernet cards. Isn't there also > another mini form factor? I see that places like Iron Systems and other > rack-mount outlets have some boxes that aren't mini-itx, but are still > only 14" deep (about the size of an old Cisco 25xx router)... > > It also seems the built-in ethernet on the Via boards is not the best > either... Don't know about the processing power, compatibility or cases but if all you really need is ethernet slots this might just be what you're looking for: http://www.2hightech.com/products/embedded%20boards/other/ISS102.htm -- Tuomo From owner-freebsd-stable@FreeBSD.ORG Tue Jul 22 17:57:36 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E231137B401 for ; Tue, 22 Jul 2003 17:57:36 -0700 (PDT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 734E843F3F for ; Tue, 22 Jul 2003 17:57:36 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from salty.rapid.stbernard.com (corp-2.ipinc.com [199.245.188.2]) by smtp-relay.omnis.com (Postfix) with ESMTP id 2A83E5B6AB; Tue, 22 Jul 2003 17:57:35 -0700 (PDT) From: Wes Peters Organization: Softweyr.com To: Charles Sprickman , Rudolph Pereira Date: Tue, 22 Jul 2003 17:57:35 -0700 User-Agent: KMail/1.5.2 References: <006601c29cab$ec3a9c80$0100000a@D9NLZD0J> <20030721203209.GO1414@starfleet.org.au> <20030721195854.P20962@shell.inch.com> In-Reply-To: <20030721195854.P20962@shell.inch.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307221757.35027.wes@softweyr.com> cc: freebsd-stable@freebsd.org Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 00:57:37 -0000 On Monday 21 July 2003 17:02, Charles Sprickman wrote: > On Tue, 22 Jul 2003, Rudolph Pereira wrote: > > Just to drag this thread on a bit further ... > > > > I've been looking into these little boxes, thinking I could use one > > as a firewall/gateway. My one requirement is that it would need to > > have two PCI slots (one can be low-profile), and although I've seen > > PCI riser cards that can give me two slots, they've been rare, > > And all the dual or triple slot ones I've seen also have an edge > connector that goes into another PCI slot on the mainboard, so I > don't know that they would even work. > > > and cases that are suitable (i.e have the space, and back panels > > are compatible) even rarer (I've yet to find one). Does anyone > > know of any such cases (it'd be even better if they're available in > > au)? > > No, but if you find something, please post! I've been searching for > something that is nice and small yet has more power than say a > Soekris box and can handle more than one or two ethernet cards. > Isn't there also another mini form factor? I see that places like > Iron Systems and other rack-mount outlets have some boxes that aren't > mini-itx, but are still only 14" deep (about the size of an old Cisco > 25xx router)... Those mostly use Micro-ATX form factor boards. Some of them are getting dirt cheap, too; a local screwdriver shop advertises one with a P4 for $499 these days. Wowsers. Probably a crappy motherboard, but toss in another $100 for a good mobo & power supply and you've got yourself quite a 1u system. Then just wait for them to overheat... -- "Where am I, and what am I doing in this handbasket?" Wes Peters wes@softweyr.com From owner-freebsd-stable@FreeBSD.ORG Tue Jul 22 18:03:48 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9870437B401 for ; Tue, 22 Jul 2003 18:03:48 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01AE643F85 for ; Tue, 22 Jul 2003 18:03:48 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.9/8.12.3) with ESMTP id h6N13jqh018696; Tue, 22 Jul 2003 18:03:45 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id h6N13jke018695; Tue, 22 Jul 2003 18:03:45 -0700 Date: Tue, 22 Jul 2003 18:03:45 -0700 From: Brooks Davis To: Wes Peters Message-ID: <20030723010344.GA18028@Odin.AC.HMC.Edu> References: <006601c29cab$ec3a9c80$0100000a@D9NLZD0J> <20030721203209.GO1414@starfleet.org.au> <20030721195854.P20962@shell.inch.com> <200307221757.35027.wes@softweyr.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <200307221757.35027.wes@softweyr.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-stable@freebsd.org Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 01:03:48 -0000 --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 22, 2003 at 05:57:35PM -0700, Wes Peters wrote: > > No, but if you find something, please post! I've been searching for > > something that is nice and small yet has more power than say a > > Soekris box and can handle more than one or two ethernet cards.=20 > > Isn't there also another mini form factor? I see that places like > > Iron Systems and other rack-mount outlets have some boxes that aren't > > mini-itx, but are still only 14" deep (about the size of an old Cisco > > 25xx router)... >=20 > Those mostly use Micro-ATX form factor boards. Some of them are getting= =20 > dirt cheap, too; a local screwdriver shop advertises one with a P4 for=20 > $499 these days. Wowsers. Probably a crappy motherboard, but toss in=20 > another $100 for a good mobo & power supply and you've got yourself=20 > quite a 1u system. Then just wait for them to overheat... The Iron Systems A110's are Via C3's on mini-itx boards. I've got four of them. They definaly won't overheat. If anything, they are over cooled. They are quite loud. If you do buy a 1U box, make sure the vendor does real thermal testing. It's hard to cool something that small and there's a lot of crap out there. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/Hd7wXY6L6fI4GtQRAi+KAJ4rB9CPI7YsQ0V9MpDpffr9nIH7lACfYSI4 L8/bEwkOf86wcFgZ2JDt1Ic= =3Kxn -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 03:04:43 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD6E737B404 for ; Wed, 23 Jul 2003 03:04:43 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA3EE43FE0 for ; Wed, 23 Jul 2003 03:04:42 -0700 (PDT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19fGSQ-0004IU-00 for ; Wed, 23 Jul 2003 12:02:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19fGSN-0004IA-00 for ; Wed, 23 Jul 2003 12:02:47 +0200 From: Samuel Tardieu Date: Wed, 23 Jul 2003 12:03:34 +0200 Organization: Avian Carrier & Friends Lines: 8 Message-ID: <87adb5a7bd.fsf@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.5 (cauliflower, i386--freebsd) Cancel-Lock: sha1:2S3+QQuoT78+uA5PWpgzPzbITvc= X-Leafnode-NNTP-Posting-Host: 127.0.0.1 Sender: news Subject: 802.1x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 10:04:44 -0000 Hi. Is there a 802.1x implementation (client and server) for FreeBSD -STABLE? Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 03:23:22 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4D0C37B401 for ; Wed, 23 Jul 2003 03:23:22 -0700 (PDT) Received: from scribble.fsn.hu (scribble.fsn.hu [193.224.40.95]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F61A43F85 for ; Wed, 23 Jul 2003 03:23:21 -0700 (PDT) (envelope-from bra@fsn.hu) Received: (qmail 31532 invoked from network); 23 Jul 2003 10:23:19 -0000 Received: from unknown (HELO fsn.hu) (127.0.0.1) by localhost with SMTP; 23 Jul 2003 10:23:19 -0000 Message-ID: <3F1E6216.4060707@fsn.hu> Date: Wed, 23 Jul 2003 12:23:18 +0200 From: Attila Nagy Organization: Free Software Network Foundation - http://www.fsn.hu/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: hu, en-us, en MIME-Version: 1.0 To: Samuel Tardieu References: <87adb5a7bd.fsf@inf.enst.fr> In-Reply-To: <87adb5a7bd.fsf@inf.enst.fr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: 802.1x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 10:23:23 -0000 Samuel Tardieu wrote: > Is there a 802.1x implementation (client and server) for FreeBSD > -STABLE? http://www.open1x.org/ ? BTW, I don't really get how could FreeBSD act as a 802.1x "server". Do you mean a RADIUS server, from which the 802.1x aware devices can authenticate? Install FreeRADIUS for example. -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone @work: +361 210 1415/127 ISOs: http://www.fsn.hu/?f=download cell.: +3630 306 6758 From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 03:27:46 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E63DA37B401 for ; Wed, 23 Jul 2003 03:27:46 -0700 (PDT) Received: from mail.rfc1149.net (marvin.enst.fr [137.194.161.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC9B443F85 for ; Wed, 23 Jul 2003 03:27:45 -0700 (PDT) (envelope-from sam@rfc1149.net) Received: from beeblebrox.rfc1149.net (beeblebrox-tun.enst.fr [137.194.161.40]) by mail.rfc1149.net (Postfix) with ESMTP id DD3C5A802E; Wed, 23 Jul 2003 12:27:43 +0200 (CEST) Received: by beeblebrox.rfc1149.net (Postfix, from userid 1000) id 893AF404; Wed, 23 Jul 2003 12:27:43 +0200 (CEST) Date: Wed, 23 Jul 2003 12:27:43 +0200 To: Attila Nagy References: <87adb5a7bd.fsf@inf.enst.fr> <3F1E6216.4060707@fsn.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F1E6216.4060707@fsn.hu> User-Agent: Mutt/1.4.1i From: Samuel Tardieu Organization: RFC 1149 (see http://www.rfc1149.net/) Content-Transfer-Encoding: 8bit Precedence: special-delivery X-WWW: http://www.rfc1149.net/sam X-Mail-Processing: Sam's procmail tools X-Jabber: (see http://www.jabber.org/) X-OpenPGP-Fingerprint: 79C0 AE3C CEA8 F17B 0EF1 45A5 F133 2241 1B80 ADE6 (see http://www.gnupg.org/) X-Sam-Laptop: yes Message-Id: <2003-07-23-12-27-43+trackit+sam@rfc1149.net> cc: freebsd-stable@freebsd.org Subject: Re: 802.1x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 10:27:47 -0000 On 23/07, Attila Nagy wrote: | Samuel Tardieu wrote: | >Is there a 802.1x implementation (client and server) for FreeBSD | >-STABLE? | http://www.open1x.org/ ? | | BTW, I don't really get how could FreeBSD act as a 802.1x "server". Do | you mean a RADIUS server, from which the 802.1x aware devices can | authenticate? Install FreeRADIUS for example. No, I'd like my desktop PC with a PCI WiFi card to act as a 802.1x-protected access point instead of being wide-open. Sam From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 03:34:25 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6042437B404 for ; Wed, 23 Jul 2003 03:34:24 -0700 (PDT) Received: from expresso.netweaver.net (expresso.netweaver.net [217.151.99.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 3801B43FBD for ; Wed, 23 Jul 2003 03:34:23 -0700 (PDT) (envelope-from howells@kde.org) Received: (qmail 23183 invoked from network); 23 Jul 2003 10:26:46 -0000 Received: from unknown (HELO 213-78-107-30.friaco.onetel.net.uk) (chris@chrishowells.co.uk@213.78.107.30) by 0 with SMTP; 23 Jul 2003 10:26:46 -0000 From: Chris Howells Organization: K Desktop Environment To: freebsd-stable@freebsd.org Date: Wed, 23 Jul 2003 11:33:43 +0100 User-Agent: KMail/1.5.9 References: <87adb5a7bd.fsf@inf.enst.fr> <3F1E6216.4060707@fsn.hu> <2003-07-23-12-27-43+trackit+sam@rfc1149.net> In-Reply-To: <2003-07-23-12-27-43+trackit+sam@rfc1149.net> X-GPG-Fingerprint: 5863 DF82 C34D 7291 CC63 CA1B 17C2 2ED7 3379 5A2C MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200307231133.43761.howells@kde.org> Subject: Re: 802.1x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 10:34:25 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Wednesday 23 July 2003 11:27, Samuel Tardieu wrote: > No, I'd like my desktop PC with a PCI WiFi card to act as a > 802.1x-protected access point instead of being wide-open. I wrote up my experiences of using FreeBSD on a wireless bridge (you can th= en=20 implement a firewall on the ethernet cards), don't know if it will be of an= y=20 assistance: http://developer.kde.org/~howells/wlan/ =2D --=20 Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP ID: 33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/HmSHF8Iu1zN5WiwRApQCAJ4sqx04YO84XRqawVUbiv142zUuWwCeOCCN =46loOg3mgp/t7OkmKABf38Ek=3D =3DreyJ =2D----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 03:36:57 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B882237B401 for ; Wed, 23 Jul 2003 03:36:57 -0700 (PDT) Received: from proton.hexanet.fr (proton.hexanet.fr [81.23.32.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2916243FAF for ; Wed, 23 Jul 2003 03:36:56 -0700 (PDT) (envelope-from c.prevotaux@hexanet.fr) Received: from proton.hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.12.9/8.12.9) with SMTP id h6NAarwa023594; Wed, 23 Jul 2003 12:36:53 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Wed, 23 Jul 2003 12:36:53 +0200 From: Christophe Prevotaux To: Samuel Tardieu Message-Id: <20030723123653.05f03267.c.prevotaux@hexanet.fr> In-Reply-To: <2003-07-23-12-27-43+trackit+sam@rfc1149.net> References: <87adb5a7bd.fsf@inf.enst.fr> <3F1E6216.4060707@fsn.hu> <2003-07-23-12-27-43+trackit+sam@rfc1149.net> Organization: HEXANET Sarl X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable cc: freebsd-stable@freebsd.org Subject: Re: 802.1x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 10:36:58 -0000 AFAIK , 802.1x will only do auth and do any equivalent of VPN if you need to crypt the transmission of the data and not only auth then you need to do something else like PPTP , IPSEC etc... I also would someone to make include open802.1x in the port tree I have not seen it in there so far On Wed, 23 Jul 2003 12:27:43 +0200 Samuel Tardieu wrote: > On 23/07, Attila Nagy wrote: >=20 > | Samuel Tardieu wrote: > | >Is there a 802.1x implementation (client and server) for FreeBSD > | >-STABLE? > | http://www.open1x.org/ ? > |=20 > | BTW, I don't really get how could FreeBSD act as a 802.1x "server". Do= =20 > | you mean a RADIUS server, from which the 802.1x aware devices can=20 > | authenticate? Install FreeRADIUS for example. >=20 > No, I'd like my desktop PC with a PCI WiFi card to act as a 802.1x-protec= ted > access point instead of being wide-open. >=20 > Sam >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A.C Les Charmilles Tel: +33 (0)3 26 79 30 05=20 3 All=E9e Thierry Sabine Direct: +33 (0)3 26 61 77 72=20 BP202 Fax: +33 (0)3 26 79 30 06 51686 Reims Cedex 2 =20 FRANCE HEXANET Network Operation Center =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 03:37:11 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E46C837B425 for ; Wed, 23 Jul 2003 03:37:11 -0700 (PDT) Received: from scribble.fsn.hu (scribble.fsn.hu [193.224.40.95]) by mx1.FreeBSD.org (Postfix) with SMTP id 2310843FA3 for ; Wed, 23 Jul 2003 03:37:10 -0700 (PDT) (envelope-from bra@fsn.hu) Received: (qmail 31832 invoked from network); 23 Jul 2003 10:37:08 -0000 Received: from unknown (HELO fsn.hu) (127.0.0.1) by localhost with SMTP; 23 Jul 2003 10:37:08 -0000 Message-ID: <3F1E6553.6070600@fsn.hu> Date: Wed, 23 Jul 2003 12:37:07 +0200 From: Attila Nagy Organization: Free Software Network Foundation - http://www.fsn.hu/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: hu, en-us, en MIME-Version: 1.0 To: Samuel Tardieu References: <87adb5a7bd.fsf@inf.enst.fr> <3F1E6216.4060707@fsn.hu> <2003-07-23-12-27-43+trackit+sam@rfc1149.net> In-Reply-To: <2003-07-23-12-27-43+trackit+sam@rfc1149.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: 802.1x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 10:37:12 -0000 Samuel Tardieu wrote: > No, I'd like my desktop PC with a PCI WiFi card to act as a 802.1x-protected > access point instead of being wide-open. Ah, I never used 802.1x on wireless, so that's the cause of my false assumption that you are willing to use it on wired networks. Maybe this one is what you are searching for: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=18928+0+archive/2003/freebsd-net/20030223.freebsd-net http://www.cdt.luth.se/~peppar/weartech/radiosphere-archive/0344.html -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone @work: +361 210 1415/127 ISOs: http://www.fsn.hu/?f=download cell.: +3630 306 6758 From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 03:40:30 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAB0F37B401 for ; Wed, 23 Jul 2003 03:40:30 -0700 (PDT) Received: from mail.rfc1149.net (marvin.enst.fr [137.194.161.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A00043F75 for ; Wed, 23 Jul 2003 03:40:30 -0700 (PDT) (envelope-from sam@rfc1149.net) Received: from beeblebrox.rfc1149.net (beeblebrox-tun.enst.fr [137.194.161.40]) by mail.rfc1149.net (Postfix) with ESMTP id A78A7A802E; Wed, 23 Jul 2003 12:40:27 +0200 (CEST) Received: by beeblebrox.rfc1149.net (Postfix, from userid 1000) id DE7F2341; Wed, 23 Jul 2003 12:40:26 +0200 (CEST) Date: Wed, 23 Jul 2003 12:40:26 +0200 To: Christophe Prevotaux References: <87adb5a7bd.fsf@inf.enst.fr> <3F1E6216.4060707@fsn.hu> <2003-07-23-12-27-43+trackit+sam@rfc1149.net> <20030723123653.05f03267.c.prevotaux@hexanet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723123653.05f03267.c.prevotaux@hexanet.fr> User-Agent: Mutt/1.4.1i From: Samuel Tardieu Organization: RFC 1149 (see http://www.rfc1149.net/) Content-Transfer-Encoding: 8bit Precedence: special-delivery X-WWW: http://www.rfc1149.net/sam X-Mail-Processing: Sam's procmail tools X-Jabber: (see http://www.jabber.org/) X-OpenPGP-Fingerprint: 79C0 AE3C CEA8 F17B 0EF1 45A5 F133 2241 1B80 ADE6 (see http://www.gnupg.org/) X-Sam-Laptop: yes Message-Id: <2003-07-23-12-40-26+trackit+sam@rfc1149.net> cc: freebsd-stable@freebsd.org Subject: Re: 802.1x X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 10:40:31 -0000 On 23/07, Christophe Prevotaux wrote: | AFAIK , 802.1x will only do auth and do any equivalent of VPN | if you need to crypt the transmission of the data and not only auth | then you need to do something else like PPTP , IPSEC etc... That's exactly (the "auth" part) what I want to do. I already use IPSEC in tunnel mode, but I'd prefer separate authentication and crypto (the former goes between the mobile device and the access point while the latter is between the mobile device and the service being accessed). | I also would someone to make include open802.1x in the port tree | I have not seen it in there so far Did anyone test it with FreeBSD? Sam From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 03:47:19 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21E0F37B401 for ; Wed, 23 Jul 2003 03:47:19 -0700 (PDT) Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id E040243FA3 for ; Wed, 23 Jul 2003 03:47:17 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta03-svc.ntlworld.comESMTP <20030723104716.QUEB2652.mta03-svc.ntlworld.com@llama.fishballoon.org>; Wed, 23 Jul 2003 11:47:16 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19fH8h-00039C-U6; Wed, 23 Jul 2003 11:46:31 +0100 Date: Wed, 23 Jul 2003 11:46:31 +0100 From: Scott Mitchell To: freebsd-stable@freebsd.org Message-ID: <20030723104631.GA11861@llama.fishballoon.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell Subject: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 10:47:19 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, We recently moved our CVS repository from a 4.6-STABLE machine to a brand new 4.8 install, on another identical machine. The server runs cvs in 'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD clients. We pretty soon noticed that the cvs server process was occasionally crashing on sig11 (ie. a segfault). The only evidence for this was in the message log, the cvs operations always completed normally on the client side. This *never* happened on the old server, so I figured it had to be a hardware problem on the new machine, or some issue with 4.8. Probably happening about 1 in every 100 times the cvs server was run. I compiled a debug version of cvs from the 4.8 sources and was able to get a few cores, once I figured out how to make it actually dump core. I've attached the log of a gdb session on one of these -- all the cores I have show the process crashing in the same place, where it's clearly trying to follow a NULL pointer. I've since copied the cvs binary from the 4.6 machine across to the new server -- we've run with this for the past two weeks and had exactly zero problems with it. Given that all the cores are the same, and that the only thing we've seen fail on this machine is the 4.8 cvs code, this smells like a cvs bug to me. I've no idea if it's in our local extensions or the base cvs code -- should I be sending the bug report to FreeBSD.org or cvshome.org? Is there anyone on here familiar with the internals of cvs who wants to take a look at this? I can provide any additional configuration details or more grovelling in the core dumps on request... Cheers, Scott --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="gdb.log" Content-Transfer-Encoding: quoted-printable Script started on Wed Jul 23 11:14:55 2003 pukeko# gdb `which cvs.debug` cvs.debug.81697.core=0D=0D GNU gdb 4.18 (FreeBSD)=0D Copyright 1998 Free Software Foundation, Inc.=0D GDB is free software, covered by the GNU General Public License, and you ar= e=0D welcome to change it and/or distribute copies of it under certain condition= s.=0D Type "show copying" to see the conditions.=0D There is absolutely no warranty for GDB. Type "show warranty" for details.= =0D This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read cal= led at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxrea= d.c line 2627 in elfstab_build_psymtabs=0D Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../..= /contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf=0D =0D Core was generated by `cvs.debug'.=0D Program terminated with signal 11, Segmentation fault.=0D Reading symbols from /usr/lib/libgnuregex.so.2...done.=0D Reading symbols from /usr/lib/libmd.so.2...done.=0D Reading symbols from /usr/lib/libcrypt.so.2...done.=0D Reading symbols from /usr/lib/libz.so.2...done.=0D Reading symbols from /usr/lib/libc.so.4...done.=0D Reading symbols from /usr/libexec/ld-elf.so.1...done.=0D #0 buf_shutdown (buf=3D0x0)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/buffer.c:12= 08=0D 1208 if (buf->shutdown)=0D (gdb) where=0D #0 buf_shutdown (buf=3D0x0)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/buffer.c:12= 08=0D #1 0x8087e2b in server_cleanup (sig=3D0)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/server.c:48= 92=0D #2 0x805ec67 in error_exit ()=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/error.c:71= =0D #3 0x805ef27 in error (status=3D1, errnum=3D0, =0D message=3D0x80ab4b9 "received %s signal")=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/error.c:212= =0D #4 0x806daae in main_cleanup (sig=3D13)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/main.c:395= =0D #5 0x80926e4 in strip_trailing_slashes ()=0D #6 0xbfbfffac in ?? ()=0D #7 0x804d85a in buf_send_output (buf=3D0x80c1040)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/buffer.c:28= 7=0D #8 0x804d900 in buf_flush (buf=3D0x80c1040, block=3D1)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/buffer.c:35= 2=0D #9 0x8087eb7 in server_cleanup (sig=3D0)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/server.c:50= 07=0D #10 0x80883e2 in server (argc=3D1, argv=3D0xbfbffc88)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/server.c:52= 34=0D #11 0x806e636 in main (argc=3D1, argv=3D0xbfbffc88)=0D at /usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/main.c:1028= =0D #12 0x804a67a in _start ()=0D (gdb) list=0D 1203 =0D 1204 int=0D 1205 buf_shutdown (buf)=0D 1206 struct buffer *buf;=0D 1207 {=0D 1208 if (buf->shutdown)=0D 1209 return (*buf->shutdown) (buf);=0D 1210 return 0;=0D 1211 }=0D 1212 =0D (gdb) quit=0D pukeko# ^D=08=08exit=0D Script done on Wed Jul 23 11:15:28 2003 --qDbXVdCdHGoSgWSk-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 10:04:49 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39AC537B401 for ; Wed, 23 Jul 2003 10:04:49 -0700 (PDT) Received: from frontend2.aha.ru (bird.zenon.net [213.189.198.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6718D43F93 for ; Wed, 23 Jul 2003 10:04:47 -0700 (PDT) (envelope-from uitm@blackflag.ru) Received: from [195.2.90.70] (HELO slt.oz) by frontend2.aha.ru (CommuniGate Pro SMTP 4.0.6) with ESMTP id 200701622 for freebsd-stable@freebsd.org; Wed, 23 Jul 2003 21:04:45 +0400 Received: (from uitm@localhost) by slt.oz (8.8.8/8.8.8) id VAA00542 for freebsd-stable@freebsd.org; Wed, 23 Jul 2003 21:07:03 +0400 (MSD) From: Andrey Alekseyev Message-Id: <200307231707.VAA00542@slt.oz> To: freebsd-stable@freebsd.org Date: Wed, 23 Jul 2003 21:07:02 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: problem w/ php3+php4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 17:04:49 -0000 Hello, Has anybody experienced any problems with php3+php4 combo in systems newer than 4.6-STABLE (as of June-Aug 2002)? Briefly, the problem looks very similar to what is stated in the following reports: http://groups.google.com/groups?q=%22php3+kills+apache%22&hl=ru&lr=&ie=UTF-8&oe=UTF-8&selm=wqz8yrfzbug.wl%40hurt.theclones.net&rnum=1 http://groups.google.com/groups?q=%2Bfreebsd+%2B4.8+%2Bphp3&hl=ru&lr=&ie=UTF-8&oe=UTF-8&selm=b41uk8%241qnklv%241%40fu-berlin.de&rnum=3 I'm stumped :) Any information would be much appreciated. TIA From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 10:34:29 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14E7C37B47C for ; Wed, 23 Jul 2003 10:34:28 -0700 (PDT) Received: from vnode.vmunix.com (vnode.vmunix.com [64.7.135.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id A771A43FDD for ; Wed, 23 Jul 2003 10:34:27 -0700 (PDT) (envelope-from gabor@vmunix.com) Received: by vnode.vmunix.com (Postfix, from userid 1004) id 41938A1A56; Wed, 23 Jul 2003 17:34:27 +0000 (GMT) Date: Wed, 23 Jul 2003 13:34:27 -0400 From: Gabor To: freebsd-stable@freebsd.org Message-ID: <20030723173427.GA72876@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.7-STABLE Subject: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 17:34:29 -0000 We have a little soekris box running freebsd that uses racoon for key management. It's used for setting up an ipsec tunnel. I noticed that one of these devices lost the tunnel this morning. I looked in the log and saw this Jul 23 01:37:57 m0n0wall /kernel: pid 80 (racoon), uid 0, was killed: out of swap space I reproduced this problem using this code. #include int main(int argc, char **argv) { char *p; int cnt = 0; while (1) { p = malloc(100000); printf("%d %p\n", ++cnt, p); if (p) memset(p, 0, 100000); else break; } return 0; } Here is the tail end of the output. It dies when trying to poke at the memory using memset. If I just malloc without the memset, it never even dies. 210 0x94b5000 211 0x94ce000 212 0x94e7000 213 0x9500000 214 0x9519000 215 0x9532000 216 0x954b000 217 0x9564000 218 0x957d000 219 0x9596000 220 0x95af000 221 0x95c8000 Killed The kernel for this has the NO_SWAPPING option enabled since there is essentially no disk, it boots from a CF. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 13:59:23 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19A1D37B401 for ; Wed, 23 Jul 2003 13:59:23 -0700 (PDT) Received: from anchor-post-39.mail.demon.net (anchor-post-39.mail.demon.net [194.217.242.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BCBD43F3F for ; Wed, 23 Jul 2003 13:59:22 -0700 (PDT) (envelope-from steve@sliderule.demon.co.uk) Received: from sliderule.demon.co.uk ([80.177.21.188]) by anchor-post-39.mail.demon.net with esmtp (Exim 3.36 #2) id 19fQhl-0004eb-0U for freebsd-stable@FreeBSD.ORG; Wed, 23 Jul 2003 21:59:21 +0100 Message-ID: <3F1EF728.70406@sliderule.demon.co.uk> Date: Wed, 23 Jul 2003 21:59:20 +0100 From: Steve Burton User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG References: <000601c35043$2dda2d90$3364a8c0@cmlaptop> In-Reply-To: <000601c35043$2dda2d90$3364a8c0@cmlaptop> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 20:59:23 -0000 Carl Morley wrote: > See bottom of email for CLM's comments; > > >>-----Original Message----- >>From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- >>stable@freebsd.org] On Behalf Of Rudolph Pereira >>Sent: Tuesday, 22 July 2003 06:32 >>To: freebsd-stable@FreeBSD.ORG >>Subject: Re: Via EPIA Mini-ITX motherboard >> >>Just to drag this thread on a bit further ... > > > No worries, I have found it a useful thread. > > >>I've been looking into these little boxes, thinking I could use one as > > a > >>firewall/gateway. My one requirement is that it would need to have two >>PCI slots (one can be low-profile), and although I've seen PCI riser >>cards that can give me two slots, they've been rare, and cases that > > are > >>suitable (i.e have the space, and back panels are compatible) >>even rarer (I've yet to find one). Does anyone know of any such >>cases (it'd be even better if they're available in au)? > > > And they can be got - www.traverse.com.au, speak to a bloke by the name > of Guy Ellis. > > >>thanks > > > No probs, but be warned about the vr0 cards. The CPU/chipset is great, > and who cares about sound and video for routing - plus they look bloody > great. I only wish they came with something other than the Rhine > chipset NIC's..... > > Cheers, > Carl. I've two mini-itx machines, one with FreeBSD 5.1 REL and I've had no problems with the vr interface connected to a Cisco switch. I tried the same chip some time ago (about 4.4 or 4.5) with the same switch and the results were lousy. Mine are built in Morex Cubid 2699R cases which look like this: http://www.mini-itx.com/store/images/2699R.jpg quite cool. They could be quieter as I opted for the fastest board which has a fan on the cpu and two in the case. The same people (www.mini-itx.com) also sell two models of silent PC's - totally passive cooling. http://www.mini-itx.com/store/images/tranquil1.jpg and http://www.mini-itx.com/news/images/story0161a.jpg if noise is an issue. The Cubid case comes with a riser and will take one PCI card though I haven't tried fitting a one so I can't comment on what sizes will fit. Actually, there is a review of the Sigma Designs’ REALmagic Xcard on the same site which show it fitting in the Cubid case and that card looks like this: http://www.mini-itx.com/store/images/xcard.jpg The other one has Windows XP Pro (sorry) which I thought I'd try since we're about to roll it out at work. Works very well as a client to the FreeBSD server which I mainly use to run Apache, Samba, ISC-DHCP and BIND which I use for file sharing and cgi programming. I also use it to play^H^H^H^H research on and it normally has more services on than would be good for a gateway so I keep it behind a firewall rather than run it as a firewall. The sound and graphics are more than adequate and the XP box will play DVD's without dropping frames (no DVD in the 'server' box). BTW I've no connection with mini-itx.com other than as a (satisfied) customer - it was just a convenient site for the photos. Hope this helps. Steve. > > >>_______________________________________________ >>freebsd-stable@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>To unsubscribe, send any mail to > > "freebsd-stable-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 14:02:56 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75D3A37B401 for ; Wed, 23 Jul 2003 14:02:56 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10A2B43FB1 for ; Wed, 23 Jul 2003 14:02:56 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id F334C72DD1; Wed, 23 Jul 2003 14:02:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id ED8B472DD0; Wed, 23 Jul 2003 14:02:55 -0700 (PDT) Date: Wed, 23 Jul 2003 14:02:55 -0700 (PDT) From: Doug White To: Scott Mitchell In-Reply-To: <20030723104631.GA11861@llama.fishballoon.org> Message-ID: <20030723140217.P92624@carver.gumbysoft.com> References: <20030723104631.GA11861@llama.fishballoon.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 21:02:56 -0000 On Wed, 23 Jul 2003, Scott Mitchell wrote: > We recently moved our CVS repository from a 4.6-STABLE machine to a brand > new 4.8 install, on another identical machine. The server runs cvs in > 'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD > clients. > > We pretty soon noticed that the cvs server process was occasionally crashing > on sig11 (ie. a segfault). Does the new machine have ECC memory? If not, it could be something as simple as bad RAM in the new system. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 14:09:01 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6048237B401 for ; Wed, 23 Jul 2003 14:09:01 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E911243F3F for ; Wed, 23 Jul 2003 14:09:00 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id DBF3872DD1; Wed, 23 Jul 2003 14:09:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id D972A72DD0; Wed, 23 Jul 2003 14:09:00 -0700 (PDT) Date: Wed, 23 Jul 2003 14:09:00 -0700 (PDT) From: Doug White To: Gabor In-Reply-To: <20030723173427.GA72876@vmunix.com> Message-ID: <20030723140329.C92624@carver.gumbysoft.com> References: <20030723173427.GA72876@vmunix.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 21:09:01 -0000 On Wed, 23 Jul 2003, Gabor wrote: > We have a little soekris box running freebsd that uses racoon for key > management. It's used for setting up an ipsec tunnel. I noticed that > one of these devices lost the tunnel this morning. I looked in the > log and saw this > > Jul 23 01:37:57 m0n0wall /kernel: pid 80 (racoon), uid 0, was killed: out of swap space [...] > Here is the tail end of the output. It dies when trying to poke at > the memory using memset. If I just malloc without the memset, it > never even dies. That's normal. If you malloc() memory and never touch it then it is never actually allocated. Your problem is that you're running out of memory. Try killing off unneeded daemons and set maxusers to a low value (like 32). Also try reducing the size of your mfs partitions, if you're using rc.diskless2. I don't think raccoon is much of a memory pig, unless you have a huge number of connections. > The kernel for this has the NO_SWAPPING option enabled since there is > essentially no disk, it boots from a CF. Do you have the 32MB or 64MB version? I have a net4501 (64MB) and I still have 39MB free. Its just running natd, sshd, named and dhcpd. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 14:32:09 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5408F37B401 for ; Wed, 23 Jul 2003 14:32:09 -0700 (PDT) Received: from hyperreal.org (taz3.hyperreal.org [209.237.226.90]) by mx1.FreeBSD.org (Postfix) with SMTP id 9CFF343F3F for ; Wed, 23 Jul 2003 14:32:08 -0700 (PDT) (envelope-from brian@collab.net) Received: (qmail 55233 invoked from network); 23 Jul 2003 21:32:10 -0000 Received: from localhost.hyperreal.org (HELO fez.hyperreal.org) (127.0.0.1) by localhost.hyperreal.org with SMTP; 23 Jul 2003 21:32:10 -0000 Received: (qmail 34054 invoked by uid 1000); 23 Jul 2003 21:32:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Jul 2003 21:32:06 -0000 Date: Wed, 23 Jul 2003 14:32:06 -0700 (PDT) From: Brian Behlendorf X-X-Sender: brian@fez.hyperreal.org To: freebsd-stable@freebsd.org In-Reply-To: <20030723140217.P92624@carver.gumbysoft.com> Message-ID: <20030723143055.B33445@fez.hyperreal.org> References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost.hyperreal.org 1.6.2 0/1000/N Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 21:32:09 -0000 On Wed, 23 Jul 2003, Doug White wrote: > On Wed, 23 Jul 2003, Scott Mitchell wrote: > > > We recently moved our CVS repository from a 4.6-STABLE machine to a brand > > new 4.8 install, on another identical machine. The server runs cvs in > > 'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD > > clients. > > > > We pretty soon noticed that the cvs server process was occasionally crashing > > on sig11 (ie. a segfault). > > Does the new machine have ECC memory? If not, it could be something as > simple as bad RAM in the new system. For what it's worth, we see it at apache.org too, and haven't seen any other evidence of hardware-related problems. Brian From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 14:41:48 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF8F037B401 for ; Wed, 23 Jul 2003 14:41:48 -0700 (PDT) Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8490B43F3F for ; Wed, 23 Jul 2003 14:41:47 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta06-svc.ntlworld.comESMTP <20030723214144.SBAU16215.mta06-svc.ntlworld.com@llama.fishballoon.org>; Wed, 23 Jul 2003 22:41:44 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19fRM4-0004Mu-0Q; Wed, 23 Jul 2003 22:41:00 +0100 Date: Wed, 23 Jul 2003 22:40:59 +0100 From: Scott Mitchell To: Doug White Message-ID: <20030723214059.GA16594@llama.fishballoon.org> References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723140217.P92624@carver.gumbysoft.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 21:41:49 -0000 On Wed, Jul 23, 2003 at 02:02:55PM -0700, Doug White wrote: > On Wed, 23 Jul 2003, Scott Mitchell wrote: > > > We recently moved our CVS repository from a 4.6-STABLE machine to a brand > > new 4.8 install, on another identical machine. The server runs cvs in > > 'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD > > clients. > > > > We pretty soon noticed that the cvs server process was occasionally crashing > > on sig11 (ie. a segfault). > > Does the new machine have ECC memory? If not, it could be something as > simple as bad RAM in the new system. It does have ECC, as does the old machine. Bad RAM was my first thought, too, but surely that's a bit unlikely when it's only one program that crashes, and always at *exactly* the same point in the code... The machine is due for a RAM upgrade anyway, so maybe I'll swap the whole lot out and see if that makes any difference, but I'm not hopeful. Scott From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 15:13:37 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7A4037B401 for ; Wed, 23 Jul 2003 15:13:37 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1629243FA3 for ; Wed, 23 Jul 2003 15:13:37 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6NMDan8027099; Wed, 23 Jul 2003 18:13:36 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6NMDaJf027098; Wed, 23 Jul 2003 18:13:36 -0400 (EDT) (envelope-from barney) Date: Wed, 23 Jul 2003 18:13:36 -0400 From: Barney Wolff To: Doug White Message-ID: <20030723221336.GA26555@pit.databus.com> References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723140329.C92624@carver.gumbysoft.com> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org cc: Gabor Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 22:13:38 -0000 On Wed, Jul 23, 2003 at 02:09:00PM -0700, Doug White wrote: > On Wed, 23 Jul 2003, Gabor wrote: > > > We have a little soekris box running freebsd that uses racoon for key > > management. It's used for setting up an ipsec tunnel. I noticed that > > one of these devices lost the tunnel this morning. I looked in the > > log and saw this > > > > Jul 23 01:37:57 m0n0wall /kernel: pid 80 (racoon), uid 0, was killed: out of swap space > > [...] > > > Here is the tail end of the output. It dies when trying to poke at > > the memory using memset. If I just malloc without the memset, it > > never even dies. > > That's normal. If you malloc() memory and never touch it then it is never > actually allocated. > > Your problem is that you're running out of memory. Try killing off > unneeded daemons and set maxusers to a low value (like 32). Also try > reducing the size of your mfs partitions, if you're using rc.diskless2. I > don't think raccoon is much of a memory pig, unless you have a huge number > of connections. Shouldn't malloc return 0 when out of memory rather than returning an address that won't work? I believe that was the complaint. Presumably having NO_SWAPPING has something to do with it, but filling the swap might well do the same thing. One might argue that this is a config error, and ulimit should be used to cut the address space to below actually available memory. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 15:22:33 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCDE937B404 for ; Wed, 23 Jul 2003 15:22:33 -0700 (PDT) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FE9143F75 for ; Wed, 23 Jul 2003 15:22:33 -0700 (PDT) (envelope-from darrylo@soco.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id E551115CE4; Wed, 23 Jul 2003 16:22:29 -0600 (MDT) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by relcos2.cos.agilent.com (Postfix) with ESMTP id CE69D21; Wed, 23 Jul 2003 16:22:31 -0600 (MDT) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id PAA26360; Wed, 23 Jul 2003 15:22:31 -0700 (PDT) Message-Id: <200307232222.PAA26360@mina.soco.agilent.com> To: Barney Wolff In-Reply-To: Your message of "Wed, 23 Jul 2003 18:13:36 EDT." <20030723221336.GA26555@pit.databus.com> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Wed, 23 Jul 2003 15:22:30 -0700 From: Darryl Okahata cc: freebsd-stable@freebsd.org cc: Gabor Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 22:22:34 -0000 Barney Wolff wrote: > Shouldn't malloc return 0 when out of memory rather than returning > an address that won't work? I believe that was the complaint. Presumably > having NO_SWAPPING has something to do with it, but filling the swap > might well do the same thing. Well, it goes against the man page, but FreeBSD typically never returns NULL [*] when you run out of VM. It's been this way for YEARS. [*] -- Yes, it's annoying as h*ll, but that's the way it works. I thought that there was a FAQ or handbook entry on this, but I couldn't find any. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 15:23:19 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C733B37B401 for ; Wed, 23 Jul 2003 15:23:18 -0700 (PDT) Received: from laptop.tenebras.com (laptop.tenebras.com [66.92.188.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 8052543F85 for ; Wed, 23 Jul 2003 15:23:14 -0700 (PDT) (envelope-from kudzu@tenebras.com) Received: (qmail 23502 invoked from network); 23 Jul 2003 22:23:13 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241) by 0 with SMTP; 23 Jul 2003 22:23:13 -0000 Message-ID: <3F1F0ACF.7000705@tenebras.com> Date: Wed, 23 Jul 2003 15:23:11 -0700 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, zh-tw, zh-cn, fr, en, de-de MIME-Version: 1.0 To: Gabor References: <20030723173427.GA72876@vmunix.com> In-Reply-To: <20030723173427.GA72876@vmunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 22:23:20 -0000 > The kernel for this has the NO_SWAPPING option enabled since there is > essentially no disk, it boots from a CF. man malloc. In particular, see the MALLOC_OPTIONS you might place in /etc/malloc.conf From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 15:37:23 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83C2537B401 for ; Wed, 23 Jul 2003 15:37:23 -0700 (PDT) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id D722443F3F for ; Wed, 23 Jul 2003 15:37:22 -0700 (PDT) (envelope-from mkb@moghedien.mukappabeta.net) Received: by moghedien.mukappabeta.net (Postfix, from userid 1000) id CD7502D2F; Thu, 24 Jul 2003 00:36:54 +0200 (CEST) Date: Thu, 24 Jul 2003 00:36:54 +0200 From: Matthias Buelow To: Barney Wolff Message-ID: <20030723223654.GA24008@moghedien.mukappabeta.net> References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723221336.GA26555@pit.databus.com> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org cc: Gabor Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 22:37:23 -0000 Barney Wolff writes: >One might argue that this is a config error, and ulimit should be used >to cut the address space to below actually available memory. Wasn't there a sysctl flag to enable/disable overcommitting? I think I remember something but I can't find it; it might not have been on FreeBSD. -- Matthias Buelow; mkb@{mukappabeta.de,informatik.uni-wuerzburg.de} From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 15:44:46 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFE4337B401 for ; Wed, 23 Jul 2003 15:44:46 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E9A443F75 for ; Wed, 23 Jul 2003 15:44:46 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.9/8.12.3) with ESMTP id h6NMibqh013282; Wed, 23 Jul 2003 15:44:37 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id h6NMiaAp013277; Wed, 23 Jul 2003 15:44:36 -0700 Date: Wed, 23 Jul 2003 15:44:36 -0700 From: Brooks Davis To: Matthias Buelow Message-ID: <20030723224436.GD22166@Odin.AC.HMC.Edu> References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AbQceqfdZEv+FvjW" Content-Disposition: inline In-Reply-To: <20030723223654.GA24008@moghedien.mukappabeta.net> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Barney Wolff cc: freebsd-stable@freebsd.org cc: Gabor Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 22:44:47 -0000 --AbQceqfdZEv+FvjW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 24, 2003 at 12:36:54AM +0200, Matthias Buelow wrote: > Barney Wolff writes: >=20 > >One might argue that this is a config error, and ulimit should be used > >to cut the address space to below actually available memory. >=20 > Wasn't there a sysctl flag to enable/disable overcommitting? > I think I remember something but I can't find it; it might > not have been on FreeBSD. No there isn't. Overcommit is a fundamental design feature of the BSD VM. If you don't like it, find an OS that doesn't do it. The only one I can think of off the top of my head in Irix where I've found it to be a serious pain in the ass. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --AbQceqfdZEv+FvjW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/Hw+zXY6L6fI4GtQRAsg6AJ95BgSlfEWbFU5wqRIXZn6I8rSIogCeI+b+ DBGWL17RtQYfBrKp9vhw34U= =1YO1 -----END PGP SIGNATURE----- --AbQceqfdZEv+FvjW-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 15:48:49 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F47337B401 for ; Wed, 23 Jul 2003 15:48:49 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 568F943FA3 for ; Wed, 23 Jul 2003 15:48:48 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6NMmkn8027774; Wed, 23 Jul 2003 18:48:46 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6NMmkcJ027773; Wed, 23 Jul 2003 18:48:46 -0400 (EDT) (envelope-from barney) Date: Wed, 23 Jul 2003 18:48:46 -0400 From: Barney Wolff To: Darryl Okahata Message-ID: <20030723224846.GB26555@pit.databus.com> References: <20030723221336.GA26555@pit.databus.com> <200307232222.PAA26360@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307232222.PAA26360@mina.soco.agilent.com> User-Agent: Mutt/1.4.1i cc: Barney Wolff cc: freebsd-stable@freebsd.org cc: Gabor Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 22:48:49 -0000 On Wed, Jul 23, 2003 at 03:22:30PM -0700, Darryl Okahata wrote: > Barney Wolff wrote: > > > Shouldn't malloc return 0 when out of memory rather than returning > > an address that won't work? I believe that was the complaint. Presumably > > having NO_SWAPPING has something to do with it, but filling the swap > > might well do the same thing. > > Well, it goes against the man page, but FreeBSD typically never > returns NULL [*] when you run out of VM. It's been this way for YEARS. > > [*] -- Yes, it's annoying as h*ll, but that's the way it works. I > thought that there was a FAQ or handbook entry on this, but I > couldn't find any. This test prog appears to work correctly: #include main() { char *p; int i=0; while (p=(char*)malloc(102400)) { *p = i; fprintf(stderr,"Ok after %d mallocs\n",++i); } fprintf(stderr,"Malloc returned 0 after %d calls\n",i); exit(0); } FreeBSD pit.databus.com 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 8 23:22:41 EDT 2003 toor@pit.databus.com:/usr/obj/usr/src/sys/PIT i386 ulimit -a says my data limit is 524288 KB, and the test says: Malloc returned 0 after 5242 calls When I ulimit -v 20000, malloc returns 0 after 191 calls. So I believe things work correctly on my host, which does have swap although the test does not use it. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 16:01:02 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76EF937B401 for ; Wed, 23 Jul 2003 16:01:02 -0700 (PDT) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE33543F75 for ; Wed, 23 Jul 2003 16:01:01 -0700 (PDT) (envelope-from mkb@moghedien.mukappabeta.net) Received: by moghedien.mukappabeta.net (Postfix, from userid 1000) id 8A8B42D2F; Thu, 24 Jul 2003 01:00:34 +0200 (CEST) Date: Thu, 24 Jul 2003 01:00:34 +0200 From: Matthias Buelow To: freebsd-stable@freebsd.org Message-ID: <20030723230034.GB24008@moghedien.mukappabeta.net> References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> <20030723224436.GD22166@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723224436.GD22166@Odin.AC.HMC.Edu> User-Agent: Mutt/1.4.1i Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 23:01:02 -0000 Brooks Davis writes: >No there isn't. Overcommit is a fundamental design feature of the BSD >VM. If you don't like it, find an OS that doesn't do it. The only one >I can think of off the top of my head in Irix where I've found it to be >a serious pain in the ass. Hmm, I could've sworn that fbsd's got some option to toggle it. But apparently this is not so, a pity. I'd like to have the choice between better resource usage (with overcommit enabled) and safer operation (disabled, when an application won't crash at some random point because it cannot get mapped memory). -- Matthias Buelow; mkb@{mukappabeta.de,informatik.uni-wuerzburg.de} From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 16:38:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1BD637B404 for ; Wed, 23 Jul 2003 16:38:50 -0700 (PDT) Received: from anchor-post-39.mail.demon.net (anchor-post-39.mail.demon.net [194.217.242.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FADA43FB1 for ; Wed, 23 Jul 2003 16:38:50 -0700 (PDT) (envelope-from steve@sliderule.demon.co.uk) Received: from sliderule.demon.co.uk ([80.177.21.188]) by anchor-post-39.mail.demon.net with esmtp (Exim 3.36 #2) id 19fTC4-0003rS-0U; Thu, 24 Jul 2003 00:38:48 +0100 Message-ID: <3F1F1C88.5040101@sliderule.demon.co.uk> Date: Thu, 24 Jul 2003 00:38:48 +0100 From: Steve Burton User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: "Andrew P. Lentvorski, Jr." , stable References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 23:38:51 -0000 Andrew P. Lentvorski, Jr. wrote: > On Wed, 23 Jul 2003, Steve Burton wrote: > > >>I've two mini-itx machines, one with FreeBSD 5.1 REL and I've had no >>problems with the vr interface connected to a Cisco switch. > > > I've had good luck with everything on these boards except for XFree86 and > the Castlerock graphics. Did you manage to get that working somehow? > > Even if you didn't, that data would be useful too. > > -a > I didn't even try. As I said I use this one as a server. Didn't even buy a mouse for it. Sorry. Steve. > > > From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 17:05:25 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A902937B401 for ; Wed, 23 Jul 2003 17:05:25 -0700 (PDT) Received: from blues.jpj.net (blues.jpj.net [208.210.80.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBBFB43FB1 for ; Wed, 23 Jul 2003 17:05:24 -0700 (PDT) (envelope-from benh@jpj.net) Received: from [192.168.11.10] (dryden.horked.net [216.162.122.26]) by blues.jpj.net (8.12.9/8.12.3) with ESMTP id h6O05LFh088795 for ; Wed, 23 Jul 2003 20:05:21 -0400 (EDT) (envelope-from benh@jpj.net) X-Sender: benh@blues.jpj.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 23 Jul 2003 19:05:42 -0500 To: freebsd-stable@freebsd.org From: Ben Hockenhull Subject: Qlogic Fibrechannel and detecting new LUNs on the fly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 00:05:26 -0000 Hi there, I've installed a Qlogic HBA in a 4.8-STABLE machine and I'm able to present LUNs to this machine from an HDS array and use them. That all works perfectly. However, the only time I pick up new LUNs is on a reboot. Seems like I should be able to rescan the fabric and pick up new LUNs, but there doesn't seem to be a way to do this. I tried camcontrol rescan, but that didn't work. Any ideas? Thanks ben From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 18:52:32 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DE7837B401 for ; Wed, 23 Jul 2003 18:52:32 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A47EB43F85 for ; Wed, 23 Jul 2003 18:52:31 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h6O1qCM7053256; Wed, 23 Jul 2003 18:52:15 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200307240152.h6O1qCM7053256@gw.catspoiler.org> Date: Wed, 23 Jul 2003 18:52:12 -0700 (PDT) From: Don Lewis To: brooks@one-eyed-alien.net In-Reply-To: <20030723224436.GD22166@Odin.AC.HMC.Edu> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: mkb@mukappabeta.de cc: barney@databus.com cc: freebsd-stable@FreeBSD.org cc: gabor@vmunix.com Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 01:52:32 -0000 On 23 Jul, Brooks Davis wrote: > On Thu, Jul 24, 2003 at 12:36:54AM +0200, Matthias Buelow wrote: >> Barney Wolff writes: >> >> >One might argue that this is a config error, and ulimit should be used >> >to cut the address space to below actually available memory. >> >> Wasn't there a sysctl flag to enable/disable overcommitting? >> I think I remember something but I can't find it; it might >> not have been on FreeBSD. > > No there isn't. Overcommit is a fundamental design feature of the BSD > VM. If you don't like it, find an OS that doesn't do it. The only one > I can think of off the top of my head in Irix where I've found it to be > a serious pain in the ass. I think it's a pain in the ass when swap runs out and the kernel decides to kill off my X11 server to fix the problem. In addition to losing everything I'm working on, it also hoses the console. The only reason that I can avoid having to hit the reset switch and risking further system damage is that I have another machine that I can ssh in from to do a clean shutdown. I used SunOS 4.x, which did not overcommit, for many years. Its typical failure mode when swap was exhausted is that large processes would get a error when they attempted to fork() and large memory alloction requests would fail. Everything else would generally keep working because smaller memory allocation requests would still succeed. This usually gave me enough time to take corrective action (generally by cleaning up junk files in /tmp which was a tmpfs mount). From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 19:17:33 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E11137B401 for ; Wed, 23 Jul 2003 19:17:33 -0700 (PDT) Received: from alcanet.com.au (mail3.alcanet.com.au [208.178.117.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9B6943FBF for ; Wed, 23 Jul 2003 19:17:30 -0700 (PDT) (envelope-from peter.jeremy@alcatel.com.au) Received: from sydsmtp01.alcatel.com.au (IDENT:root@localhost.localdomain [127.0.0.1])h6O2HRvU021024; Thu, 24 Jul 2003 12:17:27 +1000 Received: from gsmx07.alcatel.com.au ([139.188.20.247]) by sydsmtp01.alcatel.com.au (Lotus Domino Release 5.0.12) with ESMTP id 2003072412172712:68446 ; Thu, 24 Jul 2003 12:17:27 +1000 Received: from gsmx07.alcatel.com.au (localhost [127.0.0.1]) by gsmx07.alcatel.com.au (8.12.9/8.12.9) with ESMTP id h6O2HQ7d083364; Thu, 24 Jul 2003 12:17:26 +1000 (EST) (envelope-from peter.jeremy@alcatel.com.au) Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.12.9/8.12.9/Submit) id h6O2HQ97083363; Thu, 24 Jul 2003 12:17:26 +1000 (EST) (envelope-from peter.jeremy@alcatel.com.au) Date: Thu, 24 Jul 2003 12:17:26 +1000 From: Peter Jeremy To: Brooks Davis Message-ID: <20030724021726.GJ430@gsmx07.alcatel.com.au> Mail-Followup-To: Brooks Davis , Matthias Buelow , freebsd-stable@freebsd.org References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> <20030723224436.GD22166@Odin.AC.HMC.Edu> Mime-Version: 1.0 In-Reply-To: <20030723224436.GD22166@Odin.AC.HMC.Edu> User-Agent: Mutt/1.4.1i X-MIMETrack: Itemize by SMTP Server on SYDSMTP01/AlcatelAustralia(Release 5.0.12 |February 13, 2003) at 24/07/2003 12:17:27 PM,|February 13, 2003) at 24/07/2003 12:17:28 PM, Serialize complete at 24/07/2003 12:17:28 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline cc: Matthias Buelow cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 02:17:33 -0000 On 2003-Jul-23 15:44:36 -0700, Brooks Davis wrote: >On Thu, Jul 24, 2003 at 12:36:54AM +0200, Matthias Buelow wrote: >> Wasn't there a sysctl flag to enable/disable overcommitting? >> I think I remember something but I can't find it; it might >> not have been on FreeBSD. > >No there isn't. Overcommit is a fundamental design feature of the BSD >VM. If you don't like it, find an OS that doesn't do it. The only one >I can think of off the top of my head in Irix where I've found it to be >a serious pain in the ass. DEC/Compaq/HP Tru64 has a flag to enable/disable overcommit. The major benefit seems to accrue to disk vendors with all the additional swap space needed. FreeBSD behaviour in the face of swap shortage is a regular and popular discussion topic. I suggest that a perusal of the archives will probably answer any questions. If anyone wishes to suggest a "solution" to FreeBSD's behaviour when there is a shortage of swap, please include patches. Peter From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 19:31:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90E4D37B401 for ; Wed, 23 Jul 2003 19:31:00 -0700 (PDT) Received: from altair.mukappabeta.net (p3E9BE28C.dip.t-dialin.net [62.155.226.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43B5843F85 for ; Wed, 23 Jul 2003 19:30:58 -0700 (PDT) (envelope-from mkb@mukappabeta.de) Received: from mukappabeta.de (localhost [127.0.0.1]) by altair.mukappabeta.net (Postfix) with ESMTP id 8F71F5959 for ; Thu, 24 Jul 2003 04:35:14 +0200 (CEST) Message-ID: <3F1F45E2.5080506@mukappabeta.de> Date: Thu, 24 Jul 2003 04:35:14 +0200 From: Matthias Buelow Organization: GeFoekoM e.V. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4a) Gecko/20030504 X-Accept-Language: de-de, de, en-gb, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> <20030723224436.GD22166@Odin.AC.HMC.Edu> <20030724021726.GJ430@gsmx07.alcatel.com.au> In-Reply-To: <20030724021726.GJ430@gsmx07.alcatel.com.au> X-Enigmail-Version: 0.75.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 02:31:00 -0000 Peter Jeremy wrote: > FreeBSD behaviour in the face of swap shortage is a regular and > popular discussion topic. I suggest that a perusal of the archives > will probably answer any questions. If anyone wishes to suggest a > "solution" to FreeBSD's behaviour when there is a shortage of swap, > please include patches. What makes me ask the following (note that it's neither a flame, nor a suggestion). Does FreeBSD actually account the used swap/vm so far (it needn't since it doesn't guarantee that it'll be available, with overcommit) or does it not do that (i.e., it has no idea of how much vm was requested by all processes so far, without having to go through the maps of all processes, of course)? And is it planned in the (distant) future to add a knob to toggle overcommitting of swap? While with large disks and hence swap sizes this probably isn't a pressing problem for most applications, it might be nice to be able to control the system not to randomly kill off applications or force the user to meticulously plan and calculate memory load of the planned application zoo in order to tune the ulimits of various memory-hungry processes in a way that they'll all fit into swap in the worst case situation. -- Matthias Buelow; mkb@{mukappabeta.de,informatik.uni-wuerzburg.de} From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 19:34:37 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDF1837B401 for ; Wed, 23 Jul 2003 19:34:37 -0700 (PDT) Received: from altair.mukappabeta.net (p3E9BE28C.dip.t-dialin.net [62.155.226.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ABBD43FAF for ; Wed, 23 Jul 2003 19:34:36 -0700 (PDT) (envelope-from mkb@mukappabeta.de) Received: from mukappabeta.de (localhost [127.0.0.1]) by altair.mukappabeta.net (Postfix) with ESMTP id 4FAE35959 for ; Thu, 24 Jul 2003 04:38:58 +0200 (CEST) Message-ID: <3F1F46C2.5000106@mukappabeta.de> Date: Thu, 24 Jul 2003 04:38:58 +0200 From: Matthias Buelow Organization: GeFoekoM e.V. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4a) Gecko/20030504 X-Accept-Language: de-de, de, en-gb, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> <20030723224436.GD22166@Odin.AC.HMC.Edu> <20030724021726.GJ430@gsmx07.alcatel.com.au> In-Reply-To: <20030724021726.GJ430@gsmx07.alcatel.com.au> X-Enigmail-Version: 0.75.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 02:34:38 -0000 Peter Jeremy wrote: > FreeBSD behaviour in the face of swap shortage is a regular and > popular discussion topic. I suggest that a perusal of the archives Yes but I for example have had this issue since 2.1-R (when I started using it), freezing when the system trashes, without hope for resolve, or other short-on-memory related ailments. The fact that it's still on-topic in mailing lists after many years shows that the issue hasn't really been resolved yet. You'll see postings like the above in 5 or even 10 years still if a proper solution won't be found and implemented until then. -- Matthias Buelow; mkb@{mukappabeta.de,informatik.uni-wuerzburg.de} From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 20:09:15 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0CF937B401 for ; Wed, 23 Jul 2003 20:09:15 -0700 (PDT) Received: from mailgate.sri.com (mailgate.SRI.COM [128.18.243.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 039B643F3F for ; Wed, 23 Jul 2003 20:09:15 -0700 (PDT) (envelope-from gilham@csl.sri.com) Received: (qmail 23760 invoked from network); 24 Jul 2003 02:20:11 -0000 Received: from localhost (HELO mailgate.SRI.COM) (127.0.0.1) by mailgate.sri.com with SMTP; 24 Jul 2003 02:20:11 -0000 Received: from quarter.csl.sri.com ([130.107.1.30]) by mailgate.SRI.COM (SAVSMTP 3.1.0.29) with SMTP id M2003072319201126074 for ; Wed, 23 Jul 2003 19:20:11 -0700 Received: from snapdragon.csl.sri.com (snapdragon.csl.sri.com [130.107.19.20]) by quarter.csl.sri.com (8.12.9/8.12.9) with ESMTP id h6O2K8dW032615; Wed, 23 Jul 2003 19:20:08 -0700 Message-Id: <200307240220.h6O2K8dW032615@quarter.csl.sri.com> To: freebsd-stable@freebsd.org Date: Wed, 23 Jul 2003 19:20:08 -0700 From: Fred Gilham cc: gilham@sdl.sri.com Subject: Question about malloc, mmap etc. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 03:09:16 -0000 I'm trying to do a little system hacking on CMU Lisp. Currently CMU Lisp has a minimum of two files needed to execute. One is a program usually called "lisp" that the OS runs, which basically a loader for the other file, a lisp.core file that contains the actual lisp system. People have been asking for a way to make a "lisp executable" meaning putting everything into a single file. It's more than just tidiness --- the core and loader have to stay synchronized, and in the normal process of keeping the system up to date you can sometimes wind up with an old core file that you can no longer run because you don't have the corresponding loader any more and it would be tedious to recover it. Anyway I created a utility that post-processes the lisp.core file, creating three ELF compatible ".o" files, one for each memory space that lisp uses. I then hacked a linker script so that GNU ld will put these .o files in the executable and add the proper program headers. It all worked, and I can actually run the resulting executable. Unfortunately it doesn't get far. The first time it calls malloc, malloc tries to call sbrk (I think it's sbrk) twice and those calls return invalid argument errors. Malloc then returns 0. I used ktrace and the "U" malloc_option to determine this --- the calls show up as follows: 89021 testit CALL readlink(0x680bbf14,0xbfbff3b0,0x3f) 89021 testit NAMI "/etc/malloc.conf" 89021 testit RET readlink -1 errno 2 No such file or directory 89021 testit CALL utrace(0xbfbff3a4,0xc) 89021 testit USER 12 00 00 00 00 00 00 00 00 00 00 00 00 89021 testit RET utrace 0 89021 testit CALL mmap(0,0x1000,0x3,0x1002,0xffffffff,0,0,0) 89021 testit RET mmap 1745698816/0x680d4000 89021 testit CALL break(0x8067000) 89021 testit RET break -1 errno 22 Invalid argument 89021 testit CALL break(0x81e6000) 89021 testit RET break -1 errno 22 Invalid argument 89021 testit CALL utrace(0xbfbff414,0xc) 89021 testit USER 12 00 00 00 00 00 00 18 00 00 00 00 00 89021 testit RET utrace 0 I tried to look at the source to see if I could find out what is causing the "break" calls to return EINVAL but I couldn't find the actual code that does these system calls. The man page says EINVAL gets returned when "The requested break value was beyond the beginning of the data segment," which doesn't quite make sense to me. The segments my program creates are at 0x10000000, 0x28f00000 and 0x48000000 if that makes a difference. Anyway my question is whether anyone knows why this might be happening or if someone can point me in the right direction to find out. Thanks for any help! -- Fred Gilham gilham@csl.sri.com If you want to be largely ignored by women, playing jazz guitar is pretty good strategy... --- Bob Russell From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 20:16:13 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B96C137B401 for ; Wed, 23 Jul 2003 20:16:13 -0700 (PDT) Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40A9243F85 for ; Wed, 23 Jul 2003 20:16:13 -0700 (PDT) (envelope-from kris@citusc.usc.edu) Received: (from kris@localhost) by citusc.usc.edu (8.11.6/8.11.2) id h6O3FaW22040; Wed, 23 Jul 2003 20:15:36 -0700 Date: Wed, 23 Jul 2003 20:15:36 -0700 From: Kris Kennaway To: Gabor Message-ID: <20030723201536.A22031@citusc.usc.edu> References: <20030723173427.GA72876@vmunix.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030723173427.GA72876@vmunix.com>; from gabor@vmunix.com on Wed, Jul 23, 2003 at 01:34:27PM -0400 cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 03:16:14 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote: > Here is the tail end of the output. It dies when trying to poke at > the memory using memset. If I just malloc without the memset, it > never even dies. Ah, the annual "memory overcommit" thread. I thought we were overdue for one. Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/H09XWry0BWjoQKURAnKjAJwP/0VGv1n7tqhh0t5Cn9unc6Pj8gCgnmSc Oacq7AHYJb9RdTSOfAcIwJA= =jJLE -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 20:46:22 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F69A37B401 for ; Wed, 23 Jul 2003 20:46:22 -0700 (PDT) Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D0DE43FA3 for ; Wed, 23 Jul 2003 20:46:19 -0700 (PDT) (envelope-from mike@sentex.net) Received: from house.sentex.net (fcage [192.168.0.2])h6O3kDlD072707; Wed, 23 Jul 2003 23:46:14 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 23 Jul 2003 23:44:11 -0400 To: Kris Kennaway From: Mike Tancsa In-Reply-To: <20030723201536.A22031@citusc.usc.edu> References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: amavis-20020220 cc: freebsd-stable@freebsd.org cc: Gabor Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 03:46:22 -0000 At 08:15 PM 7/23/2003 -0700, Kris Kennaway wrote: >On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote: > > > Here is the tail end of the output. It dies when trying to poke at > > the memory using memset. If I just malloc without the memset, it > > never even dies. > >Ah, the annual "memory overcommit" thread. I thought we were overdue >for one. But why does the man page for malloc (3) say, If malloc() fails, a NULL pointer is returned. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 23:58:39 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7704837B404 for ; Wed, 23 Jul 2003 23:58:39 -0700 (PDT) Received: from mta02bw.bigpond.com (mta02bw.bigpond.com [144.135.24.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A1C643F85 for ; Wed, 23 Jul 2003 23:58:30 -0700 (PDT) (envelope-from areilly@bigpond.net.au) Received: from areilly.bpc-users.org ([144.135.24.72]) by mta02bw.email.bigpond.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0HII008KQOC4D2@mta02bw.email.bigpond.com> for freebsd-stable@freebsd.org; Thu, 24 Jul 2003 16:50:28 +1000 (EST) Received: from cpe-144-132-191-61.nsw.bigpond.net.au ([144.132.191.61]) by bwmam02bpa.bigpond.com(MAM REL_3_3_2c 17/10252856); Thu, 24 Jul 2003 16:50:27 +0000 Received: (qmail 17832 invoked from network); Thu, 24 Jul 2003 06:50:28 +0000 Received: from unknown (HELO bigpond.net.au) (203.202.138.82) by localhost with SMTP; Thu, 24 Jul 2003 06:50:28 +0000 Date: Thu, 24 Jul 2003 16:49:34 +1000 From: Andrew Reilly In-reply-to: <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> To: Mike Tancsa Message-id: <3F1F817E.7040504@bigpond.net.au> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030716 Thunderbird/0.1a References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> cc: Gabor cc: freebsd-stable@freebsd.org cc: Kris Kennaway Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 06:58:39 -0000 Mike Tancsa wrote: > At 08:15 PM 7/23/2003 -0700, Kris Kennaway wrote: > >> On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote: >> >> > Here is the tail end of the output. It dies when trying to poke at >> > the memory using memset. If I just malloc without the memset, it >> > never even dies. >> >> Ah, the annual "memory overcommit" thread. I thought we were overdue >> for one. > > > > But why does the man page for malloc (3) say, > > If malloc() fails, a NULL pointer is returned. Because that's what happens. See the subthread with the ulimit examples. In the cases being cited, the malloc itself is not failing, because it is able to return a pointer to a chunk of *VM*. The problem occurrs later, when the program attempts to read or write to that memory, and it doesn't occur because malloc was wrong, but because no other process has exited or unmapped something in the mean-time, to free up a page to back that address space. -- Andrew From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 00:09:40 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6731B37B401 for ; Thu, 24 Jul 2003 00:09:40 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-67-119-53-152.dsl.lsan03.pacbell.net [67.119.53.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 947E343FD7 for ; Thu, 24 Jul 2003 00:09:39 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id ECADD66D32; Thu, 24 Jul 2003 00:09:36 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id CC054C12; Thu, 24 Jul 2003 00:09:36 -0700 (PDT) Date: Thu, 24 Jul 2003 00:09:36 -0700 From: Kris Kennaway To: Mike Tancsa Message-ID: <20030724070936.GA16762@rot13.obsecurity.org> References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> User-Agent: Mutt/1.4.1i cc: Gabor cc: freebsd-stable@freebsd.org cc: Kris Kennaway Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 07:09:40 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 23, 2003 at 11:44:11PM -0400, Mike Tancsa wrote: > At 08:15 PM 7/23/2003 -0700, Kris Kennaway wrote: > >On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote: > > > >> Here is the tail end of the output. It dies when trying to poke at > >> the memory using memset. If I just malloc without the memset, it > >> never even dies. > > > >Ah, the annual "memory overcommit" thread. I thought we were overdue > >for one. >=20 >=20 > But why does the man page for malloc (3) say, >=20 > If malloc() fails, a NULL pointer is returned. Words fail me. Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/H4YwWry0BWjoQKURAprjAJwJSPTpVGWuQ/ogsKX5pcxhGd3rMACfTji2 XzkCbfFRSeaUr49gbieOasw= =tW8v -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 01:53:46 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1CE637B401 for ; Thu, 24 Jul 2003 01:53:46 -0700 (PDT) Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id A112443F75 for ; Thu, 24 Jul 2003 01:53:45 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta06-svc.ntlworld.comESMTP <20030724085344.TDN16215.mta06-svc.ntlworld.com@llama.fishballoon.org>; Thu, 24 Jul 2003 09:53:44 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19fbqO-0005Nl-3j; Thu, 24 Jul 2003 09:53:00 +0100 Date: Thu, 24 Jul 2003 09:53:00 +0100 From: Scott Mitchell To: Brian Behlendorf Message-ID: <20030724085300.GA20583@llama.fishballoon.org> References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> <20030723143055.B33445@fez.hyperreal.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723143055.B33445@fez.hyperreal.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 08:53:47 -0000 On Wed, Jul 23, 2003 at 02:32:06PM -0700, Brian Behlendorf wrote: > On Wed, 23 Jul 2003, Doug White wrote: > > On Wed, 23 Jul 2003, Scott Mitchell wrote: > > > > > We recently moved our CVS repository from a 4.6-STABLE machine to a brand > > > new 4.8 install, on another identical machine. The server runs cvs in > > > 'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD > > > clients. > > > > > > We pretty soon noticed that the cvs server process was occasionally > > > crashing on sig11 (ie. a segfault). > > > > Does the new machine have ECC memory? If not, it could be something as > > simple as bad RAM in the new system. > > For what it's worth, we see it at apache.org too, and haven't seen any > other evidence of hardware-related problems. > > Brian That's interesting... any idea if it's crashing in the same place as mine? I haven't looked into the code in any great detail, but it seems to be all going wrong in some cleanup/shutdown code -- I guess this explains why the clients don't notice anything, nor is there any impact on the contents of the repository, as far as we can see, anyway. I'll probably run a few buildworlds and swap out the RAM on this machine anyway, just to eliminate that as a potential cause. Scott From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 02:04:43 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2E0937B401; Thu, 24 Jul 2003 02:04:42 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id B272043FDD; Thu, 24 Jul 2003 02:04:41 -0700 (PDT) (envelope-from se@freebsd.org) Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19fc1f-0005pl-00; Thu, 24 Jul 2003 11:04:39 +0200 Received: from [80.132.230.151] (helo=Gatekeeper.FreeBSD.org) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 19fc1e-0001LA-00; Thu, 24 Jul 2003 11:04:38 +0200 Received: from StefanEsser.FreeBSD.org (StefanEsser [10.0.0.1]) by Gatekeeper.FreeBSD.org (Postfix) with ESMTP id 315D15F1A; Thu, 24 Jul 2003 11:04:36 +0200 (CEST) Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id 164F1232E; Thu, 24 Jul 2003 11:04:36 +0200 (CEST) Date: Thu, 24 Jul 2003 11:04:36 +0200 From: Stefan =?iso-8859-1?Q?E=DFer?= To: Don Lewis Message-ID: <20030724090436.GA1095@StefanEsser.FreeBSD.org> References: <20030723224436.GD22166@Odin.AC.HMC.Edu> <200307240152.h6O1qCM7053256@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307240152.h6O1qCM7053256@gw.catspoiler.org> User-Agent: Mutt/1.5.4i cc: brooks@one-eyed-alien.net cc: mkb@mukappabeta.de cc: freebsd-stable@FreeBSD.org cc: barney@databus.com cc: gabor@vmunix.com Subject: RFC: reserved VM space (was: Re: malloc does not return null when out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 09:04:43 -0000 On 2003-07-23 18:52 -0700, Don Lewis wrote: > On 23 Jul, Brooks Davis wrote: > > On Thu, Jul 24, 2003 at 12:36:54AM +0200, Matthias Buelow wrote: > >> Barney Wolff writes: > >> > >> >One might argue that this is a config error, and ulimit should be used > >> >to cut the address space to below actually available memory. > >> > >> Wasn't there a sysctl flag to enable/disable overcommitting? > >> I think I remember something but I can't find it; it might > >> not have been on FreeBSD. > > > > No there isn't. Overcommit is a fundamental design feature of the BSD > > VM. If you don't like it, find an OS that doesn't do it. The only one > > I can think of off the top of my head in Irix where I've found it to be > > a serious pain in the ass. > > I think it's a pain in the ass when swap runs out and the kernel decides > to kill off my X11 server to fix the problem. In addition to losing > everything I'm working on, it also hoses the console. The only reason > that I can avoid having to hit the reset switch and risking further > system damage is that I have another machine that I can ssh in from to > do a clean shutdown. Hmmm, might it be possible to have an upper limit on the amount of available memory (RAM+SWAP) used, before malloc() fails for non-root processes ? (A little bit like the "reserved" space in FFS, though I know that you can't directly compare the two.) Think about having a sysctl variable that is set to the amount of RAM (in KB, MB or %VM) that should be free for further calls to malloc() to succeed. Programs that need more heap space after this limit is crossed, will receive NULL as a result and can take appropriate measures. The limit is VM *used* (not *allocated*) against total VM, so this does not imply that memory overcommit should be abandoned. Programs that touch malloced space immediately, will see some percent less available VM, but that is cheap today (even a 64MB Soekris box might be able to cut off some 1 or 2MB, I guess). This does not protect against malicous code that on purpose allocates lots of heap space, but only touches it, when overcommit of this one program extends avalaible VM. But there are other places where it is hard to protect against malicious users and you can already enforce resource limits for users. The proposed implementation would just take a single sysctl (initially set to 0, so no difference to now) and brk/sbrk would check allocation request for non-root processes against available VM space. Forking of non-root processes might be restricted as well, if the VM use limit is exceeded ... Any comments ? Regards, STefan From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 02:04:45 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E25837B401 for ; Thu, 24 Jul 2003 02:04:45 -0700 (PDT) Received: from ren.fdy2.net (fdy2.demon.co.uk [80.177.11.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10CF343F93 for ; Thu, 24 Jul 2003 02:04:44 -0700 (PDT) (envelope-from rjs@ren.fdy2.net) Received: from ren.fdy2.net (localhost [127.0.0.1]) by ren.fdy2.net (8.12.9/8.11.3) with ESMTP id h6O93TD0070986; Thu, 24 Jul 2003 10:03:29 +0100 (BST) (envelope-from rjs@ren.fdy2.net) Received: (from rjs@localhost) by ren.fdy2.net (8.12.9/8.12.9/Submit) id h6O93Sxg070983; Thu, 24 Jul 2003 10:03:28 +0100 (BST) Date: Thu, 24 Jul 2003 10:03:28 +0100 (BST) Message-Id: <200307240903.h6O93Sxg070983@ren.fdy2.net> From: Robert Swindells To: gilham@csl.sri.com In-reply-to: <200307240220.h6O2K8dW032615@quarter.csl.sri.com> (message from Fred Gilham on Wed, 23 Jul 2003 19:20:08 -0700) cc: freebsd-stable@freebsd.org Subject: Re: Question about malloc, mmap etc. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 09:04:45 -0000 [CMUCL changes snipped] >The segments my program creates are at 0x10000000, 0x28f00000 and >0x48000000 if that makes a difference. >Anyway my question is whether anyone knows why this might be happening >or if someone can point me in the right direction to find out. What does the memory map of the lisp process look like at this point ? Things will break if you put in any extra printf calls before the segments are set up. You might want to recompile malloc.c with some extra debug around the call to mmap(2), but using write(2) not printf, just to check where in the setup sequence it is being called. Robert Swindells From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 02:59:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CA7737B401 for ; Thu, 24 Jul 2003 02:59:50 -0700 (PDT) Received: from smtp-2.paradise.net.nz (smtp-2a.paradise.net.nz [202.0.32.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1031B43F93 for ; Thu, 24 Jul 2003 02:59:49 -0700 (PDT) (envelope-from andy@fud.org.nz) Received: from [192.168.10.254] (203-79-110-29.cable.paradise.net.nz [203.79.110.29]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id 957239E6C1 for ; Thu, 24 Jul 2003 21:59:47 +1200 (NZST) From: Andrew Thompson To: freebsd-stable@freebsd.org Content-Type: text/plain Message-Id: <1059041034.89782.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 24 Jul 2003 22:03:55 +1200 Content-Transfer-Encoding: 7bit Subject: Route caching X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 09:59:50 -0000 Hi, I have a 4.8 RELEASE server that I use to graph our wan links with cacti/rrdtool. Occasionally one of the wan links may go down so the main router removes the route to that site (ospf). That means that when cacti goes to poll a device on that subnet it is redirected to the main routers default route (internet gateway on same network). When the wan link in question comes back up my server continues to send the traffic to the internet gateway instead of the main router, how do I get it to forget the route? I have left it for weeks and weeks and I always have to go and manually remove the route to the remote device. The servers default-route is to the main router (not the internet gateway). Any suggestions? Andy From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 03:01:41 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A111F37B404 for ; Thu, 24 Jul 2003 03:01:40 -0700 (PDT) Received: from host185.dolanmedia.com (host185.dolanmedia.com [209.98.197.185]) by mx1.FreeBSD.org (Postfix) with SMTP id 9F20D43FBD for ; Thu, 24 Jul 2003 03:01:35 -0700 (PDT) (envelope-from greg.panula@dolaninformation.com) Received: (qmail 24881 invoked by uid 0); 24 Jul 2003 10:01:34 -0000 Received: from greg.panula@dolaninformation.com by proxy by uid 82 with qmail-scanner-1.16 ( Clear:. Processed in 1.788466 secs); 24 Jul 2003 10:01:34 -0000 X-Qmail-Scanner-Mail-From: greg.panula@dolaninformation.com via proxy X-Qmail-Scanner-Rcpt-To: uitm@blackflag.ru,freebsd-stable@freebsd.org X-Qmail-Scanner: 1.16 (Clear:. Processed in 1.788466 secs) Received: from unknown (HELO mail.dolanmedia.com) (10.1.1.23) by host185.dolanmedia.com with SMTP; 24 Jul 2003 10:01:32 -0000 Received: from dolaninformation.com (10.1.1.135) by mail.dolanmedia.com (Worldmail 1.3.167); 24 Jul 2003 05:01:32 -0500 Sender: pang@FreeBSD.ORG Message-ID: <3F1FAE7B.511F986@dolaninformation.com> Date: Thu, 24 Jul 2003 05:01:31 -0500 From: Greg Panula Organization: Dolan Information Center Inc X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrey Alekseyev References: <200307231707.VAA00542@slt.oz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: problem w/ php3+php4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: greg.panula@dolaninformation.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 10:01:41 -0000 Andrey Alekseyev wrote: > > Hello, > > Has anybody experienced any problems with php3+php4 combo > in systems newer than 4.6-STABLE (as of June-Aug 2002)? > > Briefly, the problem looks very similar to what is > stated in the following reports: > > http://groups.google.com/groups?q=%22php3+kills+apache%22&hl=ru&lr=&ie=UTF-8&oe=UTF-8&selm=wqz8yrfzbug.wl%40hurt.theclones.net&rnum=1 > http://groups.google.com/groups?q=%2Bfreebsd+%2B4.8+%2Bphp3&hl=ru&lr=&ie=UTF-8&oe=UTF-8&selm=b41uk8%241qnklv%241%40fu-berlin.de&rnum=3 > > I'm stumped :) Any information would be much appreciated. > I've got a box running 4.7-STABLE (Oct 15th 2002) with both PHP4 & PHP3 installed and working without problems. Don't remember much about the setup... think the only hassle was getting the right the parser to handle the php3 & php4 pages. Here is the relavent part from my httpd.conf (load module statements) # php3 is needed for the helpdesk apps LoadModule php3_module libexec/apache/libphp3.so # ldap is for provide authenication against Active Directory LoadModule auth_ldap_module libexec/apache/auth_ldap.so LoadModule ssl_module libexec/apache/libssl.so LoadModule php4_module libexec/apache/libphp4.so (apache runs with ssl enabled, but in case it gets restarted without ssl enabled at least the helpdesk will still work.) AddModule mod_php3.c AddModule auth_ldap.c AddModule mod_ssl.c AddModule mod_php4.c AddModule mod_dav.c AddModule mod_auth_external.c (DirectoryIndex stuff) # DirectoryIndex: Name of the file or files to use as a pre-written HTML # directory index. Separate multiple entries with spaces. # DirectoryIndex index.php index.php3 index.html AddType application/x-httpd-php3 .php3 AddType application/x-httpd-php .php .php4 AddType application/x-httpd-php-source .phps DirectoryIndex index.php3 index.html DirectoryIndex index.php index.html DirectoryIndex index.html ~~~~ ## PHP info ## pkg_info | grep -i php adodb-2.50 A database library for PHP4 mod_php3-3.0.18_3 PHP3 module for Apache mod_php4-4.2.3 PHP4 module for Apache good luck, greg From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 03:39:57 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A0E737B401; Thu, 24 Jul 2003 03:39:57 -0700 (PDT) Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DF0343F93; Thu, 24 Jul 2003 03:39:56 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta03-svc.ntlworld.comESMTP <20030724103954.ZIND2652.mta03-svc.ntlworld.com@llama.fishballoon.org>; Thu, 24 Jul 2003 11:39:54 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19fdV8-0005Wh-Gp; Thu, 24 Jul 2003 11:39:10 +0100 Date: Thu, 24 Jul 2003 11:39:10 +0100 From: Scott Mitchell To: Josef Karthauser , freebsd-stable@freebsd.org Message-ID: <20030724103910.GB20583@llama.fishballoon.org> References: <20030616210235.GB691@tuatara.fishballoon.org> <20030717184648.GB851@genius.tao.org.uk> <20030718103123.GB5243@llama.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030718103123.GB5243@llama.fishballoon.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell Subject: Re: Weird USB lockup with Linksys USB100TX NIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 10:39:58 -0000 On Fri, Jul 18, 2003 at 11:31:23AM +0100, Scott Mitchell wrote: > On Thu, Jul 17, 2003 at 07:46:48PM +0100, Josef Karthauser wrote: > > On Mon, Jun 16, 2003 at 10:02:35PM +0100, Scott Mitchell wrote: > This card is supposed to sit between my cable modem and new firewall/router > box. Fortunately the modem (Terayon TJ210) appears to only have a 10BaseT > port so I should be OK there. OK, played around with this a bit more. The card seems perfectly happy to make a 10Mbit link with the cable modem, so it's fine for what I'm planning to use it for. There's definitely an issue with 100Mbit and/or autosensing connections though. I'll add this to my list of things to look at when I have some time (ha!), in the meantime any objection to my filing a PR on this, so it doesn't get forgotten about? Scott From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 04:21:05 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 421EC37B401 for ; Thu, 24 Jul 2003 04:21:05 -0700 (PDT) Received: from c210-49-151-50.thorn1.nsw.optusnet.com.au (c210-49-151-50.thorn1.nsw.optusnet.com.au [210.49.151.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F147343FBD for ; Thu, 24 Jul 2003 04:21:03 -0700 (PDT) (envelope-from tonymaher@optushome.com.au) Received: from dt.home (localhost [127.0.0.1]) ESMTP id h6OBL2x2037134; Thu, 24 Jul 2003 21:21:02 +1000 (EST) (envelope-from tonym@dt.home) Received: (from tonym@localhost) by dt.home (8.12.9/8.12.9/Submit) id h6OBKvDr037095; Thu, 24 Jul 2003 21:20:57 +1000 (EST) (envelope-from tonym) Date: Thu, 24 Jul 2003 21:20:57 +1000 (EST) From: Tony Maher Message-Id: <200307241120.h6OBKvDr037095@dt.home> To: benh@jpj.net, freebsd-stable@freebsd.org In-Reply-To: Subject: Re: Qlogic Fibrechannel and detecting new LUNs on the fly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 11:21:05 -0000 On Thu Jul 24 20:33:58 2003 Ben Hockenhull wrote: > I've installed a Qlogic HBA in a 4.8-STABLE machine and I'm able to present > LUNs to this machine from an HDS array and use them. That all works > perfectly. However, the only time I pick up new LUNs is on a reboot. > > Seems like I should be able to rescan the fabric and pick up new LUNs, but > there doesn't seem to be a way to do this. I tried camcontrol rescan, but > that didn't work. > > Any ideas? Weird. I have had opposite problem (as discussed on scsi mailing list in last couple of days). Booting would not see the SAN disk but an explicit 'camcontrol rescan 1:0:4' would show the disk. My problem has to do with how cam code scans. If there is no device at lun 0 it does not probe the other luns. This should not be your problem since booting does pick them up. (and this is under 5.1, I'll reinstall 4.8 tomorrow not that I expect behaviour to change) What is the exact camcontrol command you use? -- tonym From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 05:26:37 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A45337B401 for ; Thu, 24 Jul 2003 05:26:37 -0700 (PDT) Received: from genius.tao.org.uk (genius.tao.org.uk [212.135.162.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5918A43F3F for ; Thu, 24 Jul 2003 05:26:36 -0700 (PDT) (envelope-from joe@genius.tao.org.uk) Received: by genius.tao.org.uk (Postfix, from userid 100) id 8C43A423E; Thu, 24 Jul 2003 13:26:06 +0100 (BST) Date: Thu, 24 Jul 2003 13:26:04 +0100 From: Josef Karthauser To: Scott Mitchell Message-ID: <20030724122604.GA52069@genius.tao.org.uk> Mail-Followup-To: Josef Karthauser , Scott Mitchell , freebsd-stable@freebsd.org References: <20030616210235.GB691@tuatara.fishballoon.org> <20030717184648.GB851@genius.tao.org.uk> <20030718103123.GB5243@llama.fishballoon.org> <20030724103910.GB20583@llama.fishballoon.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline In-Reply-To: <20030724103910.GB20583@llama.fishballoon.org> User-Agent: Mutt/1.5.4i cc: freebsd-stable@freebsd.org Subject: Re: Weird USB lockup with Linksys USB100TX NIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 12:26:37 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 24, 2003 at 11:39:10AM +0100, Scott Mitchell wrote: > On Fri, Jul 18, 2003 at 11:31:23AM +0100, Scott Mitchell wrote: > > On Thu, Jul 17, 2003 at 07:46:48PM +0100, Josef Karthauser wrote: > > > On Mon, Jun 16, 2003 at 10:02:35PM +0100, Scott Mitchell wrote: > > This card is supposed to sit between my cable modem and new firewall/ro= uter > > box. Fortunately the modem (Terayon TJ210) appears to only have a 10Ba= seT > > port so I should be OK there. >=20 > OK, played around with this a bit more. The card seems perfectly happy to > make a 10Mbit link with the cable modem, so it's fine for what I'm planni= ng > to use it for. There's definitely an issue with 100Mbit and/or autosensi= ng > connections though. I'll add this to my list of things to look at when I > have some time (ha!), in the meantime any objection to my filing a PR on > this, so it doesn't get forgotten about? >=20 Go for it. I have a suspicion that it's a problem with memory allocation somewhere that slows the machine to a grind. The recent bus_dma changes in -current triggered a similar feeling problem, even with 10base connections. I've not looked too closely at the code yet. Joe --=20 Josef Karthauser (joe@tao.org.uk) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D An eclectic mix of fact an= d theory. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iEYEARECAAYFAj8f0FsACgkQXVIcjOaxUBZY+ACgntsdqkWxXukuAVQ3UvqPKcw7 fugAoIDoXL+bIcTz76L3RitrUx2hf4kO =LWta -----END PGP SIGNATURE----- --DocE+STaALJfprDB-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 06:26:36 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 149A537B401; Thu, 24 Jul 2003 06:26:36 -0700 (PDT) Received: from moo.sysabend.org (moo.sysabend.org [66.111.41.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AE3943FAF; Thu, 24 Jul 2003 06:26:35 -0700 (PDT) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id 98C4910DC; Thu, 24 Jul 2003 06:26:34 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 968F510D0; Thu, 24 Jul 2003 06:26:34 -0700 (PDT) Date: Thu, 24 Jul 2003 06:26:34 -0700 (PDT) From: Jamie Bowden To: Don Lewis In-Reply-To: <200307240152.h6O1qCM7053256@gw.catspoiler.org> Message-ID: <20030724062152.G50019-100000@moo.sysabend.org> X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: brooks@one-eyed-alien.net cc: mkb@mukappabeta.de cc: freebsd-stable@FreeBSD.org cc: barney@databus.com cc: gabor@vmunix.com Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 13:26:36 -0000 On Wed, 23 Jul 2003, Don Lewis wrote: > On 23 Jul, Brooks Davis wrote: > > On Thu, Jul 24, 2003 at 12:36:54AM +0200, Matthias Buelow wrote: > >> Wasn't there a sysctl flag to enable/disable overcommitting? > >> I think I remember something but I can't find it; it might > >> not have been on FreeBSD. > > No there isn't. Overcommit is a fundamental design feature of the BSD > > VM. If you don't like it, find an OS that doesn't do it. The only one > > I can think of off the top of my head in Irix where I've found it to be > > a serious pain in the ass. > > I think it's a pain in the ass when swap runs out and the kernel decides > to kill off my X11 server to fix the problem. In addition to losing > everything I'm working on, it also hoses the console. The only reason > that I can avoid having to hit the reset switch and risking further > system damage is that I have another machine that I can ssh in from to > do a clean shutdown. Irix allows for use of what it calls 'vswap' as well, which is just a file that lives on a normal filesystem that the system can fall back on when actual RAM and swap are exhausted. It allows for extremely large commits on memory limited systems while guaranteeing that it has somewhere to page out to if necessary. The poster above may not like Irix, but I do. There's a lot of good stuff in there, but SGI aren't the best at telling people it exists and how to use it. > I used SunOS 4.x, which did not overcommit, for many years. Its typical > failure mode when swap was exhausted is that large processes would get a > error when they attempted to fork() and large memory alloction requests > would fail. Everything else would generally keep working because > smaller memory allocation requests would still succeed. This usually > gave me enough time to take corrective action (generally by cleaning up > junk files in /tmp which was a tmpfs mount). My experience with SunOS 4.x was mostly positive (I chose FreeBSD over Linux/Slakware back in 94 due to FBSD being far closer to what I dealt with daily), but never with respect to running out of system resources. SunOS was happy right up to the point where it started screaming and then usually panic'd. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 06:41:05 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9F6E37B401 for ; Thu, 24 Jul 2003 06:41:05 -0700 (PDT) Received: from vnode.vmunix.com (vnode.vmunix.com [64.7.135.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BD9643FA3 for ; Thu, 24 Jul 2003 06:41:05 -0700 (PDT) (envelope-from gabor@vmunix.com) Received: by vnode.vmunix.com (Postfix, from userid 1004) id 9CD98A1AD8; Thu, 24 Jul 2003 13:41:04 +0000 (GMT) Date: Thu, 24 Jul 2003 09:41:04 -0400 From: Gabor To: Doug White Message-ID: <20030724134104.GA83799@vmunix.com> References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723140329.C92624@carver.gumbysoft.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.7-STABLE cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 13:41:06 -0000 On Wed, Jul 23, 2003 at 02:09:00PM -0700, Doug White wrote: # On Wed, 23 Jul 2003, Gabor wrote: # # > We have a little soekris box running freebsd that uses racoon for key # > management. It's used for setting up an ipsec tunnel. I noticed that # > one of these devices lost the tunnel this morning. I looked in the # > log and saw this # > # > Jul 23 01:37:57 m0n0wall /kernel: pid 80 (racoon), uid 0, was killed: out of swap space # # [...] # # > Here is the tail end of the output. It dies when trying to poke at # > the memory using memset. If I just malloc without the memset, it # > never even dies. # # That's normal. If you malloc() memory and never touch it then it is never # actually allocated. It's not normal. If malloc cannot allocate memory it should return a null pointer. How would my application know there is no more memory? Dying is not a very good behavior. The C standard and even the man page says that malloc will return null when there is no more memory to be had by the process. It shouldn't return a bogus pointer so I can happily attempt to use it and then my program bombs. Obviously sbrk is somehow broken and allows a break to be set when it shouldn't. # Your problem is that you're running out of memory. Try killing off # unneeded daemons and set maxusers to a low value (like 32). Also try # reducing the size of your mfs partitions, if you're using rc.diskless2. I # don't think raccoon is much of a memory pig, unless you have a huge number # of connections. # # > The kernel for this has the NO_SWAPPING option enabled since there is # > essentially no disk, it boots from a CF. # # Do you have the 32MB or 64MB version? I have a net4501 (64MB) and I still # have 39MB free. Its just running natd, sshd, named and dhcpd. I believe it's 64M and we're using mpd and racoon on it to set up an ipsec tunnel. There is usually about 21M of free memory on it. We have 14 live boxes in the field and only one has experienced this problem but the problem is reproducable on all of them using the little C program. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 06:54:47 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57A0537B401 for ; Thu, 24 Jul 2003 06:54:47 -0700 (PDT) Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.200.93.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CBD643F75 for ; Thu, 24 Jul 2003 06:54:46 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 4.12) id 19fgYM-0007SV-00 for freebsd-stable@freebsd.org; Thu, 24 Jul 2003 14:54:42 +0100 To: freebsd-stable@freebsd.org In-Reply-To: <20030724134104.GA83799@vmunix.com> Message-Id: From: Pete French Date: Thu, 24 Jul 2003 14:54:42 +0100 Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 13:54:47 -0000 > It's not normal. If malloc cannot allocate memory it should return a > null pointer. How would my application know there is no more memory? But the point is that is *can* allocate the memory. Allocating it is not the same as being able to use it. The behaviour you want is for the system to not only allocate the memory, but to also ensure that the total amount allocated by the system can never exceed the amount the system has available. > page says that malloc will return null when there is no more memory to > be had by the process. It shouldn't return a bogus pointer so I can Its not bogus - the trouble is that you cant tell at the time malloc returns whether the pointer will be useable or not. You only find that out when you try and use it, and whether theres any space or not depends oon what else may have munched up (or released) memory between you making the call to malloc() and actually writing to the location returned. -pcf. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 08:15:47 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B14DF37B401 for ; Thu, 24 Jul 2003 08:15:47 -0700 (PDT) Received: from pop018.verizon.net (pop018pub.verizon.net [206.46.170.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4F5543FDD for ; Thu, 24 Jul 2003 08:15:46 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by pop018.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030724151546.PGIU11703.pop018.verizon.net@mac.com> for ; Thu, 24 Jul 2003 10:15:46 -0500 Message-ID: <3F1FF81F.5050701@mac.com> Date: Thu, 24 Jul 2003 11:15:43 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> <20030724070936.GA16762@rot13.obsecurity.org> In-Reply-To: <20030724070936.GA16762@rot13.obsecurity.org> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [141.149.47.46] at Thu, 24 Jul 2003 10:15:45 -0500 Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 15:15:48 -0000 Kris Kennaway wrote: > On Wed, Jul 23, 2003 at 11:44:11PM -0400, Mike Tancsa wrote: [ ... ] >>> Ah, the annual "memory overcommit" thread. I thought we were overdue >>> for one. >> >> But why does the man page for malloc (3) say, >> >> If malloc() fails, a NULL pointer is returned. > > Words fail me. Don't worry about it; you've still got sarcasm to fall back on. :-) I don't think the following is a particularly good idea, as the existing prezero ('Z') or junk ('J') options will also serve to reference memory and prevent the "memory overcommit issue", but: 22-sec# diff -du malloc.c_old malloc.c --- malloc.c_old Thu Jul 24 10:36:43 2003 +++ malloc.c Thu Jul 24 10:49:41 2003 @@ -229,6 +229,9 @@ /* junk fill ? */ static int malloc_junk; +/* write a single byte per page to disable overcommit behavior */ +static int malloc_overcommit; + #ifdef HAS_UTRACE /* utrace ? */ @@ -418,6 +421,8 @@ case 'R': malloc_realloc = 1; break; case 'j': malloc_junk = 0; break; case 'J': malloc_junk = 1; break; + case 'o': malloc_overcommit = 0; break + case 'O': malloc_overcommit = 1; break #ifdef HAS_UTRACE case 'u': malloc_utrace = 0; break; case 'U': malloc_utrace = 1; break; @@ -705,6 +710,7 @@ imalloc(size_t size) { void *result; + int stride; if (suicide) abort(); @@ -716,8 +722,13 @@ else result = malloc_pages(size); - if (malloc_zero && result) - memset(result, 0, size); + if (result) { + if (malloc_zero) + memset(result, 0, size); + else if (malloc_overcommit) + for (stride = 0; stride <= size; stride += malloc_pagesize) + ((char *)result)[stride] = SOME_JUNK; + } return result; } -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 09:00:09 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B9FF37B401 for ; Thu, 24 Jul 2003 09:00:09 -0700 (PDT) Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.200.93.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94D2543F93 for ; Thu, 24 Jul 2003 09:00:08 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 4.12) id 19fiVj-000E9u-00 for stable@FreeBSD.ORG; Thu, 24 Jul 2003 17:00:07 +0100 To: stable@FreeBSD.ORG Message-Id: From: Pete French Date: Thu, 24 Jul 2003 17:00:07 +0100 Subject: 'which' and installing Linux software on -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 16:00:09 -0000 Has anyone else had frustrating problems with the use of 'which' in Linux mode ? I have some SUN software which I am trying to install. I am running Linux bash to run the install script - running 'uname' returns 'Linux' But the SUn code does 'which uname' to get the path to 'uname' before running it. the ;which' command is a bash builtin, and this returns the '/usr/bin/uname' command rather than '/bin/uname'. Thus it runs /usr/bin;uname, egts the answer 'FreeBSD' and refuses to install. Any ideas ? I did a search on this but didnt come up with any answers. -pcf. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 09:29:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50E0337B401 for ; Thu, 24 Jul 2003 09:29:50 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D53C43F85 for ; Thu, 24 Jul 2003 09:29:49 -0700 (PDT) (envelope-from RoKlein@roklein.de) Received: from [212.227.126.155] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19fiyS-0002LN-00; Thu, 24 Jul 2003 18:29:48 +0200 Received: from [217.234.134.133] (helo=z105-e.intern.studentenwohnheim-rhein-main.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 19fiyR-000230-00; Thu, 24 Jul 2003 18:29:48 +0200 From: Robert Klein Organization: roklein.de To: Pete French Date: Thu, 24 Jul 2003 18:30:04 +0200 User-Agent: KMail/1.5.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307241830.04993.RoKlein@roklein.de> cc: stable@FreeBSD.ORG Subject: Re: 'which' and installing Linux software on -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: RoKlein@roklein.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 16:29:50 -0000 On Donnerstag, 24. Juli 2003 18:00, Pete French wrote: > Has anyone else had frustrating problems with the use of > 'which' in Linux mode ? I have some SUN software which I am > trying to install. I am running Linux bash to run the install > script - running 'uname' returns 'Linux' > > But the SUn code does 'which uname' to get the path to 'uname' > before running it. the ;which' command is a bash builtin, and > this returns the '/usr/bin/uname' command rather than > '/bin/uname'. Thus it runs /usr/bin;uname, egts the answer > 'FreeBSD' and refuses to install. > > Any ideas ? I did a search on this but didnt come up with any > answers. Put /compat/linux/bin at the beginning of your PATH environment variable for the installation. Regards, Robert From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 09:43:38 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8454737B401 for ; Thu, 24 Jul 2003 09:43:38 -0700 (PDT) Received: from smtp2.adl2.internode.on.net (smtp2.adl2.internode.on.net [203.16.214.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5ABD43FD7 for ; Thu, 24 Jul 2003 09:43:36 -0700 (PDT) (envelope-from malcolm.kay@internode.on.net) Received: from smtp2.adl2.internode.on.net (localhost [127.0.0.1]) h6OGhYO4093498 for ; Fri, 25 Jul 2003 02:13:35 +0930 (CST) Received: (from mailnull@localhost)h6OGhYgL093494 for ; Fri, 25 Jul 2003 02:13:34 +0930 (CST) X-Authentication-Warning: smtp2.adl2.internode.on.net: mailnull set sender to using -f Received: from beta.home (ppp1874.sa.padsl.internode.on.net [150.101.26.81]) h6OGhWO4093489; Fri, 25 Jul 2003 02:13:34 +0930 Content-Type: text/plain; charset="iso-8859-1" From: Malcolm Kay Organization: At home To: freebsd-stable@freebsd.org, Gabor , Doug White Date: Fri, 25 Jul 2003 02:13:31 +0930 User-Agent: KMail/1.4.3 References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030724134104.GA83799@vmunix.com> In-Reply-To: <20030724134104.GA83799@vmunix.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307250213.31956.malcolm.kay@internode.on.net> X-Proc-As: freebsd-stable X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 16:43:38 -0000 On Thu, 24 Jul 2003 23:11, Gabor wrote: > On Wed, Jul 23, 2003 at 02:09:00PM -0700, Doug White wrote: > # On Wed, 23 Jul 2003, Gabor wrote: > # > # > We have a little soekris box running freebsd that uses racoon for k= ey > # > management. It's used for setting up an ipsec tunnel. I noticed t= hat > # > one of these devices lost the tunnel this morning. I looked in the > # > log and saw this > # > > # > Jul 23 01:37:57 m0n0wall /kernel: pid 80 (racoon), uid 0, was kille= d: > out of swap space # > # [...] > # > # > Here is the tail end of the output. It dies when trying to poke at > # > the memory using memset. If I just malloc without the memset, it > # > never even dies. > # > # That's normal. If you malloc() memory and never touch it then it is n= ever > # actually allocated. > > It's not normal. If malloc cannot allocate memory it should return a > null pointer. How would my application know there is no more memory? > Dying is not a very good behavior. The C standard and even the man > page says that malloc will return null when there is no more memory to > be had by the process. While this might be a desirable state of affairs I can't find any stateme= nt=20 in the (draft) standard or the man page that malloc returns null when the= re is=20 no more memory (whatever that might mean) . The (draft) standard says it=20 either returns a pointer to allocated memory or null, without any reason=20 given for the different behaviours. The man page merely says null if the=20 call fails without reference to why. Malcolm Kay From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 09:43:39 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0779237B401 for ; Thu, 24 Jul 2003 09:43:39 -0700 (PDT) Received: from smtp2.adl2.internode.on.net (smtp2.adl2.internode.on.net [203.16.214.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A797343FDF for ; Thu, 24 Jul 2003 09:43:37 -0700 (PDT) (envelope-from malcolm.kay@internode.on.net) Received: from smtp2.adl2.internode.on.net (localhost [127.0.0.1]) h6OGhYO4093509 for ; Fri, 25 Jul 2003 02:13:35 +0930 (CST) Received: (from mailnull@localhost)h6OGhYGN093505 for ; Fri, 25 Jul 2003 02:13:34 +0930 (CST) X-Authentication-Warning: smtp2.adl2.internode.on.net: mailnull set sender to using -f Received: from beta.home (ppp1874.sa.padsl.internode.on.net [150.101.26.81]) h6OGhWO4093489; Fri, 25 Jul 2003 02:13:34 +0930 Content-Type: text/plain; charset="iso-8859-1" From: Malcolm Kay Organization: At home To: freebsd-stable@freebsd.org, Gabor , Doug White Date: Fri, 25 Jul 2003 02:13:31 +0930 User-Agent: KMail/1.4.3 References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030724134104.GA83799@vmunix.com> In-Reply-To: <20030724134104.GA83799@vmunix.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307250213.31956.malcolm.kay@internode.on.net> X-Proc-As: freebsd-stable X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 16:43:39 -0000 On Thu, 24 Jul 2003 23:11, Gabor wrote: > On Wed, Jul 23, 2003 at 02:09:00PM -0700, Doug White wrote: > # On Wed, 23 Jul 2003, Gabor wrote: > # > # > We have a little soekris box running freebsd that uses racoon for k= ey > # > management. It's used for setting up an ipsec tunnel. I noticed t= hat > # > one of these devices lost the tunnel this morning. I looked in the > # > log and saw this > # > > # > Jul 23 01:37:57 m0n0wall /kernel: pid 80 (racoon), uid 0, was kille= d: > out of swap space # > # [...] > # > # > Here is the tail end of the output. It dies when trying to poke at > # > the memory using memset. If I just malloc without the memset, it > # > never even dies. > # > # That's normal. If you malloc() memory and never touch it then it is n= ever > # actually allocated. > > It's not normal. If malloc cannot allocate memory it should return a > null pointer. How would my application know there is no more memory? > Dying is not a very good behavior. The C standard and even the man > page says that malloc will return null when there is no more memory to > be had by the process. While this might be a desirable state of affairs I can't find any stateme= nt=20 in the (draft) standard or the man page that malloc returns null when the= re is=20 no more memory (whatever that might mean) . The (draft) standard says it=20 either returns a pointer to allocated memory or null, without any reason=20 given for the different behaviours. The man page merely says null if the=20 call fails without reference to why. Malcolm Kay From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 09:45:24 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7010237B401 for ; Thu, 24 Jul 2003 09:45:24 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8976943FCB for ; Thu, 24 Jul 2003 09:45:23 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6OGjMn8040277; Thu, 24 Jul 2003 12:45:22 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6OGjMmG040276; Thu, 24 Jul 2003 12:45:22 -0400 (EDT) (envelope-from barney) Date: Thu, 24 Jul 2003 12:45:22 -0400 From: Barney Wolff To: Chuck Swiger Message-ID: <20030724164522.GA39964@pit.databus.com> References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> <20030724070936.GA16762@rot13.obsecurity.org> <3F1FF81F.5050701@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F1FF81F.5050701@mac.com> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 16:45:24 -0000 On Thu, Jul 24, 2003 at 11:15:43AM -0400, Chuck Swiger wrote: > > +/* write a single byte per page to disable overcommit behavior */ > +static int malloc_overcommit; Won't this merely die in malloc, not return 0? I don't think that's the behavior the original poster was looking for. The wanted behavior would be fairly expensive to achieve, especially on an smp machine. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 10:00:48 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40D5E37B401 for ; Thu, 24 Jul 2003 10:00:48 -0700 (PDT) Received: from smtp2.adl2.internode.on.net (smtp2.adl2.internode.on.net [203.16.214.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF0943F3F for ; Thu, 24 Jul 2003 10:00:47 -0700 (PDT) (envelope-from malcolm.kay@internode.on.net) Received: from smtp2.adl2.internode.on.net (localhost [127.0.0.1]) h6OH0iO4096283 for ; Fri, 25 Jul 2003 02:30:45 +0930 (CST) Received: (from mailnull@localhost)h6OH0ifV096279 for ; Fri, 25 Jul 2003 02:30:44 +0930 (CST) X-Authentication-Warning: smtp2.adl2.internode.on.net: mailnull set sender to using -f Received: from beta.home (ppp1874.sa.padsl.internode.on.net [150.101.26.81]) h6OH0gO4096272; Fri, 25 Jul 2003 02:30:44 +0930 Content-Type: text/plain; charset="iso-8859-1" From: Malcolm Kay Organization: At home To: Pete French , stable@freebsd.org Date: Fri, 25 Jul 2003 02:30:42 +0930 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307250230.42360.malcolm.kay@internode.on.net> X-Proc-As: stable X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) Subject: Re: 'which' and installing Linux software on -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 17:00:48 -0000 On Fri, 25 Jul 2003 01:30, Pete French wrote: > Has anyone else had frustrating problems with the use of 'which' in > Linux mode ? I have some SUN software which I am trying to install. > I am running Linux bash to run the install script - running 'uname' > returns 'Linux' > > But the SUn code does 'which uname' to get the path to 'uname' before > running it. the ;which' command is a bash builtin, and this returns > the '/usr/bin/uname' command rather than '/bin/uname'. Thus it > runs /usr/bin;uname, egts the answer 'FreeBSD' and refuses to install. > > Any ideas ? I did a search on this but didnt come up with any answers. I don't know where bash gets its answer from if uname is builtin, but if = you=20 have linux compatibility installed you should have a Linux version of the= =20 uname utility in /usr/compat/linux/bin/ which returns Linux. Maybe you can trick the installation by temporarily switching the uname=20 utilities or perhaps even by adding /usr/compat/linux/bin/ at the front o= f=20 your PATH. Then again perhaps it won't work! Or if its not called with any options why not temporarily set up a uname=20 script which simpley echos Linux. Malcolm From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 10:19:14 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9657037B40E for ; Thu, 24 Jul 2003 10:19:14 -0700 (PDT) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD95743F93 for ; Thu, 24 Jul 2003 10:19:13 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9/8.12.8) with ESMTP id h6OHJ8Ra015569; Thu, 24 Jul 2003 13:19:08 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030724114115.0849c450@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Thu, 24 Jul 2003 13:20:26 -0400 To: Andrew Reilly From: Mike Tancsa In-Reply-To: <3F1F817E.7040504@bigpond.net.au> References: <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: By Sentex Communications (lava/20020517) cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 17:19:15 -0000 At 04:49 PM 24/07/2003 +1000, Andrew Reilly wrote: >Mike Tancsa wrote: > >>At 08:15 PM 7/23/2003 -0700, Kris Kennaway wrote: >> >>>On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote: >>> >>> > Here is the tail end of the output. It dies when trying to poke at >>> > the memory using memset. If I just malloc without the memset, it >>> > never even dies. >>> >>>Ah, the annual "memory overcommit" thread. I thought we were overdue >>>for one. >> >> >> >>But why does the man page for malloc (3) say, >> >> If malloc() fails, a NULL pointer is returned. > > >Because that's what happens. See the subthread with the ulimit examples. > >In the cases being cited, the malloc itself is not failing, because it is >able to return a pointer to a chunk of *VM*. The problem occurrs later, >when the program attempts to read or write to that memory, and it doesn't >occur because malloc was wrong, but because no other process has exited or >unmapped something in the mean-time, to free up a page to back that >address space. Thanks for the clarification. I guess it would be helpful if there was an * or caveat perhaps in the man page after "If malloc() fails, a NULL pointer is returned." I see what you mean that it "never fails" in the strict sense, but there is a potential for a failure in the process of memory allocation and usage which I think is helpful for the programmer / user to understand. What if something like this were added to /usr/share/man/man3/malloc.3. Note: malloc will return a pointer to memory even when there is not enough actual physical memory and swap to handle the request. It will only fail once you actually try to access that allocation and if by that time the system has not freed up memory from elsewhere to honor that request. The idea behind this strategy being that at any given time programs will ask for more memory than there is actually available, and more memory than they actually need. By having the VM tell the program, "yes, you can have this memory allocation", the chances are by the time the program actually uses the memory, it will be available as some other program has freed up their memory allocation. For further information, see ***** ---Mike From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 10:27:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11B3337B401 for ; Thu, 24 Jul 2003 10:27:50 -0700 (PDT) Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [192.160.51.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16E3143F3F for ; Thu, 24 Jul 2003 10:27:49 -0700 (PDT) (envelope-from jandrese@mitre.org) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.12.9/8.12.8) with ESMTP id h6OHRlEx015836 for ; Thu, 24 Jul 2003 13:27:47 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.12.9/8.12.8) with ESMTP id h6OHRho1016367 for ; Thu, 24 Jul 2003 13:27:45 -0400 (EDT) Received: from mm112324-2k.mitre.org (128.29.3.33) by mailhub2.mitre.org with SMTP id 3292114; Thu, 24 Jul 2003 13:27:39 -0400 Message-ID: <3F20170A.8080408@mitre.org> Date: Thu, 24 Jul 2003 13:27:38 -0400 From: Jason Andresen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> <20030724070936.GA16762@rot13.obsecurity.org> <3F1FF81F.5050701@mac.com> <20030724164522.GA39964@pit.databus.com> In-Reply-To: <20030724164522.GA39964@pit.databus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 17:27:50 -0000 Barney Wolff wrote: > On Thu, Jul 24, 2003 at 11:15:43AM -0400, Chuck Swiger wrote: > >>+/* write a single byte per page to disable overcommit behavior */ >>+static int malloc_overcommit; > > > Won't this merely die in malloc, not return 0? > I don't think that's the behavior the original poster was looking for. > The wanted behavior would be fairly expensive to achieve, especially > on an smp machine. The upshot seem to be that it is impossible to write a program that handles out-of-memory errors gracefully with this scheme. Even if you check all of your return values and configure exit paths for failed mallocs, your program is still going to crash and die in a random location without warning when memory fills up. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 10:34:39 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3A6F37B401 for ; Thu, 24 Jul 2003 10:34:39 -0700 (PDT) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 335E043F93 for ; Thu, 24 Jul 2003 10:34:39 -0700 (PDT) (envelope-from darrylo@soco.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 6A67716AB0 for ; Thu, 24 Jul 2003 11:34:36 -0600 (MDT) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 7709FC8 for ; Thu, 24 Jul 2003 11:34:38 -0600 (MDT) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id KAA04726 for ; Thu, 24 Jul 2003 10:34:38 -0700 (PDT) Message-Id: <200307241734.KAA04726@mina.soco.agilent.com> To: freebsd-stable@freebsd.org In-Reply-To: Your message of "Thu, 24 Jul 2003 16:49:34 +1000." <3F1F817E.7040504@bigpond.net.au> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Thu, 24 Jul 2003 10:34:37 -0700 From: Darryl Okahata Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 17:34:40 -0000 Andrew Reilly wrote: > Mike Tancsa wrote: > > >> Ah, the annual "memory overcommit" thread. I thought we were overdue > >> for one. > > > > But why does the man page for malloc (3) say, > > > > If malloc() fails, a NULL pointer is returned. > > Because that's what happens. See the subthread with the ulimit examples. You know, we could probably eliminate many of these periodic "why doesn't malloc() return NULL?" threads by simply enhancing the malloc(3) man page and adding a FAQ entry. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 10:55:25 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FAB737B401 for ; Thu, 24 Jul 2003 10:55:25 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AE5443F3F for ; Thu, 24 Jul 2003 10:55:24 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6OHtOn8041442; Thu, 24 Jul 2003 13:55:24 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6OHtOk1041441; Thu, 24 Jul 2003 13:55:24 -0400 (EDT) (envelope-from barney) Date: Thu, 24 Jul 2003 13:55:24 -0400 From: Barney Wolff To: Jason Andresen Message-ID: <20030724175524.GA41037@pit.databus.com> References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> <20030724070936.GA16762@rot13.obsecurity.org> <3F1FF81F.5050701@mac.com> <20030724164522.GA39964@pit.databus.com> <3F20170A.8080408@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F20170A.8080408@mitre.org> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 17:55:25 -0000 On Thu, Jul 24, 2003 at 01:27:38PM -0400, Jason Andresen wrote: > > The upshot seem to be that it is impossible to write a program that > handles out-of-memory errors gracefully with this scheme. Even if you > check all of your return values and configure exit paths for failed > mallocs, your program is still going to crash and die in a random > location without warning when memory fills up. On a production server, when you know what will be running, you can use ulimit to constrain each process's memory use, and malloc will happily return 0 if you hit a constraint. On a client machine, if you start getting these errors, the proper reaction is to configure more swap, or fix the program that has runaway memory use. Does anybody know if c++ exception handling on new would make recovery from out-of-swap practical? I have a feeling it ought to do the trick. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 11:01:07 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD6B537B401 for ; Thu, 24 Jul 2003 11:01:07 -0700 (PDT) Received: from vnode.vmunix.com (vnode.vmunix.com [64.7.135.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D6CA43F93 for ; Thu, 24 Jul 2003 11:01:07 -0700 (PDT) (envelope-from gabor@vmunix.com) Received: by vnode.vmunix.com (Postfix, from userid 1004) id D6BD7A1A7B; Thu, 24 Jul 2003 18:01:06 +0000 (GMT) Date: Thu, 24 Jul 2003 14:01:06 -0400 From: Gabor To: Darryl Okahata Message-ID: <20030724180106.GA86680@vmunix.com> References: <20030723221336.GA26555@pit.databus.com> <200307232222.PAA26360@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307232222.PAA26360@mina.soco.agilent.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.7-STABLE cc: Barney Wolff cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 18:01:08 -0000 On Wed, Jul 23, 2003 at 03:22:30PM -0700, Darryl Okahata wrote: # Barney Wolff wrote: # # > Shouldn't malloc return 0 when out of memory rather than returning # > an address that won't work? I believe that was the complaint. Presumably # > having NO_SWAPPING has something to do with it, but filling the swap # > might well do the same thing. # # Well, it goes against the man page, but FreeBSD typically never # returns NULL [*] when you run out of VM. It's been this way for YEARS. # # [*] -- Yes, it's annoying as h*ll, but that's the way it works. I # thought that there was a FAQ or handbook entry on this, but I # couldn't find any. Here is another test. This box has swap and I get a null pointer even though ulimit -a says memory unlimited. 5230 0x27ef1000 5231 0x27f0a000 5232 0x27f23000 5233 0x27f3c000 5234 0x27f55000 5235 0x27f6e000 5236 0x27f87000 5237 0x27fa0000 5238 0x27fb9000 5239 0x27fd2000 5240 0x27feb000 5241 0x28004000 5242 0x2801d000 5243 0x0 No more mem =0= 6g # ulimit -a time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 524288 stack(kbytes) 65536 lockedmem(kbytes) unlimited memory(kbytes) unlimited nofiles(descriptors) 11095 processes 5547 vmemory(kbytes) unlimited #include int main(int argc, char **argv) { char *p; int cnt = 0; while (1) { p = malloc(100000); printf("%d %p\n", ++cnt, p); if (!p) { puts("No more mem"); break; } } return 0; } =0= 6g # sysctl vm.swap_enabled vm.swap_enabled: 1 =0= 6g # sysctl hw.physmem hw.physmem: 1061859328 =0= 6g # sysctl hw.usermem hw.usermem: 906907648 =0= 6g # pstat -sk Device 1K-blocks Used Avail Capacity Type /dev/twed0s1b 1048448 0 1048448 0% Interleaved From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 11:13:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BAD0437B401 for ; Thu, 24 Jul 2003 11:13:27 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFD1943F75 for ; Thu, 24 Jul 2003 11:13:26 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6OIDQn8041790 for ; Thu, 24 Jul 2003 14:13:26 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6OIDQID041789 for freebsd-stable@freebsd.org; Thu, 24 Jul 2003 14:13:26 -0400 (EDT) (envelope-from barney) Date: Thu, 24 Jul 2003 14:13:26 -0400 From: Barney Wolff To: freebsd-stable@freebsd.org Message-ID: <20030724181326.GA41709@pit.databus.com> References: <20030723221336.GA26555@pit.databus.com> <200307232222.PAA26360@mina.soco.agilent.com> <20030724180106.GA86680@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030724180106.GA86680@vmunix.com> User-Agent: Mutt/1.4.1i Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 18:13:28 -0000 On Thu, Jul 24, 2003 at 02:01:06PM -0400, Gabor wrote: > ... > Here is another test. This box has swap and I get a null pointer even > though ulimit -a says memory unlimited. > ... > 5242 0x2801d000 > 5243 0x0 > No more mem > # ulimit -a > data(kbytes) 524288 <<<<<<<<<<<<<<<<<<<<<<< -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 11:17:11 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E71F137B401 for ; Thu, 24 Jul 2003 11:17:11 -0700 (PDT) Received: from smtp5.wanadoo.nl (smtp5.wanadoo.nl [194.134.35.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CF8743F75 for ; Thu, 24 Jul 2003 11:17:11 -0700 (PDT) (envelope-from steve@sohara.org) Received: from ams-gw.sohara.org (rot2-p1513.dial.wanadoo.nl [62.234.203.233]) by smtp5.wanadoo.nl (Postfix) with SMTP id 4EE8B7650B; Thu, 24 Jul 2003 20:17:06 +0200 (CEST) Date: Thu, 24 Jul 2003 20:17:02 +0200 From: Steve O'Hara-Smith To: Barney Wolff Message-Id: <20030724201702.6667b707.steve@sohara.org> In-Reply-To: <20030724164522.GA39964@pit.databus.com> References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> <20030724070936.GA16762@rot13.obsecurity.org> <3F1FF81F.5050701@mac.com> <20030724164522.GA39964@pit.databus.com> X-Mailer: Sylpheed version 0.9.3 (GTK+ 1.2.10; i386-portbld-freebsd4.8) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX,Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 18:17:12 -0000 On Thu, 24 Jul 2003 12:45:22 -0400 Barney Wolff wrote: BW> On Thu, Jul 24, 2003 at 11:15:43AM -0400, Chuck Swiger wrote: BW> > BW> > +/* write a single byte per page to disable overcommit behavior */ BW> > +static int malloc_overcommit; BW> BW> Won't this merely die in malloc, not return 0? Yes - it needs to trap the SEGV as well to produce the wanted behaviour, something like: + else if (malloc_overcommit) { + ocsighandleron(); + for (stride = 0; stride <= size; stride += malloc_pagesize) { + ((char *)result)[stride] = SOME_JUNK; + if (ocsignalled) { + ocsighandleroff(); + return NULL; + } + } + ocsighandleroff(); + } Where ocsighandleron() installs a SEGV handler that sets ocsignalled when called and ocsighandleroff() installs the original one. BTW malloc_overcommit seems to be upside down, I left it that way. -- C:>WIN | Directable Mirrors The computer obeys and wins. |A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 12:09:29 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0871C37B405 for ; Thu, 24 Jul 2003 12:09:28 -0700 (PDT) Received: from vnode.vmunix.com (vnode.vmunix.com [64.7.135.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17FAC43FBF for ; Thu, 24 Jul 2003 12:09:28 -0700 (PDT) (envelope-from gabor@vmunix.com) Received: by vnode.vmunix.com (Postfix, from userid 1004) id 8E96DA1AD5; Thu, 24 Jul 2003 19:09:27 +0000 (GMT) Date: Thu, 24 Jul 2003 15:09:27 -0400 From: Gabor To: freebsd-stable@freebsd.org Message-ID: <20030724190927.GA87428@vmunix.com> References: <20030723221336.GA26555@pit.databus.com> <200307232222.PAA26360@mina.soco.agilent.com> <20030724180106.GA86680@vmunix.com> <20030724181326.GA41709@pit.databus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030724181326.GA41709@pit.databus.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.7-STABLE Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 19:09:29 -0000 On Thu, Jul 24, 2003 at 02:13:26PM -0400, Barney Wolff wrote: # On Thu, Jul 24, 2003 at 02:01:06PM -0400, Gabor wrote: # > ... # > Here is another test. This box has swap and I get a null pointer even # > though ulimit -a says memory unlimited. # > ... # > 5242 0x2801d000 # > 5243 0x0 # > No more mem # > # ulimit -a # > data(kbytes) 524288 <<<<<<<<<<<<<<<<<<<<<<< Ah, I am a cone head! I fired up four of my test procs and put in an infinite while after they ran out of memory. After starting the fourth and it chugging away eating up swap, one of the other three got killed off. So at least I know it has nothing to do with the NO_SWAPPING option. It's still disconcerting to me. I would much prefer to get back a null pointer that just have the kernel randomly pick a victim who's a high memory user. It's like a starving guy being given food and then being shot in the head when he reaches for it. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 12:43:02 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFDF237B401 for ; Thu, 24 Jul 2003 12:43:02 -0700 (PDT) Received: from wrzx35.rz.uni-wuerzburg.de (wrzx35.rz.uni-wuerzburg.de [132.187.3.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B39243F85 for ; Thu, 24 Jul 2003 12:43:01 -0700 (PDT) (envelope-from mkb@mukappabeta.de) Received: from wrzx34.rz.uni-wuerzburg.de (wrzx34.rz.uni-wuerzburg.de [132.187.3.34]) by wrzx35.rz.uni-wuerzburg.de (Postfix) with ESMTP id DFE1E7320 for ; Thu, 24 Jul 2003 21:42:59 +0200 (CEST) Received: from virusscan (localhost [127.0.0.1]) by wrzx34.rz.uni-wuerzburg.de (Postfix) with ESMTP id CF6E177C05 for ; Thu, 24 Jul 2003 21:42:59 +0200 (CEST) Received: from wrzx28.rz.uni-wuerzburg.de ([132.187.3.28]) ESMTP id 02066-01 for ; Thu, 24 Jul 2003 21:42:59 +0200 (CEST) Received: from haegar.informatik.uni-wuerzburg.de (wi4x41.informatik.uni-wuerzburg.de [132.187.101.41]) by wrzx28.rz.uni-wuerzburg.de (Postfix) with ESMTP id A77C31504 for ; Thu, 24 Jul 2003 21:42:59 +0200 (CEST) Received: from reiher.informatik.uni-wuerzburg.de (wi4d22.informatik.uni-wuerzburg.de [132.187.101.122])96D892544F for ; Thu, 24 Jul 2003 21:42:59 +0200 (CEST) Received: from mukappabeta.de (localhost.informatik.uni-wuerzburg.de [127.0.0.1])725C25C46 for ; Thu, 24 Jul 2003 21:44:44 +0200 (CEST) Message-ID: <3F20372C.5040606@mukappabeta.de> Date: Thu, 24 Jul 2003 21:44:44 +0200 From: Matthias Buelow User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030716 X-Accept-Language: de, de-de, en-gb, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <200307241734.KAA04726@mina.soco.agilent.com> In-Reply-To: <200307241734.KAA04726@mina.soco.agilent.com> X-Enigmail-Version: 0.76.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new (Rechenzentrum Universitaet Wuerzburg) Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 19:43:03 -0000 Darryl Okahata wrote: > You know, we could probably eliminate many of these periodic "why > doesn't malloc() return NULL?" threads by simply enhancing the malloc(3) > man page and adding a FAQ entry. Or better yet, fix the VM and disable the dreadful overcommit, or at least provide a knob for the user for disabling it. -- Matthias Buelow; mkb@{mukappabeta.de,informatik.uni-wuerzburg.de} From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 13:19:35 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9026E37B401 for ; Thu, 24 Jul 2003 13:19:35 -0700 (PDT) Received: from web14806.mail.yahoo.com (web14806.mail.yahoo.com [216.136.224.222]) by mx1.FreeBSD.org (Postfix) with SMTP id 41FCB43F93 for ; Thu, 24 Jul 2003 13:19:35 -0700 (PDT) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20030724201934.59075.qmail@web14806.mail.yahoo.com> Received: from [192.114.47.54] by web14806.mail.yahoo.com via HTTP; Thu, 24 Jul 2003 13:19:34 PDT Date: Thu, 24 Jul 2003 13:19:34 -0700 (PDT) From: Rostislav Krasny To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 20:19:35 -0000 The Single UNIX Specification extends malloc() function, a little. Following URL is of the manual page of this function: http://www.opengroup.org/onlinepubs/007904975/functions/malloc.html Read "ERRORS" and "Issue 6" sections. Should FreeBSD be conformed to this standard? __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 13:40:57 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 059D137B401 for ; Thu, 24 Jul 2003 13:40:57 -0700 (PDT) Received: from laptop.tenebras.com (laptop.tenebras.com [66.92.188.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 633EC43FA3 for ; Thu, 24 Jul 2003 13:40:56 -0700 (PDT) (envelope-from kudzu@tenebras.com) Received: (qmail 28504 invoked from network); 24 Jul 2003 20:40:55 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241) by 0 with SMTP; 24 Jul 2003 20:40:55 -0000 Message-ID: <3F204456.1000000@tenebras.com> Date: Thu, 24 Jul 2003 13:40:54 -0700 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, zh-tw, zh-cn, fr, en, de-de MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20030724201934.59075.qmail@web14806.mail.yahoo.com> In-Reply-To: <20030724201934.59075.qmail@web14806.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 20:40:57 -0000 Rostislav Krasny wrote: > The Single UNIX Specification extends malloc() function, a little. > Following URL is of the manual page of this function: > http://www.opengroup.org/onlinepubs/007904975/functions/malloc.html > Read "ERRORS" and "Issue 6" sections. Should FreeBSD be conformed to > this standard? FreeBSD malloc is POSIX/SUSv3 compliant. It returns NULL and sets errno to ENOMEM if insufficient storage space is available. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 13:43:40 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14C8437B401 for ; Thu, 24 Jul 2003 13:43:40 -0700 (PDT) Received: from mailgate.sri.com (mailgate.SRI.COM [128.18.243.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B0E943FB1 for ; Thu, 24 Jul 2003 13:43:39 -0700 (PDT) (envelope-from gilham@csl.sri.com) Received: (qmail 11208 invoked from network); 24 Jul 2003 20:43:38 -0000 Received: from localhost (HELO mailgate.SRI.COM) (127.0.0.1) by mailgate.sri.com with SMTP; 24 Jul 2003 20:43:38 -0000 Received: from quarter.csl.sri.com ([130.107.1.30]) by mailgate.SRI.COM (SAVSMTP 3.1.0.29) with SMTP id M2003072413433831666 for ; Thu, 24 Jul 2003 13:43:38 -0700 Received: from snapdragon.csl.sri.com (snapdragon.csl.sri.com [130.107.19.20]) by quarter.csl.sri.com (8.12.9/8.12.9) with ESMTP id h6OKhcdW006094 for ; Thu, 24 Jul 2003 13:43:38 -0700 Message-Id: <200307242043.h6OKhcdW006094@quarter.csl.sri.com> To: freebsd-stable@freebsd.org In-Reply-To: Message from Gabor of "Thu, 24 Jul 2003 15:09:27 EDT." <20030724190927.GA87428@vmunix.com> Date: Thu, 24 Jul 2003 13:43:38 -0700 From: Fred Gilham Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 20:43:40 -0000 Gabor, Did you try the following? ln -s 'J' /etc/malloc.conf This will make malloc touch the bytes as it allocates them, and should cause it to realize it can't get the memory sooner. It will cause a slowdown for every program on the system that uses malloc, but perhaps it could at least solve the problem you are having. -- Fred Gilham gilham@csl.sri.com The spam folder --- you will never find a more wretched hive of scum and villainy. We must be cautious. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 13:59:51 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C27937B404 for ; Thu, 24 Jul 2003 13:59:51 -0700 (PDT) Received: from smtp.web.de (smtp02.web.de [217.72.192.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97C6743FA3 for ; Thu, 24 Jul 2003 13:59:50 -0700 (PDT) (envelope-from f.dei@web.de) Received: from pd958d5e3.dip.t-dialin.net ([217.88.213.227] helo=web.de) by smtp.web.de with asmtp (TLSv1:RC4-MD5:128) (WEB.DE 4.99 #420) id 19fnBl-0005kh-00 for freebsd-stable@freebsd.org; Thu, 24 Jul 2003 22:59:49 +0200 Message-ID: <3F2048C8.3080306@web.de> Date: Thu, 24 Jul 2003 22:59:52 +0200 From: Felix Deichmann User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.4) Gecko/20030721 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: f.dei@web.de Subject: Promise Ultra100 TX2 support broken? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 20:59:51 -0000 Hi. I have a Promise Ultra100 TX2 card with 2 brand new Maxtor drives. The setup should work in UDMA100 mode, but is downgraded to PIO mode 4 under FreeBSD 4.8. Hardware is definitely OK, I have 2 controllers, 6 different 80 wire IDE cables, shielded and unshielded and no irq conflicts. Always the same problem. Disks work perfectly on an onboard VIA controller under NetBSD. The Promise BIOS is the latest. NetBSD also downgrades to PIO mode 4 in an Alpha AXPpci33. Maybe some registers not setup correctly by the driver(s)? dmesg excerpt: [...] atapci0: port 0xe080-0xe08f,0xe0a0-0xe0a3,0xe090-0xe097,0xe0a4-0xe0a7,0xe098-0xe09f mem 0x84000000-0x84003fff irq 10 at device 14.0 on pci 0 [...] ad4: 39205MB [79656/16/63] at ata2-master UDMA100 [...] ad4: UDMA ICRC error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) retrying ad4: UDMA ICRC error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) retrying ad4: UDMA ICRC error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) retrying ad4: UDMA ICRC error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) falling back to PIO mode Help would be greatly appreciated! Regards Felix From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 08:59:32 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01A8237B401 for ; Thu, 24 Jul 2003 08:59:32 -0700 (PDT) Received: from smithers.nildram.co.uk (smithers.nildram.co.uk [195.112.4.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 163B143F85 for ; Thu, 24 Jul 2003 08:59:31 -0700 (PDT) (envelope-from muttley@nildram.co.uk) Received: from UebiMiau (jupiter2.nildram.co.uk [195.112.4.138]) by smithers.nildram.co.uk (Postfix) with SMTP id 7305F231C11; Thu, 24 Jul 2003 16:59:26 +0100 (BST) Received: from client 194.62.232.65 for UebiMiau2.7 (webmail client); Thu, 24 Jul 2003 16:59:30 +0100 Date: Thu, 24 Jul 2003 16:59:30 +0100 From: "Muttley" To: "Chuck Swiger" , "freebsd-stable@freebsd.org"@smithers.nildram.co.uk X-Priority: 3 X-Mailer: UebiMiau 2.7 X-Original-IP: 194.62.232.65 Content-Transfer-Encoding: 8bit X-MSMail-Priority: Medium Importance: Medium Message-Id: <20030724155926.7305F231C11@smithers.nildram.co.uk> X-Mailman-Approved-At: Thu, 24 Jul 2003 14:16:40 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Muttley List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 15:59:32 -0000 Yes, I thought briefly about something like this. Then I thought 'there's a race condition'. Then I realised that other processes might not link against this malloc. Then I realised the race condition doesn't even matter; processes will still be killed, as the kernel doesn't care that you're still in malloc() when the overcommitted memory is touched, it just knows you've touched it and there's no actual memory there. This will result in far more processes being killed. I believe that's a bad thing. Any patch for this is going to have to be in kernelland not userland. Cheers, Matt From: "Chuck Swiger" Date: 24/07/03 15:16 I don't think the following is a particularly good idea, as the existing prezero ('Z') or junk ('J') options will also serve to reference memory and prevent the "memory overcommit issue", but: From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 14:37:24 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E26FF37B401 for ; Thu, 24 Jul 2003 14:37:23 -0700 (PDT) Received: from alcanet.com.au (mail2.alcanet.com.au [203.62.196.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D99643F75 for ; Thu, 24 Jul 2003 14:37:22 -0700 (PDT) (envelope-from peter.jeremy@alcatel.com.au) Received: from sydsmtp01.alcatel.com.au (IDENT:root@localhost.localdomain [127.0.0.1])h6OLbAx3002267; Fri, 25 Jul 2003 07:37:11 +1000 Received: from gsmx07.alcatel.com.au ([139.188.20.247]) by sydsmtp01.alcatel.com.au (Lotus Domino Release 5.0.12) with ESMTP id 2003072507370996:75451 ; Fri, 25 Jul 2003 07:37:09 +1000 Received: from gsmx07.alcatel.com.au (localhost [127.0.0.1]) by gsmx07.alcatel.com.au (8.12.9/8.12.9) with ESMTP id h6OLb97d085825; Fri, 25 Jul 2003 07:37:09 +1000 (EST) (envelope-from peter.jeremy@alcatel.com.au) Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.12.9/8.12.9/Submit) id h6OLb730085824; Fri, 25 Jul 2003 07:37:07 +1000 (EST) (envelope-from peter.jeremy@alcatel.com.au) Date: Fri, 25 Jul 2003 07:37:07 +1000 From: Peter Jeremy To: "Steve O'Hara-Smith" Message-ID: <20030724213707.GU430@gsmx07.alcatel.com.au> Mail-Followup-To: Steve O'Hara-Smith , Barney Wolff , freebsd-stable@freebsd.org References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> <20030724070936.GA16762@rot13.obsecurity.org> <3F1FF81F.5050701@mac.com> <20030724164522.GA39964@pit.databus.com> <20030724201702.6667b707.steve@sohara.org> Mime-Version: 1.0 In-Reply-To: <20030724201702.6667b707.steve@sohara.org> User-Agent: Mutt/1.4.1i X-MIMETrack: Itemize by SMTP Server on SYDSMTP01/AlcatelAustralia(Release 5.0.12 |February 13, 2003) at 25/07/2003 07:37:10 AM,|February 13, 2003) at 25/07/2003 07:37:11 AM, Serialize complete at 25/07/2003 07:37:11 AM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline cc: Barney Wolff cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 21:37:24 -0000 On 2003-Jul-24 20:17:02 +0200, Steve O'Hara-Smith wrote: >On Thu, 24 Jul 2003 12:45:22 -0400 >Barney Wolff wrote: > >BW> On Thu, Jul 24, 2003 at 11:15:43AM -0400, Chuck Swiger wrote: >BW> > >BW> > +/* write a single byte per page to disable overcommit behavior */ >BW> > +static int malloc_overcommit; >BW> >BW> Won't this merely die in malloc, not return 0? > > Yes - it needs to trap the SEGV as well to produce the wanted >behaviour, something like: ... > Where ocsighandleron() installs a SEGV handler that sets ocsignalled >when called and ocsighandleroff() installs the original one. This still can't handle all cases. Handling the SEGV may require additional memory - particularly stack - which isn't available. You also need to free() the memory before returning NULL. This may allow a future smaller malloc to succeed. I'd suggest adding code in the "malloc_overcommit" path to touch stack that is likely to be used, close to the top of {m,c,re}alloc(). There's a gcc-specific extension "__builtin_frame_address()" that will let you do this. This ensures that the stack pages you need are present before you try to sbrk() the data. There may still be other corner cases I've missed. Cleanly recovering in all cases when there is no additional memory available is a very hard problem. Most of the suggested fixes generally rely on the kernel providing a warning when the VM system is under stress but can still satisfy some requests. Unfortunately, I don't think any of them included the necessary patches. I think the idea of adding entries to both the FAQ and malloc(3) explaining what happens is good. The text that was posted is probably "good-enough" for a start - all that's needed is a decent URL to provide a more detailed explanation to replace the '****'. Peter From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 14:38:19 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62C9737B401 for ; Thu, 24 Jul 2003 14:38:19 -0700 (PDT) Received: from web14807.mail.yahoo.com (web14807.mail.yahoo.com [216.136.224.223]) by mx1.FreeBSD.org (Postfix) with SMTP id 04D4A43F3F for ; Thu, 24 Jul 2003 14:38:19 -0700 (PDT) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20030724213818.46089.qmail@web14807.mail.yahoo.com> Received: from [192.114.47.54] by web14807.mail.yahoo.com via HTTP; Thu, 24 Jul 2003 14:38:18 PDT Date: Thu, 24 Jul 2003 14:38:18 -0700 (PDT) From: Rostislav Krasny To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 21:38:19 -0000 > > The Single UNIX Specification extends malloc() function, a little. > > Following URL is of the manual page of this function: > > http://www.opengroup.org/onlinepubs/007904975/functions/malloc.html > > Read "ERRORS" and "Issue 6" sections. Should FreeBSD be conformed to > > this standard? > > FreeBSD malloc is POSIX/SUSv3 compliant. It returns NULL and sets > errno to ENOMEM if insufficient storage space is available. Then why Gabor reported that it doesn't return NULL when insufficient storage space is available? Am I misunderstand something? __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 14:50:25 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 265F337B401 for ; Thu, 24 Jul 2003 14:50:25 -0700 (PDT) Received: from alcanet.com.au (mail2.alcanet.com.au [203.62.196.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id A235943F3F for ; Thu, 24 Jul 2003 14:50:23 -0700 (PDT) (envelope-from peter.jeremy@alcatel.com.au) Received: from sydsmtp01.alcatel.com.au (IDENT:root@localhost.localdomain [127.0.0.1])h6OLoLx3002988; Fri, 25 Jul 2003 07:50:22 +1000 Received: from gsmx07.alcatel.com.au ([139.188.20.247]) by sydsmtp01.alcatel.com.au (Lotus Domino Release 5.0.12) with ESMTP id 2003072507502085:75535 ; Fri, 25 Jul 2003 07:50:20 +1000 Received: from gsmx07.alcatel.com.au (localhost [127.0.0.1]) by gsmx07.alcatel.com.au (8.12.9/8.12.9) with ESMTP id h6OLoK7d085859; Fri, 25 Jul 2003 07:50:20 +1000 (EST) (envelope-from peter.jeremy@alcatel.com.au) Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.12.9/8.12.9/Submit) id h6OLoKUU085858; Fri, 25 Jul 2003 07:50:20 +1000 (EST) (envelope-from peter.jeremy@alcatel.com.au) Date: Fri, 25 Jul 2003 07:50:20 +1000 From: Peter Jeremy To: Matthias Buelow Message-ID: <20030724215020.GV430@gsmx07.alcatel.com.au> Mail-Followup-To: Matthias Buelow , freebsd-stable@freebsd.org References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> <20030723224436.GD22166@Odin.AC.HMC.Edu> <20030724021726.GJ430@gsmx07.alcatel.com.au> <3F1F45E2.5080506@mukappabeta.de> Mime-Version: 1.0 In-Reply-To: <3F1F45E2.5080506@mukappabeta.de> User-Agent: Mutt/1.4.1i X-MIMETrack: Itemize by SMTP Server on SYDSMTP01/AlcatelAustralia(Release 5.0.12 |February 13, 2003) at 25/07/2003 07:50:21 AM,|February 13, 2003) at 25/07/2003 07:50:22 AM, Serialize complete at 25/07/2003 07:50:22 AM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 21:50:25 -0000 On 2003-Jul-24 04:35:14 +0200, Matthias Buelow wrote: >What makes me ask the following (note that it's neither a flame, nor a >suggestion). Does FreeBSD actually account the used swap/vm so far (it >needn't since it doesn't guarantee that it'll be available, with >overcommit) or does it not do that (i.e., it has no idea of how much vm >was requested by all processes so far, without having to go through the >maps of all processes, of course)? Have a look at how systat(1) or top(1) calculate the number they report. AFAIK, the kernel doesn't accumulate this information into a single total or make use of it in VM allocation decisions. > And is it planned in the (distant) >future to add a knob to toggle overcommitting of swap? All I can say is I'm unaware of any such plan. Based on the previous threads, the VM experts appear to be either against this or don't see any benefit. > While with large >disks and hence swap sizes this probably isn't a pressing problem for >most applications, it might be nice to be able to control the system not > to randomly kill off applications or force the user to meticulously >plan and calculate memory load of the planned application zoo in order >to tune the ulimits of various memory-hungry processes in a way that >they'll all fit into swap in the worst case situation. This comes up every time this thread starts. As I said before - read the archives. If you think you have a solution that works and avoids at least the larger pitfalls (see the archives), you need to provide patches (or show a willingness to pay someone else to write the code). Peter From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 15:11:31 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 563A337B401 for ; Thu, 24 Jul 2003 15:11:31 -0700 (PDT) Received: from updegrove.net (12-246-251-12.client.attbi.com [12.246.251.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 8337D43F93 for ; Thu, 24 Jul 2003 15:11:28 -0700 (PDT) (envelope-from freebsdstable@updegrove.net) Received: (qmail 70607 invoked from network); 24 Jul 2003 22:12:49 -0000 Received: from adsl-64-166-46-11.dsl.scrm01.pacbell.net (HELO updegrove.net) (64.166.46.11) by updegrove.net with SMTP; 24 Jul 2003 22:12:49 -0000 Message-ID: <3F2059F0.4070302@updegrove.net> Date: Thu, 24 Jul 2003 15:13:04 -0700 From: Rick Updegrove User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG References: <3F1C8A82.6030804@updegrove.net> <3F1D7108.2010300@updegrove.net> <040501c3522f$f60f8a60$0201640a@cns> In-Reply-To: <040501c3522f$f60f8a60$0201640a@cns> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: LH3 SMP hangs for no apparent reason X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 22:11:31 -0000 Eric Parusel wrote: >Hello, > >I just noticed this thread. Months ago I tried one of our LH3's with >SMP, and had the same behaviour.. > >Did the change you made in the BIOS fix all the problems you were having? YES! So far so good. : ) It has not locked up once yet since making that one and only change to eh BIOS. I plan to post all the details to http://prioris.mini.pw.edu.pl/~gregory/FreeBSD by the end of next week (as soon as I can) From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 15:52:07 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03BEA37B401 for ; Thu, 24 Jul 2003 15:52:07 -0700 (PDT) Received: from laptop.tenebras.com (laptop.tenebras.com [66.92.188.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 6253843F93 for ; Thu, 24 Jul 2003 15:52:06 -0700 (PDT) (envelope-from kudzu@tenebras.com) Received: (qmail 29237 invoked from network); 24 Jul 2003 22:52:06 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241) by 0 with SMTP; 24 Jul 2003 22:52:06 -0000 Message-ID: <3F206314.7000602@tenebras.com> Date: Thu, 24 Jul 2003 15:52:04 -0700 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, zh-tw, zh-cn, fr, en, de-de MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20030724213818.46089.qmail@web14807.mail.yahoo.com> In-Reply-To: <20030724213818.46089.qmail@web14807.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 22:52:07 -0000 Rostislav Krasny wrote: >>>The Single UNIX Specification extends malloc() function, a little. >>>Following URL is of the manual page of this function: >>>http://www.opengroup.org/onlinepubs/007904975/functions/malloc.html >>>Read "ERRORS" and "Issue 6" sections. Should FreeBSD be conformed > > to > >>>this standard? >> >>FreeBSD malloc is POSIX/SUSv3 compliant. It returns NULL and sets >>errno to ENOMEM if insufficient storage space is available. > > > Then why Gabor reported that it doesn't return NULL > when insufficient storage space is available? Am I misunderstand something? There was sufficient storage space -- sadly, we had to shoot your mother in order to get it. ;-) Running up against VM limits is inherently ugly. The OP is running in 64MB w/o swap. I have a Soekris box myself. Process limits are your friend. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 16:08:41 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3DF437B401 for ; Thu, 24 Jul 2003 16:08:41 -0700 (PDT) Received: from skyline.tdkt.org (skyline.tdkt.org [209.98.211.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id C41C243F3F for ; Thu, 24 Jul 2003 16:08:40 -0700 (PDT) (envelope-from b.j.casavant@ieee.org) Received: from skyline.tdkt.org (IDENT:bcasavan@skyline.tdkt.org [209.98.211.67])h6ON8cn7008270 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 24 Jul 2003 18:08:39 -0500 (CDT) Date: Thu, 24 Jul 2003 18:08:38 -0500 (CDT) From: Brent Casavant X-X-Sender: bcasavan@skyline.tdkt.org To: freebsd-stable@freebsd.org In-Reply-To: <20030724163012.E295C37B49D@hub.freebsd.org> Message-ID: Organization: "Angeltread Software Organization" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Brent Casavant List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 23:08:42 -0000 [hopefully I didn't mess up the attribution, replying to a digest sucks] On Thu, 24 Jul 2003, Jamie Bowden wrote: > On Wed, 23 Jul 2003, Don Lewis wrote: > > > On 23 Jul, Brooks Davis wrote: > > > > No there isn't. Overcommit is a fundamental design feature of the BSD > > > VM. If you don't like it, find an OS that doesn't do it. The only one > > > I can think of off the top of my head in Irix where I've found it to be > > > a serious pain in the ass. > > Irix allows for use of what it calls 'vswap' as well, which is just a file > that lives on a normal filesystem that the system can fall back on when > actual RAM and swap are exhausted. It allows for extremely large commits > on memory limited systems while guaranteeing that it has somewhere to page > out to if necessary. The poster above may not like Irix, but I do. > There's a lot of good stuff in there, but SGI aren't the best at telling > people it exists and how to use it. Almost. Having actually worked on the IRIX VM system, and on vswap issues in particular... Don is correct in that IRIX doesn't overcommit. But that is only the default swap configuration. The amount of "vswap" you add to the system is the amount by which the VM system is allowed to overcommit total memory (real swap + RAM). If the system is overcommitted and runs into a genuine memory outage, then processes will start to be killed (hopefully intelligently). In particular "vswap" is not a file that lives in the normal filesystem that gets swapped to. The somewhat ugly syntax for adding vswap means that vswap does get configured along with a normal swap area (file or device), but vswap itself has no backing store. Clear as mud? BTW, I've found that more people are confused by memory overcommitting than the abscence thereof. I've found an analogy to overbooking airline flights to be useful in clarifying the situation. That said, I think overcommitting is the right thing to do for typical system usage, but that this behavior should be configurable for the unusual cases. Brent -- Brent Casavant http://www.angeltread.org/ 44.9067N 93.0558N 907F -.- -.. ..... . -- -... From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 16:18:12 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CF0537B401 for ; Thu, 24 Jul 2003 16:18:12 -0700 (PDT) Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id A342843FB1 for ; Thu, 24 Jul 2003 16:18:11 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by out005.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030724231810.ZKNU20032.out005.verizon.net@mac.com> for ; Thu, 24 Jul 2003 18:18:10 -0500 Message-ID: <3F20692E.2060107@mac.com> Date: Thu, 24 Jul 2003 19:18:06 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-stable@freebsd.org References: <20030724155926.7305F231C11@smithers.nildram.co.uk> In-Reply-To: <20030724155926.7305F231C11@smithers.nildram.co.uk> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [141.149.47.46] at Thu, 24 Jul 2003 18:18:10 -0500 Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 23:18:12 -0000 Muttley wrote: > Yes, I thought briefly about something like this. > > Then I thought 'there's a race condition'. Where? The FreeBSD implementation is wrapped in a THREAD_LOCK()...? > Then I realised that other processes might not link against this malloc. Perhaps. > Then I realised the race condition doesn't even matter; processes will > still be killed, as the kernel doesn't care that you're still in > malloc() when the overcommitted memory is touched, it just knows you've > touched it and there's no actual memory there. This will result in far > more processes being killed. I believe that's a bad thing. Someone stated that it was a problem that malloc() returned pointers to virtual address space that had been mapped but not allocated. This patch does not guarantee that malloc() will return, but, if malloc() does returns a pointer, using the memory being pointed to will refer to memory that is allocated. As Barny Wolff said: > Won't this merely die in malloc, not return 0? True. This isn't a perfect solution, but given the choice between: 1) malloc(LOTS) returning a pointer, and then sometime later the program dies with a bus error when using that memory because no more VM is available, or 2) malloc(LOTS) causing an immediate failure in malloc(), ...choice #2 appears to be significantly better. Figuring out what went wrong from a coredump or backtrace for #2 when the signal happens in malloc() should be obvious; determining why the program crashed in the middle of referencing memory in some large buffer is potentially misleading. Programs which take care to preallocate regions of memory they need before they start doing a transaction or some other operation that needs to be atomic would also prefer #2; the patch I proposed could have a beneficial impact on data integrity for such programs. -- People who encounter programs crashing in malloc() are likely going to continue to complain about malloc() not returning NULL when the system is out of memory. If malloc() is referencing memory before returning the pointer, means that the system is going to reserve VM resources with temporal locality towards memory _allocation_ rather than memory _reference_. Having the program crash at memory allocation time rather than usage helps identify when and where this problem actually happens more clearly, if only by a little bit. I'm not sure whether allocating memory sooner that way will make it more likely that brk()/sbrk() or mmap() will return ENOMEM to the libc malloc() implementation, but if it does not help, perhaps that means something and we've identified the location of problem more precisely. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 16:48:01 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36A9C37B401 for ; Thu, 24 Jul 2003 16:48:01 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9770743FAF for ; Thu, 24 Jul 2003 16:48:00 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h6ONlqM7055640; Thu, 24 Jul 2003 16:47:56 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200307242347.h6ONlqM7055640@gw.catspoiler.org> Date: Thu, 24 Jul 2003 16:47:52 -0700 (PDT) From: Don Lewis To: b.j.casavant@ieee.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-stable@FreeBSD.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 23:48:01 -0000 On 24 Jul, Brent Casavant wrote: > [hopefully I didn't mess up the attribution, replying to a digest sucks] > > On Thu, 24 Jul 2003, Jamie Bowden wrote: > >> On Wed, 23 Jul 2003, Don Lewis wrote: >> >> > On 23 Jul, Brooks Davis wrote: >> >> > > No there isn't. Overcommit is a fundamental design feature of the BSD >> > > VM. If you don't like it, find an OS that doesn't do it. The only one >> > > I can think of off the top of my head in Irix where I've found it to be >> > > a serious pain in the ass. >> >> Irix allows for use of what it calls 'vswap' as well, which is just a file >> that lives on a normal filesystem that the system can fall back on when >> actual RAM and swap are exhausted. It allows for extremely large commits >> on memory limited systems while guaranteeing that it has somewhere to page >> out to if necessary. The poster above may not like Irix, but I do. >> There's a lot of good stuff in there, but SGI aren't the best at telling >> people it exists and how to use it. > > Almost. Having actually worked on the IRIX VM system, and on vswap > issues in particular... > > Don is correct in that IRIX doesn't overcommit. But that is only > the default swap configuration. I didn't say this, Jamie did. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 16:51:25 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64B8537B401 for ; Thu, 24 Jul 2003 16:51:25 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99E0143F85 for ; Thu, 24 Jul 2003 16:51:24 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h6ONpGM7055649; Thu, 24 Jul 2003 16:51:21 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200307242351.h6ONpGM7055649@gw.catspoiler.org> Date: Thu, 24 Jul 2003 16:51:16 -0700 (PDT) From: Don Lewis To: cswiger@mac.com In-Reply-To: <3F20692E.2060107@mac.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-stable@FreeBSD.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 23:51:25 -0000 On 24 Jul, Chuck Swiger wrote: > Muttley wrote: >> Yes, I thought briefly about something like this. >> >> Then I thought 'there's a race condition'. > > Where? The FreeBSD implementation is wrapped in a THREAD_LOCK()...? > >> Then I realised that other processes might not link against this malloc. > > Perhaps. > >> Then I realised the race condition doesn't even matter; processes will >> still be killed, as the kernel doesn't care that you're still in >> malloc() when the overcommitted memory is touched, it just knows you've >> touched it and there's no actual memory there. This will result in far >> more processes being killed. I believe that's a bad thing. > > Someone stated that it was a problem that malloc() returned pointers to virtual > address space that had been mapped but not allocated. This patch does not > guarantee that malloc() will return, but, if malloc() does returns a pointer, > using the memory being pointed to will refer to memory that is allocated. > > As Barny Wolff said: > > Won't this merely die in malloc, not return 0? > > True. This isn't a perfect solution, but given the choice between: > > 1) malloc(LOTS) returning a pointer, and then sometime later the program dies > with a bus error when using that memory because no more VM is available, or > > 2) malloc(LOTS) causing an immediate failure in malloc(), > > ...choice #2 appears to be significantly better. > > Figuring out what went wrong from a coredump or backtrace for #2 when the signal > happens in malloc() should be obvious; determining why the program crashed in > the middle of referencing memory in some large buffer is potentially misleading. > > Programs which take care to preallocate regions of memory they need before they > start doing a transaction or some other operation that needs to be atomic would > also prefer #2; the patch I proposed could have a beneficial impact on data > integrity for such programs. I believe that the problem isn't confined to dynamically allocated memory. I think it is also possible to run into problems when accessing a large static array, or even when not accessing memory at all if the kernel wants to free up some swap space and the process in question is sufficently large. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 17:16:42 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23BAB37B401 for ; Thu, 24 Jul 2003 17:16:42 -0700 (PDT) Received: from out004.verizon.net (out004pub.verizon.net [206.46.170.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id D71B543F3F for ; Thu, 24 Jul 2003 17:16:40 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by out004.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030725001640.FCLZ14849.out004.verizon.net@mac.com>; Thu, 24 Jul 2003 19:16:40 -0500 Message-ID: <3F2076E3.5080607@mac.com> Date: Thu, 24 Jul 2003 20:16:35 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, Peter Jeremy References: <20030723173427.GA72876@vmunix.com> <20030723140329.C92624@carver.gumbysoft.com> <20030723221336.GA26555@pit.databus.com> <20030723223654.GA24008@moghedien.mukappabeta.net> <20030723224436.GD22166@Odin.AC.HMC.Edu> <20030724021726.GJ430@gsmx07.alcatel.com.au> <3F1F45E2.5080506@mukappabeta.de> <20030724215020.GV430@gsmx07.alcatel.com.au> In-Reply-To: <20030724215020.GV430@gsmx07.alcatel.com.au> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [141.149.47.46] at Thu, 24 Jul 2003 19:16:39 -0500 Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 00:16:42 -0000 Peter Jeremy wrote: > On 2003-Jul-24 04:35:14 +0200, Matthias Buelow wrote: > Cleanly recovering in all cases when there is no additional memory > available is a very hard problem. Most of the suggested fixes > generally rely on the kernel providing a warning when the VM system > is under stress but can still satisfy some requests. Unfortunately, > I don't think any of them included the necessary patches. [ ... ] I agree with this statement: handling system-wide resource shortages is a tricky, failure-prone, and dangerous environment to try and program for. I'm very familar with the Mach project, Mach memory management, and task/thread semantics; am I okay using that terminology, or am I going to confuse myself (or other people :-)? For instance, I know that FreeBSD's VM system includes some degree of copy-on-write semantics, but I don't believe there is support for user-mode pagers, right? Mach uses message-passing, heavily, and supported both kernel-mode and user-mode paging algorithms; it would let you set VM_NORMAL, VM_SEQUENTIAL, VM_ANOLMALOUS, or your own paging algorithm. There is a difference between "I want another page of VM" and "my process wants another frame of physical memory", but for those tasks using VM backing store which they can flush and make available to the rest of the system, being able to free up physical RAM can help make memory available for error-handling or whatever in the faulting task. In other words, Mach messaging served as a mechanism for the kernel to let tasks (processes) know that the VM system was under stress. -- Mach relies heavily on COW semantics and lazy allocation of resources, and I fully understand the benefits of VM overcommit in general, but Mach let you control allocation of VM very explicitly if you needed to. Mach also did some clever optimizations with regard to zero-filling pages: mapped but unallocated regions of memory read as zero, and the Mach exception handler which trapped writing to mapped but unreferenced memory, or memory shared copy-on-write, and would only allocate more VM if the write actually changed something. Writing zeros to an unallocated page did not cause the page to be allocated. Which is why my patch used SOME_JUNK, of course. :-) [ This is in answer to another message by Jeremy, which said: ] > This comes up every time this thread starts. As I said before - read > the archives. If you think you have a solution that works and avoids > at least the larger pitfalls (see the archives), you need to provide > patches (or show a willingness to pay someone else to write the code). Let me criticise the proposed patch I made: 1) To force pages to be allocated, you only need to write one byte per page: mine writes at least one byte per malloc(). malloc_pages() could use the existing stride algorithm, and malloc_bytes() should do something else appropriate. 2) I use malloc_pagesize rather than, what, getpagesize(), or god only knows what else is appropriate. 3) What to do with regard to error-handling, as discussed above and elsewhere. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 20:53:33 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AB6137B401 for ; Thu, 24 Jul 2003 20:53:33 -0700 (PDT) Received: from hsph.harvard.edu (hsph.harvard.edu [128.103.75.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F4FB43FB1 for ; Thu, 24 Jul 2003 20:53:32 -0700 (PDT) (envelope-from pzhang@hsph.harvard.edu) Received: from localhost (pzhang@localhost) by hsph.harvard.edu (8.11.7+Sun/8.11.7) with ESMTP id h6P3rnr05294 for ; Thu, 24 Jul 2003 23:53:49 -0400 (EDT) Date: Thu, 24 Jul 2003 23:53:49 -0400 (EDT) From: Peng Zhang To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: problem with gdm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 03:53:33 -0000 Hi folks, I just used cvsup to upgrade my system to 4.8 stable. Now I have problem with gdm. When I have logged in as other user, I will log in as root. That happens when I automatically start gdm after booting. But if I start gdm myself after boot, I won't have this problem. I don't know why. Does somebody have the same problem before? Thanks! Peng From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 20:57:38 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C105E37B401 for ; Thu, 24 Jul 2003 20:57:38 -0700 (PDT) Received: from ms-smtp-02.southeast.rr.com (ms-smtp-02.southeast.rr.com [24.93.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF36D43FA3 for ; Thu, 24 Jul 2003 20:57:37 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from creme-brulee.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158])h6P3sRqP023375; Thu, 24 Jul 2003 23:54:28 -0400 (EDT) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) h6P3uuiZ055178; Thu, 24 Jul 2003 23:56:56 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Peng Zhang In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4zu46wxPReC0K6BPn6oY" Organization: MarcusCom, Inc. Message-Id: <1059105455.353.14.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 24 Jul 2003 23:57:36 -0400 X-Spam-Status: No, hits=-11.6 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2, QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_XIMIAN autolearn=ham version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-stable@freebsd.org Subject: Re: problem with gdm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 03:57:39 -0000 --=-4zu46wxPReC0K6BPn6oY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2003-07-24 at 23:53, Peng Zhang wrote: > Hi folks, >=20 > I just used cvsup to upgrade my system to 4.8 stable. Now I have problem > with gdm. When I have logged in as other user, I will log in as root. Tha= t > happens when I automatically start gdm after booting. But if I start gdm > myself after boot, I won't have this problem. I don't know why. Does > somebody have the same problem before? Nope. GDM 2 works fine for me on 4.8-STABLE if it's started out of ${X11BASE}/etc/rc.d. Do you have any console messages or other errors to indicate what's going on? What does your gdm user entry look like? Joe >=20 > Thanks! >=20 > Peng > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-4zu46wxPReC0K6BPn6oY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA/IKqvb2iPiv4Uz4cRApSUAKCcmEc0rKNloub2ixxSzuCBb2DPPQCeLERs 3eMtOlfQbKMs5G+TDCLFlCM= =3lPj -----END PGP SIGNATURE----- --=-4zu46wxPReC0K6BPn6oY-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 21:21:52 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B25A37B401 for ; Thu, 24 Jul 2003 21:21:52 -0700 (PDT) Received: from hsph.harvard.edu (hsph.harvard.edu [128.103.75.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A44D43F85 for ; Thu, 24 Jul 2003 21:21:51 -0700 (PDT) (envelope-from pzhang@hsph.harvard.edu) Received: from [134.174.184.76] (sph184-76.harvard.edu [134.174.184.76]) by hsph.harvard.edu (8.11.7+Sun/8.11.7) with ESMTP id h6P4M1w08524; Fri, 25 Jul 2003 00:22:01 -0400 (EDT) From: "Zhang, Peng" To: Joe Marcus Clarke In-Reply-To: <1059105455.353.14.camel@shumai.marcuscom.com> References: <1059105455.353.14.camel@shumai.marcuscom.com> Content-Type: text/plain Message-Id: <1059106655.345.4.camel@pzhang> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 25 Jul 2003 00:17:36 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: problem with gdm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 04:21:52 -0000 I don't have any error in the console. Just log in as pzhang, then I actually enter as root account. The way I start gdm is to edit /etc/ttys, i.e. modify it to ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on secure And as I mentioned before, I don't have this problem when I manually run gdm as root after booting. I will try your way to see if it will work. Thanks! On Thu, 2003-07-24 at 23:57, Joe Marcus Clarke wrote: > On Thu, 2003-07-24 at 23:53, Peng Zhang wrote: > > Hi folks, > > > > I just used cvsup to upgrade my system to 4.8 stable. Now I have problem > > with gdm. When I have logged in as other user, I will log in as root. That > > happens when I automatically start gdm after booting. But if I start gdm > > myself after boot, I won't have this problem. I don't know why. Does > > somebody have the same problem before? > > Nope. GDM 2 works fine for me on 4.8-STABLE if it's started out of > ${X11BASE}/etc/rc.d. Do you have any console messages or other errors > to indicate what's going on? What does your gdm user entry look like? > > Joe > > > > > Thanks! > > > > Peng > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Zhang, Peng From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 21:27:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03F9437B401 for ; Thu, 24 Jul 2003 21:27:27 -0700 (PDT) Received: from hsph.harvard.edu (hsph.harvard.edu [128.103.75.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 407E543FAF for ; Thu, 24 Jul 2003 21:27:26 -0700 (PDT) (envelope-from pzhang@hsph.harvard.edu) Received: from [134.174.184.76] (sph184-76.harvard.edu [134.174.184.76]) by hsph.harvard.edu (8.11.7+Sun/8.11.7) with ESMTP id h6P4Raw08930; Fri, 25 Jul 2003 00:27:36 -0400 (EDT) From: "Zhang, Peng" To: Joe Marcus Clarke In-Reply-To: <1059105455.353.14.camel@shumai.marcuscom.com> References: <1059105455.353.14.camel@shumai.marcuscom.com> Content-Type: text/plain Message-Id: <1059106991.345.8.camel@pzhang> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 25 Jul 2003 00:23:11 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: problem with gdm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 04:27:27 -0000 On Thu, 2003-07-24 at 23:57, Joe Marcus Clarke wrote: > On Thu, 2003-07-24 at 23:53, Peng Zhang wrote: > > Hi folks, > > > > I just used cvsup to upgrade my system to 4.8 stable. Now I have problem > > with gdm. When I have logged in as other user, I will log in as root. That > > happens when I automatically start gdm after booting. But if I start gdm > > myself after boot, I won't have this problem. I don't know why. Does > > somebody have the same problem before? > > Nope. GDM 2 works fine for me on 4.8-STABLE if it's started out of > ${X11BASE}/etc/rc.d. There is a gdm.sh.sample file in this directory. You mean you start it yourself or put this script to /usr/local/etc/rc.d. And the gdm entry in my computer is: gdm:*:92:92:GNOME Display Manager:/nonexistent:/sbin/nologin > Do you have any console messages or other errors > to indicate what's going on? What does your gdm user entry look like? > > Joe > > > > > Thanks! > > > > Peng > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Zhang, Peng From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 21:30:23 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81D9937B401 for ; Thu, 24 Jul 2003 21:30:23 -0700 (PDT) Received: from altair.mukappabeta.net (pC19F61A9.dip.t-dialin.net [193.159.97.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id D51E943F3F for ; Thu, 24 Jul 2003 21:30:20 -0700 (PDT) (envelope-from mkb@mukappabeta.de) Received: from mukappabeta.de (localhost [127.0.0.1]) by altair.mukappabeta.net (Postfix) with ESMTP id A13CE596C; Fri, 25 Jul 2003 06:34:42 +0200 (CEST) Message-ID: <3F20B362.5040308@mukappabeta.de> Date: Fri, 25 Jul 2003 06:34:42 +0200 From: Matthias Buelow Organization: GeFoekoM e.V. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4a) Gecko/20030504 X-Accept-Language: de-de, de, en-gb, en-us, en MIME-Version: 1.0 To: "Zhang, Peng" References: <1059105455.353.14.camel@shumai.marcuscom.com> <1059106655.345.4.camel@pzhang> In-Reply-To: <1059106655.345.4.camel@pzhang> X-Enigmail-Version: 0.75.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: problem with gdm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 04:30:23 -0000 Zhang, Peng wrote: > I don't have any error in the console. Just log in as pzhang, then I > actually enter as root account. The way I start gdm is to edit > /etc/ttys, i.e. modify it to > ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on secure > And as I mentioned before, I don't have this problem when I manually run > gdm as root after booting. I will try your way to see if it will work. > Thanks! I have seen the same issue a couple months ago when I tried gnome2; I never considered gdm to be properly working (afair, the ports install even warned about using it) but using xdm and running gnome-session in .xsession worked. {\obrant not that I would give a flying f*ck about it anymore, considering the most obscene way that gnome is broken and misdesigned...} -- Matthias Buelow; mkb@{mukappabeta.de,informatik.uni-wuerzburg.de} From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 21:35:35 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E28A837B401 for ; Thu, 24 Jul 2003 21:35:35 -0700 (PDT) Received: from ms-smtp-02.southeast.rr.com (ms-smtp-02.southeast.rr.com [24.93.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03C4C43FA3 for ; Thu, 24 Jul 2003 21:35:35 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from creme-brulee.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158])h6P4WPqP012232; Fri, 25 Jul 2003 00:32:25 -0400 (EDT) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) h6P4YriZ055456; Fri, 25 Jul 2003 00:34:53 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: "Zhang, Peng" In-Reply-To: <1059106991.345.8.camel@pzhang> References: <1059105455.353.14.camel@shumai.marcuscom.com> <1059106991.345.8.camel@pzhang> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-g66UMWueULHEViwybnNZ" Organization: MarcusCom, Inc. Message-Id: <1059107732.353.24.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 25 Jul 2003 00:35:33 -0400 X-Spam-Status: No, hits=-11.6 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2, QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_XIMIAN autolearn=ham version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-stable@freebsd.org Subject: Re: problem with gdm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 04:35:36 -0000 --=-g66UMWueULHEViwybnNZ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2003-07-25 at 00:23, Zhang, Peng wrote: > On Thu, 2003-07-24 at 23:57, Joe Marcus Clarke wrote: > > On Thu, 2003-07-24 at 23:53, Peng Zhang wrote: > > > Hi folks, > > >=20 > > > I just used cvsup to upgrade my system to 4.8 stable. Now I have prob= lem > > > with gdm. When I have logged in as other user, I will log in as root.= That > > > happens when I automatically start gdm after booting. But if I start = gdm > > > myself after boot, I won't have this problem. I don't know why. Does > > > somebody have the same problem before? > >=20 > > Nope. GDM 2 works fine for me on 4.8-STABLE if it's started out of > > ${X11BASE}/etc/rc.d.=20 >=20 > There is a gdm.sh.sample file in this directory. You mean you start it > yourself or put this script to /usr/local/etc/rc.d.=20 GDM 2 cannot be started from /etc/ttys (as the pkg-message states). You need to copy this script to /usr/X11R6/etc/rc.d/gdm.sh, then run: /usr/X11R6/etc/rc.d/gdm.sh start This will happen automatically at boot time. >=20 > And the gdm entry in my computer is: > gdm:*:92:92:GNOME Display Manager:/nonexistent:/sbin/nologin Good, this is what it should be. Joe >=20 > > Do you have any console messages or other errors > > to indicate what's going on? What does your gdm user entry look like? > >=20 > > Joe > >=20 > > >=20 > > > Thanks! > > >=20 > > > Peng > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.= org" --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-g66UMWueULHEViwybnNZ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA/ILOUb2iPiv4Uz4cRApiGAKCawM2ipf5cCfFQBd5SMG9UwAasYwCffG7a swydJlTgbhNE9wdiiNwmpB8= =P2Jv -----END PGP SIGNATURE----- --=-g66UMWueULHEViwybnNZ-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 22:15:16 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3150E37B401 for ; Thu, 24 Jul 2003 22:15:16 -0700 (PDT) Received: from ns1.stelt.ru (ns1.stelt.ru [217.18.48.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A521643F93 for ; Thu, 24 Jul 2003 22:15:14 -0700 (PDT) (envelope-from jaroshenko@mailru.com) Received: from gate-mx.stelt.ru (gate-mx.stelt.ru [217.18.48.32]) by ns1.stelt.ru (8.12.9/8.12.9) with ESMTP id h6P5FCt7012608 for ; Fri, 25 Jul 2003 09:15:13 +0400 Received: by gate-mx.stelt.ru (Postfix, from userid 502) id AF3342F081; Fri, 25 Jul 2003 09:15:12 +0400 (MSD) Received: from mailru.com (unknown [192.168.1.41]) by gate-mx.stelt.ru (Postfix) with ESMTP id 7FB7C2F081 for ; Fri, 25 Jul 2003 09:15:12 +0400 (MSD) Message-ID: <3F20BE44.1070208@mailru.com> Date: Fri, 25 Jul 2003 09:21:08 +0400 From: Serge Yaroshenko User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: System Administrator Appreciation Day X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 05:15:16 -0000 Hi! My respect FreeBSD team!!! Great system, great work!!! http://www.sysadminday.com/ Serge. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 03:39:39 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B281B37B401 for ; Fri, 25 Jul 2003 03:39:39 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id E77BC43F3F for ; Fri, 25 Jul 2003 03:39:30 -0700 (PDT) (envelope-from ru@sunbay.com) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h6PAdC0U070641 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jul 2003 13:39:13 +0300 (EEST) (envelope-from ru@sunbay.com) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.9/8.12.8/Submit) id h6PAd6jE070626; Fri, 25 Jul 2003 13:39:06 +0300 (EEST) (envelope-from ru) Date: Fri, 25 Jul 2003 13:39:06 +0300 From: Ruslan Ermilov To: Darren Message-ID: <20030725103906.GA70382@sunbay.com> References: <15051663828.20030725004405@dazdaz.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <15051663828.20030725004405@dazdaz.org> User-Agent: Mutt/1.5.4i cc: stable@FreeBSD.org Subject: Re: Compiling OpenSSH statically on FreeBSD 4.8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 10:39:40 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 25, 2003 at 12:44:05AM +0100, Darren wrote: [...] > Thought i'd email you before mailing the list. I've been trying to > compile OpenSSH statically under FreeBSD and am running onto a linker > error that I can't resolve and wondered if you had knowledge of this > particular problem? >=20 I've just committed a fix for this: src/share/mk/bsd.libnames.mk,v 1.28.2.11 src/secure/usr.sbin/sshd/Makefile,v 1.5.2.10 Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/IQjKUkv4P6juNwoRAmyyAJ4vNxi8rMd2CaEQ/TYFxLoXtEw2UACdEG2X w+l/G62wj/FfbL+MKWH8mz8= =OoSp -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 04:12:10 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BC6437B401 for ; Fri, 25 Jul 2003 04:12:10 -0700 (PDT) Received: from vsmtp12.tin.it (vsmtp12.tin.it [212.216.176.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C9B643F3F for ; Fri, 25 Jul 2003 04:12:09 -0700 (PDT) (envelope-from voloterreno@tin.it) Received: from localhost (62.211.129.252) by vsmtp12.tin.it (7.0.019) id 3F1BB814001324A6 for freebsd-stable@freebsd.org; Fri, 25 Jul 2003 13:12:08 +0200 Date: Fri, 25 Jul 2003 13:16:25 +0200 Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Lia Maggioni To: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <6DEA8415-BE91-11D7-8E62-00039387DFA2@tin.it> X-Mailer: Apple Mail (2.482) Subject: FreeBSD doesn't find my CD-RW and sometimes my DVD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 11:12:10 -0000 Hi , I'm disperated I've recently installed FreeBSD 4.8 ,and all at the first look was ok , this was only a try in a small partition , and now I have decided to install it in a bigger partition , so I've downloaded the 5.1 ISO (to give it a try too) and I've tried to BURN it with "burncd" . Now, I've noticed that in the DEV directory there are the devices "acd0a" and "acd0c" , I've thought that acd0a was DVD and acd0c was CD-RW... but I was wrong... ACD0 is only the DVD , CD-RW (a Liteon 52x 24x 52x) isn't found at all!! Literally from DMESG: ata0-slave: ATA identify retries excedeed and sometimes it doesn't find my DVD too , with the message : ata1-slave: ATA identify retries excedeed so, I'm without CD and DVD :cry: What I can do?? My system is: Athlon XP 2400+ MSI KT4 Ultra (KT400) MoBo The CDRW and DVD are attached to the two slave of the two ATA channels Help me please , I've tried to remove the DVD in order to try to get CDRW recognised , but it doesn't work anyway Thanks for help From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 05:40:49 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6306237B404 for ; Fri, 25 Jul 2003 05:40:49 -0700 (PDT) Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41A3A43FCB for ; Fri, 25 Jul 2003 05:40:48 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta06-svc.ntlworld.comESMTP <20030725124043.SAEI16215.mta06-svc.ntlworld.com@llama.fishballoon.org>; Fri, 25 Jul 2003 13:40:43 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19g1rb-0001sB-2k; Fri, 25 Jul 2003 13:39:59 +0100 Date: Fri, 25 Jul 2003 13:39:59 +0100 From: Scott Mitchell To: Doug White Message-ID: <20030725123959.GB6218@llama.fishballoon.org> References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723140217.P92624@carver.gumbysoft.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: Brian Behlendorf cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 12:40:49 -0000 On Wed, Jul 23, 2003 at 02:02:55PM -0700, Doug White wrote: > > Does the new machine have ECC memory? If not, it could be something as > simple as bad RAM in the new system. I've just done four successive buildworlds on this machine, one with -j4, just for fun. They all completed without complaint, so I'm reasonably confident there's no dodgy RAM here. I'll send bug reports to FreeBSD and cvshome, and stick with the 4.6R binary in the meantime. Cheers, Scott From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 06:46:08 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 444CA37B401 for ; Fri, 25 Jul 2003 06:46:08 -0700 (PDT) Received: from vsmtp12.tin.it (vsmtp12.tin.it [212.216.176.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DD0E43FD7 for ; Fri, 25 Jul 2003 06:46:07 -0700 (PDT) (envelope-from voloterreno@tin.it) Received: from localhost (62.211.128.143) by vsmtp12.tin.it (7.0.019) id 3F1BB8140013B0A2; Fri, 25 Jul 2003 15:46:06 +0200 Date: Fri, 25 Jul 2003 13:58:49 +0200 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v482) To: greg.panula@dolaninformation.com From: Lia Maggioni In-Reply-To: <3F211851.C4EC8187@dolaninformation.com> Message-Id: <5A36F42C-BE97-11D7-8E62-00039387DFA2@tin.it> Content-Transfer-Encoding: quoted-printable X-Mailer: Apple Mail (2.482) cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD doesn't find my CD-RW and sometimes my DVD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 13:46:08 -0000 Venerd=EC, luglio 25, 2003, alle 01:45 , Greg Panula ha scritto: I don't use cable select :( I've ever used Jumpers. I've tried to change the position on the cable on the drives.... no way. :( Help :( Bye Marcello > Lia Maggioni wrote: >> >> Hi , I'm disperated >> >> I've recently installed FreeBSD 4.8 ,and all at the first look was ok = , >> this was only a try in a small partition , and now I have decided to >> install it in a bigger partition , so I've downloaded the 5.1 ISO (to >> give it a try too) and I've tried to BURN it with "burncd" . Now, = I've >> noticed that in the DEV directory there are the devices "acd0a" and >> "acd0c" , I've thought that acd0a was DVD and acd0c was CD-RW... but = I >> was wrong... >> >> ACD0 is only the DVD , CD-RW (a Liteon 52x 24x 52x) isn't found at=20 >> all!! >> Literally from DMESG: >> >> ata0-slave: ATA identify retries excedeed >> >> and sometimes it doesn't find my DVD too , with the message : >> >> ata1-slave: ATA identify retries excedeed >> >> so, I'm without CD and DVD :cry: >> >> What I can do?? >> > > Did you try setting the jumpers on the device(s) to slave instead of > Cable-select? > > I've had mixed results with IDE devices using cable-select(cs). > > greg > From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 07:29:41 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3188637B401 for ; Fri, 25 Jul 2003 07:29:41 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 505F643FBD for ; Fri, 25 Jul 2003 07:29:40 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h6PESrai032145; Fri, 25 Jul 2003 10:28:53 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h6PESqr6032142; Fri, 25 Jul 2003 10:28:52 -0400 (EDT) Date: Fri, 25 Jul 2003 10:28:52 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Scott Mitchell In-Reply-To: <20030725123959.GB6218@llama.fishballoon.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Brian Behlendorf cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 14:29:41 -0000 On Fri, 25 Jul 2003, Scott Mitchell wrote: > On Wed, Jul 23, 2003 at 02:02:55PM -0700, Doug White wrote: > > > > Does the new machine have ECC memory? If not, it could be something as > > simple as bad RAM in the new system. > > I've just done four successive buildworlds on this machine, one with > -j4, just for fun. They all completed without complaint, so I'm > reasonably confident there's no dodgy RAM here. > > I'll send bug reports to FreeBSD and cvshome, and stick with the 4.6R > binary in the meantime. I'd actually download your system vendor's memory diagnostic tool and run it in "No, really find the problem" mode, just to be on the safe side. I had a machine that had a one bit memory error that I didn't discover for years -- occasionally I'd see an odd segfault, but it turned out the page of memory usually got allocated to a bit of the kernel that didn't notice/care. Once in a while I'd recompile the kernel and the page would get used for something else, and turned up most frequently in Pine, and I would assume it was a Pine bug. I'd have saved myself a lot of trouble if I'd run the memory check the first time, so that's usually the solution I push on people now :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 07:59:06 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1826837B401; Fri, 25 Jul 2003 07:59:06 -0700 (PDT) Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB18543F75; Fri, 25 Jul 2003 07:59:04 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta01-svc.ntlworld.comESMTP <20030725145903.DFJZ21249.mta01-svc.ntlworld.com@llama.fishballoon.org>; Fri, 25 Jul 2003 15:59:03 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19g41T-0002EC-0T; Fri, 25 Jul 2003 15:58:19 +0100 Date: Fri, 25 Jul 2003 15:58:18 +0100 From: Scott Mitchell To: Robert Watson Message-ID: <20030725145818.GC6218@llama.fishballoon.org> References: <20030725123959.GB6218@llama.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-stable@freebsd.org cc: Brian Behlendorf Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 14:59:06 -0000 On Fri, Jul 25, 2003 at 10:28:52AM -0400, Robert Watson wrote: > I'd actually download your system vendor's memory diagnostic tool and run > it in "No, really find the problem" mode, just to be on the safe side. I > had a machine that had a one bit memory error that I didn't discover for > years -- occasionally I'd see an odd segfault, but it turned out the page > of memory usually got allocated to a bit of the kernel that didn't > notice/care. Once in a while I'd recompile the kernel and the page would > get used for something else, and turned up most frequently in Pine, and I > would assume it was a Pine bug. I'd have saved myself a lot of trouble if > I'd run the memory check the first time, so that's usually the solution I > push on people now :-). Thanks Robert - assuming I can find the relevant tool, I'll try that. This is a 3-year old Intel LG440GX+ system. It's only 'new' in the sense that it hasn't been used for anything for 2.5 of those 3 years... There's probably a CD around somewhere with some diagnostic tools for it. I do have a GB of RAM sitting here to be distributed between this machine and its twin. I will try putting the whole lot in this machine and see if that makes any difference to the behaviour. Cheers, Scott From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 08:04:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E907F37B401; Fri, 25 Jul 2003 08:04:50 -0700 (PDT) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DF7543FB1; Fri, 25 Jul 2003 08:04:50 -0700 (PDT) (envelope-from ler@lerctr.org) Received: from lerlaptop-red.iadfw.net (lerlaptop-red.iadfw.net [207.136.3.72]) (authenticated bits=0)h6PF4fNQ005090; Fri, 25 Jul 2003 10:04:41 -0500 (CDT) Date: Fri, 25 Jul 2003 10:04:41 -0500 From: Larry Rosenman To: Scott Mitchell , Robert Watson Message-ID: <51260000.1059145481@lerlaptop-red.iadfw.net> In-Reply-To: <20030725145818.GC6218@llama.fishballoon.org> References: <20030725123959.GB6218@llama.fishballoon.org> <20030725145818.GC6218@llama.fishballoon.org> X-Mailer: Mulberry/3.1.0b4 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-milter (http://amavis.org/) cc: Brian Behlendorf cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 15:04:51 -0000 --On Friday, July 25, 2003 15:58:18 +0100 Scott Mitchell wrote: > Thanks Robert - assuming I can find the relevant tool, I'll try that. > This is a 3-year old Intel LG440GX+ system. It's only 'new' in the sense > that it hasn't been used for anything for 2.5 of those 3 years... There's > probably a CD around somewhere with some diagnostic tools for it. > > I do have a GB of RAM sitting here to be distributed between this machine > and its twin. I will try putting the whole lot in this machine and see if > that makes any difference to the behaviour. you might also look at http://www.memtest86.com/ for a free memtest diagnostic. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 10:11:51 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D02CA37B401 for ; Fri, 25 Jul 2003 10:11:51 -0700 (PDT) Received: from smtp6.wanadoo.nl (smtp6.wanadoo.nl [194.134.35.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2569F43FAF for ; Fri, 25 Jul 2003 10:11:51 -0700 (PDT) (envelope-from steve@sohara.org) Received: from ams-gw.sohara.org (p2765.vwr.wanadoo.nl [194.134.218.214]) by smtp6.wanadoo.nl (Postfix) with SMTP id 9EE1276A46; Fri, 25 Jul 2003 19:11:48 +0200 (CEST) Date: Fri, 25 Jul 2003 19:11:44 +0200 From: Steve O'Hara-Smith To: Lia Maggioni Message-Id: <20030725191144.10028828.steve@sohara.org> In-Reply-To: <6DEA8415-BE91-11D7-8E62-00039387DFA2@tin.it> References: <6DEA8415-BE91-11D7-8E62-00039387DFA2@tin.it> X-Mailer: Sylpheed version 0.9.3 (GTK+ 1.2.10; i386-portbld-freebsd4.8) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX,Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD doesn't find my CD-RW and sometimes my DVD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 17:11:52 -0000 On Fri, 25 Jul 2003 13:16:25 +0200 Lia Maggioni wrote: LM> ACD0 is only the DVD , CD-RW (a Liteon 52x 24x 52x) isn't found at LM> all!! Literally from DMESG: LM> LM> ata0-slave: ATA identify retries excedeed I've had similar problems with my Samsung 48/24/48, I could usually get it recognised by using atacontrol to detach and reattach the channel. Don't do this to channel 0 if you are booting of ata0-master though. LM> and sometimes it doesn't find my DVD too , with the message : LM> LM> ata1-slave: ATA identify retries excedeed LM> LM> so, I'm without CD and DVD :cry: LM> LM> What I can do?? It might work better with them both on ata1 - I gave up and put an LG drive in, works fine . Anyone want a Samsung ? -- C:>WIN | Directable Mirrors The computer obeys and wins. |A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 10:40:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FEE937B401 for ; Fri, 25 Jul 2003 10:40:27 -0700 (PDT) Received: from sequel.rsm.ru (www2.rsm.ru [213.80.139.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id A30DD43FF5 for ; Fri, 25 Jul 2003 10:40:21 -0700 (PDT) (envelope-from aga@rsm.ru) Received: from rsm.ru (magic.rsm.ru [217.23.86.15])h6PHeJQ48311 for ; Fri, 25 Jul 2003 21:40:19 +0400 (MSD) Message-ID: <3F216B7E.2070405@rsm.ru> Date: Fri, 25 Jul 2003 21:40:14 +0400 From: Dmitry Agafonov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030423 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: OK Subject: module_register X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 17:40:28 -0000 Hello! After today's update (4.8-stable from cvs "RELENG_4") I can see in messages just after boot: Jul 25 18:34:25 gw /kernel: module_register: module miibus/ukphy already exists! Jul 25 18:34:25 gw /kernel: linker_file_sysinit "miibus.ko" failed to register! 17 Jul 25 18:34:25 gw /kernel: module_register: module pci/ed already exists! Jul 25 18:34:25 gw /kernel: linker_file_sysinit "if_ed.ko" failed to register! 17 Everything works fine, but messages like "can't" or "filed" are good reason to check... I searched google, but no good answer was found, so what can you say? -- Dmitry From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 11:29:53 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C24C237B401 for ; Fri, 25 Jul 2003 11:29:53 -0700 (PDT) Received: from smtp6.wanadoo.nl (smtp6.wanadoo.nl [194.134.35.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1541D43F3F for ; Fri, 25 Jul 2003 11:29:53 -0700 (PDT) (envelope-from steve@sohara.org) Received: from ams-gw.sohara.org (rot2-p1174.dial.wanadoo.nl [62.234.202.150]) by smtp6.wanadoo.nl (Postfix) with SMTP id 6A22176ACA; Fri, 25 Jul 2003 20:29:50 +0200 (CEST) Date: Fri, 25 Jul 2003 20:29:46 +0200 From: Steve O'Hara-Smith To: Peter Jeremy Message-Id: <20030725202946.0e554369.steve@sohara.org> In-Reply-To: <20030724213707.GU430@gsmx07.alcatel.com.au> References: <20030723173427.GA72876@vmunix.com> <20030723173427.GA72876@vmunix.com> <5.2.0.9.0.20030723234250.052821e8@192.168.0.12> <20030724070936.GA16762@rot13.obsecurity.org> <3F1FF81F.5050701@mac.com> <20030724164522.GA39964@pit.databus.com> <20030724201702.6667b707.steve@sohara.org> <20030724213707.GU430@gsmx07.alcatel.com.au> X-Mailer: Sylpheed version 0.9.3 (GTK+ 1.2.10; i386-portbld-freebsd4.8) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX,Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: barney@databus.com cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 18:29:54 -0000 On Fri, 25 Jul 2003 07:37:07 +1000 Peter Jeremy wrote: PJ> I'd suggest adding code in the "malloc_overcommit" path to touch stack PJ> that is likely to be used, close to the top of {m,c,re}alloc(). Sounds like a good move. PJ> There's a gcc-specific extension "__builtin_frame_address()" that will PJ> let you do this. This ensures that the stack pages you need are Urk - someone who understands the layout of the stack and can estimate the probable use had better look at doing that if it's going to happen. As for freeing the already allocated memory - what a good idea :) PJ> present before you try to sbrk() the data. There may still be other PJ> corner cases I've missed. PJ> PJ> Cleanly recovering in all cases when there is no additional memory PJ> available is a very hard problem. Most of the suggested fixes This is true - OTOH the OP would probably be much happier if malloc could be made to return NULL nearly always when memory can't be allocated, with a small probability of crashing. It looks like between us we might manage to produce a patch that will do that much. -- C:>WIN | Directable Mirrors The computer obeys and wins. |A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 15:13:41 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 648AE37B401 for ; Fri, 25 Jul 2003 15:13:41 -0700 (PDT) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id D17E743FA3 for ; Fri, 25 Jul 2003 15:13:40 -0700 (PDT) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (failways.internal [10.236.150.2]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 21516376; Sat, 26 Jul 2003 00:16:44 +0200 (CEST) Date: Sat, 26 Jul 2003 00:13:28 +0200 (CEST) From: Alban Hertroys To: Pete French In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20030725221644.21516376@solfertje.student.utwente.nl> cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Alban Hertroys List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 22:13:41 -0000 On 24 Jul, Pete French punched keys in this particular order: > Its not bogus - the trouble is that you cant tell at the time malloc returns > whether the pointer will be useable or not. You only find that out when > you try and use it, and whether theres any space or not depends oon what > else may have munched up (or released) memory between you making the call > to malloc() and actually writing to the location returned. This looks similar to the problem with mktemp(). Maybe it is possible to solve this in a similar way? For example, by allocating memory and filling it in the same call? That probably would mean that all the software should switch to a new way of allocating memory, but it's a start... -- Alban Hertroys http://solfertje.student.utwente.nl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This person has performed an illegal operation and will be shot down. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 15:52:36 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A419537B404 for ; Fri, 25 Jul 2003 15:52:36 -0700 (PDT) Received: from mail.allcaps.org (allcaps.org [216.240.173.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03AE843F85 for ; Fri, 25 Jul 2003 15:52:36 -0700 (PDT) (envelope-from bsder@allcaps.org) Received: from mail.allcaps.org (localhost [127.0.0.1]) by mail.allcaps.org (Postfix) with ESMTP id 35EA192FAF; Fri, 25 Jul 2003 18:52:38 -0400 (EDT) Received: from localhost (bsder@localhost)h6PMqb49008284; Fri, 25 Jul 2003 15:52:38 -0700 X-Authentication-Warning: mail.allcaps.org: bsder owned process doing -bs Date: Fri, 25 Jul 2003 15:52:37 -0700 (PDT) From: "Andrew P. Lentvorski, Jr." To: Lia Maggioni In-Reply-To: <6DEA8415-BE91-11D7-8E62-00039387DFA2@tin.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD doesn't find my CD-RW and sometimes my DVD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 22:52:37 -0000 On Fri, 25 Jul 2003, Lia Maggioni wrote: > ACD0 is only the DVD , CD-RW (a Liteon 52x 24x 52x) isn't found at all!! > Literally from DMESG: > > ata0-slave: ATA identify retries excedeed > > and sometimes it doesn't find my DVD too , with the message : > > ata1-slave: ATA identify retries excedeed I would recommend setting the jumpers rather than using the cable select; it simply removes one variable from the problem. Take the CD off of the same cable as your hard drive. I would probably replace the DVD with the CD-RW to see if that works. Then I would probably try to put the DVD and CD-RW on the same cable. Check that your ATA cable doesn't violate the ATA specs (I think that 18" is the limit for an "in-spec" ATA cable. Yes, that's *short*.) I have been seeing this kind of intermittent problem with the ATA subsystem since the ATA rewrite. It has persisted into 5.1 Release. To be fair, the failures are intermittent (read: really hard to debug), and I haven't checked any of the old FreeBSD releases; so I am reluctant to complain too loudly. It seems that heterogeneous combinations of devices on the same cable give FreeBSD problems. ie. a UDMA 100 and a PIO 4 device on the same cable. Normally this shows up as the slower device not being detected. Putting slow devices on their own cable seems to cut down on the probability. I presume that the issue is something along the lines of the chipsets in the slow device are slightly out of spec and the FreeBSD driver refusing to coddle broken hardware. I am hesitant to blame FreeBSD as this may simply be a case of FreeBSD reporting the failure while other OS's simply degrade badly and hide the problem. However, it is annoying as it's a complete crapshoot as to whether my ATA CD-RW will be found on any given day. I've tried 4 different motherboards, 6 different types of cables, and 4 different CD-RW's. All of them exhibit some intermittent failures. I'm really looking forward to Serial ATA. Point to point connection should eliminate whole classes of this kind of breakage. -a From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 03:30:51 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2381837B401 for ; Sat, 26 Jul 2003 03:30:51 -0700 (PDT) Received: from smithers.nildram.co.uk (smithers.nildram.co.uk [195.112.4.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5D3D43F93 for ; Sat, 26 Jul 2003 03:30:49 -0700 (PDT) (envelope-from muttley@gotadsl.co.uk) Received: from [192.168.0.7] (muttley.gotadsl.co.uk [213.208.123.26]) by smithers.nildram.co.uk (Postfix) with ESMTP id 947CD25B27E; Sat, 26 Jul 2003 11:30:45 +0100 (BST) Date: Sat, 26 Jul 2003 11:35:26 +0100 From: Matthew Whelan To: Chuck Swiger In-Reply-To: <3F20692E.2060107@mac.com> References: <20030724155926.7305F231C11@smithers.nildram.co.uk> <3F20692E.2060107@mac.com> Message-Id: <20030725212248.81E9.MUTTLEY@gotadsl.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.05.04 cc: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 10:30:51 -0000 On Thu, 24 Jul 2003 19:18:06 -0400 Chuck Swiger wrote: > Muttley wrote: > > Yes, I thought briefly about something like this. > > > > Then I thought 'there's a race condition'. > > Where? The FreeBSD implementation is wrapped in a THREAD_LOCK()...? Good point, well made > > Then I realised that other processes might not link against this malloc. > > Perhaps. Statically linked binaries, for example. Maybe Linux ones too? > > Then I realised the race condition doesn't even matter; processes will > > still be killed, as the kernel doesn't care that you're still in > > malloc() when the overcommitted memory is touched, it just knows you've > > touched it and there's no actual memory there. This will result in far > > more processes being killed. I believe that's a bad thing. > > Someone stated that it was a problem that malloc() returned pointers to > virtual address space that had been mapped but not allocated. This patch does > not guarantee that malloc() will return, but, if malloc() does returns a > pointer, using the memory being pointed to will refer to memory that is > allocated. Their main problem was that when memory ran out, processes got killed. The fact the process gets killed earlier doesn't alter the fact that it was killed. > As Barny Wolff said: > > Won't this merely die in malloc, not return 0? > > True. This isn't a perfect solution, but given the choice between: > > 1) malloc(LOTS) returning a pointer, and then sometime later the program dies > with a bus error when using that memory because no more VM is available, or > > 2) malloc(LOTS) causing an immediate failure in malloc(), > > ...choice #2 appears to be significantly better. > > Figuring out what went wrong from a coredump or backtrace for #2 when the > signal happens in malloc() should be obvious; determining why the program > crashed in the middle of referencing memory in some large buffer is > potentially misleading. If you re-read the original post in this thread, you will see that this appeared in the poster's syslog: Jul 23 01:37:57 m0n0wall /kernel: pid 80 (racoon), uid 0, was killed: out of swap space Finding out why the process died was never the big worry. Besides, see below... > Programs which take care to preallocate regions of memory they need before > they start doing a transaction or some other operation that needs to be atomic > would also prefer #2; the patch I proposed could have a beneficial impact on > data integrity for such programs. > Except that the process which cops the bullet in the head is the largest runnable non-system process. Check /usr/src/sys/vm/vm_pageout.c near the end of vm_pageout_scan(). Neither data integrity nor debugging from cores is helped by the patch. > -- > > People who encounter programs crashing in malloc() are likely going to > continue to complain about malloc() not returning NULL when the system is out > of memory. > > If malloc() is referencing memory before returning the pointer, means that the > system is going to reserve VM resources with temporal locality towards memory > _allocation_ rather than memory _reference_. Having the program crash at > memory allocation time rather than usage helps identify when and where this > problem actually happens more clearly, if only by a little bit. See above, and above that. > I'm not sure whether allocating memory sooner that way will make it more > likely that brk()/sbrk() or mmap() will return ENOMEM to the libc malloc() > implementation, but if it does not help, perhaps that means something and > we've identified the location of problem more precisely. Other posts suggest these calls won't ever return ENOMEM based on total system usage, as the kernel doesn't even track it. Even if they went for something in the style of Brent's description of vswap, surely this patch would effectively prevent ENOMEM due forcing the overcommit to zero by killing something as soon as a process requests memory beyond the total physical+swap. I don't see how you can change the undesired behaviour in userland. Cheers, Matt -- Matthew Whelan From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 04:13:21 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21B2A37B401 for ; Sat, 26 Jul 2003 04:13:21 -0700 (PDT) Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.200.93.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AD6543F85 for ; Sat, 26 Jul 2003 04:13:20 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 4.12) id 19gMzE-000Nau-00; Sat, 26 Jul 2003 12:13:16 +0100 To: dalroi@solfertje.student.utwente.nl, freebsd-stable@freebsd.org In-Reply-To: <20030725221644.21516376@solfertje.student.utwente.nl> Message-Id: From: Pete French Date: Sat, 26 Jul 2003 12:13:16 +0100 Subject: Re: malloc does not return null when out of memory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 11:13:21 -0000 > That probably would mean that all the software should switch to a new > way of allocating memory, but it's a start... ...its only "a start" if you consider the current behaviour to be a problem. which under most normal uses of FreeBSd (and all the other UNIXs which do this) it doesnt seem to be. I realise its a bit of a shock to realise whats going on, but its not something most people run into in practice. -pcf. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 04:55:37 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E4DA37B401 for ; Sat, 26 Jul 2003 04:55:37 -0700 (PDT) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id D750343F75 for ; Sat, 26 Jul 2003 04:55:35 -0700 (PDT) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.12.9/jtpda-5.4) with ESMTP id h6QBtSLJ096787 ; Sat, 26 Jul 2003 13:55:29 +0200 (CEST) Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) h6QBtR8C008792 ; Sat, 26 Jul 2003 13:55:27 +0200 (MEST) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.12.9/8.12.9/Submit) id h6QBtRGD008789; Sat, 26 Jul 2003 13:55:27 +0200 (MEST) To: Scott Mitchell References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> <20030725123959.GB6218@llama.fishballoon.org> From: arno@heho.snv.jussieu.fr Date: 26 Jul 2003 13:55:27 +0200 In-Reply-To: <20030725123959.GB6218@llama.fishballoon.org> Message-ID: Lines: 41 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Antivirus: scanned by sophie at shiva.jussieu.fr cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 11:55:37 -0000 Scott Mitchell writes: > On Wed, Jul 23, 2003 at 02:02:55PM -0700, Doug White wrote: > > > > Does the new machine have ECC memory? If not, it could be something as > > simple as bad RAM in the new system. > > I've just done four successive buildworlds on this machine, one with -j4, > just for fun. They all completed without complaint, so I'm reasonably > confident there's no dodgy RAM here. I second your expereinces : I see the same on my laboratory main server (Athlon 700) ever since cvs was updated from 1.10 to 1.11 (4.7-R ?) : su-2.02# fgrep 'exited on signal' messages Jun 16 19:26:26 heho /kernel: pid 1344 (cvs), uid 21: exited on signal 11 Jun 16 19:26:29 heho /kernel: pid 1345 (cvs), uid 21: exited on signal 11 Jun 16 21:23:36 heho /kernel: pid 2094 (cvs), uid 118: exited on signal 11 Jun 17 10:42:51 heho /kernel: pid 5138 (cvs), uid 21: exited on signal 11 Jun 17 13:22:44 heho /kernel: pid 11959 (cvs), uid 134: exited on signal 11 Jun 17 13:22:49 heho /kernel: pid 11961 (cvs), uid 134: exited on signal 11 Jun 17 14:24:36 heho /kernel: pid 12314 (java), uid 134: exited on signal 6 (core dumped) Jun 30 02:02:43 heho /kernel: pid 23778 (cvs), uid 0: exited on signal 11 Jul 1 16:29:31 heho /kernel: pid 609 (cvs), uid 21: exited on signal 11 Jul 7 17:13:33 heho /kernel: pid 38639 (cvs), uid 21: exited on signal 11 Jul 18 16:07:36 heho /kernel: pid 73850 (cvs), uid 21: exited on signal 11 Jul 18 16:07:39 heho /kernel: pid 73851 (cvs), uid 21: exited on signal 11 Jul 19 20:57:59 heho /kernel: pid 83113 (cvs), uid 21: exited on signal 11 Jul 22 17:26:19 heho /kernel: pid 99828 (java), uid 134: exited on signal 6 (core dumped) All other server programs run flawlessly and I doubt seriously that the java core-dumps are related to hardware problems. I will rebuild world with the patch I applied in the 4-7 days and which was supposed to prevent leaving cvsd as CPU-bound zombie processes. Regards, Arno From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 05:13:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4A7D37B401 for ; Sat, 26 Jul 2003 05:13:00 -0700 (PDT) Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 597B343FA3 for ; Sat, 26 Jul 2003 05:12:59 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta05-svc.ntlworld.comESMTP <20030726121257.VGRK28183.mta05-svc.ntlworld.com@llama.fishballoon.org>; Sat, 26 Jul 2003 13:12:57 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19gNuH-00059r-Bb; Sat, 26 Jul 2003 13:12:13 +0100 Date: Sat, 26 Jul 2003 13:12:13 +0100 From: Scott Mitchell To: arno@heho.snv.jussieu.fr Message-ID: <20030726121213.GA19771@llama.fishballoon.org> References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> <20030725123959.GB6218@llama.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 12:13:01 -0000 On Sat, Jul 26, 2003 at 01:55:27PM +0200, arno@heho.snv.jussieu.fr wrote: > Scott Mitchell writes: > > > On Wed, Jul 23, 2003 at 02:02:55PM -0700, Doug White wrote: > > > > > > Does the new machine have ECC memory? If not, it could be something as > > > simple as bad RAM in the new system. > > > > I've just done four successive buildworlds on this machine, one with -j4, > > just for fun. They all completed without complaint, so I'm reasonably > > confident there's no dodgy RAM here. > > I second your expereinces : I see the same on my laboratory > main server (Athlon 700) ever since cvs was updated from 1.10 > to 1.11 (4.7-R ?) : I've just had a look in the (freebsd.org) cvs logs -- it looks like FreeBSD was using cvs 1.11.1p1 for 4.5-R through 4.7-R, then moved to 1.11.2 and then 1.11.5 for 4.8-R. I have not seen this problem with any release before 4.8, although we skipped 4.7 entirely. That said, without knowing what the bug is, or even if there really is a bug, I'm not making any statements about which versions it appears in :-) In the dodgy RAM department, the diagnostic tools for the server board do seem to include a comprehensive RAM test, so I plan to give this and memtest86 a workout when I can schedule some downtime on the server. Will report back when that is done. Cheers, Scott From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 06:38:04 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6EF137B401 for ; Sat, 26 Jul 2003 06:38:04 -0700 (PDT) Received: from pop016.verizon.net (pop016pub.verizon.net [206.46.170.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0611843FAF for ; Sat, 26 Jul 2003 06:38:04 -0700 (PDT) (envelope-from douglasv@verizon.net) Received: from verizon.net ([65.234.185.156]) by pop016.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030726133802.JAKQ24927.pop016.verizon.net@verizon.net> for ; Sat, 26 Jul 2003 08:38:02 -0500 Received: from 192.168.123.4 for freebsd-stable@freebsd.org; Sat, 26 Jul 2003 09:39:48 -0400 Message-ID: <000e01c3537b$61b48850$047ba8c0@buster> From: "Douglas" To: Date: Sat, 26 Jul 2003 09:39:47 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Authentication-Info: Submitted using SMTP AUTH at pop016.verizon.net from [65.234.185.156] at Sat, 26 Jul 2003 08:38:02 -0500 Subject: internet connects but no make in ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 13:38:05 -0000 I upgraded to 4.8 via cvsup, but I never setup networking on the original install. I could connect to the internet with ppp but could not use a browser or use make in ports or use ftp; but I'm connected to the internet? What entry do I make/ where could I look? I have the freebsd handbook, the complete freebsd, Thank you, Doug From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 08:03:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AD1A37B401; Sat, 26 Jul 2003 08:03:50 -0700 (PDT) Received: from hub.org (hub.org [64.117.225.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B5D443FBD; Sat, 26 Jul 2003 08:03:49 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from hub.org (unknown [64.117.225.220]) by hub.org (Postfix) with ESMTP id 73D1E5B9DB1; Sat, 26 Jul 2003 12:03:48 -0300 (ADT) Date: Sat, 26 Jul 2003 12:03:48 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20030726115857.M37284@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Dump Card State Begins ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 15:03:50 -0000 Hi ... Can someone tell me whether or not this is indicative of a hardware, or software, problem? It happened a few times today, on two different drives, and it seem to "self-recover", since the server is still purring along without any noticeable problems: neptune# grep "timed out" /var/log/messages Jul 25 03:52:51 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x40 - timed out Jul 25 03:57:22 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x18 - timed out Jul 25 03:58:53 neptune /kernel: (da1:ahd1:0:1:0): SCB 0x1e - timed out Jul 26 10:55:46 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x39 - timed out The drives are all U320 Seagate Cheetah 70G ... no RAID involved, its just straight drives using the motherboard's onboard SCSI controller ... the motherboard is the Intel SE7501, in the SR2300 chassis ... It did it back on the 19th as well: Jul 19 19:37:16 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x46 - timed out Jul 19 19:38:46 neptune /kernel: (da1:ahd1:0:1:0): SCB 0x2d - timed out But again, appears to have recovered with no ill effects ... Jul 25 03:52:51 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x40 - timed out Jul 25 03:53:06 neptune /kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< Jul 25 03:53:06 neptune /kernel: ahd1: Dumping Card State at program address 0x15 Mode 0x22 Jul 25 03:53:06 neptune /kernel: Card was paused Jul 25 03:53:06 neptune /kernel: HS_MAILBOX[0x0] INTCTL[0xc0] SEQINTSTAT[0x0] SAVED_MODE[0x11] Jul 25 03:53:06 neptune /kernel: DFFSTAT[0x31] SCSISIGI[0x0] SCSIPHASE[0x0] SCSIBUS[0x0] Jul 25 03:53:06 neptune /kernel: LASTPHASE[0x1] SCSISEQ0[0x0] SCSISEQ1[0x12] SEQCTL0[0x10] Jul 25 03:53:06 neptune /kernel: SEQINTCTL[0x0] SEQ_FLAGS[0xc0] SEQ_FLAGS2[0x0] SSTAT0[0x0] Jul 25 03:53:06 neptune /kernel: SSTAT1[0x8] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x8] Jul 25 03:53:06 neptune /kernel: SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] Jul 25 03:53:06 neptune /kernel: LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x1] Jul 25 03:53:06 neptune /kernel: Jul 25 03:53:06 neptune /kernel: SCB Count = 96 CMDS_PENDING = 29 LASTSCB 0x22 CURRSCB 0x22 NEXTSCB 0xff00 Jul 25 03:53:06 neptune /kernel: qinstart = 65252 qinfifonext = 65252 Jul 25 03:53:06 neptune /kernel: QINFIFO: Jul 25 03:53:06 neptune /kernel: WAITING_TID_QUEUES: Jul 25 03:53:06 neptune /kernel: Pending list: Jul 25 03:53:06 neptune /kernel: 21 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:06 neptune /kernel: 29 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:06 neptune /kernel: 63 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:06 neptune /kernel: 65 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:06 neptune /kernel: 24 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:06 neptune /kernel: 10 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 15 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 47 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 59 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 26 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 77 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 54 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 42 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 57 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 55 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 92 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 78 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 12 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 27 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 28 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 32 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 95 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 53 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 25 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 52 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 1 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 38 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 93 FIFO_USE[0x0] SCB_CONTROL[0x62] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: 64 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x27] Jul 25 03:53:07 neptune /kernel: Total 29 Jul 25 03:53:07 neptune /kernel: Kernel Free SCB list: 7 56 34 19 4 37 20 46 40 61 11 39 31 45 58 23 73 30 5 62 8 41 18 16 13 66 51 14 44 49 36 50 70 35 9 76 74 2 48 43 3 33 79 71 75 60 67 69 91 94 6 72 0 68 17 22 90 89 88 87 86 85 84 83 82 81 80 Jul 25 03:53:07 neptune /kernel: Sequencer Complete DMA-inprog list: Jul 25 03:53:07 neptune /kernel: Sequencer Complete list: Jul 25 03:53:07 neptune /kernel: Sequencer DMA-Up and Complete list: Jul 25 03:53:07 neptune /kernel: Jul 25 03:53:07 neptune /kernel: ahd1: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x22 Jul 25 03:53:07 neptune /kernel: SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] Jul 25 03:53:07 neptune /kernel: SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] Jul 25 03:53:07 neptune /kernel: SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 Jul 25 03:53:07 neptune /kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] Jul 25 03:53:07 neptune /kernel: ahd1: FIFO1 Free, LONGJMP == 0x8277, SCB 0x7 Jul 25 03:53:07 neptune /kernel: SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x4] DFSTATUS[0x89] Jul 25 03:53:07 neptune /kernel: SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] Jul 25 03:53:07 neptune /kernel: SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 Jul 25 03:53:07 neptune /kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] Jul 25 03:53:07 neptune /kernel: LQIN: 0x55 0x0 0x0 0x7 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 Jul 25 03:53:07 neptune /kernel: ahd1: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 Jul 25 03:53:07 neptune /kernel: ahd1: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 Jul 25 03:53:07 neptune /kernel: SIMODE0[0xc] Jul 25 03:53:07 neptune /kernel: CCSCBCTL[0x0] Jul 25 03:53:07 neptune /kernel: ahd1: REG0 == 0x22, SINDEX = 0x122, DINDEX = 0x102 Jul 25 03:53:07 neptune /kernel: ahd1: SCBPTR == 0x7, SCB_NEXT == 0x49, SCB_NEXT2 == 0xfff1 Jul 25 03:53:07 neptune /kernel: CDB 2a 0 7 80 a0 ca Jul 25 03:53:07 neptune /kernel: STACK: 0x125 0x125 0x125 0x257 0x257 0x257 0x29 0x15 Jul 25 03:53:07 neptune /kernel: <<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> Jul 25 03:53:07 neptune /kernel: Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 Jul 25 03:53:07 neptune /kernel: Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 Jul 25 03:53:07 neptune /kernel: Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 08:26:30 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF00637B401 for ; Sat, 26 Jul 2003 08:26:30 -0700 (PDT) Received: from lakemtao02.cox.net (lakemtao02.cox.net [68.1.17.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id F32F643FB1 for ; Sat, 26 Jul 2003 08:26:29 -0700 (PDT) (envelope-from rjhjr@cox.net) Received: from kongemord.krig.net ([68.100.93.21]) by lakemtao02.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with SMTP id <20030726152629.PQFK24359.lakemtao02.cox.net@kongemord.krig.net> for ; Sat, 26 Jul 2003 11:26:29 -0400 Received: by kongemord.krig.net (sSMTP sendmail emulation); Sat, 26 Jul 2003 11:26:29 -0400 From: "Bob Hall" Date: Sat, 26 Jul 2003 11:26:29 -0400 To: freebsd-stable@freebsd.org Message-ID: <20030726152629.GB78553@kongemord.krig.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <000e01c3537b$61b48850$047ba8c0@buster> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000e01c3537b$61b48850$047ba8c0@buster> User-Agent: Mutt/1.4.1i Subject: Re: internet connects but no make in ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 15:26:31 -0000 On Sat, Jul 26, 2003 at 09:39:47AM -0400, Douglas wrote: > I upgraded to 4.8 via cvsup, but I never setup > networking on the original install. > > I could connect to the internet with ppp > but could not use a browser or use make in ports > or use ftp; but I'm connected to the internet? Actually, I think you're only connected to your ISP's modem. > What entry do I make/ where could I look? > I have the freebsd handbook, the complete freebsd, This first time I did this, I followed the instructions in Lehey's book. It took a while and some effort, since I started off knowing very little about the subject. How you set it up depends on your situation and wishes, so I can't tell you how to do it. Read, study, and post questions to freebsd-questions, since this doesn't relate to stable. Bob Hall From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 12:50:08 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4005537B401 for ; Sat, 26 Jul 2003 12:50:08 -0700 (PDT) Received: from archimedes.tomelliott.net (archimedes.tomelliott.net [81.6.196.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AC2D43FE0 for ; Sat, 26 Jul 2003 12:50:01 -0700 (PDT) (envelope-from tom@tomelliott.net) Received: (qmail 8309 invoked by uid 85); 26 Jul 2003 19:45:16 -0000 Received: from tom@tomelliott.net by archimedes.tomelliott.net by uid 89 with qmail-scanner-1.15 (sweep: 2.9/3.56. clamscan: 0.54. Clear:. Processed in 10.24976 secs); 26 Jul 2003 19:45:16 -0000 Received: from unknown (HELO europa) (81.6.196.152) by archimedes.tomelliott.net with SMTP; 26 Jul 2003 19:45:05 -0000 Message-ID: <073601c353af$125b2050$0a64640a@sharfleet.co.uk> From: "Thomas Elliott" To: Date: Sat, 26 Jul 2003 20:49:35 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Strange Kernel Compile Error.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 19:50:08 -0000 merlin# rm GENERIC=20 merlin# cd /usr/share/examples/cvsup/ merlin# cvsup stable-supfile=20 Connected to cvsup.uk.FreeBSD.org Updating collection src-all/cvs Checkout src/sys/i386/conf/GENERIC Finished successfully merlin# cd /usr/src merlin# make buildkernel KERNCONF=3DGENERIC -------------------------------------------------------------- >>> Kernel build for GENERIC started on Sat Jul 26 20:36:32 BST 2003 -------------------------------------------------------------- =3D=3D=3D> GENERIC mkdir -p /usr/obj/usr/src/sys cd /usr/src/sys/i386/conf; = PATH=3D/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/= obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d = /usr/obj/usr/src/sys/GENERIC /usr/src/sys/i386/conf/GENERIC config: /usr/src/sys/i386/conf/GENERIC:74: devices with zero units are = not likely to be correct *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. merlin# uname -a FreeBSD merlin.domain 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Jun 5 = 02:55:42 GMT 2003 = root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 Any ideas? This is a fresh install of 5.1, cvsup'd to the latest src. Thanks -- Tom tom@tomelliott.net ICQ: 8018364 MSN: netgeek_uk@hotmail.com Home# +44(0)1634309229 Fax# +44(0)1634710086 Mobile# +44(0)7764486175 US# +1(917)4386847 My keyboard has an F1 key. Where is the NASCAR key? From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 13:17:12 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97C1537B401 for ; Sat, 26 Jul 2003 13:17:12 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91BDF43F3F for ; Sat, 26 Jul 2003 13:17:11 -0700 (PDT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19gVTY-00084w-00 for ; Sat, 26 Jul 2003 22:17:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19gVTX-00084d-00 for ; Sat, 26 Jul 2003 22:17:07 +0200 From: Samuel Tardieu Date: Sat, 26 Jul 2003 22:08:48 +0200 Organization: Avian Carrier & Friends Lines: 11 Message-ID: <87u199jbjj.fsf@inf.enst.fr> References: <073601c353af$125b2050$0a64640a@sharfleet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.5 (cauliflower, i386--freebsd) Cancel-Lock: sha1:KTbQ3BkUmJe5PhSUfFf9jsiEmFc= X-Leafnode-NNTP-Posting-Host: 127.0.0.1 Sender: news Subject: Re: Strange Kernel Compile Error.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 20:17:12 -0000 Thomas> merlin# cvsup stable-supfile Thomas> This is a fresh install of 5.1, cvsup'd to the latest src. Your "stable-supfile" name looks like a -STABLE version. Aren't you by change trying to compile a -STABLE kernel on a 5.1 system? -STABLE is still 4.x at this time. Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 13:50:59 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6996F37B401 for ; Sat, 26 Jul 2003 13:50:59 -0700 (PDT) Received: from hermes.pressenter.com (hermes.pressenter.com [69.58.128.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBB1443F93 for ; Sat, 26 Jul 2003 13:50:58 -0700 (PDT) (envelope-from nospam@hiltonbsd.com) Received: from [69.58.130.177] (helo=daggar.sbgnet.local) by hermes.pressenter.com with smtp (Exim 3.16 #1) id 19gW0H-00017S-00 for freebsd-stable@freebsd.org; Sat, 26 Jul 2003 15:50:57 -0500 Date: Sat, 26 Jul 2003 15:50:57 -0500 From: Stephen Hilton To: freebsd-stable@freebsd.org Message-Id: <20030726155057.426cce7d.nospam@hiltonbsd.com> X-Mailer: Sylpheed version 0.9.3 (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: make index / portsdb -Uu problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 20:50:59 -0000 Cheers, Anyone seeing problems with the "make index" or the "portsdb -Uu" runs on 4.8-STABLE cvsupd today after 1PM CDT. Mine are quite borked up, and am trying to determine if the problems are local to my system. I have posted to the ports list earlier in the day also. Regards, Stephen Hilton nospam@hiltonbsd.com From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 20:10:23 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 052B737B401 for ; Sat, 26 Jul 2003 20:10:23 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-63-207-60-135.dsl.lsan03.pacbell.net [63.207.60.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4448B43F93 for ; Sat, 26 Jul 2003 20:10:22 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id F1B5866D32; Sat, 26 Jul 2003 20:10:21 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id C98C4C25; Sat, 26 Jul 2003 20:10:21 -0700 (PDT) Date: Sat, 26 Jul 2003 20:10:21 -0700 From: Kris Kennaway To: Stephen Hilton Message-ID: <20030727031021.GA55646@rot13.obsecurity.org> References: <20030726155057.426cce7d.nospam@hiltonbsd.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline In-Reply-To: <20030726155057.426cce7d.nospam@hiltonbsd.com> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: make index / portsdb -Uu problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2003 03:10:23 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 26, 2003 at 03:50:57PM -0500, Stephen Hilton wrote: > Cheers, >=20 >=20 > Anyone seeing problems with the "make index" or the "portsdb -Uu"=20 > runs on 4.8-STABLE cvsupd today after 1PM CDT. >=20 > Mine are quite borked up, and am trying to determine if the=20 > problems are local to my system. >=20 > I have posted to the ports list earlier in the day also. index is currently building successfully on a clean system. Either you don't have a complete or consistent ports tree, or something else on your system is causing the failure. Kris --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/I0KdWry0BWjoQKURAipyAJ4yNPCvQDLO0UqoHt/p+7FDgkoWawCg6YdD dqmvvDcdh0VfDiFTqdmGKF0= =rwdL -----END PGP SIGNATURE----- --DocE+STaALJfprDB-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 21:51:05 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40D8C37B401 for ; Sat, 26 Jul 2003 21:51:05 -0700 (PDT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 15CE343F3F for ; Sat, 26 Jul 2003 21:51:04 -0700 (PDT) (envelope-from blueeskimo@gmx.net) Received: (qmail 1999 invoked by uid 65534); 27 Jul 2003 04:51:02 -0000 Received: from dsl-cust-145.openweb.ca (EHLO [64.39.186.145]) (64.39.186.145) by mail.gmx.net (mp007) with SMTP; 27 Jul 2003 06:51:02 +0200 From: Adam To: freebsd-stable@freebsd.org In-Reply-To: <20030727031021.GA55646@rot13.obsecurity.org> References: <20030726155057.426cce7d.nospam@hiltonbsd.com> <20030727031021.GA55646@rot13.obsecurity.org> Content-Type: text/plain Message-Id: <1059281418.13942.3.camel@elwood> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 27 Jul 2003 00:50:19 -0400 Content-Transfer-Encoding: 7bit Subject: Re: make index / portsdb -Uu problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2003 04:51:05 -0000 On Sat, 2003-07-26 at 23:10, Kris Kennaway wrote: > index is currently building successfully on a clean system. Either > you don't have a complete or consistent ports tree, or something else > on your system is causing the failure. I just tried removing my /usr/ports and updating from scratch, and I still get a ton of 'non-existent -- dependency list incomplete' and 'no entry for' errors. Examples: gnome-swallow-1.1:"" non-existent -- dependency list incomplete gnome-swallow-1.1:"/usr/ports/graphics/libgnomecanvasgnome2-2.2.2_1" non-existent -- dependency list incomplete make_index: libgnomeuimm-1.3.16_1: no entry for /usr/ports/x11/libgnomemm make_index: libgnomeuimm-1.3.16_1: no entry for /usr/ports/x11/libgnomemm make_index: gmail-0.7.0: no entry for /usr/ports/mail/gmime make_index: gmail-0.7.0: no entry for /usr/ports/mail/gmime It doesn't complain about the same ports every time, but it does give the same errors every time. This has been happening for at least 2-3 months now. Here's the script I use to update my ports tree. /usr/local/bin/cvsup -g -L 2 /usr/share/examples/cvsup/ports-supfile /usr/local/sbin/pkgdb -aF /usr/local/sbin/portsdb -Uu /usr/local/sbin/portsclean -C /usr/local/sbin/pkgdb -u -- Adam