From owner-freebsd-hackers Sun Dec 26 5:24: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 7EE2014C08; Sun, 26 Dec 1999 05:24:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 669B81CD81C; Sun, 26 Dec 1999 05:24:02 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 26 Dec 1999 05:24:02 -0800 (PST) From: Kris Kennaway To: Theo van Klaveren Cc: Andrew Kenneth Milton , freebsd-hackers@FreeBSD.ORG Subject: Re: GLIDE for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Dec 1999, Theo van Klaveren wrote: > > Will grab new tarball shortly... (at least you know someone's testing it). > > He he... To me, that's worth a hundred bug reports :) You should submit this stuff as a port - it's not hard, and this will ensure that it gets mainstream testing/use, instead of drifting out of the public view like so much cool stuff which gets coded :-( Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 5:29:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.erlangen.netsurf.de (erlangen.netsurf.de [194.163.170.1]) by hub.freebsd.org (Postfix) with ESMTP id EF79B14EF4 for ; Sun, 26 Dec 1999 05:29:16 -0800 (PST) (envelope-from d_f0rce@gmx.de) Received: from blade (user-er-u1.erlangen.netsurf.de [194.163.170.161]) by mail.erlangen.netsurf.de (8.9.3/8.9.3) with SMTP id OAA32868 for ; Sun, 26 Dec 1999 14:29:05 +0100 (CET) Message-ID: <000c01bf4fa5$44bf5050$0201a8c0@blade> From: "Steffen Merkel" To: Subject: Posix Threads Date: Sun, 26 Dec 1999 14:23:40 +0100 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm learning C now for some weeks and today I wanted to program POSIX threads. Unfortunately my source seems not to run. Could you please have a look at my code and tell me whats wrong: #include #include #include void print( char *string ){ fprintf(stderr,"String: %s\n",string); } void main(void){ pthread_t thread; char string[] = "Hallo"; if( pthread_create( &thread, (const pthread_attr_t *)NULL, (void *)&print, &string ) != 0 ){ perror("pthread_create()"); exit(EXIT_FAILURE); } } I compiled this source with: gcc -pthreads -o pthread pthread.c Please reply to me directly, as I'm not subscribed to freebsd-hackers. Thanks in advance, Steffen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 6:21:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4E115152CE for ; Sun, 26 Dec 1999 06:20:59 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 8A38C1CA0; Sun, 26 Dec 1999 22:20:53 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: KATO Takenori Cc: FreeBSD-hackers@FreeBSD.org Subject: Re: device name of floppy disk In-Reply-To: Message from KATO Takenori of "Sat, 25 Dec 1999 23:42:13 +0900." <19991225234213C.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sun, 26 Dec 1999 22:20:53 +0800 From: Peter Wemm Message-Id: <19991226142053.8A38C1CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG KATO Takenori wrote: > The MAKEDEV has such lines as: > > # ln -f ${name}${unit}.1200 ${name}${unit}96 > # ln -f r${name}${unit}.1200 r${name}${unit}96 > # ln -f ${name}${unit}.1200 ${name}${unit}96ds15 > # ln -f r${name}${unit}.1200 r${name}${unit}96ds15 > # ln -f ${name}${unit}.1200 ${name}${unit}135ds15 > # ln -f r${name}${unit}.1200 r${name}${unit}135ds15 > > for floppy disk device. I have questions about these lines. > > 1. What is meanings of the name? I cannot understand meanings of > `96', `96ds15' and `135ds15'. Those are the SCO Unix/Xenix compatable names. SCO (and SYSV/386) uses those instead of "fdN.1440" etc. 48 = 48 tracks per inch = 5.25" disk, 96 = 96 tracks per inch = 5.25" disk, 135 = 135 tracks per inch = 3.5" disk = single sided ds = double sided = 9 sectors per track (as used on 360K disks) 15 = 15 sectors per track (as used on 5.25" 1.2M HD disks) 18 = 18 sectors per track (as used on 3.5" 1.44M HD disks There are some variations on different systems. Sometimes there is "s", "d" and "q" for single, double and quad speed in the "ds" field. > 2. Why they are commented out? Probably because they are not needed for general SCO Unix compatability (SCO apps generally let you choose the pathnames to the fd devices manually since there are so many of them) and having all the variations would just make a mess in /dev. > 3. Are these entries mandatory for all floppy disk devices? (Should I > make such lines when I add new mode for floppy disk?) I wouldn't worry about it, as long as the normal modes are supported. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 8:15: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 91AE2151FE for ; Sun, 26 Dec 1999 08:15:01 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id JAA01629 for ; Sun, 26 Dec 1999 09:14:56 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA07297; Sun, 26 Dec 1999 09:14:55 -0700 Date: Sun, 26 Dec 1999 09:14:55 -0700 Message-Id: <199912261614.JAA07297@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hackers@FreeBSD.org Subject: USB vs. parallel port X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A co-worker is looking into buying a printer, and was wondering which kind would be better, USB and/or parallel. (There are also some that do both). Parallel printers tend to load down the system when busy, but serial devices tend to load them down even more, although USB is a whole different animal. What are the trade-offs? Thanks for any help you can provide! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 9:56:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 32A791502D; Sun, 26 Dec 1999 09:55:46 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id CAA02958; Mon, 27 Dec 1999 02:55:43 +0900 (JST) To: FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG Subject: Re: indirection in bus space From: KATO Takenori In-Reply-To: Your message of "Sat, 25 Dec 1999 22:56:03 +0900" <19991225225603L.kato@gneiss.eps.nagoya-u.ac.jp> References: <19991225225603L.kato@gneiss.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991227025513Z.kato@gneiss.eps.nagoya-u.ac.jp> Date: Mon, 27 Dec 1999 02:55:13 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 27 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD-hackers list is added. KATO Takenori wrote: > I didn't realize the difference in type of bus_space_handle_t. So, > bus.h needs to be separated into bus_at386.h and bus_pc98.h. I revised bus space patch. This patch does: 1. copy bus.h to bus_at386.h. The bus_at386.h doesn't support indirection. 2. add bus_pc98.h. The bus_pc98.h supports indirection. 3. make new bus.h. The bus.h includes bus_at386.h or bus_pc98.h. 4. modify isa.c and nexus.c to support indirection. Indirection is enabled only when PC98 is defined. Because the pache is too large to attach on this mail, I put it as: http://www.freebsd.org/~kato/patches/busspace.diff.gz -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 11:49:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles506.castles.com [208.214.165.70]) by hub.freebsd.org (Postfix) with ESMTP id 2FE8B14BF2 for ; Sun, 26 Dec 1999 11:49:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA03506; Sun, 26 Dec 1999 11:53:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912261953.LAA03506@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Leif Neland Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem In-reply-to: Your message of "Sun, 26 Dec 1999 01:14:42 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 1999 11:53:44 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Sun, 26 Dec 1999, Daniel C. Sobral wrote: > > > Leif Neland wrote: > > > > > > > Just configure it correctly. Don't tell it to talk to a serial device > > > > that will be sending it gibberish. > > > > > > A hack would be to have the loader emit ATE0 to protect itself from > > > echoing modems. > > > > AFAIK, it would not protect against all modems. I think Winmodems, for > > instance, won't recognize that command. > > > A: AFAIK, winmodems are not connected to a serial port, they are internal > boards. > > B: Real men don't use anything marked win* for Real Computing. "Real Men" don't connect modems configured to echo to console ports. The first BIOS-supported serial port on your PC is the console port. End of story. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 14: 4: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 5388615132; Sun, 26 Dec 1999 14:04:03 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id EBADF2DC09; Sun, 26 Dec 1999 23:04:27 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id B45667811; Sun, 26 Dec 1999 23:02:38 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id AF87C10E10; Sun, 26 Dec 1999 23:02:38 +0100 (CET) Date: Sun, 26 Dec 1999 23:02:38 +0100 (CET) From: Andrzej Bialecki To: Tim Tsai Cc: Brian Fundakowski Feldman , freebsd-hackers@FreeBSD.org, sos@FreeBSD.org Subject: Re: using vgl In-Reply-To: <19991225123201.A6180@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Dec 1999, Tim Tsai wrote: > On Sat, Dec 25, 1999 at 01:07:50PM -0500, Brian Fundakowski Feldman wrote: > > On Sat, 25 Dec 1999, Tim Tsai wrote: > > > > > I'm trying to do some work based on vgl but it appears that it is tied to > > > syscons and any vgl programs must be started off a console. Is there any > > > way I can start a vgl program from a remote terminal (but have the output > > > be displayed on the local VGA screen) without writing a proxy of some > > > kind? See the sources for libvgl. You can do it easily by changing jus a few lines - the ioctl"s need to be executed on /dev/console instead of curent vty. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 15:34:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles554.castles.com [208.214.165.118]) by hub.freebsd.org (Postfix) with ESMTP id 81A9E14BDB for ; Sun, 26 Dec 1999 15:34:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA04024; Sun, 26 Dec 1999 15:38:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912262338.PAA04024@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@mt.sri.com (Nate Williams) Cc: freebsd-hackers@FreeBSD.org Subject: Re: USB vs. parallel port In-reply-to: Your message of "Sun, 26 Dec 1999 09:14:55 MST." <199912261614.JAA07297@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 1999 15:38:49 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A co-worker is looking into buying a printer, and was wondering which > kind would be better, USB and/or parallel. (There are also some that do > both). > > Parallel printers tend to load down the system when busy, but serial > devices tend to load them down even more, although USB is a whole > different animal. > > What are the trade-offs? USB is superior in just about every regard; a 'real' USB printer (as opposed to a non-USB printer and a USB-to-parallel cable) will be much faster, won't load the system down, and can do proper status reporting. The only downside in the BSD context is that our current USB stack is still pretty new, and has a few rough corners. I've been using a USB cable and a parallel printer now for more than 6 months with no real problems, however. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 18:31:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 1Cust245.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 90C4914CE9; Sun, 26 Dec 1999 18:31:14 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sun, 26 Dec 1999 21:31:12 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Peter Wemm Cc: KATO Takenori , FreeBSD-hackers@FreeBSD.org Subject: Re: device name of floppy disk In-Reply-To: <19991226142053.8A38C1CA0@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Dec 1999, Peter Wemm wrote: > > # ln -f ${name}${unit}.1200 ${name}${unit}135ds15 > > # ln -f r${name}${unit}.1200 r${name}${unit}135ds15 > > > > 1. What is meanings of the name? I cannot understand meanings of > > `96', `96ds15' and `135ds15'. > > Those are the SCO Unix/Xenix compatable names. SCO (and SYSV/386) uses those > instead of "fdN.1440" etc. > > 48 = 48 tracks per inch = 5.25" disk, > 96 = 96 tracks per inch = 5.25" disk, > 135 = 135 tracks per inch = 3.5" disk Eh? I thought .1200 referred to 5.25" disk drives... -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 20: 1:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 536D214E32; Sun, 26 Dec 1999 20:01:13 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 4D7F41CA0; Mon, 27 Dec 1999 12:01:07 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Fundakowski Feldman Cc: KATO Takenori , FreeBSD-hackers@FreeBSD.org Subject: Re: device name of floppy disk In-Reply-To: Message from Brian Fundakowski Feldman of "Sun, 26 Dec 1999 21:31:12 EST." Date: Mon, 27 Dec 1999 12:01:07 +0800 From: Peter Wemm Message-Id: <19991227040107.4D7F41CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > On Sun, 26 Dec 1999, Peter Wemm wrote: > > > > # ln -f ${name}${unit}.1200 ${name}${unit}135ds15 > > > # ln -f r${name}${unit}.1200 r${name}${unit}135ds15 > > > > > > 1. What is meanings of the name? I cannot understand meanings of > > > `96', `96ds15' and `135ds15'. > > > > Those are the SCO Unix/Xenix compatable names. SCO (and SYSV/386) uses tho se > > instead of "fdN.1440" etc. > > > > 48 = 48 tracks per inch = 5.25" disk, > > 96 = 96 tracks per inch = 5.25" disk, > > 135 = 135 tracks per inch = 3.5" disk > > Eh? I thought .1200 referred to 5.25" disk drives... .1200 = 1.2MB. .1440 = 1.44MB etc. You can format things differently so that you end up with different densities. Our default node names use the final capacity rather than the geometry that leads to that particular capacity. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 20:26:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id 9FBE314D77 for ; Sun, 26 Dec 1999 20:26:39 -0800 (PST) (envelope-from ken@bolingbroke.com) Received: from localhost (ken@localhost) by fremont.bolingbroke.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id UAA48434; Sun, 26 Dec 1999 20:26:32 -0800 (PST) Date: Sun, 26 Dec 1999 20:26:32 -0800 (PST) From: Ken Bolingbroke X-Sender: ken@fremont.bolingbroke.com To: Steffen Merkel Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Posix Threads In-Reply-To: <000c01bf4fa5$44bf5050$0201a8c0@blade> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When the main thread exits, all active threads are immediately terminated. Since your main subroutine has nothing after the pthread_create(), it immediately exits, thus your secondary thread has no chance to run. Add a delay at the end of the main thread to give the pthread_create() the time it needs, or just pthread_join() to wait until the secondary thread terminates. Ken Bolingbroke hacker@bolingbroke.com On Sun, 26 Dec 1999, Steffen Merkel wrote: > Hello, > > I'm learning C now for some weeks and today I wanted to program > POSIX threads. Unfortunately my source seems not to run. Could you > please have a look at my code and tell me whats wrong: > > #include > #include > #include > > void print( char *string ){ > fprintf(stderr,"String: %s\n",string); > } > > void main(void){ > pthread_t thread; > char string[] = "Hallo"; > > if( pthread_create( &thread, (const pthread_attr_t *)NULL, (void *)&print, > &string ) != 0 ){ > perror("pthread_create()"); > exit(EXIT_FAILURE); > } > > } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 26 21: 3:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtppop1.gte.net (smtppop1.gte.net [207.115.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 084E514F8E for ; Sun, 26 Dec 1999 21:02:31 -0800 (PST) (envelope-from roman.toledo@gte.net) Received: from lsanca1-ar5-219-032.dsl.gtei.net (lsanca1-ar5-219-032.dsl.gtei.net [4.33.219.32]) by smtppop1.gte.net with SMTP for ; id WAA4326284 Sun, 26 Dec 1999 22:59:58 -0600 (CST) From: roman.toledo@gte.net To: freebsd-hackers@freebsd.org Subject: subscribe Date: Sun, 26 Dec 1999 21:02:02 -0600 Message-ID: <7lld6sosqagldiv4d4kvp5k03r1h4aqm7m@4ax.com> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 4:48:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw-out.comptel.com (mgw-out.comptel.com [195.237.145.101]) by hub.freebsd.org (Postfix) with ESMTP id ACC5F14F68 for ; Mon, 27 Dec 1999 04:48:49 -0800 (PST) (envelope-from stefan.parvu@comptel.com) Received: from ctlfw1 ([195.237.145.97]) by mgw-out.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 27 Dec 1999 14:48:47 +0200 Received: from mgw-in.comptel.com ([192.102.20.150]) by ctlfw1.comptel.com; Mon, 27 Dec 1999 14:48:04 +0000 (EET) Received: from xf174 ([195.237.135.174]) by mgw-in.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 27 Dec 1999 14:48:46 +0200 Message-Id: <3.0.6.32.19991227144610.00965b80@miina.comptel.com> X-Sender: sparvu@miina.comptel.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 27 Dec 1999 14:46:10 -0800 To: Wilko Bulte , Kris Kennaway From: Stefan Parvu Subject: Re: Shrinking the BSD kernel Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19991223195946.B759@yedi.iaf.nl> References: <3.0.6.32.19991223145522.00948b70@miina.comptel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks, I will. At 07:59 PM 12/23/99 +0100, Wilko Bulte wrote: >On Thu, Dec 23, 1999 at 07:32:47AM -0800, Kris Kennaway wrote: >> On Thu, 23 Dec 1999, Stefan Parvu wrote: >> >> > Does anybody know real procedures, steps whatever to keep a small an >> > efficient kernel ? >> >> Don't include the stuff you don't need. This belongs on questions-, not >> hackers- > >Hm. I suggest to search the mailing list archives for picoBSD. This >is probably interesting reading in this context. > >-- >Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project > WWW : http://www.tcja.nl http://www.freebsd.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 6:49:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 79C3114F88 for ; Mon, 27 Dec 1999 06:49:24 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id PAA15244; Mon, 27 Dec 1999 15:45:49 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id OAA13813; Mon, 27 Dec 1999 14:55:07 +0100 (CET) Date: Mon, 27 Dec 1999 14:55:07 +0100 (CET) From: Juergen Lock Message-Id: <199912271355.OAA13813@saturn.kn-bremen.de> To: newton@internode.com.au Subject: Re: Serial boot prompt messages and a modem X-Newsgroups: local.list.freebsd.hackers In-Reply-To: <19991222133015.B13504@internode.com.au> References: <199912220138.RAA04766@mass.cdrom.com> Organization: home Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991222133015.B13504@internode.com.au> you write: >On Tue, Dec 21, 1999 at 05:38:35PM -0800, Mike Smith wrote: > > > > Hmm, last time I checked, they were just 'serial ports'. > > > > Nope. The significance is determined by the software, and you're stuck > > with the fact that the first serial port is the console port. End of > > story. (Note: if we don't make some assumption about which port will be > > the console, how do you expect the software to work out which one it > > "should" use?) > >Insist that consoles be cabled-in with "real" cables, and use the first >port we find with DCD asserted as the console, falling back to COM1 if >we can't find any ports with DCD (indicating that someone has failed to >follow our cabling insistence) Btw. I just came across a 'null modem cable' that connects DCD to: nothing! It connects DTR to DSR but _not_ to DCD... other than that the wiring appears to be normal. Well, so i hacked an `altpin' flag into sio that lets me swap the functions of DSR and DCD. (Anyone thinks that would be worth cleaning up and send-pr'ing?) And a happy new year to everyone... -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 9:16: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.erlangen.netsurf.de (erlangen.netsurf.de [194.163.170.1]) by hub.freebsd.org (Postfix) with ESMTP id EDD1014DEE for ; Mon, 27 Dec 1999 09:15:57 -0800 (PST) (envelope-from d_f0rce@gmx.de) Received: from blade (user-er-u1.erlangen.netsurf.de [194.163.170.161]) by mail.erlangen.netsurf.de (8.9.3/8.9.3) with SMTP id SAA69272 for ; Mon, 27 Dec 1999 18:15:53 +0100 (CET) Message-ID: <005101bf508e$1ab48700$0201a8c0@blade> From: "Steffen Merkel" To: Subject: Kernel threads Date: Mon, 27 Dec 1999 18:16:20 +0100 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, thanks for all your help on my previous posting. Meanwhile my thread-test works as I followed your instructions and included a sleep() call. But on experimenting on this topic I exchanged the sleep() call with a "while(1);" and had to see that the programm doesn't work any more. Why? I thougt POSIX threads would be kernel threads and therefor every thread gets a bit cpu time. Any ideas? Please answer to me directly as I'm not on the list. Stefen This programm was compiled with: gcc -pthread -o pthread pthread.c #include #include #include void print( void *ptr ){ char *string; string = (char *) ptr; fprintf(stderr,"String: %s\n",string); } void main(void){ pthread_t thread; char *string = "Hallo"; if( pthread_create( &thread, pthread_attr_default, (void *)&print, (void *) string ) != 0 ){ perror("pthread_create()"); exit(EXIT_FAILURE); } /* adding this, the programm doesn't work any more */ /* while(1); */ sleep(1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 9:35:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 2D6C415056 for ; Mon, 27 Dec 1999 09:35:06 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA24461; Mon, 27 Dec 1999 09:34:49 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 27 Dec 1999 09:34:49 -0800 Date: Mon, 27 Dec 1999 09:34:49 -0800 (PST) From: Kip Macy To: Steffen Merkel Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel threads In-Reply-To: <005101bf508e$1ab48700$0201a8c0@blade> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: d_f0rce@gmx.de,freebsd-hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The words "POSIX threads" only describes the API. It says nothing about the implementation. On FreeBSD they are non-preemptive user level threads (your main was never yielding so the thread you launched did not get any time). On Linux they are processes sharing the same virtual memory space, and are referred to as kernel threads. For compute bound activities you want kernel threads to spread the computation over multiple processors. For I/O bound activities you want user level threads so you can minimize the context switch overhead. I am sure Julian and the others have something a little bit better thought out to say but that is my two cents. -Kip > > But on experimenting on this topic I exchanged the sleep() call > with a "while(1);" and had to see that the programm doesn't work > any more. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 10:11:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 5638714E83 for ; Mon, 27 Dec 1999 10:11:01 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id MAA75089; Mon, 27 Dec 1999 12:09:31 -0600 (CST) (envelope-from dick) Date: Mon, 27 Dec 1999 12:09:31 -0600 From: "Richard Seaman, Jr." To: Kip Macy Cc: Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads Message-ID: <19991227120931.H5975@tar.com> References: <005101bf508e$1ab48700$0201a8c0@blade> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kip@lyris.com on Mon, Dec 27, 1999 at 09:34:49AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 09:34:49AM -0800, Kip Macy wrote: > The words "POSIX threads" only describes the API. It says nothing about > the implementation. On FreeBSD they are non-preemptive user level threads > (your main was never yielding so the thread you launched did not get any > time). Actually, FreeBSD user threads *are* pre-emptive. The problem is that a successful return from pthread_create guarantees that a thread is created, but not that it is started. The main thread exits before the second thread starts. Inserting a sleep allows the second thread to run. With just a while() the main thread completes before the second thread gets its time slice. As noted in a previous message, pthread_join() is intended for this kind of synchronization. > On Linux they are processes sharing the same virtual memory space, > and are referred to as kernel threads. For compute bound activities you > want kernel threads to spread the computation over multiple processors. Yes. As long as you have multiple processors. > For I/O bound activities you want user level threads so you can minimize > the context switch overhead. FreeBSD user threads have fairly high context switch overhead, especially when there are open fds that get polled on each context switch. Kernel threads are actually faster in many circumstances. The discussion in the -arch mailing list involves ideas which would make user threads much more efficient. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 10:31:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 1EA3D14DF5 for ; Mon, 27 Dec 1999 10:31:18 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id KAA24969; Mon, 27 Dec 1999 10:30:54 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 27 Dec 1999 10:30:54 -0800 Date: Mon, 27 Dec 1999 10:30:54 -0800 (PST) From: Kip Macy To: "Richard Seaman, Jr." Cc: Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads In-Reply-To: <19991227120931.H5975@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: dick@tar.com,d_f0rce@gmx.de,freebsd-hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG They may be preemptive, but I saw a lot of instances with Lyris where one thread could easily monopolize processor time at the expense of all others and I had to add sleeps in at places. > > FreeBSD user threads have fairly high context switch overhead, especially > when there are open fds that get polled on each context switch. Kernel > threads are actually faster in many circumstances. Not Linux threads. The linux threads implementation, as parts of its synchronization methods, disables interrupts. When Lyris previously used one thread for each connection, performance on FreeBSD was 20-30x that of Linux, and solaris was 30-40x that of Linux. Some simple benchmarking by a friend of mine at Berkeley indicated that Java using native threads on Linux was about 100x slower than using green threads. So maybe FreeBSD kernel threads will be better, but working with Linux's kernel threads has only made me dislike Linux more than I did previously. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 10:47:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 8AD2D14DF5 for ; Mon, 27 Dec 1999 10:47:40 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id MAA75223; Mon, 27 Dec 1999 12:47:29 -0600 (CST) (envelope-from dick) Date: Mon, 27 Dec 1999 12:47:29 -0600 From: "Richard Seaman, Jr." To: Kip Macy Cc: "Richard Seaman, Jr." , Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads Message-ID: <19991227124729.I5975@tar.com> References: <19991227120931.H5975@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kip@lyris.com on Mon, Dec 27, 1999 at 10:30:54AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 10:30:54AM -0800, Kip Macy wrote: > They may be preemptive, but I saw a lot of instances with Lyris where one > thread could easily monopolize processor time at the expense of all > others and I had to add sleeps in at places. Is this recently, or a while ago? FreeBSD user threads used to use SIGVTALRM for its pre-emption signal. This didn't count time in syscalls. So, if you had a syscall (eg I/O) intensive thread, it would hog processor time. I think that has been changed. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 10:51:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 70BED14FBD for ; Mon, 27 Dec 1999 10:51:16 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id KAA25219; Mon, 27 Dec 1999 10:50:56 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 27 Dec 1999 10:50:56 -0800 Date: Mon, 27 Dec 1999 10:50:56 -0800 (PST) From: Kip Macy To: "Richard Seaman, Jr." Cc: Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads In-Reply-To: <19991227124729.I5975@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: dick@tar.com,d_f0rce@gmx.de,freebsd-hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have not played with it for several months, so this may no longer be the case. -Kip > Is this recently, or a while ago? FreeBSD user threads used to use > SIGVTALRM for its pre-emption signal. This didn't count time in > syscalls. So, if you had a syscall (eg I/O) intensive thread, it > would hog processor time. I think that has been changed. > > -- > Richard Seaman, Jr. email: dick@tar.com > 5182 N. Maple Lane phone: 262-367-5450 > Chenequa WI 53058 fax: 262-367-5852 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 13: 1:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id A2D3014D74 for ; Mon, 27 Dec 1999 13:01:46 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA10296; Mon, 27 Dec 1999 16:01:28 -0500 (EST) Date: Mon, 27 Dec 1999 16:01:28 -0500 (EST) From: Daniel Eischen To: "Richard Seaman, Jr." Cc: Kip Macy , Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads In-Reply-To: <19991227124729.I5975@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Dec 1999, Richard Seaman, Jr. wrote: > On Mon, Dec 27, 1999 at 10:30:54AM -0800, Kip Macy wrote: > > They may be preemptive, but I saw a lot of instances with Lyris where one > > thread could easily monopolize processor time at the expense of all > > others and I had to add sleeps in at places. > > Is this recently, or a while ago? FreeBSD user threads used to use > SIGVTALRM for its pre-emption signal. This didn't count time in > syscalls. So, if you had a syscall (eg I/O) intensive thread, it > would hog processor time. I think that has been changed. Yes, we use SIGPROF now. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 20: 7:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 66A531539C for ; Mon, 27 Dec 1999 20:07:12 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA38152; Mon, 27 Dec 1999 21:07:10 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA58994; Mon, 27 Dec 1999 21:07:10 -0700 (MST) Message-Id: <199912280407.VAA58994@harmony.village.org> To: "John W. DeBoskey" Subject: Re: PCMCIA-ATA/USB support for SanDisk/Digital Cameras Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Dec 1999 21:48:14 EST." <199912230248.VAA28883@bb01f39.unx.sas.com> References: <199912230248.VAA28883@bb01f39.unx.sas.com> Date: Mon, 27 Dec 1999 21:07:10 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912230248.VAA28883@bb01f39.unx.sas.com> "John W. DeBoskey" writes: : Basically, it appears to be a combination of PCMCIA-ATA : support melded together with USB. : : Does anyone have any experience with this unit? Am I correct : that with USB support coming onboard in -current that it would : be feasible to get a driver working? No clue about the usb device, but there are patches floating about attempting to add pccard support to the ata device. For -stable there are lots of patches against wd which do support the ata devices. I suspect that there would need to be a usb attachment for the ata driver, which don't exist today (well as of dec 22), in order to use the card reader. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 27 20:11:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7590A153BB for ; Mon, 27 Dec 1999 20:11:44 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA38164; Mon, 27 Dec 1999 21:11:42 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA59018; Mon, 27 Dec 1999 21:11:40 -0700 (MST) Message-Id: <199912280411.VAA59018@harmony.village.org> To: "Daniel J. O'Connor" Subject: Re: PCMCIA-ATA/USB support for SanDisk/Digital Cameras Cc: "John W. DeBoskey" , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Dec 1999 21:11:33 +1030." References: Date: Mon, 27 Dec 1999 21:11:40 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Daniel J. O'Connor" writes: : You can get an adapter (infact I have one :) which turns a compact flash card : into a PCMCIA card.. It appears as an ATA HD. I *think* its possible for : FreeBSD to talk to it, but I haven't tried. There are patches that originated with PAO that work with the wd device. But that's one of the new bus casualties. I used a 48M and a 4M CF with the pcmcia adapter. Doug Ambrisko has some patches for the ata driver that I can't get working with my ata cards, so I'll be putting one in the mail to him tomorrow. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 1:44: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.erlangen.netsurf.de (erlangen.netsurf.de [194.163.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B6F5152EE for ; Tue, 28 Dec 1999 01:44:03 -0800 (PST) (envelope-from d_f0rce@gmx.de) Received: from blade (user-er-u1.erlangen.netsurf.de [194.163.170.161]) by mail.erlangen.netsurf.de (8.9.3/8.9.3) with SMTP id KAA91922; Tue, 28 Dec 1999 10:43:52 +0100 (CET) Message-ID: <001c01bf5118$1f4936a0$0201a8c0@blade> From: "Steffen Merkel" To: "Richard Seaman, Jr." Cc: References: <005101bf508e$1ab48700$0201a8c0@blade> <19991227120931.H5975@tar.com> Subject: Re: Kernel threads Date: Tue, 28 Dec 1999 10:44:19 +0100 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, > On Mon, Dec 27, 1999 at 09:34:49AM -0800, Kip Macy wrote: > > > The words "POSIX threads" only describes the API. It says nothing about > > the implementation. On FreeBSD they are non-preemptive user level threads > > (your main was never yielding so the thread you launched did not get any > > time). > > Actually, FreeBSD user threads *are* pre-emptive. The problem is that > a successful return from pthread_create guarantees that a thread is > created, but not that it is started. The main thread exits before > the second thread starts. Inserting a sleep allows the second thread > to run. With just a while() the main thread completes before the > second thread gets its time slice. As noted in a previous message, > pthread_join() is intended for this kind of synchronization. Sorry, but I'm learning C for only some weeks now. Why does the main thread complete if I insert a while(1); ? I thougt that this while statement would get executed forever (until I press ^C). > > On Linux they are processes sharing the same virtual memory space, > > and are referred to as kernel threads. For compute bound activities you > > want kernel threads to spread the computation over multiple processors. > > Yes. As long as you have multiple processors. > > > For I/O bound activities you want user level threads so you can minimize > > the context switch overhead. > > FreeBSD user threads have fairly high context switch overhead, especially > when there are open fds that get polled on each context switch. Kernel > threads are actually faster in many circumstances. The discussion in > the -arch mailing list involves ideas which would make user threads much > more efficient. How can I then tell FreeBSD that my threads shall be kernel threads? Steffen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 1:46:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.erlangen.netsurf.de (erlangen.netsurf.de [194.163.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 3F4B7153B6 for ; Tue, 28 Dec 1999 01:46:47 -0800 (PST) (envelope-from d_f0rce@gmx.de) Received: from blade (user-er-u1.erlangen.netsurf.de [194.163.170.161]) by mail.erlangen.netsurf.de (8.9.3/8.9.3) with SMTP id KAA92001; Tue, 28 Dec 1999 10:46:38 +0100 (CET) Message-ID: <002c01bf5118$84e701e0$0201a8c0@blade> From: "Steffen Merkel" To: "Kip Macy" Cc: References: Subject: Re: Kernel threads Date: Tue, 28 Dec 1999 10:47:06 +0100 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, From: Kip Macy To: Richard Seaman, Jr. > They may be preemptive, but I saw a lot of instances with Lyris where one > thread could easily monopolize processor time at the expense of all > others and I had to add sleeps in at places. Does this mean I've got to add sleeps in my threads to let other threads get cpu time? Is there no other possibility? Steffen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 6:30:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 57D4C1542C for ; Tue, 28 Dec 1999 06:30:18 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id IAA82998; Tue, 28 Dec 1999 08:30:08 -0600 (CST) (envelope-from dick) Date: Tue, 28 Dec 1999 08:30:08 -0600 From: "Richard Seaman, Jr." To: Steffen Merkel Cc: "Richard Seaman, Jr." , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads Message-ID: <19991228083008.A75539@tar.com> References: <005101bf508e$1ab48700$0201a8c0@blade> <19991227120931.H5975@tar.com> <001c01bf5118$1f4936a0$0201a8c0@blade> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <001c01bf5118$1f4936a0$0201a8c0@blade>; from d_f0rce@gmx.de on Tue, Dec 28, 1999 at 10:44:19AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 28, 1999 at 10:44:19AM +0100, Steffen Merkel wrote: > Sorry, but I'm learning C for only some weeks now. Why does the main > thread complete if I insert a while(1); ? I thougt that this while statement > would get executed forever (until I press ^C). You're right, of course. My brain was not fully in gear when I wrote that. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 9:11: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 8083315486 for ; Tue, 28 Dec 1999 09:11:03 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id LAA91273; Tue, 28 Dec 1999 11:10:58 -0600 (CST) (envelope-from dick) Date: Tue, 28 Dec 1999 11:10:58 -0600 From: "Richard Seaman, Jr." To: Steffen Merkel Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads Message-ID: <19991228111058.B75539@tar.com> References: <005101bf508e$1ab48700$0201a8c0@blade> <19991227120931.H5975@tar.com> <001c01bf5118$1f4936a0$0201a8c0@blade> <19991228083008.A75539@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991228083008.A75539@tar.com>; from dick@tar.com on Tue, Dec 28, 1999 at 08:30:08AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 28, 1999 at 08:30:08AM -0600, Richard Seaman, Jr. wrote: > On Tue, Dec 28, 1999 at 10:44:19AM +0100, Steffen Merkel wrote: > > > Sorry, but I'm learning C for only some weeks now. Why does the main > > thread complete if I insert a while(1); ? I thougt that this while statement > > would get executed forever (until I press ^C). > > You're right, of course. My brain was not fully in gear when I wrote that. BTW, I compiled your program with the while(1) included and it runs fine here. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 14:23:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 8D73714D9E for ; Tue, 28 Dec 1999 14:23:40 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id OAA03936; Tue, 28 Dec 1999 14:18:47 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 28 Dec 1999 14:18:47 -0800 Date: Tue, 28 Dec 1999 14:18:47 -0800 (PST) From: Kip Macy To: Steffen Merkel Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel threads In-Reply-To: <002c01bf5118$84e701e0$0201a8c0@blade> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: d_f0rce@gmx.de,freebsd-hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > They may be preemptive, but I saw a lot of instances with Lyris where one > > thread could easily monopolize processor time at the expense of all > > others and I had to add sleeps in at places. > > Does this mean I've got to add sleeps in my threads to let other threads get > cpu time? Is there no other possibility? > No, I was not correct. It turns out the behaviour I was observing was due to the use of SIGVTALARM which does not take system call time into acccount. They are now using SIGPROF which does. Sorry about the confusion. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 14:24:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 6543F1557B for ; Tue, 28 Dec 1999 14:24:30 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id OAA03952; Tue, 28 Dec 1999 14:20:47 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 28 Dec 1999 14:20:47 -0800 Date: Tue, 28 Dec 1999 14:20:47 -0800 (PST) From: Kip Macy To: "Richard Seaman, Jr." Cc: Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel threads In-Reply-To: <19991228111058.B75539@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: dick@tar.com,d_f0rce@gmx.de,freebsd-hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Dec 1999, Richard Seaman, Jr. wrote: > On Tue, Dec 28, 1999 at 08:30:08AM -0600, Richard Seaman, Jr. wrote: > > On Tue, Dec 28, 1999 at 10:44:19AM +0100, Steffen Merkel wrote: > > > > > Sorry, but I'm learning C for only some weeks now. Why does the main > > > thread complete if I insert a while(1); ? I thougt that this while statement > > > would get executed forever (until I press ^C). > > > > You're right, of course. My brain was not fully in gear when I wrote that. > > BTW, I compiled your program with the while(1) included and it runs fine > here. Newer version of the library perhaps? Just a thought. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 14:32:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 1A9311555C for ; Tue, 28 Dec 1999 14:32:20 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id OAA04043; Tue, 28 Dec 1999 14:32:05 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 28 Dec 1999 14:32:04 -0800 Date: Tue, 28 Dec 1999 14:32:04 -0800 (PST) From: Kip Macy To: Steffen Merkel Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel threads In-Reply-To: <001c01bf5118$1f4936a0$0201a8c0@blade> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: d_f0rce@gmx.de,freebsd-hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How can I then tell FreeBSD that my threads shall be kernel threads? > > > Steffen The only way I know of to do that is to use LinuxThreads which, because of my negative experience on Linux with threads, I have not tried. Try the archives. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 14:38: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eh.est.is (eh.est.is [194.144.208.34]) by hub.freebsd.org (Postfix) with ESMTP id D26CA14A2E for ; Tue, 28 Dec 1999 14:38:03 -0800 (PST) (envelope-from totii@est.is) Received: from toti.est.is (root@toti-mx.est.is [194.144.208.17]) by eh.est.is (8.8.8/8.8.8) with ESMTP id WAA16229 for ; Tue, 28 Dec 1999 22:21:21 GMT (envelope-from totii@est.is) Received: from est.is (asus.est.is [194.144.208.242]) by toti.est.is (8.9.3/8.9.1) with ESMTP id WAA72605 for ; Tue, 28 Dec 1999 22:20:55 GMT (envelope-from totii@est.is) Message-ID: <386937BD.66E787BD@est.is> Date: Tue, 28 Dec 1999 22:20:45 +0000 From: Thordur Ivarsson Reply-To: thivars@est.is X-Mailer: Mozilla 4.08 [en] (Win98; I) MIME-Version: 1.0 To: "freebsd-hackers@FreeBSD.ORG" Subject: Wireless Ethernet cards, development of driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I have here on my table Wireless ethernet card that I need driver for. The card is based on AMD 79C930VC chip and the maker is "MICRONET" from Taiwan. At AMD ftp site is lot of docs and utils for this chip (card??) and firmware in binary and .... bla bla bla for windows, BUT there are some lots of c++ sources as well. Has someone started writing driver for this card(chip) or am I alone here?? Can anybody help ?? Thordur Ivarsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 15:20:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 42B5214C36 for ; Tue, 28 Dec 1999 15:20:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA03381; Tue, 28 Dec 1999 15:25:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912282325.PAA03381@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kip Macy Cc: Steffen Merkel , freebsd-hackers@freebsd.org Subject: Re: Kernel threads In-reply-to: Your message of "Tue, 28 Dec 1999 14:32:04 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Dec 1999 15:25:46 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > How can I then tell FreeBSD that my threads shall be kernel threads? > > > > > > Steffen > The only way I know of to do that is to use LinuxThreads which, because of > my negative experience on Linux with threads, I have not tried. Try the > archives. Kip, if you have the time and energy, it would be _extremely_ interesting to us to know whether the 'linuxthreads' implementation on FreeBSD suffers from the same problems that it does under Linux for your application. I realise that there's a lot of work involved in testing this, but the upside is that it may result in FreeBSD becoming an even better platform for Lyris... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 16: 2: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 7DA1714A20 for ; Tue, 28 Dec 1999 16:01:57 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id SAA13138; Tue, 28 Dec 1999 18:01:53 -0600 (CST) (envelope-from dick) Date: Tue, 28 Dec 1999 18:01:53 -0600 From: "Richard Seaman, Jr." To: Jason Evans Cc: hackers@freebsd.org Subject: Cancellation points in Linuxthreads Message-ID: <19991228180153.B290@tar.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="YiEDa0DAkWCtVeE4" X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii The new version of linuxthreads now seems extend cancellation points into libc. However, it does so in a manner that threads can get cancelled within libc with libc holding internal locks, resulting in deadlock. I think the following example program demonstrates this. It works under libc_r, because libc_r carefully unwinds any internal locks created within libc. Linuxthreads does not have this capability, and the sample program deadlocks (at least it does here). -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="testcancel.c" #include #include #include #include #define BUFFSIZE 100000 int StateSet = 0; /* Use these to keep track of where we are. Can't use * printf's in the thread, since printf has become a * cancellation point. */ int ThreadReadStart = 0; int ThreadReadError = 0; int ThreadReadComplete = 0; int ThreadRewindComplete = 0; int ThreadRewindStart = 0; /* Install latest linuxthreads port and compile as: * compile as gcc -Wall -I/usr/local/include/pthread/linuxthreads -L/usr/local/lib -llthread -llgcc_r-o testcancel testcancel.c */ FILE *testfile; void * test_thread (void * arg) { char in; int oldstate; int oldtype; pthread_setcancelstate(PTHREAD_CANCEL_ENABLE, &oldstate); pthread_setcanceltype(PTHREAD_CANCEL_DEFERRED, &oldtype); StateSet = 1; /* Simple synchronization to allow main to cancel us */ sched_yield(); /* * main should have cancelled us by now. But since we're of type * DEFERRED, we only cancel at a cancellation point. */ ThreadRewindStart = 1; /* * It appears that rewind() has become a cancellation point. */ rewind (testfile); ThreadRewindComplete = 1; ThreadReadStart = 1; if (fread (&in, sizeof (in), 1, testfile) < 1) ThreadReadError = 1; else ThreadReadComplete = 1; return (NULL); } int main() { pthread_t th; char in; char *buffer; buffer = malloc (BUFFSIZE); memset (buffer, 'A', BUFFSIZE); testfile = fopen ("/tmp/testcancel", "w+"); if (testfile == NULL || fwrite (buffer, sizeof (*buffer), BUFFSIZE, testfile) < BUFFSIZE) exit(1); pthread_create(&th, NULL, test_thread, NULL); printf ("Thread created\n"); /* Simple syncronization to make sure the thread runs and sets its cancellation state */ if (StateSet == 0) sched_yield(); /* The thread's cancellation state and type should now be set */ printf ("Cancelling thread\n"); pthread_cancel (th); printf ("Thread cancelled\n"); /* Sleep to let the thread resume so it can do fread() */ sleep (2); printf ("Main thread sleep done\n"); printf ("ThreadRewindStart = %i\n", ThreadRewindStart); printf ("ThreadRewindComplete = %i\n", ThreadRewindComplete); printf ("ThreadReadStart = %i\n", ThreadReadStart); printf ("ThreadReadError = %i\n", ThreadReadError); printf ("ThreadReadComplete = %i\n", ThreadReadComplete); printf ("Starting rewind in main\n"); /* funlockfile (testfile); Doesn't help */ rewind (testfile); /* * We should get here. If we don't, its because the thread has * cancelled holding a lock in libc, so we're deadlocked. It's * ok for us to cancel a thread that holds a lock we created * (ok in the sense we're allowed to deadlock ourselves if we're * that stupid), but libc shouldn't silently do it to us. * * We can save ourselves by unlocking testfile, but we shouldn't have * to clean up after libc. However, even this doesn't work, since * funlockfile requires that we be the owner of the lock before we * can unlock it. */ printf ("Starting read in main\n"); if (fread (&in, sizeof (in), 1, testfile) < 1) printf ("fread error in main\n"); else printf ("fread completed in main\n"); fclose (testfile); return 0; } --YiEDa0DAkWCtVeE4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 16:16: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 195DB154E6; Tue, 28 Dec 1999 16:15:59 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA83669; Wed, 29 Dec 1999 10:45:50 +1030 (CST) Date: Wed, 29 Dec 1999 10:45:50 +1030 From: Greg Lehey To: "Xavier O'Neill" Cc: FreeBSD Questions Subject: Re: Signal 11 during setup Message-ID: <19991229104550.R1316@freebie.lemis.com> References: <19991225104026.46233.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991225104026.46233.qmail@hotmail.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to -questions; the lack of response on -hackers is understandable] On Saturday, 25 December 1999 at 2:40:25 -0800, Xavier O'Neill wrote: > Hello, > > I presently have FreeBSD 2.2.8 on my system. I downloaded FreeBSD 3.4 > Release and made two floppy images on newly formated floppies (did it > twice). During setup on the mfsroot.flp > > I get a signal 11 error (Signal 11 error, I am saving what I can. ). > >> From there the computer restarts. > > I did all kinds of trouble shooting and diagnostics as described by the > sig11 FAQ link i seen on the FreeBSD site. > > I went to a holographic terminal to see the debugging, this error always > happens as the /etc/fstab is being written. Before installing a new release of FreeBSD, read the errata, which may contain important information. For 3.4, you'll find it at http://www.freebsd.org/releases/3.4R/errata.html. There you will read: As shipped, the "Custom" installation option in 3.4 is broken. Fix: Both the "Novice" and "Express" install paths still work and can be used just as effectively (if not succinctly). Alternately, you can invoke the custom installation from the "Index" menu (Installation, Custom) or you can download a fixed mfsroot.flp floppy image (or boot.flp if you need 2.88MB boot media) from the floppies/updates/ directory under: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/3.4-RELEASE/ The 3.4 ISO installation image is also updated to contain a fix for this errata item. It's difficult to say whether this applies to you, since you didn't describe what you did, but there's a good chance this is what happened. If not, please describe what you did and when it happened. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 17:22: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 3CE7E1557C for ; Tue, 28 Dec 1999 17:22:01 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 76597 invoked by uid 1001); 29 Dec 1999 01:19:16 -0000 Date: Tue, 28 Dec 1999 17:19:16 -0800 From: Jason Evans To: "Richard Seaman, Jr." Cc: hackers@freebsd.org Subject: Re: Cancellation points in Linuxthreads Message-ID: <19991228171916.T39990@sturm.canonware.com> References: <19991228180153.B290@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991228180153.B290@tar.com>; from dick@tar.com on Tue, Dec 28, 1999 at 06:01:53PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 28, 1999 at 06:01:53PM -0600, Richard Seaman, Jr. wrote: > The new version of linuxthreads now seems extend cancellation points > into libc. However, it does so in a manner that threads can get > cancelled within libc with libc holding internal locks, resulting > in deadlock. > > I think the following example program demonstrates this. It works > under libc_r, because libc_r carefully unwinds any internal locks > created within libc. Linuxthreads does not have this capability, > and the sample program deadlocks (at least it does here). It probably isn't currently reasonable to do cancellation points correctly, partially correctly, or even partially, without causing the deadlocks that you point out. I knew that the cancellation points were extended into libc, but it didn't occur to me that it would cause the deadlocks. I'm inclined to completely remove the cancellation points from the linuxthreads port until we have better support available in libc. Any objections? It's clear that we need to add additional entry points to libc in order to support cancellation points, as well as to allow creation of a real libpthread, rather than libc_r. This is getting close to the top of my priority list now, but my experience in such things is limited, so it will be quite a learning experience. In other words, it could take me a long while, and if any more knowledgeable person would like to take this job, I wouldn't complain. =) Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 18:15:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id BC3371554C for ; Tue, 28 Dec 1999 18:15:14 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id UAA13496; Tue, 28 Dec 1999 20:15:09 -0600 (CST) (envelope-from dick) Date: Tue, 28 Dec 1999 20:15:09 -0600 From: "Richard Seaman, Jr." To: Jason Evans Cc: "Richard Seaman, Jr." , hackers@FreeBSD.ORG Subject: Re: Cancellation points in Linuxthreads Message-ID: <19991228201509.C290@tar.com> References: <19991228180153.B290@tar.com> <19991228171916.T39990@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991228171916.T39990@sturm.canonware.com>; from jasone@canonware.com on Tue, Dec 28, 1999 at 05:19:16PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 28, 1999 at 05:19:16PM -0800, Jason Evans wrote: > It probably isn't currently reasonable to do cancellation points correctly, > partially correctly, or even partially, without causing the deadlocks that > you point out. I knew that the cancellation points were extended into > libc, but it didn't occur to me that it would cause the deadlocks. I'm > inclined to completely remove the cancellation points from the linuxthreads > port until we have better support available in libc. Any objections? There is no good solution. But, removing the libc cancellation points is, IMO, the best of a set of bad choices. This is what the older linuxthreads port did. > It's clear that we need to add additional entry points to libc in order to > support cancellation points, as well as to allow creation of a real > libpthread, rather than libc_r. This is getting close to the top of my > priority list now, but my experience in such things is limited, so it will > be quite a learning experience. In other words, it could take me a long > while, and if any more knowledgeable person would like to take this job, I > wouldn't complain. =) I'm not volunteering. But, I promised you some thoughts on how to do it, which I still owe you. I don't think its "hard", just tedious. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 28 21:45: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 04D0114D58 for ; Tue, 28 Dec 1999 21:45:00 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id AAA09438; Wed, 29 Dec 1999 00:44:45 -0500 (EST) Date: Wed, 29 Dec 1999 00:44:45 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: thivars@est.is Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: Wireless Ethernet cards, development of driver In-Reply-To: <386937BD.66E787BD@est.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Dec 1999, Thordur Ivarsson wrote: > Hi there, > > I have here on my table Wireless ethernet card that I need driver for. > > The card is based on AMD 79C930VC chip and the maker is "MICRONET" from > Taiwan. > > At AMD ftp site is lot of docs and utils for this chip (card??) and > firmware in binary and .... bla bla bla for windows, BUT there are some > lots of c++ sources as well. > > > Has someone started writing driver for this card(chip) or am I alone > here?? > > > Can anybody help ?? > > Thordur Ivarsson > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > See http://www.posi.net/freebsd/drivers/ Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 0:16:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from guppy.vub.ac.be (guppy.vub.ac.be [134.184.129.2]) by hub.freebsd.org (Postfix) with ESMTP id EA1D814E60 for ; Wed, 29 Dec 1999 00:16:45 -0800 (PST) (envelope-from jdrabbe@ulb.ac.be) Received: from mach.vub.ac.be (mach.vub.ac.be [134.184.129.3]) by guppy.vub.ac.be (8.9.1b+Sun/3.17.0.ap (guppy)) id JAA00718; Wed, 29 Dec 1999 09:15:52 +0100 (MET) for Received: from www.ulb.ac.be (resu1.ulb.ac.be [164.15.59.200]) by mach.vub.ac.be (8.9.3/%I%.1.ap (mach.test)) id JAA19469; Wed, 29 Dec 1999 09:16:37 +0100 (MET) for hackers@FreeBSD.ORG Date: Wed, 29 Dec 1999 09:16:37 +0100 (MET) From: jdrabbe@ulb.ac.be (Drabbe Jean) Message-Id: <199912290816.JAA19469@mach.vub.ac.be> To: hackers@FreeBSD.ORG X-Mailer: Webmail ULB v1.42 X-Sender: jdrabbe@pop.ulb.ac.be Subject: unsubscribe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please, remove my name from your mailing lists. Thank you. Jean Drabbe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 4:33:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DC6A614A07 for ; Wed, 29 Dec 1999 04:33:30 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 123IIC-0004g1-00 for hackers@freebsd.org; Wed, 29 Dec 1999 14:33:28 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Re: SIGFPE on arithmetic overflow In-reply-to: Your message of "Fri, 24 Dec 1999 12:49:41 +0100." <19991224124941.A88203@cons.org> Date: Wed, 29 Dec 1999 14:33:28 +0200 Message-ID: <17980.946470808@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just wanted to say thanks to those who responded to my questions on the topic of SIGFPE and X_INV vs X_OFL. I found the answers most helpful, especially the references to Bruce's mail in the archives. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 6:50: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 5DD1B14A1B; Wed, 29 Dec 1999 06:49:46 -0800 (PST) From: "Jonathan M. Bresler" To: jdrabbe@ulb.ac.be Cc: hackers@FreeBSD.ORG In-reply-to: <199912290816.JAA19469@mach.vub.ac.be> (jdrabbe@ulb.ac.be) Subject: Re: unsubscribe Message-Id: <19991229144946.5DD1B14A1B@hub.freebsd.org> Date: Wed, 29 Dec 1999 06:49:46 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you were subscribed to only one list "freebsd-hackers-digest". i have removed you from that list. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 8:53: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 2027E14F78 for ; Wed, 29 Dec 1999 08:53:04 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id JAA04197 for ; Wed, 29 Dec 1999 09:53:03 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA19499; Wed, 29 Dec 1999 09:53:02 -0700 Date: Wed, 29 Dec 1999 09:53:02 -0700 Message-Id: <199912291653.JAA19499@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@Freebsd.org Subject: Buying a cheap server system X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to remember someone else asking about this a couple weeks back. Does anyone know a good place to go to buy a cheap server system? This is a sit-in-the-corner box that is a compute-processor and a very lightly loaded WWW server, similar to what freefall does. I'd like to spend around $500-600, but may spend more if I don't have to build it myself? Any help you can provide would be much appreciated. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 10: 3:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 5DD90151F8; Wed, 29 Dec 1999 10:03:20 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991229180316.RCR9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 10:03:16 -0800 Message-ID: <386A4CEC.EB948EE8@home.com> Date: Wed, 29 Dec 1999 13:03:24 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14pre17 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Temperature Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a strange problem. I run Linux stable/development kernels and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines temperatures have always been in this range with either system: 87F CPU #0 87F CPU #1 95F Case Temp Sometime last week or early this week the temperature under FreeBSD only has changed to: 113F CPU #0 113F CPU #1 109F Case Temp This is right after boot and varies 3-4 Degrees + while running. During the night periodically my temp warning has been going off. I have it set to 118F. This happens only under FreeBSD. Linux continues to run cool at the old temperatures. Apparantly some code change has caused this. Does anyone know exactly where I should look? Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 10:12:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id 24D4F1519E; Wed, 29 Dec 1999 10:12:21 -0800 (PST) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.3/8.9.2) with ESMTP id NAA11517; Wed, 29 Dec 1999 13:12:12 -0500 (EST) Date: Wed, 29 Dec 1999 13:12:12 -0500 (EST) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <386A4CEC.EB948EE8@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're referring to the temps reported via an LM78 or similar, yes? And not reporting that the machine is actually getting HOTTER under FreeBSD? -marc ------------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000x11 fax: 416.979.8223 cell: 416.346.9255 On Wed, 29 Dec 1999, Ted Sikora wrote: > Here's a strange problem. I run Linux stable/development kernels > and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines > temperatures have always been in this range with either system: > > 87F CPU #0 > 87F CPU #1 > 95F Case Temp > > Sometime last week or early this week the temperature under FreeBSD only > has changed to: > > 113F CPU #0 > 113F CPU #1 > 109F Case Temp > This is right after boot and varies 3-4 Degrees + while running. > > During the night periodically my temp warning has been going off. > I have it set to 118F. This happens only under FreeBSD. Linux continues > to run cool at the old temperatures. Apparantly some code change has > caused this. Does anyone know exactly where I should look? > > Regards, > -- > Ted Sikora > Jtl Development Group > tsikora@powerusersbbs.com > http://powerusersbbs.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 11:15:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 0D37114F14; Wed, 29 Dec 1999 11:15:23 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 17D671CA0; Thu, 30 Dec 1999 03:15:16 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: Message from Ted Sikora of "Wed, 29 Dec 1999 13:03:24 EST." <386A4CEC.EB948EE8@home.com> Date: Thu, 30 Dec 1999 03:15:16 +0800 From: Peter Wemm Message-Id: <19991229191516.17D671CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > During the night periodically my temp warning has been going off. > I have it set to 118F. This happens only under FreeBSD. Linux continues > to run cool at the old temperatures. Apparantly some code change has > caused this. Does anyone know exactly where I should look? The main difference is that Linux halts the cpu in the idle loop, we don't. As a result the cpu is in a tight spin waiting for a process to become scheduleable. I have some patches half-done that I've been working on for 4.0 that should probably be able to be adapted to the 3.x series. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 12: 9: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.erlangen.netsurf.de (erlangen.netsurf.de [194.163.170.1]) by hub.freebsd.org (Postfix) with ESMTP id E122214DA2 for ; Wed, 29 Dec 1999 12:08:58 -0800 (PST) (envelope-from d_f0rce@gmx.de) Received: from blade (user-er-u1.erlangen.netsurf.de [194.163.170.161]) by mail.erlangen.netsurf.de (8.9.3/8.9.3) with SMTP id VAA41499 for ; Wed, 29 Dec 1999 21:08:51 +0100 (CET) Message-ID: <000701bf5238$9918aa80$0201a8c0@blade> From: "Steffen Merkel" To: Subject: Sorry, but another thread problem! Date: Wed, 29 Dec 1999 21:09:20 +0100 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, first let me thank all of you for all your great help and the dozens of responses I got. Unfortunately I have a very strange problem in a multithreaded programm I'm writing now. I want to write a programm which checks if a server is up by pinging it. I looks like that: ###################################### main(){ readconfig() for (every server){ pthread_create(..... startscan() ); } while(1){ sleep(1); printf("Main Awake again\n"); } } startscan(){ ping(server); printf("Going to sleep\n"); sleep(1); printf("Awake again!"); } ######################################## I can see that the servers are getting pinged and that every thread goes to sleep. As soon as every thread did it's job and the first thread should awake the program get's a SIGSEGV. I can't see the message "Awake again" from the first thread but I saw that the first thread started to sleep and the last thread finished too and the main thread printed "Awake again!". Well with my little knowledge of C I would say that there is a problem with the sleep function. But as soon as I remove the ping() function the programm operates normally and runs forever. Can anyone tell me how I can debug such a problem? A program which seems to crash because of function which doesn't get executed at crash time. Meanwhile I'm going mad with those threads because the program worked fine using fork(). Unfortunately it takes too much ram to fork a process for every server. That's the reason I want to use threads. Steffen PS: Sorry that I have to bother you again with my incompetence. Please reply directly to me because I'm not on the list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 12:13:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id DB69E151D1 for ; Wed, 29 Dec 1999 12:13:56 -0800 (PST) (envelope-from ken@bolingbroke.com) Received: from localhost (ken@localhost) by fremont.bolingbroke.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id MAA65153; Wed, 29 Dec 1999 12:13:52 -0800 (PST) Date: Wed, 29 Dec 1999 12:13:52 -0800 (PST) From: Ken Bolingbroke X-Sender: ken@fremont.bolingbroke.com To: Steffen Merkel Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Sorry, but another thread problem! In-Reply-To: <000701bf5238$9918aa80$0201a8c0@blade> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From my own experience, altho I'm not that skilled a programmer, sleep() is not thread-safe. I believe sleep() sets a global SIGALARM, which is reset by every thread that calls it, and thus only the last one ever returns. Replacing sleep() with nanosleep() or something else that is thread-safe should solve that problem. Ken Bolingbroke hacker@bolingbroke.com On Wed, 29 Dec 1999, Steffen Merkel wrote: > Hello, > > first let me thank all of you for all your great help and the dozens > of responses I got. > Unfortunately I have a very strange problem in a multithreaded > programm I'm writing now. I want to write a programm which > checks if a server is up by pinging it. I looks like that: > > ###################################### > main(){ > readconfig() > > for (every server){ pthread_create(..... startscan() ); } > > while(1){ > sleep(1); > printf("Main Awake again\n"); > } > } > > startscan(){ > ping(server); > printf("Going to sleep\n"); > sleep(1); > printf("Awake again!"); > } > ######################################## > > I can see that the servers are getting pinged and that every > thread goes to sleep. As soon as every thread did it's job and > the first thread should awake the program get's a SIGSEGV. > I can't see the message "Awake again" from the first thread but > I saw that the first thread started to sleep and the last thread > finished too and the main thread printed "Awake again!". > Well with my little knowledge of C I would say that there is a > problem with the sleep function. But as soon as I remove the > ping() function the programm operates normally and runs forever. > > Can anyone tell me how I can debug such a problem? A program > which seems to crash because of function which doesn't get executed > at crash time. > > Meanwhile I'm going mad with those threads because the program > worked fine using fork(). Unfortunately it takes too much ram to > fork a process for every server. That's the reason I want to use > threads. > > Steffen > > PS: Sorry that I have to bother you again with my incompetence. > > Please reply directly to me because I'm not on the list. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 14: 7:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 31F2415102 for ; Wed, 29 Dec 1999 14:07:45 -0800 (PST) (envelope-from root@virtual-voodoo.com) Received: (from root@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id RAA67250 for freebsd-hackers@freebsd.org; Wed, 29 Dec 1999 17:07:53 -0500 (EST) (envelope-from root) Date: Wed, 29 Dec 1999 17:07:53 -0500 (EST) From: Charlie Root Message-Id: <199912292207.RAA67250@virtual-voodoo.com> To: freebsd-hackers@freebsd.org Subject: gcc command line ordering question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a tiny little snippit of code here (test.c): char ldap_init(); int main(int argc, char **argv) { ldap_init(); return 0; } I expect (want) a runtime error but I do expect it to compile when linked with the openldap libraries. Here's my quandery: vv# gcc -L/usr/local/lib -I/usr/local/include -lldap -llber test.c /tmp/ccj67244.o: In function `main': /tmp/ccj67244.o(.text+0x7): undefined reference to `ldap_init' Very odd... but if I changed the ordering of the arguments: vv# gcc -L/usr/local/lib -I/usr/local/include test.c -lldap -llber vv# It compiles fine. I thought gcc proccessed files in the order in which they appeard? I further thought that the only difference between specifying a fullname and using -l was that -l surrounding the name with lib*.a and searched multiple directories. If thats all true why would the ordering matter here? -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 15: 9:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 8223215725 for ; Wed, 29 Dec 1999 15:09:19 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 41091 invoked by uid 1001); 29 Dec 1999 23:09:18 -0000 Date: 29 Dec 1999 15:09:18 -0800 Date: Wed, 29 Dec 1999 15:09:18 -0800 From: Bill Swingle To: multimedia@freebsd.org Cc: hackers@freebsd.org Subject: soundcards needed to further newpcm development Message-ID: <19991229150918.A39443@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, In an attempt to help Cameron get newpcm to support widest array of soundcards available we're trying to collect as many as possible for testing and development. Below is a list of chipsets that we're still lacking. If you have any cards that have these chips on them, and would like to see support for them added or improved please consider sending them to us. Due to the sheer number of cards we'll be handling and the fact that they'll end up in the UK in the end, these cards will have to be donations to the project or indefinate loans at least. If you have a card you'd like to donate please send me some email and then send the card to: Cameron Grant c/o Bill Swingle Walnut Creek CDROM 4041 Pike Ln #F Concord, CA, 94520 If you have any questions at all please feel free to email me. Thanks! -Bill chip have board have docs supported ------------------------------------------------------------------------- ad1816 no yes yes ad1819a no yes no ad1845 no no yes ad1847 no yes no ad1849 no yes no aureal vortex 8810 no no no aureal vortex 8830 no no no cmi8330 no yes yes cmi8338 no yes no creative sb no yes yes creative sbpro no yes yes cs4231 no no yes cs4231a no yes yes cs4232 no no yes cs4232a no no yes cs4235 no yes yes cs4236 no no yes cs4236b no yes yes cs4237 no no yes cs4237b no yes no cs4238b no yes no cs4239 no yes no cs4280 no no yes cs4281 no no yes cs4610 no yes yes cs4611 no no yes cs4614 no yes yes cs4615 no no yes cs4622 no no yes cs4624 no no yes ensoniq es1370 no yes yes ess488 no no yes ess688 no yes yes ess1688 no no yes ess1788 no no no ess1868 no yes yes ess1869 no yes yes ess1878 no yes no ess1879 no yes yes ess1887 no no no ess1888 no no yes ess1938 solo-1 no yes no ess1946 solo-1e no yes no ess maestro-1 no yes no ess maestro-2 no yes no ess maestro-2em no yes no ess maestro-2e no yes no forte-media fm801 no yes no gravis ultrasound no no no gravis ultrasound max no no no gravis ultrasound pnp no no yes gravis ultrasound ace no no no intel i810 no no no intel i810e no no no intel i820 no no no neomagic 256av no yes no neomagic 256zx no yes no opti925 no no yes opti931 no no yes s3 sonicvibes no yes no trident 4d wave nx no yes yes via 82c686 no no no yamaha ymf711 no yes ? yamaha ymf715 no yes ? yamaha ymf719 no no ? yamaha ymf721 no yes ? yamaha ymf740 no no no yamaha ymf744 no no no yamaha ymf754 no no no -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 15:20:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 72164151E9; Wed, 29 Dec 1999 15:20:18 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-208-170-118-224.dialup.HiWAAY.net [208.170.118.224]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id RAA19459; Wed, 29 Dec 1999 17:20:15 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id RAA38266; Wed, 29 Dec 1999 17:20:12 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199912292320.RAA38266@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Wemm Cc: tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" From: David Kelly Subject: Re: Temperature In-reply-to: Message from Peter Wemm of "Thu, 30 Dec 1999 03:15:16 +0800." <19991229191516.17D671CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 17:20:12 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: > Ted Sikora wrote: > > > During the night periodically my temp warning has been going off. > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > to run cool at the old temperatures. Apparantly some code change has > > caused this. Does anyone know exactly where I should look? > > The main difference is that Linux halts the cpu in the idle loop, we don't. > As a result the cpu is in a tight spin waiting for a process to become > scheduleable. I have some patches half-done that I've been working on for > 4.0 that should probably be able to be adapted to the 3.x series. I'll let others debate whether or not FreeBSD halts the CPU when idle or not, or whether this has changed recently. OTOH Ted has a problem that is being ignored: that his CPU/Heatsink/Fan combination is apparently not up to a 100% duty cycle. DOS would cook it. As would most games. Or several "make buildworlds" in a row. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 15:45:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id F08E514D7B; Wed, 29 Dec 1999 15:45:39 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2123.bossig.com [208.26.242.123]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.5) with ESMTP id ; Wed, 29 Dec 1999 15:52:46 -0800 Message-ID: <386A9D29.C7F0390D@3-cities.com> Date: Wed, 29 Dec 1999 15:45:45 -0800 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: David Kelly Cc: Peter Wemm , tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature References: <199912292320.RAA38266@nospam.hiwaay.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Kelly wrote: > > Peter Wemm writes: > > Ted Sikora wrote: > > > > > During the night periodically my temp warning has been going off. > > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > > to run cool at the old temperatures. Apparantly some code change has > > > caused this. Does anyone know exactly where I should look? > > > > The main difference is that Linux halts the cpu in the idle loop, we don't. > > As a result the cpu is in a tight spin waiting for a process to become > > scheduleable. I have some patches half-done that I've been working on for > > 4.0 that should probably be able to be adapted to the 3.x series. > > I'll let others debate whether or not FreeBSD halts the CPU when idle > or not, or whether this has changed recently. > > OTOH Ted has a problem that is being ignored: that his CPU/Heatsink/Fan > combination is apparently not up to a 100% duty cycle. DOS would cook > it. As would most games. Or several "make buildworlds" in a row. Antec and Startech have some dual fans for P-II's. The old P-II style is hard to find but the K-7 Athalon apparently uses the same style of fan. One of the vendors has a monster fan for a P-III. I run setiathome in the background on all of my computers, which keeps the systems at 100% all of the time. I had a new 250W PS go out in three days. The fans that come on P-II OEM's is not that great. It also sounds like he isn't getting enough outside air. You can't cool if the inside air is hot. Kent > > -- > David Kelly N4HHE, dkelly@hiwaay.net > ===================================================================== > The human mind ordinarily operates at only ten percent of its > capacity -- the rest is overhead for the operating system. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 16:36: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id ED7C21508D for ; Wed, 29 Dec 1999 16:36:03 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id SAA19305; Wed, 29 Dec 1999 18:35:56 -0600 (CST) (envelope-from dan) Date: Wed, 29 Dec 1999 18:35:56 -0600 From: Dan Nelson To: Charlie Root Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gcc command line ordering question Message-ID: <19991229183556.A19230@dan.emsphone.com> References: <199912292207.RAA67250@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912292207.RAA67250@virtual-voodoo.com>; from "Charlie Root" on Wed Dec 29 17:07:53 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 29), Charlie Root said: > I expect (want) a runtime error but I do expect it to compile when > linked with the openldap libraries. Here's my quandery: > > vv# gcc -L/usr/local/lib -I/usr/local/include -lldap -llber test.c > /tmp/ccj67244.o: In function `main': > /tmp/ccj67244.o(.text+0x7): undefined reference to `ldap_init' > > Very odd... but if I changed the ordering of the arguments: > > vv# gcc -L/usr/local/lib -I/usr/local/include test.c -lldap -llber > vv# > > It compiles fine. I thought gcc proccessed files in the order in which > they appeard? I further thought that the only difference between > specifying a fullname and using -l was that -l surrounding the name > with lib*.a and searched multiple directories. If thats all true why > would the ordering matter here? -l specifies libraries. Libraries are special in that symbols are only used when *needed*. Your "-lldap -llber test.c" basically was a no-op for the libraries, since there were no unresolved symbols until "test.o" got linked in and asked for "ldap_init". But by that time it was too late. Moving the libs to the end of the commandline lets them resolve the "ldap_init" symbol. This is why you always see libraries at the *end* of commandlines :) -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 16:39:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6288014F67 for ; Wed, 29 Dec 1999 16:39:08 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA00627; Thu, 30 Dec 1999 11:08:58 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 30 Dec 1999 11:08:57 +1030 (CST) From: "Daniel O'Connor" To: Ken Bolingbroke Subject: Re: Sorry, but another thread problem! Cc: freebsd-hackers@FreeBSD.ORG, Steffen Merkel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Dec-99 Ken Bolingbroke wrote: > From my own experience, altho I'm not that skilled a programmer, > sleep() > is not thread-safe. I believe sleep() sets a global SIGALARM, which > is > reset by every thread that calls it, and thus only the last one ever > returns. Replacing sleep() with nanosleep() or something else that > is > thread-safe should solve that problem. Stupid question time.. If that is so why doesn't sleep just use nanosleep? :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 16:43:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 03F4914C9A for ; Wed, 29 Dec 1999 16:43:55 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 123TgI-000EJG-00; Thu, 30 Dec 1999 00:43:06 +0000 Date: Thu, 30 Dec 1999 00:43:06 +0000 From: Ben Smithurst To: Daniel O'Connor Cc: Ken Bolingbroke , freebsd-hackers@FreeBSD.ORG, Steffen Merkel Subject: Re: Sorry, but another thread problem! Message-ID: <19991230004306.B52554@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > On 29-Dec-99 Ken Bolingbroke wrote: >> From my own experience, altho I'm not that skilled a programmer, >> sleep() >> is not thread-safe. I believe sleep() sets a global SIGALARM, which >> is >> reset by every thread that calls it, and thus only the last one ever >> returns. Replacing sleep() with nanosleep() or something else that >> is >> thread-safe should solve that problem. > > Stupid question time.. > > If that is so why doesn't sleep just use nanosleep? :) It does in FreeBSD. UTSL. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 18:53:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id BC1DD1509C; Wed, 29 Dec 1999 18:53:29 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123ViT-000AZ1-00; Wed, 29 Dec 1999 18:53:29 -0800 Date: Wed, 29 Dec 1999 18:53:24 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: softupdates and debug.max_softdeps Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to find some information on reasonable settings for debug.max_softdeps on a recent FreeBSD-stable system. It seems that if you have a machine that is able to generate disk IO much faster than can be handled, has a large amount of RAM (and therefore debug.max_softdeps is large), and the filesystem is very large (about 80GB), filesystem metadata updates can get _very_ far behind. For instance, on a test system running 4 instances of postmark continuously for 24 hours, "df" reports that 40 GB of disk space is being used, even though only about 5 GB is actually used. If I kill the postmark processes, the metadata is eventually dribbled out and "df" reports 5GB in use. It takes about 20 minutes for the metadata to be updated on a completely ideal system. On this particular system, it doesn't seem to stabilize either. If the 4 postmark instances are allowed to run, disk usage seems to climb indefinitely (at 40GB it was still climbing), until eventually the machine silently reboots. debug.max_softdeps is by default set to 523,712 (1 GB of RAM). Is that a resonable value? I see some tests in the docs with max_softdeps set to 4000 or so. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 20: 4: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 5924F150D9; Wed, 29 Dec 1999 20:04:05 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230040404.GDZR9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 20:04:04 -0800 Message-ID: <386AD9BC.37852615@home.com> Date: Wed, 29 Dec 1999 23:04:12 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Kent Stewart Cc: "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature References: <199912292320.RAA38266@nospam.hiwaay.net> <386A9D29.C7F0390D@3-cities.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart wrote: > > David Kelly wrote: > > > > Peter Wemm writes: > > > Ted Sikora wrote: > > > > > > > During the night periodically my temp warning has been going off. > > > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > > > to run cool at the old temperatures. Apparantly some code change has > > > > caused this. Does anyone know exactly where I should look? > > > > > > The main difference is that Linux halts the cpu in the idle loop, we don't. > > > As a result the cpu is in a tight spin waiting for a process to become > > > scheduleable. I have some patches half-done that I've been working on for > > > 4.0 that should probably be able to be adapted to the 3.x series. > > > > I'll let others debate whether or not FreeBSD halts the CPU when idle > > or not, or whether this has changed recently. > > > > OTOH Ted has a problem that is being ignored: that his CPU/Heatsink/Fan > > combination is apparently not up to a 100% duty cycle. DOS would cook > > it. As would most games. Or several "make buildworlds" in a row. No this is right after bootup. It started right after I did a make world around Christmas or coinciding with 3.4-STABLE. It runs 26 degrees hotter right from the get go. Linux still runs cool like always. FreeBSD used to be exactly the same. I have a SMP board with 2 CPU's. > > Antec and Startech have some dual fans for P-II's. The old P-II style > is hard to find but the K-7 Athalon apparently uses the same style of > fan. One of the vendors has a monster fan for a P-III. > > I run setiathome in the background on all of my computers, which keeps > the systems at 100% all of the time. I had a new 250W PS go out in > three days. The fans that come on P-II OEM's is not that great. > > It also sounds like he isn't getting enough outside air. You can't > cool if the inside air is hot. It runs at 87F on both CPU's and a 95F case temp under Linux regardless of load maybe varies 3-4 degrees +-. It's extremely cool. FreeBSD was just like that till I did a makeworld right around or after Christmas then this started. FreeBSD runs 26F degrees hotter right after bootup with nothing. Booting back to Linux it reverts back to the old temps...cool. It's just FreeBSD. Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 20: 7:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id E303215185; Wed, 29 Dec 1999 20:07:12 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230040700.GEOR9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 20:07:00 -0800 Message-ID: <386ADA6B.5D0CEAB2@home.com> Date: Wed, 29 Dec 1999 23:07:07 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Marc Nicholas Cc: "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Nicholas wrote: > > You're referring to the temps reported via an LM78 or similar, yes? The machines bios with Winbond W83782d IC > not reporting that the machine is actually getting HOTTER under FreeBSD? It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F hotter under FreeBSD than under Linux. Sometime after 3.4-RC and now this started. (I follow the stable branch via CVSup) Under 3.3-STABLE the temerature was always the same as Linux...cool averaging 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's wierd but the machine does not lie. Under Linux it's the same as before 87-89F. > > On Wed, 29 Dec 1999, Ted Sikora wrote: > > > Here's a strange problem. I run Linux stable/development kernels > > and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines > > temperatures have always been in this range with either system: > > > > 87F CPU #0 > > 87F CPU #1 > > 95F Case Temp > > > > Sometime last week or early this week the temperature under FreeBSD only > > has changed to: > > > > 113F CPU #0 > > 113F CPU #1 > > 109F Case Temp > > This is right after boot and varies 3-4 Degrees + while running. > > > > During the night periodically my temp warning has been going off. > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > to run cool at the old temperatures. Apparantly some code change has > > caused this. Does anyone know exactly where I should look? -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 20:12:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id E811014D45; Wed, 29 Dec 1999 20:12:25 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id C11F39B4F; Wed, 29 Dec 1999 23:12:21 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id B784ABA0C; Wed, 29 Dec 1999 23:12:21 -0500 (EST) Date: Wed, 29 Dec 1999 23:12:21 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: tsikora@powerusersbbs.com Cc: Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <386ADA6B.5D0CEAB2@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999, Ted Sikora wrote: > Marc Nicholas wrote: > > > > You're referring to the temps reported via an LM78 or similar, yes? > The machines bios with Winbond W83782d IC > That may explain it, then. > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > hotter under FreeBSD than under Linux. Sometime after 3.4-RC and > now this started. (I follow the stable branch via CVSup) Under > 3.3-STABLE the temerature was always the same as Linux...cool averaging > 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's > wierd but the machine does not lie. Under Linux it's the same as before > 87-89F. > The Winbond chipsets seems to have different multipliers than the LM78 chipsets. As author of lmmon/wmlmmon, I have yet to get someone to test so I can verify what the correct multipliers are. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 22:32:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 7AA0C14C9A for ; Wed, 29 Dec 1999 22:32:47 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id WAA01442 for ; Wed, 29 Dec 1999 22:32:45 -0800 (PST) To: "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature In-reply-to: Your message of Wed, 29 Dec 1999 15:45:45 -0800. <386A9D29.C7F0390D@3-cities.com> Date: Wed, 29 Dec 1999 22:32:44 -0800 Message-ID: <1440.946535564@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <386A9D29.C7F0390D@3-cities.com>, Kent Stewart wrote: >It also sounds like he isn't getting enough outside air. You can't >cool if the inside air is hot. Right! I have bought three ``slot fans'' now for different systems I own, and I'm very happy with them. Two I bought from a place called www.icedmocha.com. The other one I just bought cheap from a guy on eBay. They also have the same things at www.3dcool.com. I had one system with two VERY hot SCSI drives in it, and one of these slot fans really made a major difference. (Both drives are now always only just barely warm to the touch, whereas before, they were practically on fire.) P.S. If you are going to buy one of these things (slot fan) be sure to get tone of the black colored ones that is rated at 42 CFM airflow. That's what I got. I also saw some much less impressive slot fans (which were blue in color) at Fry's and they were only rated at 6 CFM. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 29 23:11: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id AB55C151E0 for ; Wed, 29 Dec 1999 23:11:06 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA06324; Thu, 30 Dec 1999 02:10:03 -0500 Date: Thu, 30 Dec 1999 02:10:03 -0500 (EST) From: Mike Nowlin To: "Ronald F. Guilmette" Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <1440.946535564@monkeys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had one system with two VERY hot SCSI drives in it, and one of these > slot fans really made a major difference. (Both drives are now always > only just barely warm to the touch, whereas before, they were practically > on fire.) Got a couple of those (DEC RZ26 & RZ28) with old 486 cooling fans (w/heat sinks) nylon-wire-wrapped to the top of them... Works quite well... :) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 0:24:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 5DD51151D3 for ; Thu, 30 Dec 1999 00:24:29 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 3.03 #3) id 123asl-0003a2-00; Thu, 30 Dec 1999 01:24:28 -0700 Message-ID: <386B174E.93083E6C@softweyr.com> Date: Thu, 30 Dec 1999 01:26:54 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Charlie Root Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gcc command line ordering question References: <199912292207.RAA67250@virtual-voodoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charlie Root wrote: > > I have a tiny little snippit of code here (test.c): > > char ldap_init(); > int main(int argc, char **argv) > { > ldap_init(); > return 0; > } > > I expect (want) a runtime error but I do expect it to compile when > linked with the openldap libraries. Here's my quandery: > > vv# gcc -L/usr/local/lib -I/usr/local/include -lldap -llber test.c > /tmp/ccj67244.o: In function `main': > /tmp/ccj67244.o(.text+0x7): undefined reference to `ldap_init' > > Very odd... but if I changed the ordering of the arguments: > > vv# gcc -L/usr/local/lib -I/usr/local/include test.c -lldap -llber > vv# > > It compiles fine. I thought gcc proccessed files in the order in which > they appeard? I further thought that the only difference between > specifying a fullname and using -l was that -l surrounding the name > with lib*.a and searched multiple directories. If thats all true why > would the ordering matter here? The linker, ld, searches libraries for undefined symbols. By specifying -lldap before test.c on the command line, you told ld to scan libldap.a, then compile test.c, which creates a reference to ldap_init that cannot be resolved. Compiling test.c first creates the reference, which is later resolved by searching libldap.a. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 0:58:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id C2B9814DBF; Thu, 30 Dec 1999 00:58:33 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 15-155.008.popsite.net ([209.69.195.155] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 123bPk-0007Of-00; Thu, 30 Dec 1999 01:58:32 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id DAA90605; Thu, 30 Dec 1999 03:58:29 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <386A4CEC.EB948EE8@home.com> Date: Thu, 30 Dec 1999 03:58:29 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: tsikora@powerusersbbs.com Subject: RE: Temperature Cc: "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ not subscribed to -hackers, but -stable ] On 29-Dec-99 Ted Sikora wrote: > Here's a strange problem. I run Linux stable/development kernels > and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines > temperatures have always been in this range with either system: > > 87F CPU #0 > 87F CPU #1 > 95F Case Temp > > Sometime last week or early this week the temperature under FreeBSD only > has changed to: > > 113F CPU #0 > 113F CPU #1 > 109F Case Temp > This is right after boot and varies 3-4 Degrees + while running. > > During the night periodically my temp warning has been going off. > I have it set to 118F. This happens only under FreeBSD. Linux continues > to run cool at the old temperatures. Apparantly some code change has > caused this. Does anyone know exactly where I should look? I would first confirm this kind of anomaly by loading that overheating machine with Linux and then seeing where the temperatures go. I'm not convinced you've taken into account all environment variables (and I don't mean shell variables). My system under FreeBSD tends to stay around 32C, or a little under 90F. I run FreeBSD 3.4-STABLE here, with adequate fan power and ventilation. The box is a 25" full tower case loaded with scsi stuff, and so on.. Sometimes (after one day's power-off) it starts up with a minimum temperature of 19C (66F). I've never seen it go above 35C (95F), so I'm a little curious about your problem. I doubt it has anything to do with the OS. [ Note: These temperatures are obtained from the intpm device via wmhm. I had to calculate the F's by the formula F = (C)(9/5) + 32. ] I admit I haven't seen this machine above 60 days uptime in a long while.. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 3:23:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ii.uib.no (eik.ii.uib.no [129.177.16.3]) by hub.freebsd.org (Postfix) with ESMTP id 9392615125 for ; Thu, 30 Dec 1999 03:23:12 -0800 (PST) (envelope-from trond.davidsen@ii.uib.no) Received: from ii.uib.no (hyll.ii.uib.no [129.177.16.27]) by ii.uib.no (8.8.7/8.8.7) with ESMTP id MAA02129; Thu, 30 Dec 1999 12:23:08 +0100 (MET) Message-ID: <386B4165.7BCD2563@ii.uib.no> Date: Thu, 30 Dec 1999 12:26:29 +0100 From: Trond Davidsen X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: tsikora@powerusersbbs.com Cc: freebsd-hackers@freebsd.org Subject: Re: Temperature References: <386A4CEC.EB948EE8@home.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > > Here's a strange problem. I run Linux stable/development kernels > and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines > temperatures have always been in this range with either system: > > 87F CPU #0 > 87F CPU #1 > 95F Case Temp > > Sometime last week or early this week the temperature under FreeBSD only > has changed to: > > 113F CPU #0 > 113F CPU #1 > 109F Case Temp > This is right after boot and varies 3-4 Degrees + while running. > > During the night periodically my temp warning has been going off. > I have it set to 118F. This happens only under FreeBSD. Linux continues > to run cool at the old temperatures. Apparantly some code change has > caused this. Does anyone know exactly where I should look? > > Regards, > -- > Ted Sikora > Jtl Development Group > tsikora@powerusersbbs.com > http://powerusersbbs.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Maybe off the point, but on my fresh unmodified 3.4-Stable system, I noticed these two processes: nobody 311 93.9 0.5 808 568 con- RN 1:02pm 1268:52.05 /usr/local/distributed.net/rc5des -quiet root 277 3.7 1.2 2116 1516 ?? Ss 1:02pm 57:24.31 /usr/local/sbin/QuickTimeStreamingServer this will cause the system to never idle... Trond -- /***************************************************\ * * * Trond Davidsen * * * * Institutt for Informatikk | Tlf Kontor 5558 4237 * * Universitetet i Bergen | Tlf Mobil 917 45 822 * * Thormøhlensgt. 55 | Tlf Privat 5518 6900 * * 5008 Bergen * * * \***************************************************/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 4:47:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id AA20415125; Thu, 30 Dec 1999 04:47:06 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id NAA34572; Thu, 30 Dec 1999 13:47:23 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199912301247.NAA34572@info.iet.unipi.it> Subject: Re: soundcards needed to further newpcm development In-Reply-To: <19991229150918.A39443@dub.net> from Bill Swingle at "Dec 29, 1999 03:09:18 pm" To: Bill Swingle Date: Thu, 30 Dec 1999 13:47:23 +0100 (CET) Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello all, > > In an attempt to help Cameron get newpcm to support widest array of > soundcards available we're trying to collect as many as possible for > testing and development. if i ever manage to run a -current, i will be probably able to help doing some testing. Let me understand though, are you collecting the boards for delivery to cameron, or you plan to do the testing yourself ? In the former case, people (especially from europe) might prefer to send cards directly to cameron... Speaking of chipset and support: i would try to prioritise work as some of the chips listed are so old that supporting them is practically useless. > cs4231 no no yes the 4231 is only a codec, i think it lacks the ISA interface chip which is different on different cards and needs special initialization in some cases. > opti925 no no yes > opti931 no no yes i have the data sheets for the 931 and probably 925, they are ps/pdf files sio i can mail them to cameron. > yamaha ymf711 no yes ? > yamaha ymf715 no yes ? > yamaha ymf719 no no ? the 711 and 715 are supported in the old "pcm" driver -- apart from a couple of register writes to set the mixer volume, it is a fairly good emulation of the 4232 so it works well. The 719 is undocumented andunfortunately some of the undocumented pieces refer to the control of the mixer. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 6:50:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id CA5B415331; Thu, 30 Dec 1999 06:50:25 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 757B21CA0; Thu, 30 Dec 1999 22:50:18 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Luigi Rizzo Cc: Bill Swingle , multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, cg@freebsd.org Subject: Re: soundcards needed to further newpcm development In-Reply-To: Message from Luigi Rizzo of "Thu, 30 Dec 1999 13:47:23 +0100." <199912301247.NAA34572@info.iet.unipi.it> Date: Thu, 30 Dec 1999 22:50:18 +0800 From: Peter Wemm Message-Id: <19991230145018.757B21CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > > yamaha ymf711 no yes ? > > yamaha ymf715 no yes ? > > yamaha ymf719 no no ? > > the 711 and 715 are supported in the old "pcm" driver -- apart > from a couple of register writes to set the mixer volume, it is > a fairly good emulation of the 4232 so it works well. The 719 > is undocumented andunfortunately some of the undocumented > pieces refer to the control of the mixer. I have a YMF719E card (that's on the chip itself) that works on a week-old -current (on an Alpha no less): pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 pcm0: interrupting at ISA irq 5 joy0: at port 0x201 on isa0 unknown0: at port 0x100-0x107 on isa0 unknown1: at port 0x1e8-0x1ef,0x3ee irq 11 on isa0 I have another machine (toshiba tecra 8000 laptop) with a yamaha-something in it (this is a PNPBIOS detected device): pcm0: at port 0x220-0x233,0x530-0x537,0x388-0x38f,0x330-0x333,0x538-0x539 irq 5 drq 1,0 on isa0 I seem to recall it too was a YHM0021 pnp id, but I don't know exactly what it is. YMH0021: adding io range 0x220-0x233, size=0x14, align=0x1 YMH0021: adding io range 0x530-0x537, size=0x8, align=0x1 YMH0021: adding io range 0x388-0x38f, size=0x8, align=0x1 YMH0021: adding io range 0x330-0x333, size=0x4, align=0x1 YMH0021: adding io range 0x538-0x539, size=0x2, align=0x1 YMH0021: adding irq mask 0x20 YMH0021: adding dma mask 0x2 YMH0021: adding dma mask 0x1 YMH0021: start dependant pnpbios: handle 21 device ID YMH0021 (2100a865) It's not a pnp device like the one on the card in the Alpha system. It's statically configured by the bios setup. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 6:56:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 53DC415331; Thu, 30 Dec 1999 06:56:40 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id PAA00478; Thu, 30 Dec 1999 15:56:44 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199912301456.PAA00478@info.iet.unipi.it> Subject: Re: soundcards needed to further newpcm development In-Reply-To: <19991230145018.757B21CA0@overcee.netplex.com.au> from Peter Wemm at "Dec 30, 1999 10:50:18 pm" To: Peter Wemm Date: Thu, 30 Dec 1999 15:56:44 +0100 (CET) Cc: Bill Swingle , multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, cg@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luigi Rizzo wrote: > > I have a YMF719E card (that's on the chip itself) that works on a week-old > -current (on an Alpha no less): by "works" i mean work in full duplex. Most reports i got for the '719 is that audio capture seems not to work. I seem to remember the problem is in the mixer -- i.e. you get data out of the codec, but there is no signal. Go figure where the '719 has the mute bits and mixer input select... Does your card really _works_ as above ? cheers luigi > pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 > pcm0: interrupting at ISA irq 5 > joy0: at port 0x201 on isa0 > unknown0: at port 0x100-0x107 on isa0 > unknown1: at port 0x1e8-0x1ef,0x3ee irq 11 on isa0 > > > I have another machine (toshiba tecra 8000 laptop) with a yamaha-something > in it (this is a PNPBIOS detected device): > > pcm0: at port 0x220-0x233,0x530-0x537,0x388-0x38f,0x330-0x333,0x538-0x539 irq 5 drq 1,0 on isa0 > > I seem to recall it too was a YHM0021 pnp id, but I don't know exactly what it > is. > > YMH0021: adding io range 0x220-0x233, size=0x14, align=0x1 > YMH0021: adding io range 0x530-0x537, size=0x8, align=0x1 > YMH0021: adding io range 0x388-0x38f, size=0x8, align=0x1 > YMH0021: adding io range 0x330-0x333, size=0x4, align=0x1 > YMH0021: adding io range 0x538-0x539, size=0x2, align=0x1 > YMH0021: adding irq mask 0x20 > YMH0021: adding dma mask 0x2 > YMH0021: adding dma mask 0x1 > YMH0021: start dependant > pnpbios: handle 21 device ID YMH0021 (2100a865) > > It's not a pnp device like the one on the card in the Alpha system. It's > statically configured by the bios setup. > > Cheers, > -Peter > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 10:10:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.ifrance.com (www.ifrance.com [209.67.249.134]) by hub.freebsd.org (Postfix) with SMTP id 508CE1520F for ; Thu, 30 Dec 1999 10:10:36 -0800 (PST) (envelope-from MoA4abul@ifrance.com) Received: from 194.149.162.224 [194.149.162.224] by www.ifrance.com; Thu, 30 Dec 1999 17:59:51 GMT Message-ID: <3A4DF81F.392B57@ifrance.com> Date: Sat, 30 Dec 1999 15:58:39 +0100 From: Jonathan Bisson Organization: No_ORG X-Mailer: FreeBSD 3.3-RELEASE i386 MIME-Version: 1.0 To: hackers@FreeBSD.org Subject: I have 2 Problems. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, (Sorry,I'm French and don't speak English very well). (Please reply at MoA4abul@ifrance.com, I can't subscribe to the mailing list). 1)CD-Writer I have a CD-Writer Plus 7200i (IDE). So, I want to use it under FreeBSD. Under Linux, it works perfectly, but with the Scsi Generic Emulation blabla... I tried /usr/share/examples/worm/... This don't work. I tried /usr/share/examples/atapi/... This don't work too. When I dd if=myimage.iso of=/dev/??? (I tried many devices), my writer don't seem to work properly and my system hangs. Is this a possibility to port the Scsi Generic Emulation... under FreeBSD(I wan't to help because I want to learn how to make a device driver for FreeBSD). 2) Video Card. I've a S3 TRIO 3D/2X, under Windows(hum?), it work perfectly, but under Linux and FreeBSD, I get many graphic artifacts. And under XFree, it's the same thing. Syscons and PCVT do the same thing. Dos works perfectly too. So what will I do. Thank you. Must I reinstall Linux or Windows for writing my CDs??? Reply at: MoA4abul@ifrance.com -- Jefftf: MoA4abul@ifrance.com "Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat." FreeBSD: http://www.freebsd.org ___________________________________________________________________________ Message envoye depuis iFrance : http://www.ifrance.com ou 3615 IFRANCE Gratuit : Hebergement (50 Mo)/Vos emails (POP,HTML,20 Mo, FAX)/Votre agenda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 10:37:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C16D153B8; Thu, 30 Dec 1999 10:37:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA76049; Thu, 30 Dec 1999 10:37:12 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Dec 1999 10:37:12 -0800 (PST) From: Matthew Dillon Message-Id: <199912301837.KAA76049@apollo.backplane.com> To: Tom Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, in general I would not mess with max_softdeps - softupdates gets very inefficient if it hits its limits. I think you may have found a flaw in the code, though. Softupdates reschedules its vnode sync whenever it does something to the vnode. Postmark must be operating on the same set of files for very long periods of time, including truncating and extending them, for softupdates to get that far behind! Kirk may have to modify the vnode scheduling to not reschedule the vnode beyond a certain aggregate delay in order to ensure that things get synchronized in a reasonable period of time. Softupdates biggest problem are with overly-long delays in block reclamation - several people have commented on it. I think what you are seeing is a special case of this problem that causes it to be much worse then normal. In the mean time you have a couple of choices. You can try running 'sync' every so often, or you can write a small C program to fsync() the files postfix messes with every so often. -Matt Matthew Dillon : I'm trying to find some information on reasonable settings for :debug.max_softdeps on a recent FreeBSD-stable system. : : It seems that if you have a machine that is able to generate disk IO :much faster than can be handled, has a large amount of RAM (and therefore :debug.max_softdeps is large), and the filesystem is very large (about :80GB), filesystem metadata updates can get _very_ far behind. : : For instance, on a test system running 4 instances of postmark :continuously for 24 hours, "df" reports that 40 GB of disk space is being :used, even though only about 5 GB is actually used. If I kill the :postmark processes, the metadata is eventually dribbled out and "df" :reports 5GB in use. It takes about 20 minutes for the metadata to be :updated on a completely ideal system. : : On this particular system, it doesn't seem to stabilize either. If the :4 postmark instances are allowed to run, disk usage seems to climb :indefinitely (at 40GB it was still climbing), until eventually the machine :silently reboots. : : debug.max_softdeps is by default set to 523,712 (1 GB of RAM). Is that :a resonable value? I see some tests in the docs with max_softdeps set to :4000 or so. : : :Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 11:10:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mission.mvnc.edu (mission.mvnc.edu [149.143.2.3]) by hub.freebsd.org (Postfix) with ESMTP id EE67015407; Thu, 30 Dec 1999 11:10:49 -0800 (PST) (envelope-from kdrobnac@mission.mvnc.edu) Received: from localhost (kdrobnac@localhost) by mission.mvnc.edu (8.9.0/8.9.0) with SMTP id OAA29098; Thu, 30 Dec 1999 14:10:43 -0500 (EST) Date: Thu, 30 Dec 1999 14:10:42 -0500 (EST) From: Kenny Drobnack To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: weirdness with a directory named ~ Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a question that I really don't know where to send, but since I'm just subscribed to hackers.... Anyway, the other day I had a directory I wanted to move to my home directory. I did "mv dirname ~" Well, I didn't realize it till later, but what it did was make a directory named ~ in the directory that I did that from! I had some problems deleting it. When I did "cd ~" from there, it took me to my home directory, and when I did "rm -ir ~" it wanted to delete files in my home directory. I ended up backing up my home directory, doing an "rm -rf ~" which deleted my whole home directory. But the ~ direcotry was still there! I tried rmdir ~, but it just said my home directory didn't exist. Finally I deleted it from emacs, which hadn't worked when my home directory existed. My question is: why did it do this?!?!? Also, how hard would it be to make things so it would look for ./~, then if that file/direcotry doesn't exist, then check for a home directory? Or is that even a good idea? ----- In computer terms, hardware is the stuff you can hit with a baseball bat, and software is the stuff you can only swear at. -from a web page explaining what hardware, software, and firmware are ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 11:14:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id BDBF0153C0; Thu, 30 Dec 1999 11:14:16 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123l1X-0004iR-00; Thu, 30 Dec 1999 11:14:11 -0800 Date: Thu, 30 Dec 1999 11:14:08 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Matthew Dillon Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <199912301837.KAA76049@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, postmark operates on the same file set. I used the following postmark settings: set number 30000 set transactions 4000000 set size 1500 200000 which uses a set of 30,000 files, and does a 4,000,000 transactions them (random mix of various operations), and size between 1,500 and 200,000 bytes. BTW, I hacked my version of postmark to use unsigned ints in various places. I guess by having a very large filesystem (80GB), and mostly empty, the softupdate code is able to queue an enormous amount of metadata updates over time. I tried forcing max_softdeps down to 50,000, and within a couple of hours all processes accessing that filesystem hung! Also, postmark is filesytem benchmarking and stress tester utility. Adding fsync() would defeat the purpose a bit! So in summary, if max_softdeps is left at the default, the system will reboot in 24 to 36 hours. If max_softdeps is set down, filesystem access will eventually hang within 12 hours. On Thu, 30 Dec 1999, Matthew Dillon wrote: > Well, in general I would not mess with max_softdeps - softupdates gets > very inefficient if it hits its limits. I think you may have found a > flaw in the code, though. Softupdates reschedules its vnode sync whenever > it does something to the vnode. Postmark must be operating on the same > set of files for very long periods of time, including truncating and > extending them, for softupdates to get that far behind! Kirk may have > to modify the vnode scheduling to not reschedule the vnode beyond a > certain aggregate delay in order to ensure that things get synchronized > in a reasonable period of time. > > Softupdates biggest problem are with overly-long delays in block > reclamation - several people have commented on it. I think what you > are seeing is a special case of this problem that causes it to be much > worse then normal. > > In the mean time you have a couple of choices. You can try running > 'sync' every so often, or you can write a small C program to fsync() > the files postfix messes with every so often. > > -Matt > Matthew Dillon > > > : I'm trying to find some information on reasonable settings for > :debug.max_softdeps on a recent FreeBSD-stable system. > : > : It seems that if you have a machine that is able to generate disk IO > :much faster than can be handled, has a large amount of RAM (and therefore > :debug.max_softdeps is large), and the filesystem is very large (about > :80GB), filesystem metadata updates can get _very_ far behind. > : > : For instance, on a test system running 4 instances of postmark > :continuously for 24 hours, "df" reports that 40 GB of disk space is being > :used, even though only about 5 GB is actually used. If I kill the > :postmark processes, the metadata is eventually dribbled out and "df" > :reports 5GB in use. It takes about 20 minutes for the metadata to be > :updated on a completely ideal system. > : > : On this particular system, it doesn't seem to stabilize either. If the > :4 postmark instances are allowed to run, disk usage seems to climb > :indefinitely (at 40GB it was still climbing), until eventually the machine > :silently reboots. > : > : debug.max_softdeps is by default set to 523,712 (1 GB of RAM). Is that > :a resonable value? I see some tests in the docs with max_softdeps set to > :4000 or so. > : > : > :Tom > > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 11:17:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 9A32F14E1B; Thu, 30 Dec 1999 11:17:07 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id LAA21648; Thu, 30 Dec 1999 11:16:41 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199912301916.LAA21648@troutmask.apl.washington.edu> Subject: Re: weirdness with a directory named ~ In-Reply-To: from Kenny Drobnack at "Dec 30, 1999 02:10:42 pm" To: kdrobnac@mission.mvnc.edu (Kenny Drobnack) Date: Thu, 30 Dec 1999 11:16:41 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenny Drobnack wrote: > Anyway, the other day I had a directory I wanted to move to my > home directory. I did "mv dirname ~" Well, I didn't realize it till later, > but what it did was make a directory named ~ in the directory that I did What is your login shell? Read its manual page. [removing ~ story deleted] You need to escape the tilde character so that it isn't expanded by your shell. Try "rm -rf \~". -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 11:20: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mission.mvnc.edu (mission.mvnc.edu [149.143.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 085B3153DF; Thu, 30 Dec 1999 11:20:05 -0800 (PST) (envelope-from kdrobnac@mission.mvnc.edu) Received: from localhost (kdrobnac@localhost) by mission.mvnc.edu (8.9.0/8.9.0) with SMTP id OAA29326; Thu, 30 Dec 1999 14:19:58 -0500 (EST) Date: Thu, 30 Dec 1999 14:19:58 -0500 (EST) From: Kenny Drobnack To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: CD-RW long filenames/rw filesystem. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A couple weeks ago I got a CD-RW drive, and decided to try it out under all the different OS's I use. In FreeBSD, the only way (it seems) to use it, is grab a bunch of stuff you want to backup/record and use mkisofs and cdrecord to dump it onto a CD. Everything I read seemed to indicate that this method limits you to the 8.3 filename format of iso9660 and all Rockridge does is add file/group permissions and ownership. is there any CD recording utilities/formats that can do long filenames (hopefully with Unix permissions)? Next question. Under Windows, there was a program called Adaptec Direct CD that pretty much allowed you to treat a CD-RW disc as "a really big floppy disk" (I think that was from the docs). You can save a file to the CD-RW and then delete it later if you want to. Would it be possible, or even feasible, to implement something like this in FreeBSD? ----- In computer terms, hardware is the stuff you can hit with a baseball bat, and software is the stuff you can only swear at. -from a web page explaining what hardware, software, and firmware are ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 11:57:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from D2SI.COM (D2SI.COM [63.224.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F92314D46; Thu, 30 Dec 1999 11:57:45 -0800 (PST) (envelope-from ajk@paw-in-eye.net) Received: (from ajk@localhost) by D2SI.COM (8.9.3/8.9.3) id NAA03319; Thu, 30 Dec 1999 13:57:35 -0600 (CST) (envelope-from ajk) From: Alec Kloss Message-Id: <199912301957.NAA03319@D2SI.COM> Subject: Re: weirdness with a directory named ~ In-Reply-To: from Kenny Drobnack at "Dec 30, 1999 2:10:42 pm" To: kdrobnac@mission.mvnc.edu (Kenny Drobnack) Date: Thu, 30 Dec 1999 13:57:35 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenny Drobnack said: > My question is: why did it do this?!?!? Also, how hard would it be > to make things so it would look for ./~, then if that file/direcotry > doesn't exist, then check for a home directory? Or is that even a good > idea? 1) Don't crosspost. 2) You've essentially answered your own question. Tildes at the beginning of pathnames are relative to a home directory. Tildes elsewhere in a path are not. So, to remove a directory named ~, use rmdir ./~ as below: %mkdir ./~ %ls -ld ./~ drwxr-xr-x 2 ajk wheel 512 Dec 30 13:56 ./~ %rmdir ~ rmdir: /home/alec: Permission denied %rmdir ./~ % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 12:24:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id B0CEF14A1D; Thu, 30 Dec 1999 12:24:10 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id MAA02115; Thu, 30 Dec 1999 12:23:36 -0800 (PST) Date: Thu, 30 Dec 1999 12:23:36 -0800 From: Brooks Davis To: Kenny Drobnack Cc: freebsd-questions@freebsd.org Subject: Re: CD-RW long filenames/rw filesystem. Message-ID: <19991230122336.C25831@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from kdrobnac@mission.mvnc.edu on Thu, Dec 30, 1999 at 02:19:58PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Redirected to -questions where it belonged.] On Thu, Dec 30, 1999 at 02:19:58PM -0500, Kenny Drobnack wrote: > A couple weeks ago I got a CD-RW drive, and decided to try it out under > all the different OS's I use. In FreeBSD, the only way (it seems) to use > it, is grab a bunch of stuff you want to backup/record and use mkisofs and > cdrecord to dump it onto a CD. Everything I read seemed to indicate that > this method limits you to the 8.3 filename format of iso9660 and all > Rockridge does is add file/group permissions and ownership. is there any > CD recording utilities/formats that can do long filenames (hopefully with > Unix permissions)? This is incorrect. Rockridge adds long file names on OSes that support the extensions (i.e. UNIX). If you want them to work with windows you can use mkhybird to add Joliet extensions the disk as well. > Next question. Under Windows, there was a program called Adaptec > Direct CD that pretty much allowed you to treat a CD-RW disc as "a really > big floppy disk" (I think that was from the docs). You can save a file to > the CD-RW and then delete it later if you want to. Would it be possible, > or even feasible, to implement something like this in FreeBSD? It should be possiable, but no one has done it to my knowledge. -- Brooks -- "Those who desire to give up freedom in order to gain security, will not have, nor do they deserve, either one" --Thomas Jefferson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 12:35: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 06AA6152B5; Thu, 30 Dec 1999 12:34:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA01353; Thu, 30 Dec 1999 12:38:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912302038.MAA01353@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-reply-to: Your message of "Wed, 29 Dec 1999 23:07:07 EST." <386ADA6B.5D0CEAB2@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 12:38:50 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Marc Nicholas wrote: > > > > You're referring to the temps reported via an LM78 or similar, yes? > The machines bios with Winbond W83782d IC > > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > hotter under FreeBSD than under Linux. That's fairly hard to believe, unless your system has zero thermal inertia. I'd have an easier time suggesting that your reporting software has been broken. I'm also curious as to how you're talking to the BIOS to obtain these temperature values. > Sometime after 3.4-RC and > now this started. (I follow the stable branch via CVSup) Under > 3.3-STABLE the temerature was always the same as Linux...cool averaging > 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's > wierd but the machine does not lie. Under Linux it's the same as before > 87-89F. You can't claim "the machine does not lie" without substantiating evidence. I'd want an external thermometer at the very least. However, since you're the only one reporting this, you could do us all a great service by taking a few minutes off to perform a binary search to narrow down the date at which this purported change might have occurred. You can trivially easily check out kernels and build them to see what effect running them has on your operating temperature. You haven't by some chance just recently started running eg. the SETI @home client, or one of the distributed.net clients by any chance? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 13:31:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 21E2E1541E; Thu, 30 Dec 1999 13:31:06 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230213059.NUJZ9446.mail.rdc1.ct.home.com@home.com>; Thu, 30 Dec 1999 13:30:59 -0800 Message-ID: <386BCF19.F259CD1B@home.com> Date: Thu, 30 Dec 1999 16:31:05 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Mike Smith Cc: tsikora@powerusersbbs.com, Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <199912302038.MAA01353@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Marc Nicholas wrote: > > > > > > You're referring to the temps reported via an LM78 or similar, yes? > > The machines bios with Winbond W83782d IC > > > > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > > hotter under FreeBSD than under Linux. > > That's fairly hard to believe, unless your system has zero thermal > inertia. I'd have an easier time suggesting that your reporting software > has been broken. I'm also curious as to how you're talking to the BIOS > to obtain these temperature values. > I'm really starting to get irritaed with all these posts. I'm trying to report a potential problem and your treating me like I'm some yokel. I have been a computer engineer for 28 years so I think I have a little experience in this. Well here's some data: FreeBSD 3.3-RELEASE #0: Thu Sep 16 23:40:35 GMT 1999 jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC (lmmon -i reports) Motherboard Temp Voltages 32C / 89F / 305K Vcore1: +2.016V Vcore2: +1.469V Fan Speeds + 3.3V: +3.234V + 5.0V: +4.932V 1: 0 rpm +12.0V: +12.625V 2: 0 rpm -12.0V: -2.438V 3: 0 rpm - 5.0V: -1.383V System Winbond chip in system bios reports: 87F CPU#0 87F CPU#1 89F CASE TEMP ------------------------------------------------------------- FreeBSD 3.4-STABLE #0: Tue Dec 28 19:28:10 EST 1999 root@telecast.htfds1.ct.home.com:/usr/src/sys/compile/TELECAST (lmmon -i reports) Motherboard Temp Voltages 41C / 105F / 314K Vcore1: +2.016V Vcore2: +1.484V Fan Speeds + 3.3V: +3.250V + 5.0V: +4.932V 1: 0 rpm +12.0V: +12.625V 2: 0 rpm -12.0V: -2.375V 3: 0 rpm - 5.0V: -1.383V System Winbond chip in system bios reports: 113F CPU#0 113F CPU#1 105F CASE TEMP These are both taken right after bootup with X started and WindowMaker running. No other apps running. Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 14: 5:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from marcy.nas.nasa.gov (marcy.nas.nasa.gov [129.99.113.17]) by hub.freebsd.org (Postfix) with ESMTP id 10A1B154D7; Thu, 30 Dec 1999 14:05:50 -0800 (PST) (envelope-from wrstuden@marcy.nas.nasa.gov) Received: from localhost (wrstuden@localhost) by marcy.nas.nasa.gov (8.9.3/NAS8.8.7n) with SMTP id OAA16103; Thu, 30 Dec 1999 14:05:07 -0800 (PST) Date: Thu, 30 Dec 1999 14:05:07 -0800 (PST) From: Bill Studenmund To: tsikora@powerusersbbs.com Cc: Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <386ADA6B.5D0CEAB2@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999, Ted Sikora wrote: > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > hotter under FreeBSD than under Linux. Sometime after 3.4-RC and > now this started. (I follow the stable branch via CVSup) Under > 3.3-STABLE the temerature was always the same as Linux...cool averaging > 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's > wierd but the machine does not lie. Under Linux it's the same as before > 87-89F. The big question of course is are you sure the machine's not lying? I agree with you that i't unlikely that it's a fundamental hardware problem (like you're getting no air flow) if Linux still reports sane temperatures. But it seems quite reasonable that somehow temperture reading broke for your hardware when you upgraded. Two easy ways to settle the issue would be either to get a thermocouple thermometer, put the thermocouple in the case, and see exactly what happens with the case temperature. Another easy way to settle it is to get the voltages being returned for the temperature sensors as opposed to the reported temperature. If the voltages are the same under the two OS's, then it's definitly a reporting error. :-) Take care, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 14: 7: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp5.jps.net (smtp5.jps.net [209.63.224.55]) by hub.freebsd.org (Postfix) with ESMTP id 61E5A1525D; Thu, 30 Dec 1999 14:06:52 -0800 (PST) (envelope-from onemo@jps.net) Received: from jps.net (216-224-148-40.stk.jps.net [216.224.148.40]) by smtp5.jps.net (8.9.3/8.9.0) with ESMTP id OAA16548; Thu, 30 Dec 1999 14:06:26 -0800 (PST) Message-ID: <386BD5E2.F341E560@jps.net> Date: Thu, 30 Dec 1999 14:00:03 -0800 From: Michael Oski X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: tsikora@powerusersbbs.com Cc: "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <199912302038.MAA01353@mass.cdrom.com> <386BCF19.F259CD1B@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > I'm really starting to get irritaed with all these posts. I'm trying to > report a potential problem and your treating me like I'm some yokel. I > have been a computer engineer for 28 years so I think I have a little > experience in this. Well here's some data: OK, I'll admit I'm merely an observer in all this, but I'd like to say that I too am starting to get irritated with this. To be honest, your apparent irritation, along with the point about not being 'some yokel' has finally nudged me into replying. I would have to say that the vast majority of posts regarding your problem report were targetted at identifying whether the system 'was HOTTER' or 'was SAYING it was hotter'. When this was first pointed out to you, your reply was 'picky, it SAYS it's hotter'. This is not a matter of being picky - this is a crucial factor in determining what the source of this problem is. I can say with most certainty, that I would have had far fewer messages in my inbox had you acurately described the problem. So, you see, it is YOU that is the cause of this irritation. I would think that a professional such as yourself, with 28 years of experience, would understand this and make every effort to post clear and concise reports. Please don't flame the developers of FreeBSD for taking so long to determine what it is you are reporting, when it was up to you to specify this originally. My last $0.02 from the 20th Century. Michael. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 14:11:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 3B4C4153A9; Thu, 30 Dec 1999 14:11:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA02713; Thu, 30 Dec 1999 14:15:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912302215.OAA02713@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-reply-to: Your message of "Thu, 30 Dec 1999 16:31:05 EST." <386BCF19.F259CD1B@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 14:15:25 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > > > > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > > > hotter under FreeBSD than under Linux. > > > > That's fairly hard to believe, unless your system has zero thermal > > inertia. I'd have an easier time suggesting that your reporting software > > has been broken. I'm also curious as to how you're talking to the BIOS > > to obtain these temperature values. > > > I'm really starting to get irritaed with all these posts. I'm trying to > report a potential problem and your treating me like I'm some yokel. I > have been a computer engineer for 28 years so I think I have a little > experience in this. Since we also have some experience in this, you might want to take our responses to indicate that your thinking may be in error. I'm certainly not trying to treat you like a yokel. I'm trying to get you to think and behave like a computer engineer with nearly 30 years of experience. So far this hasn't been very successful. > Well here's some data: > > FreeBSD 3.3-RELEASE #0: Thu Sep 16 23:40:35 GMT 1999 > jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC > > (lmmon -i reports) > > Motherboard Temp Voltages > > 32C / 89F / 305K Vcore1: +2.016V ... > 41C / 105F / 314K Vcore1: +2.016V Is this the same lmmon binary in both cases? Have you confirmed these temperatures with an external thermometer? > These are both taken right after bootup with X started and WindowMaker > running. No other apps running. The first step in resolving this has simply been to try to narrow down the variables so that we have some idea what might actually be involved here. It's been a painful process, but we're almost there. Once you can confirm that the onboard temperature sensors are working and bear a good resemblance to reality we can eliminate them from the equation. I did ask for verification of this (which hasn't been forthcoming yet). I've also asked you to undertake the second phase, which is to perform a binary-search set of kernel builds to pin down the timeframe in which this change occurred. It's also been suggested that the scheduler changes made by Bruce Evans may have impacted your system; you might want to bracket those changes to quickly eliminate them as possibilities. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 16:37:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 8896614BE1; Thu, 30 Dec 1999 16:37:21 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 71BAE1CA0; Fri, 31 Dec 1999 08:37:18 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: Mike Smith , Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: Message from Ted Sikora of "Thu, 30 Dec 1999 16:31:05 EST." <386BCF19.F259CD1B@home.com> Date: Fri, 31 Dec 1999 08:37:18 +0800 From: Peter Wemm Message-Id: <19991231003718.71BAE1CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > These are both taken right after bootup with X started and WindowMaker > running. No other apps running. Can you please include: top -S -n 100 ps -axl vmstat -i sysctl kern sysctl vm And we can see if that gives some clues as to what the cpus are doing. It's a long shot but we have nothing else to go on. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 16:49:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7FC251525B; Thu, 30 Dec 1999 16:49:04 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 01D721CA0; Fri, 31 Dec 1999 08:49:02 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Cc: Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: Message from Tom of "Thu, 30 Dec 1999 11:14:08 PST." Date: Fri, 31 Dec 1999 08:49:01 +0800 From: Peter Wemm Message-Id: <19991231004902.01D721CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate softupdates on the disk containing the postfix spool, the machine reboots (silently if I recall correctly) within 5 minutes of postfix starting up. This is a much smaller system of course, with smaller memory and filesystem working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post this as a real-use datapoint. Tom wrote: > Yes, postmark operates on the same file set. I used the following > postmark settings: > > set number 30000 > set transactions 4000000 > set size 1500 200000 > > which uses a set of 30,000 files, and does a 4,000,000 transactions them > (random mix of various operations), and size between 1,500 and 200,000 > bytes. BTW, I hacked my version of postmark to use unsigned ints in > various places. > > I guess by having a very large filesystem (80GB), and mostly empty, the > softupdate code is able to queue an enormous amount of metadata updates > over time. > > I tried forcing max_softdeps down to 50,000, and within a couple of > hours all processes accessing that filesystem hung! > > Also, postmark is filesytem benchmarking and stress tester utility. > Adding fsync() would defeat the purpose a bit! > > So in summary, if max_softdeps is left at the default, the system will > reboot in 24 to 36 hours. If max_softdeps is set down, filesystem access > will eventually hang within 12 hours. > > > On Thu, 30 Dec 1999, Matthew Dillon wrote: > > > Well, in general I would not mess with max_softdeps - softupdates gets > > very inefficient if it hits its limits. I think you may have found a > > flaw in the code, though. Softupdates reschedules its vnode sync whene ver > > it does something to the vnode. Postmark must be operating on the same > > set of files for very long periods of time, including truncating and > > extending them, for softupdates to get that far behind! Kirk may have > > to modify the vnode scheduling to not reschedule the vnode beyond a > > certain aggregate delay in order to ensure that things get synchronized > > in a reasonable period of time. > > > > Softupdates biggest problem are with overly-long delays in block > > reclamation - several people have commented on it. I think what you > > are seeing is a special case of this problem that causes it to be much > > worse then normal. > > > > In the mean time you have a couple of choices. You can try running > > 'sync' every so often, or you can write a small C program to fsync() > > the files postfix messes with every so often. > > > > -Matt > > Matthew Dillon > > > > > > : I'm trying to find some information on reasonable settings for > > :debug.max_softdeps on a recent FreeBSD-stable system. > > : > > : It seems that if you have a machine that is able to generate disk IO > > :much faster than can be handled, has a large amount of RAM (and therefore > > :debug.max_softdeps is large), and the filesystem is very large (about > > :80GB), filesystem metadata updates can get _very_ far behind. > > : > > : For instance, on a test system running 4 instances of postmark > > :continuously for 24 hours, "df" reports that 40 GB of disk space is being > > :used, even though only about 5 GB is actually used. If I kill the > > :postmark processes, the metadata is eventually dribbled out and "df" > > :reports 5GB in use. It takes about 20 minutes for the metadata to be > > :updated on a completely ideal system. > > : > > : On this particular system, it doesn't seem to stabilize either. If the > > :4 postmark instances are allowed to run, disk usage seems to climb > > :indefinitely (at 40GB it was still climbing), until eventually the machine > > :silently reboots. > > : > > : debug.max_softdeps is by default set to 523,712 (1 GB of RAM). Is that > > :a resonable value? I see some tests in the docs with max_softdeps set to > > :4000 or so. > > : > > : > > :Tom > > > > > > > > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 17: 2:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id E039B15343; Thu, 30 Dec 1999 17:02:48 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123qSj-000Bhp-00; Thu, 30 Dec 1999 17:02:37 -0800 Date: Thu, 30 Dec 1999 17:02:33 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Peter Wemm Cc: Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <19991231004902.01D721CA0@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Dec 1999, Peter Wemm wrote: > FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate > softupdates on the disk containing the postfix spool, the machine reboots > (silently if I recall correctly) within 5 minutes of postfix starting up. > > This is a much smaller system of course, with smaller memory and filesystem > working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post > this as a real-use datapoint. That is interesting. So I guess the conclusion to this is, softupdates is useful for bursty IO, but not sustained because it can get far behind until it eventually reaches the point where the machine reboots silently. I guess the delay until reboot is dependent on the size of max_softdeps. If it is big, it takes a while. I still think that the default value of max_softdeps might be too big for the kernel memory space. > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 17:22:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id A829814E40; Thu, 30 Dec 1999 17:22:16 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 20-172.008.popsite.net ([209.69.196.172] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 123qkr-0003ax-00; Thu, 30 Dec 1999 18:21:23 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id UAA36875; Thu, 30 Dec 1999 20:21:16 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912302038.MAA01353@mass.cdrom.com> Date: Thu, 30 Dec 1999 20:21:16 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Mike Smith Subject: Re: Temperature Cc: "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" , Marc Nicholas , tsikora@powerusersbbs.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Dec-99 Mike Smith wrote: > You haven't by some chance just recently started running eg. the SETI > @home client, or one of the distributed.net clients by any chance? I forgot to mention that I run rc5des on my 3.4-STABLE machine here, and I rarely see the temperature higher than 32C (~90F). As I touch the grill where some of the air goes out, it feels quite cold. 32C as reported by wmhm through the intpm device. I might add this is a single PII-450 machine, with no overclocking or any stupid things like that. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 17:29:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 85F0B14D98; Thu, 30 Dec 1999 17:29:39 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id TAA22448; Thu, 30 Dec 1999 19:29:55 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912310129.TAA22448@celery.dragondata.com> Subject: Re: Temperature To: msmith@FreeBSD.ORG (Mike Smith) Date: Thu, 30 Dec 1999 19:29:55 -0600 (CST) Cc: tsikora@powerusersbbs.com, marc@netstor.com (Marc Nicholas), freebsd-hackers@FreeBSD.ORG (freebsd-hackers@FreeBSD.ORG), freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG) In-Reply-To: <199912302215.OAA02713@mass.cdrom.com> from "Mike Smith" at Dec 30, 1999 02:15:25 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've also asked you to undertake the second phase, which is to perform a > binary-search set of kernel builds to pin down the timeframe in which > this change occurred. It's also been suggested that the scheduler > changes made by Bruce Evans may have impacted your system; you might want > to bracket those changes to quickly eliminate them as possibilities. In the very very very heat sensitve embedded product I'm working on, we have a system that has thermal probes all over the place that we use for testing. It's a Celeron 333(S370), 440ZX motherboard, and SDRAM DIMMs. In a very very unscientific test, using software that's not available anywhere outside my office, I can say that if anything, I see a 1 or 2 degree (C) *decrease* in CPU temperature between 3.2 and 3.4. (I do not have a 3.3 system to compare with to see if, in fact, 3.3 was very cool and 3.4 and 3.2 share the same brokenness). I'm also using external temperature probes, not using an LM78 or anything internal to measure the temperature. My honest guess is that something broke in 3.4 that's making it screw with the temperature readings, and the bios isn't setting it back right. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 17:41:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1FFB215386; Thu, 30 Dec 1999 17:41:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA78648; Thu, 30 Dec 1999 17:41:26 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Dec 1999 17:41:26 -0800 (PST) From: Matthew Dillon Message-Id: <199912310141.RAA78648@apollo.backplane.com> To: Tom Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : That is interesting. So I guess the conclusion to this is, softupdates :is useful for bursty IO, but not sustained because it can get far behind :until it eventually reaches the point where the machine reboots silently. :I guess the delay until reboot is dependent on the size of max_softdeps. :If it is big, it takes a while. : : I still think that the default value of max_softdeps might be too big :for the kernel memory space. Well it sure isn't supposed to reboot silently! No panic message at all? No printf? Hopefully Kirk is around to help track down the problem but if not I'll take a crack at it after newyears if you create a PR for it and assign it to me. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 17:43:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from explorer.tip.CSIRO.AU (explorer.tip.CSIRO.AU [130.155.191.10]) by hub.freebsd.org (Postfix) with ESMTP id B6ECE14E40 for ; Thu, 30 Dec 1999 17:43:31 -0800 (PST) (envelope-from amy@explorer.tip.CSIRO.AU) Received: from explorer.tip.CSIRO.AU (localhost [127.0.0.1]) by explorer.tip.CSIRO.AU (8.9.3/8.9.1) with ESMTP id MAA16023; Fri, 31 Dec 1999 12:43:14 +1100 (EST) (envelope-from amy@explorer.tip.CSIRO.AU) Message-Id: <199912310143.MAA16023@explorer.tip.CSIRO.AU> To: Kenny Drobnack Cc: freebsd-hackers@freebsd.org Subject: Re: CD-RW long filenames/rw filesystem. In-reply-to: Your message of "Thu, 30 Dec 1999 14:19:58 CDT." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16019.946604593.1@explorer.tip.CSIRO.AU> Date: Fri, 31 Dec 1999 12:43:13 +1100 From: "Shaun Amy, CSIRO TIP/ATNF" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >A couple weeks ago I got a CD-RW drive, and decided to try it out under >all the different OS's I use. In FreeBSD, the only way (it seems) to use >it, is grab a bunch of stuff you want to backup/record and use mkisofs and >cdrecord to dump it onto a CD. Everything I read seemed to indicate that >this method limits you to the 8.3 filename format of iso9660 and all >Rockridge does is add file/group permissions and ownership. is there any >CD recording utilities/formats that can do long filenames (hopefully with >Unix permissions)? This is not correct. The initial ISO9660 standard did specify the 8.3 format but there are now extensions that do what you describe. Recent versions of "mkisofs" support RockRidge (long filename under UNIX support) and Joliet (MS long filename support) so you are not restricted to the 8.3 format. I wrote a couple of CDs the other day under FreeBSD (3.4-STABLE) using "mkisofs" with RockRidge support and the long filenames work fine. As this was data from a UNIX system I wasn't concerned with Windows support. > Next question. Under Windows, there was a program called Adaptec >Direct CD that pretty much allowed you to treat a CD-RW disc as "a really >big floppy disk" (I think that was from the docs). You can save a file to >the CD-RW and then delete it later if you want to. Would it be possible, >or even feasible, to implement something like this in FreeBSD? The is called "packet writing" and the drive has to support it as well as software. I haven't seen any Unix tools to date (although I haven't done a comprehensive search) that supports this. Shaun. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 19:17:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 75AB115467; Thu, 30 Dec 1999 19:17:37 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123sZA-000EJ8-00; Thu, 30 Dec 1999 19:17:24 -0800 Date: Thu, 30 Dec 1999 19:17:19 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Matthew Dillon Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <199912310141.RAA78648@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Matthew Dillon wrote: > : That is interesting. So I guess the conclusion to this is, softupdates > :is useful for bursty IO, but not sustained because it can get far behind > :until it eventually reaches the point where the machine reboots silently. > :I guess the delay until reboot is dependent on the size of max_softdeps. > :If it is big, it takes a while. > : > : I still think that the default value of max_softdeps might be too big > :for the kernel memory space. > > Well it sure isn't supposed to reboot silently! No panic message at > all? No printf? Well, a panic/printf should be recorded in the dmesg buffer, but I don't see anything. I'm using a serial terminal now, and I'm repeating my 4 x postmark test. > Hopefully Kirk is around to help track down the problem but if not I'll > take a crack at it after newyears if you create a PR for it and assign > it to me. I also don't think "sync" is a fix either. I expect "sync" to reclaim unused space. For instance, the file system currently shows 9 GB in use with "df", but there is only about 5 GB actually present on the disk. I ran "sync", and I expected "df" to report about 5GB used, but it doesn't seem to change anything. I'm going to try sync again tommorrow once the unreclaimed space is about 30GB or so, and see if it does anything. The only fix seems to be to halt IO before the mystery limit is hit, and let softupdates catch up on unreclaimed space. My 4 x postmark test completely maxes out the IO capacity of the system (ex. an ls of any empty directory taks 5 seconds). One thing that is interesting is that the following sysctl variables are always zero: debug.blk_limit_push: 0 debug.ino_limit_push: 0 debug.blk_limit_hit: 0 debug.ino_limit_hit: 0 debug.rush_requests: 0 So it doesn't look like softupdates is rushing things out. "vmstat -m" is showing that the storage for "inodedep" is steadily increasing. I _think_ I need to increase tick_delay, so when the max_softdeps limit is finally hit, syncer gets run for a while and clean things up. > -Matt Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 19:37:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1C6EE15372; Thu, 30 Dec 1999 19:37:28 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA79239; Thu, 30 Dec 1999 19:37:26 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Dec 1999 19:37:26 -0800 (PST) From: Matthew Dillon Message-Id: <199912310337.TAA79239@apollo.backplane.com> To: Tom Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : I also don't think "sync" is a fix either. I expect "sync" to reclaim :unused space. For instance, the file system currently shows 9 GB in use :with "df", but there is only about 5 GB actually present on the disk. I :ran "sync", and I expected "df" to report about 5GB used, but it doesn't :seem to change anything. I'm going to try sync again tommorrow once the :unreclaimed space is about 30GB or so, and see if it does anything. Try lots of sync's ... like one a second :-). One sync won't do it. But what we really want to do is make the thing crash and hopefully (with the serial console maybe) get a panic message. Conventionally what should be occuring is that the kernel should be running out of some memory pool. If this is what is occuring it should generate a panic message prior to rebooting. A couple of other things you can do: Compile up the kernel with DDB configured so the system drops into DDB instead of panicing (only do this if you have access to the console). Then you should be able to 'trace' and 'ps' prior to typing 'panic' manually (type as many s as necessary after that but be careful, you don't want to interrupt a kernel dump if the kernel has started one!). Using several local xterms with a large back buffer configured, ssh to the machine under test and setup a couple of csh while(1) loops to look at various kernel resources, e.g. while (1) vmstat -z; vmstat -m end end The reason you use a local xterm in which you ssh to the remote machine is so the xterm doesn't disappear on you when the remote machine crashes :-). A tail -f /var/log/messages will probably *NOT* spit out the panic message quickly enough, but a true serial console (not just a getty running on the port) should spit it out just fine. : One thing that is interesting is that the following sysctl variables are :always zero: : :debug.blk_limit_push: 0 :debug.ino_limit_push: 0 :debug.blk_limit_hit: 0 :debug.ino_limit_hit: 0 :debug.rush_requests: 0 : : So it doesn't look like softupdates is rushing things out. These aren't very useful unless you only have a tiny bit of main memory. for all practical purposes the limit is not usually ever reached (which is probably why its buggy when it *is* reached). : "vmstat -m" is showing that the storage for "inodedep" is steadily :increasing. : : I _think_ I need to increase tick_delay, so when the max_softdeps limit :is finally hit, syncer gets run for a while and clean things up. tick_delay will probably not have much of an effect. look at the vmstat -m output carefully as you run the test (as suggested above). Bad things happen if you run the kernel out of KVM, and that can happen even if you have plenty of normal ram. There are *TWO* limits involved. There is the limit for the memory pool you are observing, and there is a global limit on the grand total which is nominally 2x the per-pool limit. If either limit is reached the machine is hosed. :Tom :Uniserve -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 20:53:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 91C5014D5D for ; Thu, 30 Dec 1999 20:53:09 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 1749B1CA0; Fri, 31 Dec 1999 12:53:07 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Shaun Amy, CSIRO TIP/ATNF" Cc: Kenny Drobnack , freebsd-hackers@freebsd.org Subject: Re: CD-RW long filenames/rw filesystem. In-Reply-To: Message from "Shaun Amy, CSIRO TIP/ATNF" of "Fri, 31 Dec 1999 12:43:13 +1100." <199912310143.MAA16023@explorer.tip.CSIRO.AU> Date: Fri, 31 Dec 1999 12:53:07 +0800 From: Peter Wemm Message-Id: <19991231045307.1749B1CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Shaun Amy, CSIRO TIP/ATNF" wrote: > >A couple weeks ago I got a CD-RW drive, and decided to try it out under > >all the different OS's I use. In FreeBSD, the only way (it seems) to use > >it, is grab a bunch of stuff you want to backup/record and use mkisofs and > >cdrecord to dump it onto a CD. Everything I read seemed to indicate that > >this method limits you to the 8.3 filename format of iso9660 and all > >Rockridge does is add file/group permissions and ownership. is there any > >CD recording utilities/formats that can do long filenames (hopefully with > >Unix permissions)? > > This is not correct. The initial ISO9660 standard did specify the 8.3 format > but there are now extensions that do what you describe. Recent versions of > "mkisofs" support RockRidge (long filename under UNIX support) and Joliet > (MS long filename support) so you are not restricted to the 8.3 format. I > wrote a couple of CDs the other day under FreeBSD (3.4-STABLE) using > "mkisofs" with RockRidge support and the long filenames work fine. As this > was data from a UNIX system I wasn't concerned with Windows support. Not quite. According to mkisofs(1): -l Allow full 32 character filenames. Normally the ISO9660 filename will be in an 8.3 format which is compatible with MS-DOS, even though the ISO9660 standard allows filenames of up to 32 characters. If you use this option, the disc may be difficult to use on a MS-DOS system, but this comes in handy on some other systems (such as the Amiga). Use with caution. It's depressing to see just how long the legacy of MS-DOS persists. :-( The ISO9660 format supports 32 chars, but since nearly everything uses 8.3 to be readable by MSCDEX and windoze, the 32 character names are rarely implemented or well tested. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 22:28:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id 78F65154E5 for ; Thu, 30 Dec 1999 22:28:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00620; Thu, 30 Dec 1999 22:34:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912310634.WAA00620@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-reply-to: Your message of "Thu, 30 Dec 1999 17:02:33 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 22:34:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That is interesting. So I guess the conclusion to this is, softupdates > is useful for bursty IO, but not sustained because it can get far behind > until it eventually reaches the point where the machine reboots silently. > I guess the delay until reboot is dependent on the size of max_softdeps. > If it is big, it takes a while. I mentioned this a while back in the context of suspended I/O (in this case, a RAID array busy dealing with a failed disk). There wasn't much interest in dealing with it evinced at that point. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 22:35:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id 924A615327; Thu, 30 Dec 1999 22:35:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00658; Thu, 30 Dec 1999 22:40:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912310640.WAA00658@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Tom , freebsd-hackers@freebsd.org Subject: Re: softupdates and debug.max_softdeps In-reply-to: Your message of "Thu, 30 Dec 1999 22:34:04 PST." <199912310634.WAA00620@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 22:40:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That is interesting. So I guess the conclusion to this is, softupdates > > is useful for bursty IO, but not sustained because it can get far behind > > until it eventually reaches the point where the machine reboots silently. > > I guess the delay until reboot is dependent on the size of max_softdeps. > > If it is big, it takes a while. > > I mentioned this a while back in the context of suspended I/O (in this > case, a RAID array busy dealing with a failed disk). There wasn't much > interest in dealing with it evinced at that point. (Obviously this implies that I can reproduce it at will, and will happily do so for anyone that wants it...) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 30 22:38: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from explorer.tip.CSIRO.AU (explorer.tip.CSIRO.AU [130.155.191.10]) by hub.freebsd.org (Postfix) with ESMTP id 0D56715533 for ; Thu, 30 Dec 1999 22:37:55 -0800 (PST) (envelope-from amy@explorer.tip.CSIRO.AU) Received: from explorer.tip.CSIRO.AU (localhost [127.0.0.1]) by explorer.tip.CSIRO.AU (8.9.3/8.9.1) with ESMTP id RAA16415; Fri, 31 Dec 1999 17:37:38 +1100 (EST) (envelope-from amy@explorer.tip.CSIRO.AU) Message-Id: <199912310637.RAA16415@explorer.tip.CSIRO.AU> To: Peter Wemm Cc: freebsd-hackers@freebsd.org Subject: Re: CD-RW long filenames/rw filesystem. In-reply-to: Your message of "Fri, 31 Dec 1999 12:53:07 +0800." <19991231045307.1749B1CA0@overcee.netplex.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16410.946622257.1@explorer.tip.CSIRO.AU> Date: Fri, 31 Dec 1999 17:37:37 +1100 From: "Shaun Amy, CSIRO TIP/ATNF" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"Shaun Amy, CSIRO TIP/ATNF" wrote: >> >A couple weeks ago I got a CD-RW drive, and decided to try it out under >> >all the different OS's I use. In FreeBSD, the only way (it seems) to use >> >it, is grab a bunch of stuff you want to backup/record and use mkisofs and >> >cdrecord to dump it onto a CD. Everything I read seemed to indicate that >> >this method limits you to the 8.3 filename format of iso9660 and all >> >Rockridge does is add file/group permissions and ownership. is there any >> >CD recording utilities/formats that can do long filenames (hopefully with >> >Unix permissions)? >> >> This is not correct. The initial ISO9660 standard did specify the 8.3 forma >t >> but there are now extensions that do what you describe. Recent versions of >> "mkisofs" support RockRidge (long filename under UNIX support) and Joliet >> (MS long filename support) so you are not restricted to the 8.3 format. I >> wrote a couple of CDs the other day under FreeBSD (3.4-STABLE) using >> "mkisofs" with RockRidge support and the long filenames work fine. As this >> was data from a UNIX system I wasn't concerned with Windows support. > >Not quite. According to mkisofs(1): > > -l Allow full 32 character filenames. Normally the > ISO9660 filename will be in an 8.3 format which is > compatible with MS-DOS, even though the ISO9660 > standard allows filenames of up to 32 characters. > If you use this option, the disc may be difficult > to use on a MS-DOS system, but this comes in handy > on some other systems (such as the Amiga). Use > with caution. > >It's depressing to see just how long the legacy of MS-DOS persists. :-( >The ISO9660 format supports 32 chars, but since nearly everything uses 8.3 >to be readable by MSCDEX and windoze, the 32 character names are rarely >implemented or well tested. Ah, I was thinking along the lines of: -J Generate Joliet directory records in addition to regular iso9660 file names. This is primarily use- ful when the discs are to be used on Windows-NT or Windows-95 machines. The Joliet filenames are specified in Unicode and each path component can be up to 64 Unicode characters long. and -R Generate SUSP and RR records using the Rock Ridge protocol to further describe the files on the iso9660 filesystem. -r This is like the -R option, but file ownership and modes are set to more useful values. The uid and gid are set to zero, because they are usually only useful on the author's system, and not useful to the client. All the file read bits are set true, so that files and directories are globally readable on the client. If any execute bit is set for a file, set all of the execute bits, so that executa- bles are globally executable on the client. If any search bit is set for a directory, set all of the search bits, so that directories are globally searchable on the client. All write bits are cleared, because the CD-Rom will be mounted read- only in any case. If any of the special mode bits are set, clear them, because file locks are not useful on a read-only file system, and set-id bits are not desirable for uid 0 or gid 0. This is from the man page for 1.12b5 of "mkisofs", which does have a rather large number of options :-) So you may well be correct Peter and probably have a lot more experience than I do with this having only had a CD-R/CD-RW for a bit over a week on my home systems although we have had them for some time at work. Regards, Shaun. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 3:55:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D220F14DEC; Fri, 31 Dec 1999 03:55:07 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA85550; Fri, 31 Dec 1999 12:54:57 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912311154.MAA85550@freebsd.dk> Subject: Re: soundcards needed to further newpcm development In-Reply-To: <19991229150918.A39443@dub.net> from Bill Swingle at "Dec 29, 1999 03:09:18 pm" To: unfurl@dub.net (Bill Swingle) Date: Fri, 31 Dec 1999 12:54:57 +0100 (CET) Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bill Swingle wrote: > > Below is a list of chipsets that we're still lacking. If you have any > cards that have these chips on them, and would like to see support for them > added or improved please consider sending them to us. Due to the > sheer number of cards we'll be handling and the fact that they'll > end up in the UK in the end, these cards will have to be donations > to the project or indefinate loans at least. > > via 82c686 no no no I've finally got the docs on that one (not thanks to VIA), so I have a pdf file for grabs... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 8:24:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 722A31548D for ; Fri, 31 Dec 1999 08:24:32 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 94F8624D04 for ; Fri, 31 Dec 1999 11:24:31 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id 8964C18605; Fri, 31 Dec 1999 11:24:21 -0500 (EST) Date: Fri, 31 Dec 1999 11:24:21 -0500 From: Keith Stevenson To: freebsd-hackers@freebsd.org Subject: Re: softupdates and debug.max_softdeps Message-ID: <19991231112421.A27070@osaka.louisville.edu> References: <19991231004902.01D721CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991231004902.01D721CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 31, 1999 at 08:49:01AM +0800, Peter Wemm wrote: > FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate > softupdates on the disk containing the postfix spool, the machine reboots > (silently if I recall correctly) within 5 minutes of postfix starting up. > > This is a much smaller system of course, with smaller memory and filesystem > working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post > this as a real-use datapoint. I'm using a postfix/FreeBSD 3.3-STABLE system as the central mail hub for the University of Louisville. I have softupdates enabled on the mail spool, I process about 75K messages per day, and I have absolutely no stability problems. The system is a PentiumPro 200 MHz with 128 MB RAM. Kernel was compiled on Sep 27 14:32:45 EDT 1999. This system in only a relay/router system. It handles no local deliveries. Just another real-use data point. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 9:19:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 695FC14DCC for ; Fri, 31 Dec 1999 09:19:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA83856; Fri, 31 Dec 1999 09:19:37 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Dec 1999 09:19:37 -0800 (PST) From: Matthew Dillon Message-Id: <199912311719.JAA83856@apollo.backplane.com> To: Keith Stevenson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: <19991231004902.01D721CA0@overcee.netplex.com.au> <19991231112421.A27070@osaka.louisville.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that all the reported problems so far are on -stable systems. I wonder if the same problem occurs under -current? Also, all the reported problems so far are under 3.3 (for example, hub is running 3.3-RC in a Sep 12 build). How about 3.4? It may be possible to mitigate the problem under 3.x systems by reducing vfs.lodirtybuffers and vfs.hidirtybuffers, and under 4.x systems by reducing vfs.hidirtybuffers (lodirtybuffers does not exist in 4.x). But I still don't know enough about the problem to be able to say anything authoritative. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 9:22:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 1B9A014A29 for ; Fri, 31 Dec 1999 09:22:49 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id C4A4824D50; Fri, 31 Dec 1999 12:22:47 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id 776E418605; Fri, 31 Dec 1999 12:22:47 -0500 (EST) Date: Fri, 31 Dec 1999 12:22:47 -0500 From: Keith Stevenson To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps Message-ID: <19991231122247.A27312@osaka.louisville.edu> References: <19991231004902.01D721CA0@overcee.netplex.com.au> <19991231112421.A27070@osaka.louisville.edu> <199912311719.JAA83856@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912311719.JAA83856@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 31, 1999 at 09:19:37AM -0800, Matthew Dillon wrote: > It seems that all the reported problems so far are on -stable > systems. I wonder if the same problem occurs under -current? > > Also, all the reported problems so far are under 3.3 (for example, > hub is running 3.3-RC in a Sep 12 build). How about 3.4? I am running 3.3 and everything is fine. I'm using IDE drives on my system, so I was wondering if they might be putting enough of a brake on the I/O subsystem to avoid the problem Peter is reporting. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 10:55:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E12A15107; Fri, 31 Dec 1999 10:55:19 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA84956; Fri, 31 Dec 1999 10:54:59 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Dec 1999 10:54:59 -0800 (PST) From: Matthew Dillon Message-Id: <199912311854.KAA84956@apollo.backplane.com> To: Peter Wemm Cc: Tom , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: <19991231004902.01D721CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate :softupdates on the disk containing the postfix spool, the machine reboots :(silently if I recall correctly) within 5 minutes of postfix starting up. : :This is a much smaller system of course, with smaller memory and filesystem :working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post :this as a real-use datapoint. :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au :... :Tom wrote: :> Yes, postmark operates on the same file set. I used the following :> postmark settings: :> :> set number 30000 :> set transactions 4000000 :> set size 1500 200000 :... I'm running the postmark test on my 3.x and 4.x test boxes now using a large softupdates partition (33G on each) and large memory (512M and 1G) configuration. The 4.x box seems to have stabilized at around 14MB of KVM, the 3.x box seems to have stabilized at around 9MB of KVM. I'll leave it running for a while to see if there are any memory leaks and then try reducing debug.max_softdeps to see what happens. We are still looking for panic messages. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 11:47:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 7AA7214F3E; Fri, 31 Dec 1999 11:47:11 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 12480l-0004bV-00; Fri, 31 Dec 1999 11:46:55 -0800 Date: Fri, 31 Dec 1999 11:46:52 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Matthew Dillon Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <199912311854.KAA84956@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Dec 1999, Matthew Dillon wrote: > :FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate > :softupdates on the disk containing the postfix spool, the machine reboots > :(silently if I recall correctly) within 5 minutes of postfix starting up. > : > :This is a much smaller system of course, with smaller memory and filesystem > :working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post > :this as a real-use datapoint. > :Cheers, > :-Peter > :-- > :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > :... > :Tom wrote: > :> Yes, postmark operates on the same file set. I used the following > :> postmark settings: > :> > :> set number 30000 > :> set transactions 4000000 > :> set size 1500 200000 > :... > > I'm running the postmark test on my 3.x and 4.x test boxes now using > a large softupdates partition (33G on each) and large memory (512M and 1G) > configuration. How many instances of postmark are you running? I used 4 separate instances (you must run them in separate directories). How fast are your disks? I used an external RAID-5 array that appears as single disk to FreeBSD. It is RAID-5, so the performance isn't that great for writing. I think my virtual disk is quite slow. If your system has fast disks, run more instances of postmark. > The 4.x box seems to have stabilized at around 14MB of KVM, the 3.x box > seems to have stabilized at around 9MB of KVM. I'll leave it running > for a while to see if there are any memory leaks and then try reducing > debug.max_softdeps to see what happens. > > We are still looking for panic messages. Well, I lost last nights panic because of fsck complaining about several million unreferenced files. I'm going to log to disk next time. > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 11:50:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A40491557A; Fri, 31 Dec 1999 11:50:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA85337; Fri, 31 Dec 1999 11:50:39 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Dec 1999 11:50:39 -0800 (PST) From: Matthew Dillon Message-Id: <199912311950.LAA85337@apollo.backplane.com> To: Tom Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : How many instances of postmark are you running? I used 4 separate :instances (you must run them in separate directories). Well, you didn't say that! :-) I'm running one. I'll start up another couple to match your test. : How fast are your disks? I used an external RAID-5 array that appears :as single disk to FreeBSD. It is RAID-5, so the performance isn't that :great for writing. I think my virtual disk is quite slow. If your system :has fast disks, run more instances of postmark. Fast. Two striped 18G seacrates on each system 40 MB/sec SCSI bus on one system, 80 MB/sec SCSI bus on the other. : : Well, I lost last nights panic because of fsck complaining about several :million unreferenced files. I'm going to log to disk next time. : :Tom :Uniserve Ach. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 11:59:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E9FE914F29 for ; Fri, 31 Dec 1999 11:59:50 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p26-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.123]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id EAA15099; Sat, 1 Jan 2000 04:59:42 +0900 (JST) Message-ID: <386D0B2C.8F29EDE3@newsguy.com> Date: Sat, 01 Jan 2000 04:59:40 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Bjorn Danielsson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UTC time in crontabs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bjorn Danielsson wrote: > > I have made a small patch (about 10 lines of code) to "cron" that lets > people choose between localtime and gmtime for their crontab entries. > The choice is made depending on the setting of an environment variable > in the crontab file. The cost is a factor 2 for the tiny amount of work > that cron does when it checks all the crontab entries every minute. > > Any interest in this? I like it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Nice try, Lao Che." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 15:33: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 3695915124 for ; Fri, 31 Dec 1999 15:33:07 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA02757 for FreeBSD-hackers@freebsd.org; Sat, 1 Jan 2000 00:23:54 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA52028 for FreeBSD-hackers@freebsd.org; Sat, 1 Jan 2000 00:25:22 +0100 (CET) (envelope-from wilko) Date: Sat, 1 Jan 2000 00:25:21 +0100 From: Wilko Bulte To: FreeBSD hackers list Subject: YES: it works.. Message-ID: <20000101002521.A51978@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fri Dec 31 23:59:56 CET 1999 Fri Dec 31 23:59:57 CET 1999 Fri Dec 31 23:59:58 CET 1999 Fri Dec 31 23:59:59 CET 1999 Sat Jan 1 00:00:00 CET 2000 Sat Jan 1 00:00:01 CET 2000 Sat Jan 1 00:00:02 CET 2000 Sat Jan 1 00:00:03 CET 2000 In short: yes it works. Happy New Millenium to all of you! -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 16:54:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 836A214CFA for ; Fri, 31 Dec 1999 16:54:26 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA01155; Fri, 31 Dec 1999 16:54:25 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA41994; Fri, 31 Dec 1999 16:54:24 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 31 Dec 1999 16:54:24 -0800 (PST) Message-Id: <200001010054.QAA41994@vashon.polstra.com> To: wilko@yedi.iaf.nl Subject: Re: YES: it works.. In-Reply-To: <20000101002521.A51978@yedi.iaf.nl> References: <20000101002521.A51978@yedi.iaf.nl> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000101002521.A51978@yedi.iaf.nl>, Wilko Bulte wrote: > Fri Dec 31 23:59:56 CET 1999 > Fri Dec 31 23:59:57 CET 1999 > Fri Dec 31 23:59:58 CET 1999 > Fri Dec 31 23:59:59 CET 1999 > Sat Jan 1 00:00:00 CET 1900 > Sat Jan 1 00:00:01 CET 1900 > Sat Jan 1 00:00:02 CET 1900 > Sat Jan 1 00:00:03 CET 1900 ^^^^ > > In short: yes it works. > > Happy New Millenium to all of you! Huh? That doesn't look so good to me! (Just kidding, just kidding. ;-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 18:28:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 47D681511F for ; Fri, 31 Dec 1999 18:28:08 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 3.03 #3) id 124EH0-0000Bu-00 for freebsd-hackers@FreeBSD.ORG; Fri, 31 Dec 1999 19:28:06 -0700 Message-ID: <386D66D4.B3DB5EB3@softweyr.com> Date: Fri, 31 Dec 1999 19:30:44 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C789C.DD290597@softweyr.com> <385F2FFD.CA594829@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Prices have fallen a lot in the last year. I'm happy to be able to > get rid of my HUBs, I was constantly having to deal with packet loss > when running saturation tests and never able to figure out what > was causing it. I have a good reason to revive this thread. I thought anyone who followed this conversation might want to know that one of the switches we dicussed, the Netgear FS-105, is on a special at CompUSA right now -- THROUGH TOMORROW. The special is a $20 mail-in rebate, making the price of the switch $99.99 in the CompUSA stores. I haven't had a chance to put this through it's paces, but I bought 2 earlier today, one for me and one for a friend. When I get back to the test lab on Monday, I'll hook it up to a SmartBits and make it sweat. If you're looking for a nice little 5-port 100Base-TX switch, this is a good opportunity (if you have a CompUSA store nearby). -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 20:39:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mx0.scr3am.com (ns0.scr3am.com [209.235.34.130]) by hub.freebsd.org (Postfix) with ESMTP id 3577414D7C for ; Fri, 31 Dec 1999 20:39:08 -0800 (PST) (envelope-from ph0d@sweb.com) Received: from localhost (ph0d@localhost) by mx0.scr3am.com (8.10.0.Beta10/8.10.0.Beta6+[rimalz]) with ESMTP id e014cHY29800; Fri, 31 Dec 1999 23:38:17 -0500 Date: Fri, 31 Dec 1999 23:38:17 -0500 (EST) From: X-Sender: ph0d@vanity.scr3am.com To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price In-Reply-To: <386D66D4.B3DB5EB3@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got one currently and my FreeBSD box can do 3000-3300kBytes a second without any complaints.. Full duplex has it's advantages, no doubt On Fri, 31 Dec 1999, Wes Peters wrote: > Matthew Dillon wrote: > > Prices have fallen a lot in the last year. I'm happy to be able to > > get rid of my HUBs, I was constantly having to deal with packet loss > > when running saturation tests and never able to figure out what > > was causing it. > > I have a good reason to revive this thread. I thought anyone who followed > this conversation might want to know that one of the switches we dicussed, > the Netgear FS-105, is on a special at CompUSA right now -- THROUGH TOMORROW. > The special is a $20 mail-in rebate, making the price of the switch $99.99 > in the CompUSA stores. > > I haven't had a chance to put this through it's paces, but I bought 2 > earlier today, one for me and one for a friend. When I get back to the > test lab on Monday, I'll hook it up to a SmartBits and make it sweat. > > If you're looking for a nice little 5-port 100Base-TX switch, this is a > good opportunity (if you have a CompUSA store nearby). > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > wes@softweyr.com http://softweyr.com/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 31 20:50:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 4F6D014A2C; Fri, 31 Dec 1999 20:48:39 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA15989; Sat, 1 Jan 2000 15:18:26 +1030 (CST) Date: Sat, 1 Jan 2000 15:18:26 +1030 From: Greg Lehey To: Mike Smith Cc: Tom , freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps Message-ID: <20000101151826.L1528@freebie.lemis.com> References: <199912310634.WAA00620@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912310634.WAA00620@mass.cdrom.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 30 December 1999 at 22:34:04 -0800, Mike Smith wrote: >> That is interesting. So I guess the conclusion to this is, softupdates >> is useful for bursty IO, but not sustained because it can get far behind >> until it eventually reaches the point where the machine reboots silently. >> I guess the delay until reboot is dependent on the size of max_softdeps. >> If it is big, it takes a while. > > I mentioned this a while back in the context of suspended I/O (in this > case, a RAID array busy dealing with a failed disk). There wasn't much > interest in dealing with it evinced at that point. On a related topic, I've taken to limiting the number of outstanding transactions in Vinum, mainly to try to hunt down some strange consistency problems when a very large number of transactions were outstanding (for those of you who have been following this, this was the "NULL b_biodone" syndrome). I still think there is a problem hidden in the system which causes this. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message