From owner-freebsd-hackers Sun Mar 14 0:42:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 245FF14D68 for ; Sun, 14 Mar 1999 00:42:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA89134; Sun, 14 Mar 1999 00:42:25 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 00:42:25 -0800 (PST) From: Matthew Dillon Message-Id: <199903140842.AAA89134@apollo.backplane.com> To: Wes Peters Cc: Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903140500.VAA73230@rah.star-gate.com> <36EB482B.14BD236@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :An article in IEEE Computer magazine last summer reported achieving :320 Mb/s throughput with Myricom Myrinet boards on FreeBSD. I've :seen this number batted around industry publications like Network :World a number of times also. That would seem to require only a 10 :Mhz clock with a 32-bit bus bandwidth; is there really this much :overhead in the PCI transactions? : :-- : "Where am I, and what am I doing in this handbasket?" : :Wes Peters Softweyr LLC :http://www.softweyr.com/~softweyr wes@softweyr.com Well, a PCI bus can do 32 bits and 33 MHz, or 132 MBytes/sec. However, it takes a couple of clocks to setup a burst transfer so you can only get close to this number if the card uses reasonably-sized bursts ( e.g. 16 4-byte words per burst or better ). This, in turn, depends heavily on the card in question. Nearly all PCI cards have FIFOs, but aggregate performance with multiple cards depends heavily on the burst characteristics of the cards. Most network cards must DMA into main memory -- card-to-card transfers cannot be done. So routing a single packet requires the data to flow over the PCI bus twice. The 132 MBytes/sec become 66 MBytes/sec right off the bat. There is also the problem of per-packet interrupt overhead. This can be seriously limiting when used with cards that require lots of PCI I/O transactions to process a packet ( verses cards that put most of the information in main memory as part of the DMA chain and require a PCI I/O only to handle special cases ). -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 Sun Mar 14 1: 9: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id D208314FBB for ; Sun, 14 Mar 1999 01:08:58 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id EAA23610; Sun, 14 Mar 1999 04:12:42 -0500 (EST) Date: Sun, 14 Mar 1999 04:12:41 -0500 (EST) From: Alfred Perlstein To: Kent Vander Velden Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable In-Reply-To: <199903140421.WAA15614@isua3.iastate.edu> 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, 13 Mar 1999, Kent Vander Velden wrote: > > >As a temporary workaround please disable the screen saver code. > >I was having the same problems with 4.0 and taking out the saver > >module kept my machine from crashing. > > > >As far as the linux emulation... The same box that i disabled the > >screen saver is also running the linux module. It's still running > >it and seems stable, however the linux code itself is not being > >used, it's just loaded (i don't have any linux apps to test). > > Does this mean not loading a module or disabling the splash > pseudo-device? While both machines have the splash pseudo > device, only the 486 actually loads a screen saver module. > The dual-p133 does not load a screen saver and it crashes. The > dual-p133 loads the linux module but the functionality is > not used. Someone else suggested removing splash from your config for the time being, I agree. > > >I suggest you check if your kernels are being compiled with > >INVARIANTS or something of the likes, kernels compiled with > >these options mixed with modules that don't can crash your machine > >afaik. > > INVARIANTS and other similar diagnostic code switches are not > enabled on either machine. > > When the dual-p133 crashes the text screen is completely screwed > up. The machine is normally running X and the it crashes the screen > goes blank. The reboot cycle completes and an OS is loaded. During > the reboot cycle I nothing on the screen. If FreeBSD loads I see > nothing. If NT loads I see nothing until the login screen. If I reboot > NT I see nothing until NT loads again. Simply, when FreeBSD crashes > on this machine while in X (and perhaps when not in X) no text mode > screen is visible. So, even if DDB does kick in on this machine > I would have not way of seeing the text. > > Can the text mode problem be fixed? You seem to have a lame card that doesn't reset itself properly. If you want to see debugging output use a serial consol. Speaking of screen savers on servers, I heard a story about some dolt who set the company's NT server's screen saver to a GL saver, totally killed the box until they turned it off. The kicker? i think it was a headless box... :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 1:29:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 6506A14F33 for ; Sun, 14 Mar 1999 01:28:55 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id BAA85633; Sun, 14 Mar 1999 01:27:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903140927.BAA85633@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Wes Peters , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Sun, 14 Mar 1999 00:42:25 PST." <199903140842.AAA89134@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 01:27:49 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Most network cards must DMA into main memory -- card-to-card transfers > cannot be done. So routing a single packet requires the data to flow > over the PCI bus twice. The 132 MBytes/sec become 66 MBytes/sec right > off the bat. I am not sure that I can follow you here . Most PCI cards which are capable of doing dma to the host system's memory can do card - to - card transfer ;however, the target "card" most be able to use the stored data in the case of a network card it must have memory to receive the pack or a very elaborate protocol to accept short dma bursts which it can then process. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 1:53:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obr.software602.cz (unknown [194.108.5.200]) by hub.freebsd.org (Postfix) with ESMTP id 4C21B14DFB for ; Sun, 14 Mar 1999 01:53:20 -0800 (PST) (envelope-from bsd@obr.software602.cz) Received: from localhost (bsd@localhost) by obr.software602.cz (8.9.2/8.9.2) with ESMTP id KAA04961 for ; Sun, 14 Mar 1999 10:49:38 +0100 (CET) (envelope-from bsd@obr.software602.cz) Date: Sun, 14 Mar 1999 10:49:36 +0100 (CET) From: FreeBsd To: freebsd-hackers@FreeBSD.ORG Subject: thread and socket In-Reply-To: <199903140842.AAA89134@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 Hi, in some small application I use receive socket with setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO, &tv, sizeof(tv)); and recvfrom is waiting and after tv finish with EAGAIN. It is well in no thread version. In threaded version recvfrom is waiting and waiting and... without finish (or recevie data well). Is this problem colision on user timers or some blocking (or other)? How can I secure stop recvfrom from another thread? Thanks, Honza (version 2.2.8 and 3.1 - It's a same problem) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 3:38:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mw5.texas.net (mw5.texas.net [206.127.30.15]) by hub.freebsd.org (Postfix) with ESMTP id 4495B14BE4 for ; Sun, 14 Mar 1999 03:38:32 -0800 (PST) (envelope-from rsnow@lgc.com) Received: from basil.dympna.COM (mnet06-30.sat.texas.net [209.99.48.198]) by mw5.texas.net (2.4/2.4) with ESMTP id FAA01122; Sun, 14 Mar 1999 05:38:12 -0600 (CST) Received: from solo (solo [134.132.228.3]) by basil.dympna.COM (8.9.1/8.8.7) with SMTP id FAA30428; Sun, 14 Mar 1999 05:38:10 -0600 (CST) (envelope-from rsnow@lgc.com) Message-ID: <001b01be6e10$08061120$03e48486@dympna.com> From: "Rob Snow" To: "Amancio Hasty" , "Cory Kempf" Cc: "Bill Paul" , Subject: Re: Gigabit ethernet -- what am I doing wrong? Date: Sun, 14 Mar 1999 05:44:28 -0600 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.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking at this wondering a couple of things. How many mem copies take place in the IP stack before we're ready to transmit a frame? My question is based around whether it's the NIC's or the IP stacks and PCI holding us back. What would PCI-64@66 do for us with current stacks? -Rob ----- Original Message ----- From: Cory Kempf To: Amancio Hasty Cc: Bill Paul ; Sent: Saturday, March 13, 1999 11:22 PM Subject: Re: Gigabit ethernet -- what am I doing wrong? >Amancio Hasty writes: > >> > 200 Mb/s = 25 MB/s, which seems a little low, but is within the realm of >> > what I would expect. >> >> I think the system should be able to support at least 70MB/s at least I >> do over here >> with a bt848 video capture board capturing 640x480x4 at 30 frames per second >> and then displaying the frames on video display card 8) > >A video capture board is generally moving bulk data without any protocol >in the way. It is idealy suited for getting maximal bandwidth from PCI, >as you can essentially set up the transfer, then just let it run. > >With an ethernet driver, though, there is often additional host<->card >traffic, such as telling the card "here is some data", the card responding >"Ok, I am done with it", etc. Additionally, the protocol doesn't lend >itself to exclusively bulk data transfers. ARP and other overhead will >eat up a lot of that theoretical bandwidth. > >So, if you are seeing 70 MB/s with video, where you can probably get by >with a single ACK between frames -- i.e. 2 bus operations / block -- it >wouldn't surprise me to see an ethernet card, with a protocol that might >require five bus operations / block getting less. > >Remember too, that trip through the protocol stack was only a little >over 50 MB/s... > >+C > >-- >Thinking of purchasing RAM from the Chip Merchant? >Please read this first: > >Cory Kempf Macintosh / Unix Consulting & Software Development >ckempf@enigami.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 Sun Mar 14 4:19: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 7F3D014CD1 for ; Sun, 14 Mar 1999 04:19:00 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA30372 for ; Sun, 14 Mar 1999 22:49:40 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA14397; Sun, 14 Mar 1999 22:48:26 +0930 Date: Sun, 14 Mar 1999 22:48:24 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: hackers@freebsd.org Subject: Stripping a.out binaries 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 porting a utility which is distributed in a.out binary form, which 'install -s' is choking over (File format not recognised). How can I strip(1) an a.out executable, and can install(1) be fixed to DTRT? nftp: FreeBSD/i386 compact demand paged dynamically linked executable Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 5:35:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id E5A1314DCA for ; Sun, 14 Mar 1999 05:33:52 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id OAA17434; Sun, 14 Mar 1999 14:33:29 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id OAA01311; Sun, 14 Mar 1999 14:24:38 +0100 (CET) (envelope-from andreas) Date: Sun, 14 Mar 1999 14:24:37 +0100 From: Andreas Klemm To: Rob Snow Cc: Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? Message-ID: <19990314142436.A1292@titan.klemm.gtn.com> References: <001b01be6e10$08061120$03e48486@dympna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <001b01be6e10$08061120$03e48486@dympna.com>; from Rob Snow on Sun, Mar 14, 1999 at 05:44:28AM -0600 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 14, 1999 at 05:44:28AM -0600, Rob Snow wrote: > I'm looking at this wondering a couple of things. How many mem copies take > place in the IP stack before we're ready to transmit a frame? My question > is based around whether it's the NIC's or the IP stacks and PCI holding us > back. What would PCI-64@66 do for us with current stacks? AFAIK "zero copy tcp/ip" went into 3.1 and 4.0. Thanks to David Greenman who implemented and tested this on ftp.cdrom.com. (I hope I got the credits right ;-) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 6: 7:58 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 C329714EF3 for ; Sun, 14 Mar 1999 06:07:56 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA15838; Sun, 14 Mar 1999 23:07:38 +0900 (JST) Message-ID: <36EB9871.C162E3C1@newsguy.com> Date: Sun, 14 Mar 1999 20:07:29 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Tony Overfield Cc: Florin Nicolescu , FreeBSD-hackers Subject: Re: Y2K bug References: <199903120731.JAA11891@nick.ro> <3.0.6.32.19990312124719.03ba4b00@bugs.us.dell.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Overfield wrote: > > >In message <199903120731.JAA11891@nick.ro> Florin Nicolescu writes: > > > > According to the discontinuities in the earth move around the sun, > > Of course, this is wrong too. A year doesn't come out to a whole > number of days, so adjustments are made whenever the error builds > up sufficiently. Besides, there are no discontinuities in any stellar bodies movement. If you found it to be otherwise, you are probably in for a Nobel prize. :-) Now, if you mean irregularities... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "My theory is that his ignorance clouded his poor judgment." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 6:27: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 2E8A614E0E; Sun, 14 Mar 1999 06:24:45 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id QAA11607; Sun, 14 Mar 1999 16:24:20 +0200 (EET) (envelope-from ru) Date: Sun, 14 Mar 1999 16:24:19 +0200 From: Ruslan Ermilov To: dg@freebsd.org Cc: hackers@freebsd.org Subject: Re: ipflow and ipfirewall Message-ID: <19990314162419.A10242@relay.ucb.crimea.ua> Mail-Followup-To: dg@freebsd.org, hackers@FreeBSD.ORG References: <19990313200150.A83040@relay.ucb.crimea.ua> <199903131819.TAA29395@rt2.synx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199903131819.TAA29395@rt2.synx.com>; from Remy Nonnenmacher on Sat, Mar 13, 1999 at 07:11:19PM +0100 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 13, 1999 at 07:11:19PM +0100, Remy Nonnenmacher wrote: > On 13 Mar, Ruslan Ermilov wrote: > > Hi! > > > > I thought about starting to use fast IP forwarding, but... > > > > It seems that such "fast forwardable" packets, when passed from > > ether_input(), for example, just simply bypass all firewall checks. > > > > Am I right? > > > > you are. > It's a big security leak... David, was it supposed by design (that such packets bypass firewall)? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 6:33:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32]) by hub.freebsd.org (Postfix) with ESMTP id 25F2914E74 for ; Sun, 14 Mar 1999 06:33:27 -0800 (PST) (envelope-from myself@conterra.com) Received: from dmaddox.conterra.com (myself@dmaddox.conterra.com [209.12.169.48]) by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id JAA29875; Sun, 14 Mar 1999 09:33:07 -0500 (EST) Received: (from myself@localhost) by dmaddox.conterra.com (8.9.3/8.9.1) id JAA00727; Sun, 14 Mar 1999 09:33:11 -0500 (EST) (envelope-from myself) Date: Sun, 14 Mar 1999 09:33:11 -0500 From: "Donald J . Maddox" To: Kris Kennaway Cc: hackers@FreeBSD.ORG Subject: Re: Stripping a.out binaries Message-ID: <19990314093310.A561@dmaddox.conterra.com> Reply-To: dmaddox@conterra.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kris Kennaway on Sun, Mar 14, 1999 at 10:48:24PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can use 'strip -aout ' to strip it. As far as I know, there is currently no way to specify the executable format to 'install -s'. I haven't tried it, but you might be able to use the OBJFORMAT or OBJECT_FORMAT (not sure which form is correct) environment variable to make install DTRT for aout. On Sun, Mar 14, 1999 at 10:48:24PM +0930, Kris Kennaway wrote: > I'm porting a utility which is distributed in a.out binary form, which > 'install -s' is choking over (File format not recognised). How can I strip(1) > an a.out executable, and can install(1) be fixed to DTRT? > > nftp: FreeBSD/i386 compact demand paged dynamically linked executable > > Kris > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. > > > > 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 Sun Mar 14 6:37: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id D73AC14F20 for ; Sun, 14 Mar 1999 06:36:58 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 3443 invoked by uid 1001); 14 Mar 1999 14:36:39 +0000 (GMT) To: ru@ucb.crimea.ua Cc: dg@freebsd.org, hackers@freebsd.org Subject: Re: ipflow and ipfirewall From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 14 Mar 1999 16:24:19 +0200" References: <19990314162419.A10242@relay.ucb.crimea.ua> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 14 Mar 1999 15:36:38 +0100 Message-ID: <3441.921422198@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > It seems that such "fast forwardable" packets, when passed from > > > ether_input(), for example, just simply bypass all firewall checks. > > > > > > Am I right? > > > > > > > you are. > > > > It's a big security leak... > David, was it supposed by design (that such packets bypass firewall)? The way I see it, "fast forward" would be for router boxes at the core of your network. Here you're concerned about speed. Firewall filtering you normally want to do at the edges, where you're not so concerned about speed. Personally, I think it's a sensible tradeoff. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 8:11:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 012C714DA4; Sun, 14 Mar 1999 08:09:23 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id SAA07744; Sun, 14 Mar 1999 18:08:52 +0200 (EET) (envelope-from ru) Date: Sun, 14 Mar 1999 18:08:52 +0200 From: Ruslan Ermilov To: sheldonh@freebsd.org Cc: FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings Message-ID: <19990314180852.A7460@relay.ucb.crimea.ua> Mail-Followup-To: sheldonh@freebsd.org, FreeBSD Hackers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! You wrote: State-Changed-From-To: open->closed State-Changed-By: sheldonh State-Changed-When: Sun Mar 14 04:26:00 PST 1999 State-Changed-Why: See ftp://ftp.freebsd.org/pub/FreeBSD/3.1-RELEASE/ERRATA.TXT o Kernel change information is not saved in the new kernel, even though this is claimed to work in the docs. Fix: The change information is being written out, in fact, but to the wrong location. move /kernel.config to /boot/kernel.conf (if it exists, otherwise there were no changes to save) and add the following lines to /boot/loader.rc: load /kernel load -t userconfig_script /boot/kernel.conf autoboot 5 This will cause the kernel change information to be read in and used properly (and you just learned a little about the new 3-stage loader in the process, so the exercise wasn't a total loss). ---------------------------------------- I can't get your fix to work. I've made `boot -c' changes, and `sysctl machdep.uc_devlist' produces non-null output, but the /kernel.config is empty. Any clue? Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 8:20:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 9639B14F2F; Sun, 14 Mar 1999 08:19:19 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id SAA02248; Sun, 14 Mar 1999 18:18:53 +0200 (EET) (envelope-from ru) Date: Sun, 14 Mar 1999 18:18:51 +0200 From: Ruslan Ermilov To: Robert Nordier Cc: FreeBSD Hackers Subject: [BTX loader]: boot command doesn't work as expected Message-ID: <19990314181851.A890@relay.ucb.crimea.ua> Mail-Followup-To: Robert Nordier , FreeBSD Hackers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! boot -c - works boot /kernel - works boot -c /kernel - doesn't work Any clue? Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 8:22:11 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 CBF2715012 for ; Sun, 14 Mar 1999 08:21:59 -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 2.12 #1) id 10MDdz-0009Da-00 for hackers@freebsd.org; Sun, 14 Mar 1999 18:21:39 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Proposal: Define MAXMEM in GENERIC Date: Sun, 14 Mar 1999 18:21:38 +0200 Message-ID: <35437.921428498@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, The originator of PR i386/9755 (which related to a 3.0-RELEASE install failure) has made a valid point. We know that some people with >64MB RAM are going to have trouble with the speculative memory probe while installing FreeBSD with the GENERIC (here read any release) kernel. So why don't we add to GENERIC the following line? options "MAXMEM=(64*1024)" The major argument that comes to mind immediately is that people are going to end up running sub-optimal servers out-of-the-box. However, the change is supported by the following mindset: Gain: Make things easier for people with broken hardware. Cost: Annoy the people who have large memory configurations and who don't build custom kernels. I'm of the opinion that we're talking about a number of annoyed people so small that the gain is justified. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 8:31:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 8A44A14FED for ; Sun, 14 Mar 1999 08:31:44 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id KAA03533; Sun, 14 Mar 1999 10:31:10 -0600 (CST) Message-ID: <19990314103110.A3526@Denninger.Net> Date: Sun, 14 Mar 1999 10:31:10 -0600 From: Karl Denninger To: Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC References: <35437.921428498@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <35437.921428498@axl.noc.iafrica.com>; from Sheldon Hearn on Sun, Mar 14, 1999 at 06:21:38PM +0200 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 14, 1999 at 06:21:38PM +0200, Sheldon Hearn wrote: > > Hi folks, > > The originator of PR i386/9755 (which related to a 3.0-RELEASE install > failure) has made a valid point. > > We know that some people with >64MB RAM are going to have trouble with > the speculative memory probe while installing FreeBSD with the GENERIC > (here read any release) kernel. So why don't we add to GENERIC the > following line? > > options "MAXMEM=(64*1024)" > > The major argument that comes to mind immediately is that people are > going to end up running sub-optimal servers out-of-the-box. However, the > change is supported by the following mindset: > > Gain: > Make things easier for people with broken hardware. > > Cost: > Annoy the people who have large memory configurations and who > don't build custom kernels. > > I'm of the opinion that we're talking about a number of annoyed people > so small that the gain is justified. > > Ciao, > Sheldon. I would agree with that. Anyone using FreeBSD in that kind of a production environment where this is important (ie: big file or web servers) almost certainly has to build a custom kernel for OTHER reasons (like increasing the number of MBUF clusters). Therefore, they won't be running GENERIC, and therefore, this won't bite them after initial installation. However, it will greatly increase the odds that an initial install will work, which is the point if we want better penetration among people who don't "understand these things". -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 8:56:48 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 9ABCF1503F for ; Sun, 14 Mar 1999 08:56:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA09718; Mon, 15 Mar 1999 01:56:10 +0900 (JST) Message-ID: <36EBE9D6.7E6320FE@newsguy.com> Date: Mon, 15 Mar 1999 01:54:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC References: <35437.921428498@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm against this. Magazines test OS as they come out of the box. I'm no "all in the name of marketing and market share" zealot, but this would mean that *EVERY* benchmark we get in would be stacked against us. Sheldon Hearn wrote: > > Hi folks, > > The originator of PR i386/9755 (which related to a 3.0-RELEASE install > failure) has made a valid point. > > We know that some people with >64MB RAM are going to have trouble with > the speculative memory probe while installing FreeBSD with the GENERIC > (here read any release) kernel. So why don't we add to GENERIC the > following line? > > options "MAXMEM=(64*1024)" > > The major argument that comes to mind immediately is that people are > going to end up running sub-optimal servers out-of-the-box. However, the > change is supported by the following mindset: > > Gain: > Make things easier for people with broken hardware. > > Cost: > Annoy the people who have large memory configurations and who > don't build custom kernels. > > I'm of the opinion that we're talking about a number of annoyed people > so small that the gain is justified. > > Ciao, > Sheldon. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 9: 0:25 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 6AD5515129 for ; Sun, 14 Mar 1999 09:00:22 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA09905; Mon, 15 Mar 1999 01:59:12 +0900 (JST) Message-ID: <36EBEA87.66E7BF16@newsguy.com> Date: Mon, 15 Mar 1999 01:57:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Ruslan Ermilov Cc: FreeBSD Hackers Subject: Re: [BTX loader]: boot command doesn't work as expected References: <19990314181851.A890@relay.ucb.crimea.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > Hi! > > boot -c - works > boot /kernel - works > boot -c /kernel - doesn't work > > Any clue? You mean it doesn't work as _you_ expect it to? :-) help boot Boot boots. The -c flag is to be passed to the kernel, not to the command boot. boot /kernel -c -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 9: 6:52 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 DA09514FDF for ; Sun, 14 Mar 1999 09:05:58 -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 2.12 #1) id 10MEK8-000GRW-00; Sun, 14 Mar 1999 19:05:12 +0200 From: Sheldon Hearn To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-reply-to: Your message of "Mon, 15 Mar 1999 01:54:46 +0900." <36EBE9D6.7E6320FE@newsguy.com> Date: Sun, 14 Mar 1999 19:05:12 +0200 Message-ID: <63209.921431112@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Mar 1999 01:54:46 +0900, "Daniel C. Sobral" wrote: > I'm against this. Magazines test OS as they come out of the box. This was the argument I raised in my original mail. However, it looks pretty ugly on paper: It is quite possible that you will have problems installing FreeBSD on your high-end machine, but you'll have great benchmarks once you do. ;-) Anyway, I'm loath for this to turn into an unproductive flame war, so I won't try to argue an opinion I've already put forward. Instead, I ask whether there's any other solution you can think of, since we're likely to see more and more people having problems related to failed speculative memory probes as >64MB machines become entry-level. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 9:16:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 128D714C10 for ; Sun, 14 Mar 1999 09:16:23 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id MAA22243; Sun, 14 Mar 1999 12:13:57 -0500 (EST) Date: Sun, 14 Mar 1999 12:13:57 -0500 (EST) From: Chuck Robey To: Sheldon Hearn Cc: "Daniel C. Sobral" , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-Reply-To: <63209.921431112@axl.noc.iafrica.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 Sun, 14 Mar 1999, Sheldon Hearn wrote: > > > On Mon, 15 Mar 1999 01:54:46 +0900, "Daniel C. Sobral" wrote: > > > I'm against this. Magazines test OS as they come out of the box. > > This was the argument I raised in my original mail. However, it looks > pretty ugly on paper: > > It is quite possible that you will have problems installing > FreeBSD on your high-end machine, but you'll have great > benchmarks once you do. > > ;-) > > Anyway, I'm loath for this to turn into an unproductive flame war, so > I won't try to argue an opinion I've already put forward. Instead, I > ask whether there's any other solution you can think of, since we're > likely to see more and more people having problems related to failed > speculative memory probes as >64MB machines become entry-level. There seems to be a pretty easy solution. It hasn't been done, but it's perfectly possible, and probably desireable, to go from having just one GENERIC to having two. Having a GENERIC_BIG would solve both your problems, and create very little bloat, wouldn't it? This would be a Jordan-problem, I think. Maybe it would create other problems with regards to installation, I don't know. It doesn't immediately appear ridiculous, tho. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 9:21:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 2872D15486 for ; Sun, 14 Mar 1999 09:21:47 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA272710035; Sun, 14 Mar 1999 11:47:15 -0500 Date: Sun, 14 Mar 1999 11:47:14 -0500 (EST) From: Bill Fumerola To: Alfred Perlstein Cc: Kent Vander Velden , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable 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 Sun, 14 Mar 1999, Alfred Perlstein wrote: > Speaking of screen savers on servers, I heard a story about > some dolt who set the company's NT server's screen saver to > a GL saver, totally killed the box until they turned it off. Our Lotus Notes and PDC/File Server had GL screen savers set until one day I walked by the closet that they were in and saw this. I considered leaving it just to let it crash so I could say "See!", but I didn't want all the phone calls that afternoon. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Mar 14 9:46:30 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 63A8314F9D for ; Sun, 14 Mar 1999 09:46:15 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA13296; Mon, 15 Mar 1999 02:45:54 +0900 (JST) Message-ID: <36EBF581.FE962C9D@newsguy.com> Date: Mon, 15 Mar 1999 02:44:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Sheldon Hearn , hackers@freebsd.org Subject: Re: Proposal: Define MAXMEM in GENERIC References: <63209.921431112@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > This was the argument I raised in my original mail. However, it looks Sorry, I missed it... :-( > Anyway, I'm loath for this to turn into an unproductive flame war, so > I won't try to argue an opinion I've already put forward. Instead, I > ask whether there's any other solution you can think of, since we're > likely to see more and more people having problems related to failed > speculative memory probes as >64MB machines become entry-level. As >64Mb machines become entry level, I expect them to start to get their acts together. It's not only FreeBSD that has trouble with troubled hardware, and it will bite the makers otherwise. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 10:20: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id A6EC614E7E for ; Sun, 14 Mar 1999 10:20:01 -0800 (PST) (envelope-from mtaylor@cybernet.com) Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by gateway.cybernet.com (8.8.8/8.8.8) with SMTP id NAA19407; Sun, 14 Mar 1999 13:19:05 -0500 (EST) (envelope-from mtaylor@cybernet.com) Date: Sun, 14 Mar 1999 13:19:05 -0500 (EST) From: "Mark J. Taylor" To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-Reply-To: <35437.921428498@axl.noc.iafrica.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 It is trivial (we did it for 2.2.x) to add a boot option to always, or never, perform a speculative memory probe. For our NetMAX product (shameless plug: http://www.netmax.com/), which is 2.2.7+ based (we're working on a 3.1 version), we've added two additional boot options: 1) -M always perform speculative memory probe 2) -m never perform speculative memory probe We have one machine here that has 64 MB RAM that (used to) hang or reboot during the speculative probe. The "-m" option works great. We go in to either userconfig to modify the npx0 device to set the RAM size, or use our "kset" program to modify kernel devices, so we don't have to boot "-m" subsequently. Anyone interested in code? -Mark Taylor NetMAX Developer mtaylor@netmax.com On Sun, 14 Mar 1999, Sheldon Hearn wrote: > > Hi folks, > > The originator of PR i386/9755 (which related to a 3.0-RELEASE install > failure) has made a valid point. > > We know that some people with >64MB RAM are going to have trouble with > the speculative memory probe while installing FreeBSD with the GENERIC > (here read any release) kernel. So why don't we add to GENERIC the > following line? > > options "MAXMEM=(64*1024)" > > The major argument that comes to mind immediately is that people are > going to end up running sub-optimal servers out-of-the-box. However, the > change is supported by the following mindset: > > Gain: > Make things easier for people with broken hardware. > > Cost: > Annoy the people who have large memory configurations and who > don't build custom kernels. > > I'm of the opinion that we're talking about a number of annoyed people > so small that the gain is justified. > > Ciao, > Sheldon. > > > 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 Sun Mar 14 10:25:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 0A17B14E61; Sun, 14 Mar 1999 10:25:16 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id LAA09771; Sun, 14 Mar 1999 11:23:43 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EBFEAF.C37CFCE6@softweyr.com> Date: Sun, 14 Mar 1999 11:23:43 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: sthaug@nethelp.no Cc: ru@ucb.crimea.ua, dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall References: <19990314162419.A10242@relay.ucb.crimea.ua> <3441.921422198@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > > The way I see it, "fast forward" would be for router boxes at the core > of your network. Here you're concerned about speed. Firewall filtering > you normally want to do at the edges, where you're not so concerned about > speed. Apparently you see only networks where all users are equally trusted. Most don't. Of course, if you were really worried about security, you wouldn't be using shared media and routers, would you? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 10:30:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 142F314E70 for ; Sun, 14 Mar 1999 10:30:11 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 5420 invoked by uid 1001); 14 Mar 1999 18:29:52 +0000 (GMT) To: wes@softweyr.com Cc: ru@ucb.crimea.ua, dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 14 Mar 1999 11:23:43 -0700" References: <36EBFEAF.C37CFCE6@softweyr.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 14 Mar 1999 19:29:51 +0100 Message-ID: <5418.921436191@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The way I see it, "fast forward" would be for router boxes at the core > > of your network. Here you're concerned about speed. Firewall filtering > > you normally want to do at the edges, where you're not so concerned about > > speed. > > Apparently you see only networks where all users are equally trusted. No. > Most don't. Of course, if you were really worried about security, > you wouldn't be using shared media and routers, would you? I think you're misunderstanding what I'm saying. I think that having a "fast forward" option *available* is nice - for instance for situations where you want your FreeBSD box to *only* act as a router and want the highest performance. If you don't like the fact that the "fast foward" path doesn't include filtering, then you simply shouldn't use the "fast foward" path. Is this so difficult? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 10:40:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (Postfix) with ESMTP id D094614CAF for ; Sun, 14 Mar 1999 10:40:52 -0800 (PST) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.8.8/8.8.8) with SMTP id MAA08350; Sun, 14 Mar 1999 12:39:26 -0600 (CST) (envelope-from tony@dell.com) Message-Id: <3.0.6.32.19990314123925.039187c0@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 14 Mar 1999 12:39:25 -0600 To: Sheldon Hearn , "Daniel C. Sobral" From: Tony Overfield Subject: Re: Proposal: Define MAXMEM in GENERIC Cc: hackers@FreeBSD.ORG In-Reply-To: <63209.921431112@axl.noc.iafrica.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >... since we're >likely to see more and more people having problems related to failed >speculative memory probes as >64MB machines become entry-level. Since all(*) new machines support INT 15h AX=E820h, and FreeBSD now seems to be able to use it, why not have the speculative probe default to disabled in GENERIC and use a boot option to enable probing support for those very few older systems that supported more than 64MB or 16MB but did _not_ yet support E820h (or E801h)? (*) Good bet if the machine supports MS-Windows. p.s. FreeBSD seems to prefer E801h over E820h. I'd like to see it the other way around, since you could gain almost 64 KB of extra memory in some cases. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 11:11:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 08A0B15490 for ; Sun, 14 Mar 1999 11:11:21 -0800 (PST) (envelope-from bmilekic@oracle.dsuper.net) Received: from localhost (bmilekic@localhost) by oracle.dsuper.net (Delphi 1.3/8.6.9) with ESMTP id OAA32750; Sun, 14 Mar 1999 14:10:11 -0500 (EST) Date: Sun, 14 Mar 1999 14:10:11 -0500 (EST) From: Bosko Milekic To: FreeBsd Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: thread and socket 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 I've had a little trouble understanding you... :-) Here's an excerpt from the man page, though... if this isn't what you were looking for, please clarify a bit... --snip-- In the non-threaded library getsockopt() is implemented as the getsockopt syscall. In the threaded library, the getsockopt syscall is assembled to _thread_sys_getsockopt() and getsockopt() is implemented as a function which locks s for read and write, then calls _thread_sys_getsockopt(). Before returning, getsockopt() unlocks s. --snip-- Regards, Bosko. -- Bosko Milekic http://www.supernet.ca/~bmilekic/ Delphi SuperNet voice: (+1) 514 281-7500 fax: (+1) 514 281-6599 PGP Key available upon request. On Sun, 14 Mar 1999, FreeBsd wrote: > Date: Sun, 14 Mar 1999 10:49:36 +0100 (CET) > From: FreeBsd > To: freebsd-hackers@FreeBSD.ORG > Subject: thread and socket > > Hi, > in some small application I use receive socket with > setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO, &tv, sizeof(tv)); > and recvfrom is waiting and after tv finish with EAGAIN. It is well in no > thread version. In threaded version recvfrom is waiting and waiting and... > without finish (or recevie data well). Is this problem colision on user > timers or some blocking (or other)? How can I secure stop recvfrom from > another thread? > Thanks, > Honza > (version 2.2.8 and 3.1 - It's a same problem) > > > > 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 Sun Mar 14 11:20:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AF15314F08 for ; Sun, 14 Mar 1999 11:20:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA93395; Sun, 14 Mar 1999 11:20:28 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 11:20:28 -0800 (PST) From: Matthew Dillon Message-Id: <199903141920.LAA93395@apollo.backplane.com> To: Amancio Hasty Cc: Wes Peters , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903140927.BAA85633@rah.star-gate.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> cannot be done. So routing a single packet requires the data to flow :> over the PCI bus twice. The 132 MBytes/sec become 66 MBytes/sec right :> off the bat. : :I am not sure that I can follow you here . Most PCI cards which are capable of :doing dma to the host system's memory can do card - to - card transfer :;however, :the target "card" most be able to use the stored data in the case of a network :card it must have memory to receive the pack or a very elaborate protocol :to accept short dma bursts which it can then process. : : : Amancio You can always do a card-to-card transfer, but since most modern network cards do *NOT* have on-card memory doing a card-to-card transfer typically doesn't work. For example, if the destination card hits a collision/retry, the source card's FIFO can overflow. It just doesn't work. Using a card as a DMA destination only works well for cards that map memory, such as a video card. -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 Sun Mar 14 11:21:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (Postfix) with ESMTP id 126891511C for ; Sun, 14 Mar 1999 11:21:35 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA08186; Sun, 14 Mar 1999 13:21:16 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id NAA04544; Sun, 14 Mar 1999 13:20:45 -0600 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id NAA16212; Sun, 14 Mar 1999 13:20:44 -0600 (CST) Date: Sun, 14 Mar 1999 13:20:44 -0600 (CST) From: Jonathan Lemon Message-Id: <199903141920.NAA16212@free.pcs> To: tony@dell.com, freebsd-hackers@freebsd.org Subject: Re: Proposal: Define MAXMEM in GENERIC X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >>... since we're >>likely to see more and more people having problems related to failed >>speculative memory probes as >64MB machines become entry-level. > >Since all(*) new machines support INT 15h AX=E820h, and FreeBSD now >seems to be able to use it, why not have the speculative probe >default to disabled in GENERIC and use a boot option to enable probing >support for those very few older systems that supported more than 64MB >or 16MB but did _not_ yet support E820h (or E801h)? > >(*) Good bet if the machine supports MS-Windows. > >p.s. FreeBSD seems to prefer E801h over E820h. I'd like to see it > the other way around, since you could gain almost 64 KB of > extra memory in some cases. Not true, if you're referring to the VM86 memory probe. It tries INT 15h, AX=E820, then INT 15h, AX=E801, then INT 15h, AX=88, in that order. How about making VM86 a mandatory option? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 11:26: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from octopus.originative (49.usr02.wor.dialup.force9.net [195.166.131.113]) by hub.freebsd.org (Postfix) with ESMTP id 600E315485 for ; Sun, 14 Mar 1999 11:25:46 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Sun, 14 Mar 1999 19:23:48 -0000 Message-ID: From: paul@originative.co.uk To: mtaylor@cybernet.com, sheldonh@iafrica.com Cc: hackers@FreeBSD.ORG Subject: RE: Proposal: Define MAXMEM in GENERIC Date: Sun, 14 Mar 1999 19:23:47 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mark J. Taylor [mailto:mtaylor@cybernet.com] > Sent: 14 March 1999 18:19 > To: Sheldon Hearn > Cc: hackers@FreeBSD.ORG > Subject: Re: Proposal: Define MAXMEM in GENERIC > > > > It is trivial (we did it for 2.2.x) to add a boot option > to always, or never, perform a speculative memory probe. > > For our NetMAX product (shameless plug: http://www.netmax.com/), The OS evolution part of the demo movie is pretty neat, something like that on the FreeBSD site would be really nice. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 11:26:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 76AC6154F8 for ; Sun, 14 Mar 1999 11:26:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA93452; Sun, 14 Mar 1999 11:26:24 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 11:26:24 -0800 (PST) From: Matthew Dillon Message-Id: <199903141926.LAA93452@apollo.backplane.com> To: Kent Vander Velden Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable References: <199903132253.QAA09676@isua1.iastate.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The vga stuff in the call stack is very suspicious. It looks like it crashed trying to start up the screen saver. If you are using any dynamically loaded modules ( such as the splash module ), make sure you have recompiled and reinstaslled them. -Matt Matthew Dillon : : : : Hi. Nathan Ahlstrom has been helping me try to gather up information :to solve a problem with FreeBSD-Stable and asked me to send the following :information to freebsd-hackers. : The problem is that Freebsd-Stable crashes after just a few hours of :use. No core file is generated either. The crashing occurs on two :separate machines, one a dual-p133 and the other a 486-33. Both these :kernels are only hours old. I have been updating the kernels daily :in hopes of a fix. : If any further information is needed, please let me know. : : :Kent Vander Velden wrote: :> :> Hi. Shortly after sending you tellin you that DDB had not been working :> the 486 machine failed and dropped to DDB. I typed the intial message :> and the stack trace from the screen. If there is an easier way to capture :> the output form DDB I would sure like to hear it. Also enclosed is the :> output of dmesg. If any other information would be helpful :> please let me know. BTW: The other machine, the dual-p133 does not have :> a screen saver enabled. Both of the machines load eaxctly one module, :> the dual-p133 loads the linux module while the 486 loads the blank screen :> saver module. :> :> Thanks! :> :> Copyright (c) 1992-1999 FreeBSD Inc. :> Copyright (c) 1982, 1986, 1989, 1991, 1993 :> The Regents of the University of California. All rights reserved. :> FreeBSD 3.1-STABLE #0: Thu Mar 11 22:35:22 CST 1999 :> kent@pseudo:/usr/src/sys/compile/TOYBOX :> Timecounter "i8254" frequency 1193182 Hz :> CPU: i486DX (486-class CPU) :> real memory = 16777216 (16384K bytes) :> avail memory = 13758464 (13436K bytes) :> Preloaded elf kernel "kernel" at 0xf02cb000. :> Probing for devices on the ISA bus: :> sc0 on isa :> sc0: VGA mono <8 virtual consoles, flags=0x0> :> atkbdc0 at 0x60-0x6f on motherboard :> atkbd0 irq 1 on isa :> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa :> sio0: type 16450 :> sio1 at 0x2f8-0x2ff irq 3 on isa :> sio1: type 16450 :> sio2 at 0x3e8-0x3ef irq 5 on isa :> sio2: type 16550A :> ppc0 at 0x378 irq 7 on isa :> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode :> nlpt0: on ppbus 0 :> nlpt0: Interrupt-driven port :> ppi0: on ppbus 0 :> fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa :> lnc0 at 0x360-0x377 irq 12 drq 7 on isa :> lnc0: PCnet-ISA address 00:c0:6d:00:78:fd :> aha0 at 0x330-0x333 irq 11 drq 5 on isa :> aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs :> vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa :> npx0 on motherboard :> npx0: INT 16 interface :> sb0 at 0x220 irq 10 drq 1 on isa :> :> NOTE! SB Pro support required with your soundcard! :> snd0: :> opl0 at 0x388 on isa :> snd0: :> ccd0-3: Concatenated disk drivers :> Waiting 2 seconds for SCSI devices to settle :> da0 at aha0 bus 0 target 0 lun 0 :> da0: Fixed Direct Access SCSI-2 device :> da0: 3.300MB/s transfers :> da0: 1041MB (2131992 512 byte sectors: 64H 32S/T 1041C) :> da1 at aha0 bus 0 target 1 lun 0 :> da1: Fixed Direct Access SCSI-2 device :> da1: 3.300MB/s transfers :> da1: 1041MB (2131992 512 byte sectors: 64H 32S/T 1041C) :> changing root device to da0s1a :> WARNING: / was not properly dismounted :> :> :> :> :> Fatal trap 12: page fault while in kernel mode :> fault virtual address = 0xb8 :> fault code = supervisor read, page not present :> instruction pointer = 0x8:0xf014b15b :> stack pointer = 0x10:0xf024ad2c :> frame pointer = 0x10:0xf024ad40 :> code segment = base 0x0, limit 0xffff, type 0x1b :> = DPL 0, pres 1, def32 1, gran 1 :> processor eflags = interrupt enabled, resume, IOPL = 0 :> current process = Idle :> interrupt mask = net tty bio cam :> kernel: type 12 trap, code=0 :> Stopped at tsleep+0x1b: movl 0xb8(%ebx),%eax :> :> :> :> db> trace :> tsleep(f1147f90,4,f023e255,7d0) at tsleep+0x1b :> swap_pager_getpages(f2ae35d8,f024ae4c,1,0,f024ae8c) at swap_pager_getpages+0x3c8 :> vm_pager_get_pages(f2ae35b8,f024ae4c,1,0,) at vm_pager_get_pages+0x1f :> vm_fault(f026f4a4,f00000000,3,0,0) at vm_fault+0x464 :> trap_pfault(...) at trap_pfault+0xc4 :> trap(...) at trap+0x3b6 :> calltrap() at calltrap()+0x1c :> --- trap 0xc, eip=0xf022d857, esp=0xf024af2c, ebp=0xf024af48 :> vga_load_state(...) at vga_load_state+0x13b :> vga_set_mode(...) at vga_set_mode+0x2c2 :> set_mode(...) at set_mode+0x5c :> restore_scrn_saver_mode(...) at restore_scrn_saver_mode+0x47 :> scsplash_saver(...) at scsplash_saver+0xc7 :> stop_scrn_saver(...) at stop_scrn_saver+0xa :> scrn_timer(...) at scrn_timer+0x177 :> softclock(...) at softclock+0xc3 :> doreti_swi(...) at doreti_swi+0xf : :--- :Kent Vander Velden :kent@iastate.edu : : : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 11:47:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 0864614D25 for ; Sun, 14 Mar 1999 11:47:20 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id LAA87562; Sun, 14 Mar 1999 11:45:21 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903141945.LAA87562@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Wes Peters , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Sun, 14 Mar 1999 11:20:28 PST." <199903141920.LAA93395@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 11:45:21 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If the pci device has the concept of a program store like in the case of a bt848 chipset it is conceivable for dma or internal operations to do a retry. It is a different issue if the network chipset designers chose not to have a programmable dma or process control like in the bt848 . Best Regards, Amancio > > :> cannot be done. So routing a single packet requires the data to flow > :> over the PCI bus twice. The 132 MBytes/sec become 66 MBytes/sec right > :> off the bat. > : > :I am not sure that I can follow you here . Most PCI cards which are capable of > :doing dma to the host system's memory can do card - to - card transfer > :;however, > :the target "card" most be able to use the stored data in the case of a network > :card it must have memory to receive the pack or a very elaborate protocol > :to accept short dma bursts which it can then process. > : > : > : Amancio > > You can always do a card-to-card transfer, but since most modern network > cards do *NOT* have on-card memory doing a card-to-card transfer typically > doesn't work. For example, if the destination card hits a collision/retry, > the source card's FIFO can overflow. > > It just doesn't work. > > Using a card as a DMA destination only works well for cards that map > memory, such as a video card. > > -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 Sun Mar 14 11:52:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles161.castles.com [208.214.165.161]) by hub.freebsd.org (Postfix) with ESMTP id 8628C14F0A; Sun, 14 Mar 1999 11:52:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA08030; Sun, 14 Mar 1999 11:42:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903141942.LAA08030@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ruslan Ermilov Cc: Robert Nordier , FreeBSD Hackers Subject: Re: [BTX loader]: boot command doesn't work as expected In-reply-to: Your message of "Sun, 14 Mar 1999 18:18:51 +0200." <19990314181851.A890@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 11:42:32 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi! > > boot -c - works > boot /kernel - works > boot -c /kernel - doesn't work > > Any clue? The help text is wrong, mea culpa. The arguments are for the kernel, not the boot command. The correct syntax is: boot [] [- ...] -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 14 11:57: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5324915392 for ; Sun, 14 Mar 1999 11:57:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA93779; Sun, 14 Mar 1999 11:56:45 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 11:56:45 -0800 (PST) From: Matthew Dillon Message-Id: <199903141956.LAA93779@apollo.backplane.com> To: Amancio Hasty Cc: Wes Peters , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903141945.LAA87562@rah.star-gate.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :If the pci device has the concept of a program store like in the case of :a bt848 chipset it is conceivable for dma or internal operations to do a retry. :It is a different issue if the network chipset designers chose not to have :a programmable dma or process control like in the bt848 . : : : Best Regards, : Amancio I know of *NO* DMA device that can do 'retries' of the magnitude that would be required, and this in any case does not solve the problem of the FIFO overflowing. Network chipset designers tend to assume that they will be DMAing to or from main memory somewhere such that the DMA will not get 'stuck'. FIFOs are typically only large enough to hold a packet or two, and many can only hold a partial packet. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 11:58:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles161.castles.com [208.214.165.161]) by hub.freebsd.org (Postfix) with ESMTP id 5A5FF1504F for ; Sun, 14 Mar 1999 11:58:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA08097; Sun, 14 Mar 1999 11:52:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903141952.LAA08097@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Sheldon Hearn Cc: hackers@freebsd.org Subject: Re: Proposal: Define MAXMEM in GENERIC In-reply-to: Your message of "Sun, 14 Mar 1999 18:21:38 +0200." <35437.921428498@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 11:52:41 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi folks, > > The originator of PR i386/9755 (which related to a 3.0-RELEASE install > failure) has made a valid point. > > We know that some people with >64MB RAM are going to have trouble with > the speculative memory probe while installing FreeBSD with the GENERIC > (here read any release) kernel. So why don't we add to GENERIC the > following line? > > options "MAXMEM=(64*1024)" > > The major argument that comes to mind immediately is that people are > going to end up running sub-optimal servers out-of-the-box. However, the > change is supported by the following mindset: > > Gain: > Make things easier for people with broken hardware. > > Cost: > Annoy the people who have large memory configurations and who > don't build custom kernels. > > I'm of the opinion that we're talking about a number of annoyed people > so small that the gain is justified. We'd probably be better off using VM86 and the BIOS memory probe code, which will give us the best of both worlds. The code's been in the system for a long time now, and completely obsoletes the (bogus from day 1) speculative probe. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 14 12:16:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from niobe.ewox.org (ppp044.uio.no [129.240.240.45]) by hub.freebsd.org (Postfix) with ESMTP id 0E33014F16 for ; Sun, 14 Mar 1999 12:16:45 -0800 (PST) (envelope-from des@niobe.ewox.org) Received: (from des@localhost) by niobe.ewox.org (8.9.3/8.9.1) id SAA85998; Sun, 14 Mar 1999 18:21:10 +0100 (CET) (envelope-from des) To: freebsd-hackers@freebsd.org Subject: ioctl numbers From: Dag-Erling Smorgrav Date: 14 Mar 1999 18:21:09 +0100 Message-ID: <86r9qsf0my.fsf@niobe.ewox.org> Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any meaning in the way ioctl numbers are selected? There seem to be several ioctl numbers which have different and totally unrelated meanings for different devices. If I want to add an ioctl to a driver, can I just pick any number which is not currently meaningful to that driver? Specifically, will anybody mind if I define and implement the following ioctls, as documented in tun(4): #define TUNSIFMODE _IOW('t', 93, int) /* set ptp/bcast mode */ #define TUNSLMODE _IOW('t', 94, int) /* set link layer mode */ DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 12:27:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m1-15-dbn.dial-up.net [196.34.155.15]) by hub.freebsd.org (Postfix) with ESMTP id 5199E1514A for ; Sun, 14 Mar 1999 12:27:19 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA09966; Sun, 14 Mar 1999 22:24:10 +0200 (SAT) From: Robert Nordier Message-Id: <199903142024.WAA09966@ceia.nordier.com> Subject: Re: [BTX loader]: boot command doesn't work as expected In-Reply-To: <36EBEA87.66E7BF16@newsguy.com> from "Daniel C. Sobral" at "Mar 15, 99 01:57:43 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Sun, 14 Mar 1999 22:24:08 +0200 (SAT) Cc: ru@ucb.crimea.ua, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Daniel C. Sobral wrote: > Ruslan Ermilov wrote: > > > > Hi! > > > > boot -c - works > > boot /kernel - works > > boot -c /kernel - doesn't work > > > > Any clue? > > You mean it doesn't work as _you_ expect it to? :-) > > help boot > > Boot boots. The -c flag is to be passed to the kernel, not to the > command boot. > > boot /kernel -c I may be missing some subtle point here, but there should be no difference between boot -c /kernel and boot /kernel -c The "official" boot2 syntax, in both the old and the new bootblocks, is also [kernel_name] [options] but [options] [kernel_name] is equally acceptable in practice. In the case of loader, either way results in the same settings in the "howto" flags passed to the kernel. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 12:28: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m1-15-dbn.dial-up.net [196.34.155.15]) by hub.freebsd.org (Postfix) with ESMTP id 2F46D15038 for ; Sun, 14 Mar 1999 12:28:01 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA09907; Sun, 14 Mar 1999 22:15:10 +0200 (SAT) From: Robert Nordier Message-Id: <199903142015.WAA09907@ceia.nordier.com> Subject: Re: [BTX loader]: boot command doesn't work as expected In-Reply-To: <19990314181851.A890@relay.ucb.crimea.ua> from Ruslan Ermilov at "Mar 14, 99 06:18:51 pm" To: ru@ucb.crimea.ua (Ruslan Ermilov) Date: Sun, 14 Mar 1999 22:15:09 +0200 (SAT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (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 > Hi! > > boot -c - works > boot /kernel - works > boot -c /kernel - doesn't work > > Any clue? What are you actually getting, when it doesn't work? Is the -c option simply ignored? I ask because I've tried about 8 times here, using various permutations, and got some unexpected results. Though, in all cases, I did get a "config>" prompt. Is the behavior consistently reproducible? -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 12:28:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from niobe.ewox.org (ppp044.uio.no [129.240.240.45]) by hub.freebsd.org (Postfix) with ESMTP id B276B15383 for ; Sun, 14 Mar 1999 12:28:25 -0800 (PST) (envelope-from des@niobe.ewox.org) Received: (from des@localhost) by niobe.ewox.org (8.9.3/8.9.1) id VAA91478; Sun, 14 Mar 1999 21:29:16 +0100 (CET) (envelope-from des) To: hackers@freebsd.org Subject: CVS: Just Say No From: Dag-Erling Smorgrav Date: 14 Mar 1999 21:29:16 +0100 Message-ID: <86pv6bg6hv.fsf@niobe.ewox.org> Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG des@flood ~/freebsd/rc% fcvs update -j1.181 -j1.182 etc/rc R etc/rc assertion "rev == NULL || isdigit (*rev)" failed: file "/d/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/src/rcs.c", line 3589 Terminated with fatal signal 6 Core dumped; preserving /tmp/cvs-serv16363 on server. CVS locks may need cleaning up. DES (eagerly awaiting OVCS) -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 12:30: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id DE54B14E8F for ; Sun, 14 Mar 1999 12:29:55 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id PAA24852 for hackers@freebsd.org; Sun, 14 Mar 1999 15:36:24 -0500 From: Bill Paul Message-Id: <199903142036.PAA24852@skynet.ctr.columbia.edu> Subject: Re: Fifabit ethernet -- what am I doing wrong? To: hackers@freebsd.org Date: Sun, 14 Mar 1999 15:36:23 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1985 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, here's an update. I've been reading all the replies to this thread, but it turns out that my main problem is that, as expected, I was screwing something up. The Tigon has a PCI state register which lets you configure several aspects operation. Two of the parameters are PCI read max and PCI write max, which force termination of PCI reads or writes at a specified boundaries 4 bytes, 16, 32, 64, 128, 256, 1K. I had originally set the read and write max values for 32. It turns out that disabling these settings (by making them 0) yields _much_ better performance. After fixing that, I ran into another situation where I kept filling up the transmit ring (or rather, the NIC wasn't emptying the transmit ring fast enough). Normally the Tigon has both the PCI read and write DMA channels active at the same time, but you can force only one to be active at a time by setting a bit in the operating mode register. The manual recommends _not_ doing this, but setting it yielded yet another jump in performance. Right now I can transmit UDP packets at around 55MB/sec with the normal MTU and can get 91MB/sec by setting the MTU to 9000 (using jumbo frames). TCP speed has improved too, but not quite so much as I expected (I can get 40MB/sec with a window size of 64K and normal MTU, 66MB/sec with jumbo frames). I still need to experiment with the various tuning options though. I also haven't really tried checksum offloading yet. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 12:36:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peotl.tuebingen.netsurf.de (host-347.tuebingen.netsurf.de [195.180.140.147]) by hub.freebsd.org (Postfix) with ESMTP id 3A6D3153EC for ; Sun, 14 Mar 1999 12:36:39 -0800 (PST) (envelope-from thz@tuebingen.netsurf.de) Received: (from thz@localhost) by peotl.tuebingen.netsurf.de (8.9.2/8.9.2) id VAA00579 for freebsd-hackers@FreeBSD.ORG; Sun, 14 Mar 1999 21:35:47 +0100 (MET) (envelope-from thz) Date: Sun, 14 Mar 1999 21:35:47 +0100 From: Thomas Zenker To: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable Message-ID: <19990314213546.A269@peotl.tuebingen.netsurf.de> References: <199903132253.QAA09676@isua1.iastate.edu> <199903141926.LAA93452@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199903141926.LAA93452@apollo.backplane.com>; from Matthew Dillon on Sun, Mar 14, 1999 at 11:26:24AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 14, 1999 at 11:26:24AM -0800, Matthew Dillon wrote: > The vga stuff in the call stack is very suspicious. It looks like it > crashed trying to start up the screen saver. > > If you are using any dynamically loaded modules ( such as the splash > module ), make sure you have recompiled and reinstaslled them. > Exactly the same panic here. This is as 486 system with world and kernel from 7th march. Until today the system freezed simply the screensaver,... today there was the first time I saw the panic and the kernel fell into the debugger after pressing a key to get rid of the saver. (probably the first time that the system had been left on console?) The trace shows stopping the saver and trying to restore the screen, then in vga_load_state+136 a missing page causing a pagefault. ... So later on swap_pager_getpages does a tsleep, but we are the "idle" process. As far as I know, "idle" should never tsleep and may not have pages pagedout. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 12:37:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles161.castles.com [208.214.165.161]) by hub.freebsd.org (Postfix) with ESMTP id EC54915449 for ; Sun, 14 Mar 1999 12:37:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA08229; Sun, 14 Mar 1999 12:30:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903142030.MAA08229@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier Cc: ru@ucb.crimea.ua (Ruslan Ermilov), hackers@freebsd.org Subject: Re: [BTX loader]: boot command doesn't work as expected In-reply-to: Your message of "Sat, 14 Mar 1999 22:15:09 +0200." <199903142015.WAA09907@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 12:30:43 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi! > > > > boot -c - works > > boot /kernel - works > > boot -c /kernel - doesn't work > > > > Any clue? > > What are you actually getting, when it doesn't work? Is the -c option > simply ignored? I ask because I've tried about 8 times here, using > various permutations, and got some unexpected results. Though, in all > cases, I did get a "config>" prompt. Is the behavior consistently > reproducible? The loader explicitly checks argv[1] for a kernel name in command_boot. If you put an argument first, the kernel name will be passed to the MD boot code as an argument as well. Not what the user wantsm for sure. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 14 12:47:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id C29671531E for ; Sun, 14 Mar 1999 12:47:16 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA87857; Sun, 14 Mar 1999 12:46:08 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903142046.MAA87857@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Wes Peters , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Sun, 14 Mar 1999 11:56:45 PST." <199903141956.LAA93779@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 12:46:07 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure what the problem here is . Can a network chipset designer create a chipset with a concept of a program store? The answer is yes , if they chose to implement a sloppy design thats a different issue. Amancio > > : > :If the pci device has the concept of a program store like in the case of > :a bt848 chipset it is conceivable for dma or internal operations to do a retry. > :It is a different issue if the network chipset designers chose not to have > :a programmable dma or process control like in the bt848 . > : > : > : Best Regards, > : Amancio > > I know of *NO* DMA device that can do 'retries' of the magnitude that would > be required, and this in any case does not solve the problem of the FIFO > overflowing. > > Network chipset designers tend to assume that they will be DMAing to or > from main memory somewhere such that the DMA will not get 'stuck'. > FIFOs are typically only large enough to hold a packet or two, and many > can only hold a partial packet. > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 12:52:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by hub.freebsd.org (Postfix) with ESMTP id 5FB15156F6 for ; Sun, 14 Mar 1999 12:52:31 -0800 (PST) (envelope-from durham@w2xo.pgh.pa.us) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by w2xo.pgh.pa.us (8.9.2/8.9.1) with ESMTP id PAA22996 for ; Sun, 14 Mar 1999 15:52:31 -0500 (EST) (envelope-from durham@w2xo.pgh.pa.us) Message-ID: <36EC218E.AD43242B@w2xo.pgh.pa.us> Date: Sun, 14 Mar 1999 15:52:30 -0500 From: Jim Durham Organization: dis- X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd hackers Subject: VM changes 3.0 to 3.1 RELEASES ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I posted this to questions, but got no replies. I am having problems since upgrading from 3.0-SNAP- 981225 to 3.0 and 3.1 RELEASES. The machine is very modest, a 5X86, 40 mb of RAM and 1.5 gb of disk, 75 mb of swap. It is a firewall for a small LAN and also runs apache and RealAudio servers as well as an amateur radio ax.25 networking userland process. It also runs X on the console with Netscape 4.5 used a lot and uses ghostscript/apsfilter for printing, both of which are resource hogs. The worst symptom is natd either core-dumping or getting into a state where it is using about 95% of the CPU and network throughput is almost zero. I began to recompile natd and the alias library with symbolsto run a core dump trace with gdb, when I realized that sendmail and inetd were also having problems (core dumps, eating CPU cycles). During these episodes, I noticed that swap space was down to a few mb. When 3.1 came out, I upgraded and things are much better, but ghostscript/apsfilter has gone into the CPU-cycle-eating mode twice on a big print job. natd , sendmail and inetd have had no problems on 3.1 . I have spoken to several people who had the problem with natd. The stack trace showed that it was trying to execute the address of the packet buffer as a function from the alias stuff. It was hopelessly confused, apparently. I didn't get to do any tracing on sendmail or inetd. I also saw the "pointer too low to make sense" error message. I have searched through RELNOTES, etc and can't find any mention of any VM changes from 3.0 to 3.1. Can anyone shed any light on this? Is this something that is being worked on? Should I upgrade to -STABLE? What was suspicious to me was that the old 3.0-SNAP never showed these problems and , I believe, shut down processes gracefully when system resources became scarce. -- Thanks, Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 13: 3:20 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 6EEDE15733 for ; Sun, 14 Mar 1999 13:03:15 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id GAA21753; Mon, 15 Mar 1999 06:02:43 +0900 (JST) Message-ID: <36EC2360.BCDF6296@newsguy.com> Date: Mon, 15 Mar 1999 06:00:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Robert Nordier Cc: ru@ucb.crimea.ua, hackers@FreeBSD.ORG Subject: Re: [BTX loader]: boot command doesn't work as expected References: <199903142024.WAA09966@ceia.nordier.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, tell the truth, you are right. There is no *reason* for it not to accept both ways, since boot doesn't take flags. Yeah... sorry, Ruslan, you are correct. I'll see what I can do about it. Robert Nordier wrote: > > Daniel C. Sobral wrote: > > > Ruslan Ermilov wrote: > > > > > > Hi! > > > > > > boot -c - works > > > boot /kernel - works > > > boot -c /kernel - doesn't work > > > > > > Any clue? > > > > You mean it doesn't work as _you_ expect it to? :-) > > > > help boot > > > > Boot boots. The -c flag is to be passed to the kernel, not to the > > command boot. > > > > boot /kernel -c > > I may be missing some subtle point here, but there should be no > difference between > > boot -c /kernel > > and > > boot /kernel -c > > The "official" boot2 syntax, in both the old and the new bootblocks, > is also > > [kernel_name] [options] > > but > > [options] [kernel_name] > > is equally acceptable in practice. > > In the case of loader, either way results in the same settings in the > "howto" flags passed to the kernel. > > -- > Robert Nordier -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 13: 4:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.ici.net (pike.ici.net [207.180.0.23]) by hub.freebsd.org (Postfix) with ESMTP id 5010D1573A for ; Sun, 14 Mar 1999 13:04:03 -0800 (PST) (envelope-from curtis@ici.net) Received: (from curtis@localhost) by pike.ici.net (8.9.0/8.9.0) id QAA17943 for freebsd-hackers@freebsd.org; Sun, 14 Mar 1999 16:03:44 -0500 (EST) Date: Sun, 14 Mar 1999 16:03:44 -0500 (EST) From: "Curtis Wilbar [STAFF]" Message-Id: <199903142103.QAA17943@pike.ici.net> To: freebsd-hackers@freebsd.org Subject: bootable cd q Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone point me to a website, ftpsite, etc that would detail how to make a freebsd bootable cd-rom ? I've found info on mkisofs and in general how it works, but I'm looking for freebsd specific info (i.e. how to make a bootable cd from the downloaded images/etc). I'd appreciate any info you could provide. I'm not subscribed to freebsd-hackers (yet :-) ), so please reply off list, or if you want the response to the list too, cc me, so I it as well :-) In the process of disecting how my freebsd 2.2.6 and 2.2.8 cds boot, I've wondered about how to loopback mount a file that contains a filesystem (either a ufs or cd9660 image). In linux they have a loopback filesystem device. I have been unable to find out how to do this under freebsd 2.2.6. Anyone have any info on that ? Thanks in advance, -- Curt curtis@ici.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 13:12: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id BC3F21504F for ; Sun, 14 Mar 1999 13:12:00 -0800 (PST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from libr.scitec.kobe-u.ac.jp (cs22138.ppp.infoweb.ne.jp [202.219.4.54]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id GAA23925 for ; Mon, 15 Mar 1999 06:02:53 +0900 (JST) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id GAA25610 for ; Mon, 15 Mar 1999 06:08:52 +0900 (JST) From: takawata@shidahara1.planet.sci.kobe-u.ac.jp Message-Id: <199903142108.GAA25610@libr.scitec.kobe-u.ac.jp> To: FreeBSD-hackers@FreeBSD.org Subject: Re: Proposal: Define MAXMEM in GENERIC In-reply-to: Your message of "Sun, 14 Mar 1999 13:20:44 CST." <199903141920.NAA16212@free.pcs> Date: Mon, 15 Mar 1999 06:08:50 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903141920.NAA16212@free.pcs>, Jonathan Lemon wrote: >In article s.dell.com> you write: >Not true, if you're referring to the VM86 memory probe. It tries >INT 15h, AX=E820, then INT 15h, AX=E801, then INT 15h, AX=88, in >that order. As I mentioned send-pr i386/10485, INT15h AX=E820 should not be called from VM86 mode. It should be called from REAL mode. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 13:21:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isua1.iastate.edu (isua1.iastate.edu [129.186.1.201]) by hub.freebsd.org (Postfix) with ESMTP id 18D1514D20 for ; Sun, 14 Mar 1999 13:21:09 -0800 (PST) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua1.iastate.edu (8.8.5/8.8.5) with SMTP id PAA28736; Sun, 14 Mar 1999 15:20:48 -0600 (CST) Message-Id: <199903142120.PAA28736@isua1.iastate.edu> To: Kazutaka YOKOTA Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 3.1-Stable Being Unstable In-reply-to: Your message of "Sun, 14 Mar 1999 15:55:05 +0900." <199903140655.PAA19274@zodiac.mech.utsunomiya-u.ac.jp> Date: Sun, 14 Mar 1999 15:20:48 CST From: Kent Vander Velden Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Remove my previous patch and apply the following patch to >/sys/i386/isa/vga_isa.c. > >With this patch, you can use the splash pseudo-device, screen savers, >and the X server without crashing the machine. > >This is a workaround which I rather don't like, but is known to work. >(A couple of other users reported success...) This patch seems to have solved my problem. I have been able to run jobs that never completed before. I also disabled the splash pseudo device and screen savers since they really do not give me any additional functionality and apparently were at least partially to blame. Thanks for all your help! --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 16:20:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eterna.binary.net (eterna.binary.net [12.13.84.6]) by hub.freebsd.org (Postfix) with ESMTP id 567BF15392 for ; Sun, 14 Mar 1999 16:20:47 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id SAA91827; Sun, 14 Mar 1999 18:20:28 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id SAA26490; Sun, 14 Mar 1999 18:20:28 -0600 (CST) Date: Sun, 14 Mar 1999 19:20:28 -0500 From: Nathan Dorfman To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: Proposed patch to /etc/rc Message-ID: <19990314192028.A26063@rtfm.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Mar 12, 1999 at 07:14:56PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 12, 1999 at 07:14:56PM +0100, Dag-Erling Smorgrav wrote: > # Whack the pty perms back into shape. > chmod 666 /dev/tty[pqrsPQRS]* > +chown root.tty /dev/tty/[pqrsPQRS]* ^ Should that be there? -- Nathan Dorfman The statements and opinions in my Unix Admin @ Frontline Communications public posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 16:47:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 563FF14C5A for ; Sun, 14 Mar 1999 16:47:19 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:3aLF26tvu1nhBECy2wR5GS3pxVf8DM8d@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id JAA12736; Mon, 15 Mar 1999 09:45:57 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA06054; Mon, 15 Mar 1999 09:49:14 +0900 (JST) Message-Id: <199903150049.JAA06054@zodiac.mech.utsunomiya-u.ac.jp> To: Matthew Dillon Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: FreeBSD 3.1-Stable Being Unstable In-reply-to: Your message of "Sun, 14 Mar 1999 11:26:24 PST." <199903141926.LAA93452@apollo.backplane.com> References: <199903132253.QAA09676@isua1.iastate.edu> <199903141926.LAA93452@apollo.backplane.com> Date: Mon, 15 Mar 1999 09:49:13 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The vga stuff in the call stack is very suspicious. It looks like it > crashed trying to start up the screen saver. > > If you are using any dynamically loaded modules ( such as the splash > module ), make sure you have recompiled and reinstaslled them. > > -Matt > Matthew Dillon > To be precise, the system is crashing when syscons is trying to stop the screen saver and restore the video mode. What I know about this crash is as follows: The section of the code which is triggering the panic is in the vga driver in the kernel, not in any KLD modules. The users are seeing the problem on 486DX, P54C/133, Cyrix (I don't know which one it is) CPUs. (I cannot reproduce the problem on my test bed, a dual P-Pro machine.) The vga driver is trying to write to the BIOS data variables in the physical memory region 0x0-0x4ff, the very first page of the physical memory, when this panic occurs The region is supposed to be always mapped to the beginning of the kernel memory space. The vga driver reads from that region when initializing itself and there is no panic at that point. I suspect the page table entry for the above region may be corrupted at some point. Any comment? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 16:55: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id CAC851509A for ; Sun, 14 Mar 1999 16:55:06 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id B074C18C2; Mon, 15 Mar 1999 01:54:56 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id AD0814992; Mon, 15 Mar 1999 01:54:56 +0100 (CET) Date: Mon, 15 Mar 1999 01:54:53 +0100 (CET) From: Andrzej Bialecki To: "Daniel C. Sobral" Cc: Chuck Robey , Andrzej Bialecki , freebsd-hackers@freebsd.org Subject: Re: HEADS UP: new loader.rc stuff In-Reply-To: <36EBF364.E33203BD@newsguy.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, 15 Mar 1999, Daniel C. Sobral wrote: > > sure how it affects the other set of lines I've been told to stick into > > loader.rc: > > > > load kernel > > load -t userconfig_script /boot/kernel.conf > > autoboot 10 > > > > I see now, the center of those lines is the one that loads my > > kernel.conf ... which is nearly the output of kget. I'd thought that > > kget might have a file to write to hardcoded, so I was confused when it > > appeared that either /kernel.config OR /boot/kernel.conf appeared to > > have duplicate functions ... in my README, I think I can say that > > they're the same file, and since /boot/kernel.conf is the way things are > > going, to get rid of /kernel.config. > > /kernel.config was used before 3.1. That's why the confusion, and > you might want to clear that up on the README. Any comments here, > Andrzej? Well, it really doesn't matter what you call this file, because you explicitly load it by name. From my POV both locations are good, but the /boot/kernel.conf seems a bit more fashionable... :-) > > Kget seems also to stick in an extra line, either "q" or "quit", after > > the pnp line it finds from the userconfig process. I think I can tell > > users to clip that off, right? > > I don't know. :-) Andrzej? I _think_ you have to use 'quit' as the last command in the script, otherwise it will loop endlessly awaiting next command. But I know someone rewrote this piece of UserConfig after I tried to correct its logic, so I'm not sure. Can you check? > > BTW, I notice that kget doesn't install it's man page .. why, do you > > know that? > > Andrzej? Yes, I know why. I mean, I didn't have time to play with nroff. Besides, some people didn't feel comfortable with putting it as a complete replacement of dset, because of the way it treats the previous /kernel.config [namely, it ignores it]. This is somewhat complicated issue: what should you do with the previous contents of your /kernel.config? Preserve it? Merge it? Ignore it? So, I would need to get something like a consensus from users on what should really be done, and then we could move kget to some normal place in the tree (together with a man page). 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 Mar 14 17: 3:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id F20EA14F2A; Sun, 14 Mar 1999 17:03:13 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 8F04D18C2; Mon, 15 Mar 1999 02:03:07 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 7B54A49CE; Mon, 15 Mar 1999 02:03:07 +0100 (CET) Date: Mon, 15 Mar 1999 02:03:07 +0100 (CET) From: Andrzej Bialecki To: Ruslan Ermilov Cc: sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-Reply-To: <19990314180852.A7460@relay.ucb.crimea.ua> 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, 14 Mar 1999, Ruslan Ermilov wrote: > o Kernel change information is not saved in the new kernel, even > though this is claimed to work in the docs. > > Fix: The change information is being written out, in fact, but to the ^^^^^^^^^^^^^^^^^^^^ Hmm... Really? What writes this info? > I can't get your fix to work. > > I've made `boot -c' changes, and `sysctl machdep.uc_devlist' produces > non-null output, but the /kernel.config is empty. > > Any clue? Either create /kernel.config manually, or run kget (available in src/release/picobsd/tinyware/kget). 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 Mar 14 17:14:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 606C3155C8 for ; Sun, 14 Mar 1999 17:14:51 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id EE73618C3; Mon, 15 Mar 1999 02:14:45 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id E45CC4992; Mon, 15 Mar 1999 02:14:45 +0100 (CET) Date: Mon, 15 Mar 1999 02:14:44 +0100 (CET) From: Andrzej Bialecki To: Mike Smith Cc: Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-Reply-To: <199903141952.LAA08097@dingo.cdrom.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 Sun, 14 Mar 1999, Mike Smith wrote: > We'd probably be better off using VM86 and the BIOS memory probe code, > which will give us the best of both worlds. > > The code's been in the system for a long time now, and completely > obsoletes the (bogus from day 1) speculative probe. I wonder if it's possible to add a MAXMEM environment variable in bootloader... then those who know better could set it to the real value. 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 Mar 14 17:15:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gwi.net (mail.gwi.net [204.120.68.142]) by hub.freebsd.org (Postfix) with ESMTP id C9AB8155C1 for ; Sun, 14 Mar 1999 17:14:26 -0800 (PST) (envelope-from fkittred@mail.gwi.net) Received: from mail.gwi.net (fkittred@localhost [127.0.0.1]) by mail.gwi.net (8.8.5/8.8.7) with ESMTP id UAA23160; Sun, 14 Mar 1999 20:13:35 -0500 (EST) Message-Id: <199903150113.UAA23160@mail.gwi.net> To: Amancio Hasty Cc: Matthew Dillon , Wes Peters , Cory Kempf , Bill Paul , freebsd-hackers@freebsd.org Reply-To: Matthew Dillon Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Sun, 14 Mar 1999 12:46:07 PST." <199903142046.MAA87857@rah.star-gate.com> Date: Sun, 14 Mar 1999 20:13:34 -0500 From: Fletcher E Kittredge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Mar 1999 12:46:07 -0800 Amancio Hasty wrote: > > Not sure what the problem here is . Can a network chipset designer > create a chipset with a concept of a program store? The answer is yes > , if they chose to implement a sloppy design thats a different issue. Amancio; How big do you envision the queues on a NIC card need to be to handle a moderately loaded, full duplex gigabit ethernet? Basically I think the answer is that the buffers and the logic get so huge, the cost of the card would be prohibitive. regards, fletcher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 19: 1:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles125.castles.com [208.214.165.125]) by hub.freebsd.org (Postfix) with ESMTP id 392C914DF6 for ; Sun, 14 Mar 1999 19:01:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA09228; Sun, 14 Mar 1999 18:55:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903150255.SAA09228@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki Cc: Mike Smith , Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-reply-to: Your message of "Mon, 15 Mar 1999 02:14:44 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 18:55:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 14 Mar 1999, Mike Smith wrote: > > > We'd probably be better off using VM86 and the BIOS memory probe code, > > which will give us the best of both worlds. > > > > The code's been in the system for a long time now, and completely > > obsoletes the (bogus from day 1) speculative probe. > > I wonder if it's possible to add a MAXMEM environment variable in > bootloader... then those who know better could set it to the real value. You'd do this the same way the other tunables were done. I've actually been talking to David Filo about tunables, and I think I have a better model for them in the works. It should make it possible to just about completely eliminate param.c (some statically-sized items may need to be fixed up). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 14 19: 9:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 52A4E150C5 for ; Sun, 14 Mar 1999 19:09:21 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-65-74.atl.bellsouth.net [209.214.65.74]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id WAA26654; Sun, 14 Mar 1999 22:08:17 -0500 (EST) Received: from localhost (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id VAA25141; Sun, 14 Mar 1999 21:59:44 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) To: dillon@apollo.backplane.com, fkittred@mail.gwi.net Cc: hasty@rah.star-gate.com, wes@softweyr.com, ckempf@enigami.com, wpaul@skynet.ctr.columbia.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-Reply-To: Your message of "Sun, 14 Mar 1999 20:13:34 -0500" <199903150113.UAA23160@mail.gwi.net> References: <199903150113.UAA23160@mail.gwi.net> X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990314215944E.wghicks@wghicks.bellsouth.net> Date: Sun, 14 Mar 1999 21:59:44 -0500 From: W Gerald Hicks X-Dispatcher: imput version 980905(IM100) Lines: 15 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Fletcher E Kittredge > > Basically I think the answer is that the buffers and the logic get so > huge, the cost of the card would be prohibitive. > Erm... Depends on what one wants to do with it :) I believe certain market segments would welcome a Gigabit Ethernet subsystem on a Rambus with huge memory buffers. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 20:49:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 73A4B14E02 for ; Sun, 14 Mar 1999 20:49:07 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id VAA11162; Sun, 14 Mar 1999 21:48:03 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EC9102.119A6973@softweyr.com> Date: Sun, 14 Mar 1999 21:48:02 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@freebsd.org Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903150113.UAA23160@mail.gwi.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fletcher E Kittredge wrote: > > On Sun, 14 Mar 1999 12:46:07 -0800 Amancio Hasty wrote: > > > > Not sure what the problem here is . Can a network chipset designer > > create a chipset with a concept of a program store? The answer is yes > > , if they chose to implement a sloppy design thats a different issue. > > Amancio; How big do you envision the queues on a NIC card need to be > to handle a moderately loaded, full duplex gigabit ethernet? 8 MB of high-speed SDRAM for 2 ports, with hardware queueing support. I can't tell you how I know this, or I'd have to kill -1 you. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 21:58:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (Postfix) with ESMTP id 8389614E0E for ; Sun, 14 Mar 1999 21:58:32 -0800 (PST) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.8.8/8.8.8) with SMTP id XAA09192; Sun, 14 Mar 1999 23:57:40 -0600 (CST) (envelope-from tony@dell.com) Message-Id: <3.0.6.32.19990314235738.03ba2a10@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 14 Mar 1999 23:57:38 -0600 To: Jonathan Lemon , freebsd-hackers@freebsd.org From: Tony Overfield Subject: Re: Proposal: Define MAXMEM in GENERIC In-Reply-To: <199903141920.NAA16212@free.pcs> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:20 PM 3/14/99 -0600, Jonathan Lemon wrote: >>p.s. FreeBSD seems to prefer E801h over E820h. I'd like to see it >> the other way around, since you could gain almost 64 KB of >> extra memory in some cases. > >Not true, if you're referring to the VM86 memory probe. It tries >INT 15h, AX=E820, then INT 15h, AX=E801, then INT 15h, AX=88, in >that order. Sorry about that. I have all three of the BIOS functions in my box, but I still see this: BIOS basemem: 639K, extmem: 64512K (from 0xe801 call) so I made an assumption. I did say it *seems* to prefer E801h. Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 22: 3:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 4336114EA8 for ; Sun, 14 Mar 1999 22:03:40 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id AAA01202 for freebsd-hackers@freebsd.org; Mon, 15 Mar 1999 00:03:21 -0600 (CST) From: Mohit Aron Message-Id: <199903150603.AAA01202@cs.rice.edu> Subject: bug in performance monitoring code To: freebsd-hackers@freebsd.org Date: Mon, 15 Mar 1999 00:03:21 -0600 (CST) X-Mailer: ELM [version 2.4 PL25] 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 Hi, there's a bug in the performance monitoring code in the file /sys/i386/i386/perfmon.c that implements ioctl calls to the device /dev/perfmon. I'm using FreeBSD-3.1 running on a Pentium-Pro processor. The problem is that the Intel performance counters are 40 bits wide and reading them using the rdmsr instruction results in the higher 24 bits of the 64 bit value to be undefined (as stated in Intel's manuals). However, the code in perfmon.c doesn't clear the higher 24 bits after calling rdmsr(). Here's a sample output of the /usr/share/examples/perfmon program (this particular example montiors the floating point operations in 1 second): % perfmon -u -e -s 1 -l 1 193 1: 61572651155456 total: 61572651155456.000000 mean: 61572651155456.000000 clocks (at 166-MHz): 166827310 Here's the sample output after applying a fix to /sys/i386/i386/perfmon.c: % perfmon -u -e -s 1 -l 1 193 1: 0 total: 0.000000 mean: 0.000000 clocks (at 166-MHz): 166632751 - Mohit Aron aron@cs.rice.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 22:16:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id B8AC314EE0 for ; Sun, 14 Mar 1999 22:16:26 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id WAA92542; Sun, 14 Mar 1999 22:15:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903150615.WAA92542@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wes Peters Cc: Matthew Dillon , Cory Kempf , Bill Paul , freebsd-hackers@freebsd.org Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Sun, 14 Mar 1999 21:48:02 MST." <36EC9102.119A6973@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 22:15:14 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, Don't worry I know that there are people on this list that know the answer that you have suggested --- for instance just take a peek at http://www.juniper.net those guys operate in the giga packet per second range of course if we want to know what they are doing we may have to resort to Mediaval Spanish Inquisition style of interrogation 8) That aside I just bought an NVIDIA Tnt AGP video card with 16MB of memory for $150 I think it has sdram (not sure ) at any rate the next version of Nvidia's chipset based boards are going to have fast sdram probably sub 8 nano second range at least the demo models I read about have them which I read about on Tom's hardware page *http://www.tomshardware.com". Have Fun Guys, Amancio > Fletcher E Kittredge wrote: > > > > On Sun, 14 Mar 1999 12:46:07 -0800 Amancio Hasty wrote: > > > > > > Not sure what the problem here is . Can a network chipset designer > > > create a chipset with a concept of a program store? The answer is yes > > > , if they chose to implement a sloppy design thats a different issue. > > > > Amancio; How big do you envision the queues on a NIC card need to be > > to handle a moderately loaded, full duplex gigabit ethernet? > > 8 MB of high-speed SDRAM for 2 ports, with hardware queueing support. > I can't tell you how I know this, or I'd have to kill -1 you. ;^) > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 22:51:35 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 DB70E1505E for ; Sun, 14 Mar 1999 22:51:29 -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 2.12 #1) id 10MRAr-000BpV-00; Mon, 15 Mar 1999 08:48:29 +0200 From: Sheldon Hearn To: Andrzej Bialecki Cc: Ruslan Ermilov , FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-reply-to: Your message of "Mon, 15 Mar 1999 02:03:07 +0100." Date: Mon, 15 Mar 1999 08:48:29 +0200 Message-ID: <45476.921480509@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Mar 1999 02:03:07 +0100, Andrzej Bialecki wrote: > Either create /kernel.config manually, or run kget (available in > src/release/picobsd/tinyware/kget). With CURRENT, that should be /boot/kernel.conf, no? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 23:33:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 16B5814EE1; Sun, 14 Mar 1999 23:32:31 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id JAA65549; Mon, 15 Mar 1999 09:30:43 +0200 (EET) (envelope-from ru) Date: Mon, 15 Mar 1999 09:30:43 +0200 From: Ruslan Ermilov To: Andrzej Bialecki Cc: sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings Message-ID: <19990315093043.A64525@relay.ucb.crimea.ua> Mail-Followup-To: Andrzej Bialecki , sheldonh@FreeBSD.ORG, FreeBSD Hackers References: <19990314180852.A7460@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Andrzej Bialecki on Mon, Mar 15, 1999 at 02:03:07AM +0100 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 02:03:07AM +0100, Andrzej Bialecki wrote: > On Sun, 14 Mar 1999, Ruslan Ermilov wrote: > > > o Kernel change information is not saved in the new kernel, even > > though this is claimed to work in the docs. > > > > Fix: The change information is being written out, in fact, but to the > ^^^^^^^^^^^^^^^^^^^^ > Hmm... Really? What writes this info? > > > I can't get your fix to work. > > > > I've made `boot -c' changes, and `sysctl machdep.uc_devlist' produces > > non-null output, but the /kernel.config is empty. > > > > Any clue? > > Either create /kernel.config manually, or run kget (available in > src/release/picobsd/tinyware/kget). > > Andrzej Bialecki > Yes, I know, it's your child. And in -CURRENT it is available as src/sbin/kget/. I just worried about ERRATA - it is incorrect!!! `boot -c' changes are not written into /kernel.config. In 2.2.8 boot2 worried about reading /kernel.config, and dset worried about writing /kernel.config. Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 23:47:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 79789150A2 for ; Sun, 14 Mar 1999 23:46:11 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id JAA69603; Mon, 15 Mar 1999 09:41:51 +0200 (EET) (envelope-from ru) Date: Mon, 15 Mar 1999 09:41:51 +0200 From: Ruslan Ermilov To: Sheldon Hearn Cc: FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings Message-ID: <19990315094151.B64525@relay.ucb.crimea.ua> Mail-Followup-To: Sheldon Hearn , FreeBSD Hackers References: <19990314180852.A7460@relay.ucb.crimea.ua> <42980.921428831@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.95.3i In-Reply-To: <42980.921428831@axl.noc.iafrica.com>; from Sheldon Hearn on Sun, Mar 14, 1999 at 06:27:11PM +0200 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 14, 1999 at 06:27:11PM +0200, Sheldon Hearn wrote: >=20 >=20 > On Sun, 14 Mar 1999 18:08:52 +0200, Ruslan Ermilov wrote: >=20 > > I've made `boot -c' changes, and `sysctl machdep.uc_devlist' produces > > non-null output, but the /kernel.config is empty. >=20 > I don't know what you're talking about. The ERRATA notice says: >=20 man 8 kget, if you're running CURRENT. `cd /usr/src/sbin/kget; nroff -man kget.8', if you don't. > | Fix: The change information is being written out, in fact, but to the > | wrong location. move /kernel.config to /boot/kernel.conf (if it > | exists, otherwise there were no changes to save) and add the > | following lines to /boot/loader.rc: > |=20 > | load /kernel > | load -t userconfig_script /boot/kernel.conf > | autoboot 5 >=20 > What has ``sysctl machdep.uc_devlist'' got to do with anything? When I > do that, I get=20 >=20 > sysctl: unknown oid 'machdep.uc_devlist' >=20 Then you're not running(tracking) RELENG_3 ;-) # uname -r 3.1-STABLE # sysctl machdep.uc_devlist machdep.uc_devlist: =0B > The way to test whether the instructions in the ERRATA notice are > working is to make changes with -c and then check the contents of > /boot/kernel.conf . I did this (`sysctl machdep.uc_devlist' is not empty), but neither /kernel.config nor /boot/boot.conf are created. "Who" writes these changes into /kernel.config and/or /boot/boot.conf? In 2.2.8 stage2 boot (boot2) was reading info from /kernel.config, and `dset' was used in /etc/rc to update the /kernel.config with UserConfig changes. I think you should test this on 3.1-RELEASE(STABLE) and re-open the PR. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 14 23:47:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E27C150A7 for ; Sun, 14 Mar 1999 23:46:41 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id JAA69658; Mon, 15 Mar 1999 09:44:42 +0200 (EET) (envelope-from ru) Date: Mon, 15 Mar 1999 09:44:42 +0200 From: Ruslan Ermilov To: "Daniel C. Sobral" Cc: FreeBSD Hackers Subject: Re: [BTX loader]: boot command doesn't work as expected Message-ID: <19990315094442.C64525@relay.ucb.crimea.ua> Mail-Followup-To: "Daniel C. Sobral" , FreeBSD Hackers References: <19990314181851.A890@relay.ucb.crimea.ua> <36EBEA87.66E7BF16@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <36EBEA87.66E7BF16@newsguy.com>; from Daniel C. Sobral on Mon, Mar 15, 1999 at 01:57:43AM +0900 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 01:57:43AM +0900, Daniel C. Sobral wrote: > Ruslan Ermilov wrote: > > > > Hi! > > > > boot -c - works > > boot /kernel - works > > boot -c /kernel - doesn't work > > > > Any clue? > > You mean it doesn't work as _you_ expect it to? :-) No :-( I mean what I mean: `help boot' says: boot [- ...] [] Boot the system. If arguments are specified, they are added to the arguments for the kernel. If is specified, and a kernel has not already been loaded, it will be booted instead of the default kernel. > > help boot > > Boot boots. The -c flag is to be passed to the kernel, not to the > command boot. > > boot /kernel -c > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "What happened?" > "It moved, sir!" -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 0: 2:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A386214D3E for ; Mon, 15 Mar 1999 00:02:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA96407; Mon, 15 Mar 1999 00:02:01 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 00:02:01 -0800 (PST) From: Matthew Dillon Message-Id: <199903150802.AAA96407@apollo.backplane.com> To: Amancio Hasty Cc: Wes Peters , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903142046.MAA87857@rah.star-gate.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Not sure what the problem here is . Can a network chipset designer create a :chipset :with a concept of a program store? The answer is yes , if they chose to :implement :a sloppy design thats a different issue. : : Amancio You'd have to stuff wayyyy too much memory on the network card to make it useful that way, and the increased performance would only be helpful to a very small percentage of the market verses using the computer's main memory for store. It just isn't cost effective for a network card for the target audience. If the card were made for a high-end router, it would be a different story. But if you are talking PC architecture, you aren't talking high-end router. If performance is a requirement, it's cheaper to use a motherboard that has better main memory performance and perhaps even runs multiple PCI busses or a 64 bit wide PCI bus ( verses the 32 bit wide PCI that most people are used to ). You are more likely to see this then you are to see a network card with a lot of on-card memory. -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 Mon Mar 15 0:19: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.portal2.com (ns1.portal2.com [203.85.226.193]) by hub.freebsd.org (Postfix) with SMTP id C519C15379 for ; Mon, 15 Mar 1999 00:18:53 -0800 (PST) (envelope-from yusufg@huge.net) Received: (qmail 6998 invoked from network); 15 Mar 1999 08:33:21 -0000 Received: from yusufg.portal2.com (203.85.226.249) by ns1.portal2.com with SMTP; 15 Mar 1999 08:33:21 -0000 Received: (qmail 1036 invoked by uid 500); 15 Mar 1999 08:27:04 -0000 Date: 15 Mar 1999 08:27:04 -0000 Message-ID: <19990315082704.1035.qmail@yusufg.portal2.com> From: Yusuf Goolamabbas To: freebsd-hackers@freebsd.org Cc: reiser@ricochet.net, sct@redhat.com Subject: Has anybody used Postmark for file system benchmark Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Postmark is available at http://www.netapp.com/technology/level3/3022.html I am currently trying it out on various FreeBSD 3.1-STABLE boxes (It compiled cleanly). Thought I would check with others if they had any experience with this. According to the paper , UFS on Solaris 2.5 sucks so I am seeing what FreeBSD (and possibly softupdates can do) Hope to provide some results soon. I shall be also trying on Linux boxes (On Linux, I am getting the following error) /tmp/cca010271.o: In function `cli_show': /tmp/cca010271.o(.text+0x1e3d): the `getwd' function is dangerous and should not be used. Cheers, Yusuf cc: Stephen Twiddle (ext3 fame) and Hans Reiser (Reiserfs fame) -- Yusuf Goolamabbas yusufg@huge.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 0:21: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A97B715465 for ; Mon, 15 Mar 1999 00:21:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA96533; Mon, 15 Mar 1999 00:20:34 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 00:20:34 -0800 (PST) From: Matthew Dillon Message-Id: <199903150820.AAA96533@apollo.backplane.com> To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: Fifabit ethernet -- what am I doing wrong? References: <199903142036.PAA24852@skynet.ctr.columbia.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Okay, here's an update. I've been reading all the replies to this :thread, but it turns out that my main problem is that, as expected, :I was screwing something up. : :The Tigon has a PCI state register which lets you configure several :aspects operation. Two of the parameters are PCI read max and PCI write :max, which force termination of PCI reads or writes at a specified :boundaries 4 bytes, 16, 32, 64, 128, 256, 1K. I had originally set :the read and write max values for 32. It turns out that disabling :these settings (by making them 0) yields _much_ better performance. 32 bytes is only 4 PCI clocks -- a serious waste of PCI burst bandwidth. However, you should get good results with 128, 256, or 1K. You don't want completely unlimited unless you don't mind the card completely hogging the PCI bus for long periods of time. :ring fast enough). Normally the Tigon has both the PCI read and write :DMA channels active at the same time, but you can force only one to :be active at a time by setting a bit in the operating mode register. :The manual recommends _not_ doing this, but setting it yielded yet :another jump in performance. That's very interesting. Perhaps it is trying to interleave read and write requests and is blowing the burst transfers in so doing. You ought to be able to mess around with the burst length such that you can leave the DMA set for simultaniously-enabled operation. :Right now I can transmit UDP packets at around 55MB/sec with the :normal MTU and can get 91MB/sec by setting the MTU to 9000 (using :jumbo frames). TCP speed has improved too, but not quite so much as I :expected (I can get 40MB/sec with a window size of 64K and normal :MTU, 66MB/sec with jumbo frames). I still need to experiment with :the various tuning options though. I also haven't really tried :checksum offloading yet. : :-Bill These are impressive numbers. If you can increase the size of the TX and RX ring, you may be able to get even better performance. If you can avoid doing *any* PCI I/O in the heavy-load rx/tx ring case you can bump up performance another notch. That is, if the card can continue to go around the ring ( assuming you are able to process requests quickly enough such that the card never hits a 'ring full' condition and auto-disable it's DMA ), then all you may have to touch is main memory. I'm not familiar with this particular card so these sorts of features might not even exist :-( Any PCI I/O op you do will stall the cpu significantly. This is the same sort of problem that limits SCSI transactional capabilities. -Matt Matthew Dillon :-- :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 0:25:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles125.castles.com [208.214.165.125]) by hub.freebsd.org (Postfix) with ESMTP id 74A1014E96 for ; Mon, 15 Mar 1999 00:25:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA10739; Mon, 15 Mar 1999 00:19:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903150819.AAA10739@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Bill Paul , hackers@FreeBSD.ORG Subject: Re: Fifabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Mon, 15 Mar 1999 00:20:34 PST." <199903150820.AAA96533@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 00:19:45 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Okay, here's an update. I've been reading all the replies to this > :thread, but it turns out that my main problem is that, as expected, > :I was screwing something up. > : > :The Tigon has a PCI state register which lets you configure several > :aspects operation. Two of the parameters are PCI read max and PCI write > :max, which force termination of PCI reads or writes at a specified > :boundaries 4 bytes, 16, 32, 64, 128, 256, 1K. I had originally set > :the read and write max values for 32. It turns out that disabling > :these settings (by making them 0) yields _much_ better performance. > > 32 bytes is only 4 PCI clocks -- a serious waste of PCI burst > bandwidth. However, you should get good results with 128, 256, or > 1K. You don't want completely unlimited unless you don't mind > the card completely hogging the PCI bus for long periods of > time. It won't ever hog it for (much) longer than the PCI latency count; the arbiter will push it off the bus once the latency counter expires after someone else requests it. If the bus is relatively quiet, not re-cycling every few dozen cycles will improve things (a little). > :ring fast enough). Normally the Tigon has both the PCI read and write > :DMA channels active at the same time, but you can force only one to > :be active at a time by setting a bit in the operating mode register. > :The manual recommends _not_ doing this, but setting it yielded yet > :another jump in performance. > > That's very interesting. Perhaps it is trying to interleave read > and write requests and is blowing the burst transfers in so doing. > You ought to be able to mess around with the burst length such > that you can leave the DMA set for simultaniously-enabled > operation. I'd guess that it may only have a single PCI FIFO in the bridge, and it has to drain/fill it as it turns around. That'd certainly hurt. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Mar 15 0:42: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 401C614DA8; Mon, 15 Mar 1999 00:41:58 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 2268C18C3; Mon, 15 Mar 1999 09:41:49 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 1B3D04992; Mon, 15 Mar 1999 09:41:49 +0100 (CET) Date: Mon, 15 Mar 1999 09:41:47 +0100 (CET) From: Andrzej Bialecki To: Ruslan Ermilov Cc: sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-Reply-To: <19990315093043.A64525@relay.ucb.crimea.ua> 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, 15 Mar 1999, Ruslan Ermilov wrote: > I just worried about ERRATA - it is incorrect!!! > `boot -c' changes are not written into /kernel.config. > > In 2.2.8 boot2 worried about reading /kernel.config, > and dset worried about writing /kernel.config. Ehm, not quite. boot2 in 2.2.8 read the boot.conf which was just the boot flags. The actual changes from UserConfig were being extracted and written out as binary patches to the kernel (can you say "ugly"?). Or, alternatively, you could write them manually into /kernel.config, and they would be automatically read by /kernel, whether you wanted it or not. Now, boot2 reads about the same info, but from /boot/boot.conf, but if you don't load /kernel.config explicitely, /kernel ignores it. 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 Mon Mar 15 1:13:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 8300514E6B; Mon, 15 Mar 1999 01:12:27 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id LAA91533; Mon, 15 Mar 1999 11:11:08 +0200 (EET) (envelope-from ru) Date: Mon, 15 Mar 1999 11:11:08 +0200 From: Ruslan Ermilov To: Andrzej Bialecki Cc: sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings Message-ID: <19990315111108.A91476@relay.ucb.crimea.ua> Mail-Followup-To: Andrzej Bialecki , sheldonh@FreeBSD.ORG, FreeBSD Hackers References: <19990315093043.A64525@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Andrzej Bialecki on Mon, Mar 15, 1999 at 09:41:47AM +0100 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 09:41:47AM +0100, Andrzej Bialecki wrote: > On Mon, 15 Mar 1999, Ruslan Ermilov wrote: > > > I just worried about ERRATA - it is incorrect!!! > > `boot -c' changes are not written into /kernel.config. > > > > In 2.2.8 boot2 worried about reading /kernel.config, > > and dset worried about writing /kernel.config. > > Ehm, not quite. boot2 in 2.2.8 read the boot.conf which was just the boot > flags. The actual changes from UserConfig were being extracted and written > out as binary patches to the kernel (can you say "ugly"?). Or, > alternatively, you could write them manually into /kernel.config, and > they would be automatically read by /kernel, whether you wanted it or not. > > Now, boot2 reads about the same info, but from /boot/boot.conf, but if you > don't load /kernel.config explicitely, /kernel ignores it. > So, what is the current way to save kernel changes? Is it possible without kget? Is ERRATA.TXT correct? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 1:21: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obr.software602.cz (unknown [194.108.5.200]) by hub.freebsd.org (Postfix) with ESMTP id C3F6114D6B for ; Mon, 15 Mar 1999 01:20:48 -0800 (PST) (envelope-from bsd@obr.software602.cz) Received: from localhost (bsd@localhost) by obr.software602.cz (8.9.2/8.9.2) with ESMTP id KAA07076; Mon, 15 Mar 1999 10:16:29 +0100 (CET) (envelope-from bsd@obr.software602.cz) Date: Mon, 15 Mar 1999 10:16:27 +0100 (CET) From: FreeBsd To: Bosko Milekic Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: thread and socket 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 in multithreaded app is recvfrom only waiting for data, but cannot finish with EAGAIN error, when I set SO_RCVTIMEO. I need stop recv function after timeout. in the non threaded version rcv is finish after timeout (no data is received) , but in multi threaded ver doesn't stop and still is waiting for data. any data is not comming and ercvfrom is still wiating. WHY????? thanks. honza On Sun, 14 Mar 1999, Bosko Milekic wrote: > > I've had a little trouble understanding you... :-) > > Here's an excerpt from the man page, though... if this isn't what you were > looking for, please clarify a bit... > > --snip-- > In the non-threaded library getsockopt() is implemented as the > getsockopt syscall. > > In the threaded library, the getsockopt syscall is assembled to _thread_sys_getsockopt() > and getsockopt() is implemented as a function which locks s for read and > write, then calls _thread_sys_getsockopt(). > Before returning, getsockopt() unlocks s. > --snip-- > > Regards, > Bosko. > > -- > Bosko Milekic http://www.supernet.ca/~bmilekic/ > Delphi SuperNet voice: (+1) 514 281-7500 fax: (+1) 514 281-6599 > PGP Key available upon request. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 2: 7:13 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 9705714CFE for ; Mon, 15 Mar 1999 02:07:11 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA22450; Mon, 15 Mar 1999 19:05:49 +0900 (JST) Message-ID: <36ECDB2B.5608480E@newsguy.com> Date: Mon, 15 Mar 1999 19:04:27 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Ruslan Ermilov Cc: FreeBSD Hackers Subject: Re: [BTX loader]: boot command doesn't work as expected References: <19990314181851.A890@relay.ucb.crimea.ua> <36EBEA87.66E7BF16@newsguy.com> <19990315094442.C64525@relay.ucb.crimea.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > No :-( > > I mean what I mean: > > `help boot' says: > > boot [- ...] [] > > Boot the system. If arguments are specified, they are added to the > arguments for the kernel. If is specified, and a kernel > has not already been loaded, it will be booted instead of the default > kernel. Ouch! The help message is so wrong that I never even suspected it could have been this wrong... :-( -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 2:20:26 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 858C814E8F for ; Mon, 15 Mar 1999 02:20:21 -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 2.12 #1) id 10MURW-000CDh-00; Mon, 15 Mar 1999 12:17:54 +0200 From: Sheldon Hearn To: Ruslan Ermilov Cc: FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-reply-to: Your message of "Mon, 15 Mar 1999 09:41:51 +0200." <19990315094151.B64525@relay.ucb.crimea.ua> Date: Mon, 15 Mar 1999 12:17:54 +0200 Message-ID: <46976.921493074@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Mar 1999 09:41:51 +0200, Ruslan Ermilov wrote: > > sysctl: unknown oid 'machdep.uc_devlist' > Then you're not running(tracking) RELENG_3 ;-) You're right, I'm tracking HEAD, that is CURRENT. > I think you should test this on 3.1-RELEASE(STABLE) and re-open the PR. Basically, from the other mail I've seen from you, you want ERRATA.TXT to be correct, yes? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 2:23:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 5E4FF14DFB for ; Mon, 15 Mar 1999 02:22:32 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id MAA09322; Mon, 15 Mar 1999 12:18:24 +0200 (EET) (envelope-from ru) Date: Mon, 15 Mar 1999 12:18:24 +0200 From: Ruslan Ermilov To: "Daniel C. Sobral" Cc: FreeBSD Hackers Subject: Re: [BTX loader]: boot command doesn't work as expected Message-ID: <19990315121824.A9285@relay.ucb.crimea.ua> Mail-Followup-To: "Daniel C. Sobral" , FreeBSD Hackers References: <19990314181851.A890@relay.ucb.crimea.ua> <36EBEA87.66E7BF16@newsguy.com> <19990315094442.C64525@relay.ucb.crimea.ua> <36ECDB2B.5608480E@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <36ECDB2B.5608480E@newsguy.com>; from Daniel C. Sobral on Mon, Mar 15, 1999 at 07:04:27PM +0900 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 07:04:27PM +0900, Daniel C. Sobral wrote: > Ruslan Ermilov wrote: > > > > No :-( > > > > I mean what I mean: > > > > `help boot' says: > > > > boot [- ...] [] > > > > Boot the system. If arguments are specified, they are added to the > > arguments for the kernel. If is specified, and a kernel > > has not already been loaded, it will be booted instead of the default > > kernel. > > Ouch! The help message is so wrong that I never even suspected it > could have been this wrong... :-( > Thanks! Mike Smith has already updated help. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 2:29:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id E90C914F37 for ; Mon, 15 Mar 1999 02:28:15 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id MAA10725; Mon, 15 Mar 1999 12:25:08 +0200 (EET) (envelope-from ru) Date: Mon, 15 Mar 1999 12:25:08 +0200 From: Ruslan Ermilov To: Sheldon Hearn Cc: FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings Message-ID: <19990315122508.A9370@relay.ucb.crimea.ua> Mail-Followup-To: Sheldon Hearn , FreeBSD Hackers References: <19990315094151.B64525@relay.ucb.crimea.ua> <46976.921493074@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <46976.921493074@axl.noc.iafrica.com>; from Sheldon Hearn on Mon, Mar 15, 1999 at 12:17:54PM +0200 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 12:17:54PM +0200, Sheldon Hearn wrote: > > > On Mon, 15 Mar 1999 09:41:51 +0200, Ruslan Ermilov wrote: > > > > sysctl: unknown oid 'machdep.uc_devlist' > > Then you're not running(tracking) RELENG_3 ;-) > > You're right, I'm tracking HEAD, that is CURRENT. > > > I think you should test this on 3.1-RELEASE(STABLE) and re-open the PR. > > Basically, from the other mail I've seen from you, you want ERRATA.TXT > to be correct, yes? > In fact, I would like to be able to save/restore `boot -c' changes on my 3.1-STABLE system. The method you have provided in ERRATA.TXT does not work. What is the correct way to do it? According to your ERRATA entry, these changes are saved to /kernel.config. What part of kernel/boot blocks/loader saves these changes to /kernel.config? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 3: 2:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id DCBE515425 for ; Mon, 15 Mar 1999 03:02:53 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id MAA45110; Mon, 15 Mar 1999 12:02:30 +0100 (CET) (envelope-from des) To: Nathan Dorfman Cc: hackers@FreeBSD.ORG Subject: Re: Proposed patch to /etc/rc References: <19990314192028.A26063@rtfm.net> From: Dag-Erling Smorgrav Date: 15 Mar 1999 12:02:30 +0100 In-Reply-To: Nathan Dorfman's message of "Sun, 14 Mar 1999 19:20:28 -0500" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nathan Dorfman writes: > On Fri, Mar 12, 1999 at 07:14:56PM +0100, Dag-Erling Smorgrav wrote: > > # Whack the pty perms back into shape. > > chmod 666 /dev/tty[pqrsPQRS]* > > +chown root.tty /dev/tty/[pqrsPQRS]* > ^ > Should that be there? No. It's already been fixed. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 4:46: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from at.dotat.com (zed.dotat.com [203.2.134.254]) by hub.freebsd.org (Postfix) with ESMTP id 8D7DA150EF for ; Mon, 15 Mar 1999 04:45:52 -0800 (PST) (envelope-from hart@at.dotat.com) Received: from at.dotat.com (localhost.dotat.com [127.0.0.1]) by at.dotat.com (8.8.8/8.8.8) with ESMTP id XAA14560; Mon, 15 Mar 1999 23:15:24 +1030 (CST) Message-Id: <199903151245.XAA14560@at.dotat.com> To: "Curtis Wilbar [STAFF]" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bootable cd q In-reply-to: Your message of "Sun, 14 Mar 1999 16:03:44 CDT." <199903142103.QAA17943@pike.ici.net> Date: Mon, 15 Mar 1999 23:15:24 +1030 From: Leigh Hart Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Curtis, "Curtis Wilbar [STAFF]" wrote: > > Can anyone point me to a website, ftpsite, etc that would detail > how to make a freebsd bootable cd-rom ? I've found info on mkisofs > and in general how it works, but I'm looking for freebsd specific > info (i.e. how to make a bootable cd from the downloaded images/etc). > > I'd appreciate any info you could provide. cd /usr/share/examples/worm/ read it and weep (it is *not* easy). then go to /usr/src/release and investigate write_mfs_in_kernel.c, you will need it. The process has changed a bit since I did it on FreeBSD-2.2.5, so I won't go into detaills here about what I did, it was an ugly hack, but then again, el toro (yip yip yeehaa sp!??!) CD booting is ugly at the best of times. Cheers Leigh -- | "By the time they had diminished | Leigh Hart, | | from 50 to 8, the other dwarves | Dotat Communications Pty Ltd | | began to suspect 'Hungry' ..." | GPO Box 487 Adelaide SA 5001 | | -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 5:39:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 7D7A914E47 for ; Mon, 15 Mar 1999 05:39:42 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id IAA03845; Mon, 15 Mar 1999 08:39:05 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199903151339.IAA03845@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty Cc: Wes Peters , Matthew Dillon , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903150615.WAA92542@rah.star-gate.com> In-reply-to: Your message of "Sun, 14 Mar 1999 22:15:14 PST." <199903150615.WAA92542@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 08:39:05 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oh, Don't worry I know that there are people on this list that know the answer > that you have suggested --- for instance just take a peek at > http://www.juniper.net those guys operate in the giga packet per second range > of course if we want to know what they are doing we may have > to resort to Mediaval Spanish Inquisition style of interrogation 8) The FreeBSD part of the Juniper M40 is not at all involved in the packet forwarding function, other than computing routing tables for the, er.., very interesting hardware. PCI bus bandwidth is just not an issue in this application at all. The FreeBSD part of the juniper router has a an Ethernet interface on it for management and control purposes; it's primary job is to run the routing protocols. As far as performance, it's just not meaninful to talk about packets per second and the like. The only important measure is "wire-speed forwarding performance on all interfaces all the time regardless of packet size." On a box with 8 OC-48c interfaces (2.4 Gb/s, full duplex), this sure doesn't involve a bunch of boards on a PCI bus. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 5:50: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gwi.net (mail.gwi.net [204.120.68.142]) by hub.freebsd.org (Postfix) with ESMTP id 8CC1614E6B for ; Mon, 15 Mar 1999 05:49:57 -0800 (PST) (envelope-from fkittred@mail.gwi.net) Received: from mail.gwi.net (fkittred@localhost [127.0.0.1]) by mail.gwi.net (8.8.5/8.8.7) with ESMTP id IAA23796; Mon, 15 Mar 1999 08:48:03 -0500 (EST) Message-Id: <199903151348.IAA23796@mail.gwi.net> To: W Gerald Hicks Cc: dillon@apollo.backplane.com, hasty@rah.star-gate.com, wes@softweyr.com, ckempf@enigami.com, wpaul@skynet.ctr.columbia.edu, freebsd-hackers@freebsd.org Reply-To: dillon@apollo.backplane.com, fkittred@mail.gwi.net Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Sun, 14 Mar 1999 21:59:44 EST." <19990314215944E.wghicks@wghicks.bellsouth.net> Date: Mon, 15 Mar 1999 08:48:02 -0500 From: Fletcher E Kittredge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Mar 1999 21:59:44 -0500 W Gerald Hicks wrote: > Erm... Depends on what one wants to do with it :) > > I believe certain market segments would welcome a Gigabit > Ethernet subsystem on a Rambus with huge memory buffers. Hum, the only use of such cards would be PC routers? You are talking with a builder/maintainer of PC routers :) Having said that, our market niche is *way* small. I don't think this is a profitable niche. I think that one would be building so few cards, the cost would be so great per card that it would be cheaper to buy a Cisco. There are many hidden costs to developing/building/testing/maintaining/operating PC routers and Ciscos are already probably cheaper in the long run. regards, fletcher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 5:53:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gwi.net (mail.gwi.net [204.120.68.142]) by hub.freebsd.org (Postfix) with ESMTP id 7D125150BD for ; Mon, 15 Mar 1999 05:53:17 -0800 (PST) (envelope-from fkittred@mail.gwi.net) Received: from mail.gwi.net (fkittred@localhost [127.0.0.1]) by mail.gwi.net (8.8.5/8.8.7) with ESMTP id IAA26873; Mon, 15 Mar 1999 08:52:12 -0500 (EST) Message-Id: <199903151352.IAA26873@mail.gwi.net> To: Wes Peters Cc: Matthew Dillon , Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@freebsd.org Reply-To: Matthew Dillon Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Sun, 14 Mar 1999 21:48:02 MST." <36EC9102.119A6973@softweyr.com> Date: Mon, 15 Mar 1999 08:52:11 -0500 From: Fletcher E Kittredge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Mar 1999 21:48:02 -0700 Wes Peters wrote: > > > > On Sun, 14 Mar 1999 12:46:07 -0800 Amancio Hasty wrote: > > > > > > Not sure what the problem here is . Can a network chipset designer > > > create a chipset with a concept of a program store? The answer is yes > > > , if they chose to implement a sloppy design thats a different issue. > > > > Amancio; How big do you envision the queues on a NIC card need to be > > to handle a moderately loaded, full duplex gigabit ethernet? > > 8 MB of high-speed SDRAM for 2 ports, with hardware queueing support. > I can't tell you how I know this, or I'd have to kill -1 you. ;^) > -- Well, good luck Wes; I will be rooting for you and yours. However, I have been building/tinkering with this kind of router since 1984, and I don't think it is going to survive in any meaningful way. The marketing/economic challenges are just too great. regards, fletcher P.S. I hope to be one of your first customers! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 6:38:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 057D214F81 for ; Mon, 15 Mar 1999 06:38:44 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA15530; Mon, 15 Mar 1999 15:37:54 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA98709; Mon, 15 Mar 1999 15:37:36 +0100 (MET) Date: Mon, 15 Mar 1999 15:37:35 +0100 From: Eivind Eklund To: Yusuf Goolamabbas Cc: freebsd-hackers@FreeBSD.ORG, reiser@ricochet.net, sct@redhat.com Subject: Re: Has anybody used Postmark for file system benchmark Message-ID: <19990315153735.B98270@bitbox.follo.net> References: <19990315082704.1035.qmail@yusufg.portal2.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990315082704.1035.qmail@yusufg.portal2.com>; from Yusuf Goolamabbas on Mon, Mar 15, 1999 at 08:27:04AM -0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 08:27:04AM -0000, Yusuf Goolamabbas wrote: > Postmark is available at > > http://www.netapp.com/technology/level3/3022.html > > I am currently trying it out on various FreeBSD 3.1-STABLE boxes (It > compiled cleanly). Thought I would check with others if they had any > experience with this. According to the paper , UFS on Solaris 2.5 > sucks so I am seeing what FreeBSD (and possibly softupdates can do) > > Hope to provide some results soon. I shall be also trying on Linux > boxes (On Linux, I am getting the following error) Remember that the default tuning on the FreeBSD boxes and the Linux boxes are different; this has to be reflected if you're going to attempt to do a fair benchmark. The different modes are Linux FreeBSD Fully synchronous sync sync "Synchronous" metadata, async data N/A (default mode) Fully async (unordered metadata writes)[1] default async Tracking dependencies N/A "soft updates" [1] This mode is highly disfunctional if your data is critical. The normal file system invariants (e.g, that data you write end up in a file you own) are not honoured across unscheduled reboots. It is very useful for news spools etc, of course. Comparing the Linux default to the FreeBSD default is pretty uninteresting; the tradeoffs are totally different. IMO, the most interesting compares are Linux sync against FreeBSD anything-but-async, and Linux async vs FreeBSD async. When you're giving out results, please also include information about the exact hardware platform - a hardware platform that caches will tend to skew the results. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 7:34:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id AE2BE14E7F for ; Mon, 15 Mar 1999 07:34:02 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id KAA08262; Mon, 15 Mar 1999 10:33:23 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id KAA90456; Mon, 15 Mar 1999 10:33:08 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 15 Mar 1999 10:33:08 -0500 (EST) To: Wes Peters Cc: Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-Reply-To: <36EB482B.14BD236@softweyr.com> References: <199903140500.VAA73230@rah.star-gate.com> <36EB482B.14BD236@softweyr.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14061.8781.846625.55858@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > Amancio Hasty wrote: > > > > > 200 Mb/s = 25 MB/s, which seems a little low, but is within the realm of > > > what I would expect. > > > > I think the system should be able to support at least 70MB/s at least I do over here > > with a bt848 video capture board capturing 640x480x4 at 30 frames per second > > and then displaying the frames on video display card 8) > > An article in IEEE Computer magazine last summer reported achieving > 320 Mb/s throughput with Myricom Myrinet boards on FreeBSD. I've > seen this number batted around industry publications like Network > World a number of times also. That would seem to require only a 10 > Mhz clock with a 32-bit bus bandwidth; is there really this much > overhead in the PCI transactions? Its possible to do far better with Myrinet hardware. I haven't read the article in question, but I suspect that they're using the Myricom supplied firmware. If so, the overhead is not the Myrinet PCI adaptor, nor is it the PCI bus, nor is it in FreeBSD, rather its in the firmware running on the card. The Myricom MyriApi firmware is overly complex and quite slow. Their API also forces one to do many memory-mapped reads from the adaptor. As you can imagine, doing reads across the PCI bus is painfully slow. Using much more efficient firmware (the Duke Trapeze MCP) we're able to get 660Mb/s between 2 450Mhz PIIs (Asus P2B) using a standard FreeBSD-4.0 IP stack & a very large MTU (57k): <9:55am>muffin/gallatin:api>netperf -Hgrits-my TCP STREAM TEST to grits-my : histogram Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 1048576 1048576 1048576 10.01 660.97 Using local zero-copy modifications on both the send & receive side, we see better than 800Mb/s: <9:57am>muffin/gallatin:api>netperf -Hgrits-my TCP STREAM TEST to grits-my : histogram Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 524288 524288 524288 10.01 808.61 This 101MB/sec is still far below the measured DMA bandwidth of the LANai4 in a 440BX motherboard (over 130MB/sec for both reads and writes). Most of the difference between the theoretical 132MB/sec max bandwidth and our 100MB/sec is due to the fact that the LANai4 has a slow CPU and terrible memory bandwidth. The new LANai7's will have a much faster CPU, and much better memory bandwidth (as well as a DMA engine which can do IP checksum offloading). We expect to see much better performance from these boards. Given that the Tigon-II adaptors have 2 Mips R4000 CPU's and can do checksum offloading, I expect wonderful things from them as well. I've been playing with the latest revision Bill's tigon driver (where he's found some chip settings which optimize DMA performance) and have seen UDP xmit performance of 850Mb/s. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 7:59:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 8CEDF14EEC for ; Mon, 15 Mar 1999 07:59:01 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id IAA12360; Mon, 15 Mar 1999 08:58:07 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36ED2E0F.6B0028DB@softweyr.com> Date: Mon, 15 Mar 1999 08:58:07 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@freebsd.org Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903151352.IAA26873@mail.gwi.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fletcher E Kittredge wrote: > > On Sun, 14 Mar 1999 21:48:02 -0700 Wes Peters wrote: > > > > > > On Sun, 14 Mar 1999 12:46:07 -0800 Amancio Hasty wrote: > > > > > > > > Not sure what the problem here is . Can a network chipset designer > > > > create a chipset with a concept of a program store? The answer is yes > > > > , if they chose to implement a sloppy design thats a different issue. > > > > > > Amancio; How big do you envision the queues on a NIC card need to be > > > to handle a moderately loaded, full duplex gigabit ethernet? > > > > 8 MB of high-speed SDRAM for 2 ports, with hardware queueing support. > > I can't tell you how I know this, or I'd have to kill -1 you. ;^) > > -- > > Well, good luck Wes; I will be rooting for you and yours. However, I > have been building/tinkering with this kind of router since 1984, and > I don't think it is going to survive in any meaningful way. The > marketing/economic challenges are just too great. Tell that to Alcatel, who just agreed to pay $2 billion for us. > P.S. I hope to be one of your first customers! You're about 5 years too late for that. See http://www.xylan.com/ for the full poop. You'll specifically want to look at the Omni Switch/ Router and the 2-port GSX Gigabit Ethernet card. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 8: 0:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id E695114F96; Mon, 15 Mar 1999 08:00:43 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 5ACFF18C4; Mon, 15 Mar 1999 17:00:32 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 5312D4988; Mon, 15 Mar 1999 17:00:32 +0100 (CET) Date: Mon, 15 Mar 1999 17:00:32 +0100 (CET) From: Andrzej Bialecki To: Ruslan Ermilov Cc: sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-Reply-To: <19990315111108.A91476@relay.ucb.crimea.ua> 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, 15 Mar 1999, Ruslan Ermilov wrote: > So, what is the current way to save kernel changes? Use kget. > Is it possible without kget? Yes, if you write an application like kget. :-) > Is ERRATA.TXT correct? Probably not. 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 Mon Mar 15 8: 3:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 594D0150B0 for ; Mon, 15 Mar 1999 08:03:31 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id JAA12375; Mon, 15 Mar 1999 09:01:47 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36ED2EEB.E4A0DDCE@softweyr.com> Date: Mon, 15 Mar 1999 09:01:47 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903140500.VAA73230@rah.star-gate.com> <36EB482B.14BD236@softweyr.com> <14061.8781.846625.55858@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin wrote: > > Wes Peters writes: > > Amancio Hasty wrote: > > > > > > > 200 Mb/s = 25 MB/s, which seems a little low, but is within the realm of > > > > what I would expect. > > > > > > I think the system should be able to support at least 70MB/s at least I do over here > > > with a bt848 video capture board capturing 640x480x4 at 30 frames per second > > > and then displaying the frames on video display card 8) > > > > An article in IEEE Computer magazine last summer reported achieving > > 320 Mb/s throughput with Myricom Myrinet boards on FreeBSD. I've > > seen this number batted around industry publications like Network > > World a number of times also. That would seem to require only a 10 > > Mhz clock with a 32-bit bus bandwidth; is there really this much > > overhead in the PCI transactions? > > Its possible to do far better with Myrinet hardware. > > I haven't read the article in question, but I suspect that they're > using the Myricom supplied firmware. If so, the overhead is not the > Myrinet PCI adaptor, nor is it the PCI bus, nor is it in FreeBSD, > rather its in the firmware running on the card. The Myricom MyriApi > firmware is overly complex and quite slow. Their API also forces one > to do many memory-mapped reads from the adaptor. As you can imagine, > doing reads across the PCI bus is painfully slow. > > Using much more efficient firmware (the Duke Trapeze MCP) we're able > to get 660Mb/s between 2 450Mhz PIIs (Asus P2B) using a standard > FreeBSD-4.0 IP stack & a very large MTU (57k): > > <9:55am>muffin/gallatin:api>netperf -Hgrits-my > TCP STREAM TEST to grits-my : histogram > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > > 1048576 1048576 1048576 10.01 660.97 > > Using local zero-copy modifications on both the send & receive side, > we see better than 800Mb/s: > > <9:57am>muffin/gallatin:api>netperf -Hgrits-my > TCP STREAM TEST to grits-my : histogram > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > > 524288 524288 524288 10.01 808.61 > > This 101MB/sec is still far below the measured DMA bandwidth of the > LANai4 in a 440BX motherboard (over 130MB/sec for both reads and > writes). Most of the difference between the theoretical 132MB/sec max > bandwidth and our 100MB/sec is due to the fact that the LANai4 has a > slow CPU and terrible memory bandwidth. The new LANai7's will have a > much faster CPU, and much better memory bandwidth (as well as a DMA > engine which can do IP checksum offloading). We expect to see much > better performance from these boards. > > Given that the Tigon-II adaptors have 2 Mips R4000 CPU's and can do > checksum offloading, I expect wonderful things from them as well. > I've been playing with the latest revision Bill's tigon driver (where > he's found some chip settings which optimize DMA performance) and have > seen UDP xmit performance of 850Mb/s. I guess I should take a look at your software and get a card or two in for testing. I'd like to see what we can do between two Tigon equipped systems with a Xylan switch in the middle. Most of our testing on our Gigabit modules so far has been done with a SmartBits packet generator, but I don't really believe the numbers until I've seen some real host-generated data streams. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 8:19:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (Postfix) with ESMTP id B4E4514C08 for ; Mon, 15 Mar 1999 08:19:14 -0800 (PST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id LAA04085 for ; Mon, 15 Mar 1999 11:18:55 -0500 (EST) Received: from bmcgover-pc.cisco.com (localhost.pa.dtd.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.9.2/8.9.2) with ESMTP id LAA00541 for ; Mon, 15 Mar 1999 11:18:54 -0500 (EST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <199903151618.LAA00541@bmcgover-pc.cisco.com> To: hackers@freebsd.org Subject: Docs on Interrupt registration changes (2.2.x to 3.0 to 3.1) ??? Date: Mon, 15 Mar 1999 11:18:54 -0500 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, managed to get blindsided again today trying to move some device drivers to 3.1... Apparently, at least with ISA device drivers, you must now register the interrupts that they use. So, from what I've seen, in 2.2.X, ISA drivers register themselves based on the kernel configuration. PCI just "did the right thing" In 3.0, you had to add ISA device drivers to isa_device.h in one of the kernel directories to get them registered automatically. PCI, again, appears to do the "right thing"(tm) automatically. In 3.1, it appears that you have to call functions out of kern_intr.c to get ISA interrupts registered properly. So far, it appears PCI continues to work as it did (although I really haven't looked at this in 3.1). So, given the changes, could someone point me at a primer for 3.1 for the "expected changes" to ISA drivers to get them up and running under 3.1? Thanks. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 8:22: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8929614C08 for ; Mon, 15 Mar 1999 08:22:02 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA09136; Mon, 15 Mar 1999 11:21:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id LAA91676; Mon, 15 Mar 1999 11:21:28 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 15 Mar 1999 11:21:28 -0500 (EST) To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-Reply-To: <36ED2EEB.E4A0DDCE@softweyr.com> References: <199903140500.VAA73230@rah.star-gate.com> <36EB482B.14BD236@softweyr.com> <14061.8781.846625.55858@grasshopper.cs.duke.edu> <36ED2EEB.E4A0DDCE@softweyr.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14061.12878.855490.654177@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > > I guess I should take a look at your software and get a card or two > in for testing. I'd like to see what we can do between two Tigon > equipped systems with a Xylan switch in the middle. Most of our If the switch doesn't support jumbo frames, you may be disappointed... > testing on our Gigabit modules so far has been done with a SmartBits > packet generator, but I don't really believe the numbers until I've > seen some real host-generated data streams. If possible, wait until the end of April for the Lanai7.. We're about to put out a new release of Trapeze and what we have on the web is very stale. Contact me privately if you'd like early access. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 8:48:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 1C88315143 for ; Mon, 15 Mar 1999 08:48:12 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id JAA28147 for ; Mon, 15 Mar 1999 09:55:54 -0700 (MST) Message-Id: <199903151655.JAA28147@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: hackers@FreeBSD.ORG Subject: power-off without halt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 09:55:54 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We are looking at using FreeBSD as an "embedded OS" inside a line of instruments we are building. I think I have a handle on all the issues except how to cleanly handle shutdown where there is no console, and thus no way to send a 'halt' command. The requirement is that the user can merely turn off the power, nothing more required. I can modify the disk setup, kernel/util code as needed, I just need some idea for a workable solution. Has anyone delt with this problem before? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 9: 0:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (Postfix) with SMTP id 20A1814D8A for ; Mon, 15 Mar 1999 09:00:52 -0800 (PST) (envelope-from jamie@itribe.net) Message-Id: <199903130407.XAA17643@gatekeeper.itribe.net> Received: forwarded by SMTP 1.5.2. Received: from localhost (jamie@localhost) by marsellus.itribe.net (8.8.5/8.8.6) with SMTP id XAA15796; Fri, 12 Mar 1999 23:04:27 -0500 (EST) Date: Fri, 12 Mar 1999 23:04:27 -0500 (EST) From: Jamie Bowden To: Mike Smith Cc: Wes Peters , Charles Mott , freebsd-hackers@FreeBSD.ORG Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) In-Reply-To: <199903122218.OAA01216@dingo.cdrom.com> 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, 12 Mar 1999, Mike Smith wrote: > A staffer at WC recently ordered service from @home, and reported that > it took about 30 seconds to configure his FreeBSD system to use it, > compared to about 5 reboots and 30+ minutes for W95 on the same > machine. He's written up a FAQ entry for @home and is hoping that they > will add it to their list. The thing your going to run into here is that depending on your reseller(mine is cox@home service), depends on how you get your ip, and it's status. Mine is dhcp'd, but it's the same one everytime. I've run into other @home users on different cable systems with different setups. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 9: 4: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id DD45C14BD6; Mon, 15 Mar 1999 09:03:59 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA29998; Mon, 15 Mar 1999 12:08:14 -0500 (EST) Date: Mon, 15 Mar 1999 12:08:12 -0500 (EST) From: Alfred Perlstein To: Eivind Eklund Cc: freebsd-hackers@FreeBSD.ORG Subject: tuneing, was: Re: Has anybody used Postmark for file system benchmark In-Reply-To: <19990315153735.B98270@bitbox.follo.net> 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, 15 Mar 1999, Eivind Eklund wrote: > On Mon, Mar 15, 1999 at 08:27:04AM -0000, Yusuf Goolamabbas wrote: > > Postmark is available at > > > > http://www.netapp.com/technology/level3/3022.html > > > > I am currently trying it out on various FreeBSD 3.1-STABLE boxes (It > > compiled cleanly). Thought I would check with others if they had any > > experience with this. According to the paper , UFS on Solaris 2.5 > > sucks so I am seeing what FreeBSD (and possibly softupdates can do) > > > > Hope to provide some results soon. I shall be also trying on Linux > > boxes (On Linux, I am getting the following error) > > Remember that the default tuning on the FreeBSD boxes and the Linux > boxes are different; this has to be reflected if you're going to > attempt to do a fair benchmark. The different modes are > > Linux FreeBSD > Fully synchronous sync sync > "Synchronous" metadata, > async data N/A (default mode) > Fully async (unordered > metadata writes)[1] default async > Tracking dependencies N/A "soft updates" > > [1] This mode is highly disfunctional if your data is critical. The > normal file system invariants (e.g, that data you write end up in a > file you own) are not honoured across unscheduled reboots. It is very > useful for news spools etc, of course. > > Comparing the Linux default to the FreeBSD default is pretty > uninteresting; the tradeoffs are totally different. IMO, the most > interesting compares are Linux sync against FreeBSD > anything-but-async, and Linux async vs FreeBSD async. > > When you're giving out results, please also include information about > the exact hardware platform - a hardware platform that caches will > tend to skew the results. I think that it's very important that a file, perhaps BENCH.TXT or equiv explain these issues. A lot of performance options are turned off to help the install actually work, just because it installs this way doesn't mean it's tuned. Several of my friends use FreeBSD but aren't on these lists and don't have the time/knowledge to look into /usr/src/sys to tune things. Things to consider: pointers to: softupdates, turning on DMA/multiblock for IDE, removing the 386/486 options in the kernel increasing MAXUSERS/NMBCLUSTERS for heavily loaded machines I started to put togther a "tuning freebsd" page a year ago, it sucks, it's out of date, but you can check it out here: http://www.genx.net/~bright/unix/optimizing.html don't laugh, i haven't touched the pages in over a year... :) I think it's so important that a link off the main freebsd page would be a good idea (not to my page) but something done and kept updated like src/UPDATING and perhaps a dialog at the end of sysinstall: "Your install is complete, please visit http://www.freebsd.org/tuning for information on improving your machine's performance" I know people using freebsd longer than I have who didn't know about IDE tuning until I told them about it. Doesn't it suck when you see a FreeBSD benchmark and you see the quote "we used the default settings"? -Alfred > > Eivind. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 9: 6:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 52FD614E87 for ; Mon, 15 Mar 1999 09:06:39 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA22610; Mon, 15 Mar 1999 12:10:49 -0500 (EST) Date: Mon, 15 Mar 1999 12:10:48 -0500 (EST) From: Alfred Perlstein To: Steve Passe Cc: hackers@FreeBSD.ORG Subject: Re: power-off without halt In-Reply-To: <199903151655.JAA28147@Ilsa.StevesCafe.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, 15 Mar 1999, Steve Passe wrote: > Hi, > > We are looking at using FreeBSD as an "embedded OS" inside a line > of instruments we are building. I think I have a handle on all the > issues except how to cleanly handle shutdown where there is no > console, and thus no way to send a 'halt' command. The requirement > is that the user can merely turn off the power, nothing more required. > > I can modify the disk setup, kernel/util code as needed, I just need some > idea for a workable solution. Has anyone delt with this problem before? Some sort of inexpensive internal UPS system that would notify a deamon the the power has been cut to allow for a clean shutdown? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 9:13:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 2B3DE14C3F for ; Mon, 15 Mar 1999 09:13:56 -0800 (PST) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id MAA09318; Mon, 15 Mar 1999 12:12:58 -0500 (EST) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [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: <199903151245.XAA14560@at.dotat.com> Date: Mon, 15 Mar 1999 12:13:42 -0500 (EST) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: Leigh Hart Subject: Re: bootable cd q Cc: freebsd-hackers@FreeBSD.ORG, "Curtis Wilbar [STAFF]" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, it is not all that difficult (if I am reading your question correctly): you just have to provide mkisofs with the 1.44 MB boot floppy image (or 2.88 MB). If I remember correctly: The EL-TORITO standard expects a certain header on the CD-ROM ("EL-TORITO", go figure), which points to a catalog file, which has the location (in blocks, I belive) of the file to use for the floppy image (during boot, the CD-ROM emulates the "A:" drive). The image can be 1.44 MB or 2.88 MB (not sure if 720 KB is acceptable). On FreeBSD's 2.2.x's bootable CD-ROM, the floppy image used is the standard GENERIC kernel with a MFS root file system (boot.flp). I haven't figured out how 3.1 does it yet (there is a new 3-stage boot loader now), but I'd bet that they are using a 2.88 MB disk image, to get around the 2 boot floppy install. If you want to use the CD-ROM's filesystem, then you should investigate using "-C" boot prompt. Alternatively, in your /etc/rc script that is in the boot floppy image, you can search for and mount the CD-ROM somewhere, and chroot all of your commands. Take a look at the src/release/ directory for boot floppy creation. It's a little complicated to roll your own, but there are lots of "templates" there. :) --- Mark J. Taylor Networking Research Cybernet Systems mtaylor@cybernet.com 727 Airport Blvd. PHONE (734) 668-2567 Ann Arbor, MI 48108 FAX (734) 668-8780 http://www.cybernet.com/ http://www.netmax.com/ On 15-Mar-99 Leigh Hart wrote: > Hi Curtis, > > "Curtis Wilbar [STAFF]" wrote: >> >> Can anyone point me to a website, ftpsite, etc that would detail >> how to make a freebsd bootable cd-rom ? I've found info on mkisofs >> and in general how it works, but I'm looking for freebsd specific >> info (i.e. how to make a bootable cd from the downloaded images/etc). >> >> I'd appreciate any info you could provide. > > cd /usr/share/examples/worm/ > > read it and weep (it is *not* easy). > > then go to /usr/src/release and investigate write_mfs_in_kernel.c, > you will need it. The process has changed a bit since I did it on > FreeBSD-2.2.5, so I won't go into detaills here about what I did, > it was an ugly hack, but then again, el toro (yip yip yeehaa sp!??!) > CD booting is ugly at the best of times. > > Cheers > > Leigh > -- >| "By the time they had diminished | Leigh Hart, | >| from 50 to 8, the other dwarves | Dotat Communications Pty Ltd | >| began to suspect 'Hungry' ..." | GPO Box 487 Adelaide SA 5001 | >| -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | > > > 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 Mon Mar 15 9:20: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (Postfix) with ESMTP id EE4E814C0E for ; Mon, 15 Mar 1999 09:19:57 -0800 (PST) (envelope-from smp@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id KAA28743; Mon, 15 Mar 1999 10:27:04 -0700 (MST) Message-Id: <199903151727.KAA28743@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Alfred Perlstein Cc: Steve Passe , hackers@FreeBSD.ORG Subject: Re: power-off without halt In-reply-to: Your message of "Mon, 15 Mar 1999 12:10:48 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 10:27:04 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > On Mon, 15 Mar 1999, Steve Passe wrote: > > > Hi, > > > > We are looking at using FreeBSD as an "embedded OS" inside a line > > of instruments we are building. I think I have a handle on all the > > issues except how to cleanly handle shutdown where there is no > > console, and thus no way to send a 'halt' command. The requirement > > is that the user can merely turn off the power, nothing more required. > > > > I can modify the disk setup, kernel/util code as needed, I just need some > > idea for a workable solution. Has anyone delt with this problem before? > > Some sort of inexpensive internal UPS system that would notify a deamon > the the power has been cut to allow for a clean shutdown? No, package would too small to accommidate this. And the product is too cost sensative. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 9:24:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (Postfix) with ESMTP id 0187A14E6A for ; Mon, 15 Mar 1999 09:24:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA13208; Mon, 15 Mar 1999 09:16:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903151716.JAA13208@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Leigh Hart Cc: "Curtis Wilbar [STAFF]" , freebsd-hackers@FreeBSD.ORG Subject: Re: bootable cd q In-reply-to: Your message of "Mon, 15 Mar 1999 23:15:24 +1030." <199903151245.XAA14560@at.dotat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 09:16:53 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi Curtis, > > "Curtis Wilbar [STAFF]" wrote: > > > > Can anyone point me to a website, ftpsite, etc that would detail > > how to make a freebsd bootable cd-rom ? I've found info on mkisofs > > and in general how it works, but I'm looking for freebsd specific > > info (i.e. how to make a bootable cd from the downloaded images/etc). > > > > I'd appreciate any info you could provide. > > cd /usr/share/examples/worm/ > > read it and weep (it is *not* easy). > > then go to /usr/src/release and investigate write_mfs_in_kernel.c, > you will need it. The process has changed a bit since I did it on > FreeBSD-2.2.5, so I won't go into detaills here about what I did, > it was an ugly hack, but then again, el toro (yip yip yeehaa sp!??!) > CD booting is ugly at the best of times. Uh, what? If you are building CDs from downloaded ISO images, you just splat the images onto the CD and you are done - the images are already bootable. If you want to generate your own set, the makecdfs.sh script just requires a bootable floppy image. And with the new loader, you don't have to futz with any of that MFS in kernel crap. So it's actually pretty easy. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Mar 15 9:27:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from redbox.venux.net (redbox.venux.net [216.47.238.10]) by hub.freebsd.org (Postfix) with ESMTP id 859941510E for ; Mon, 15 Mar 1999 09:26:36 -0800 (PST) (envelope-from matthew@venux.net) Received: from thunder (net177138.hcv.com [209.153.177.138]) by redbox.venux.net (Postfix) with SMTP for id 2E6622E20A; Mon, 15 Mar 1999 12:27:41 -0500 (EST) Message-Id: <4.1.19990315121447.009ae700@mail.venux.net> X-Sender: mhagerty@mail.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 15 Mar 1999 12:26:30 -0500 To: freebsd-hackers@freebsd.org From: Matthew Hagerty Subject: Program can't get pointer-to-function, gdb can... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I'm running 2.2.7-RELEASE (I know, I know), and I am trying to use a pdf lib inside php3. The program crashes when I try to call the function PDF_get_info. I ran the program in gdb, it fails when trying to get the address of the pdf_default_error_handler function (listing 1). However, if I step up to that point in the program, set the value by hand, then skip over the program assignment, it works (listing 2)!! Any insight would be greatly appreciated. Thanks, Matthew bash-2.02# gdb php GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... (gdb) list p_basic.c:95 90 91 PDF_info* 92 PDF_get_info(void) 93 { 94 PDF_info *info; 95 96 info = (PDF_info *) PDF_malloc(sizeof(PDF_info), "PDF_get_info"); 97 98 info->binary_mode = false; 99 info->required_compatibility= PDF1_1; (gdb) break 96 Breakpoint 1 at 0x590ff: file p_basic.c, line 96. (gdb) run -f test2.php3 Starting program: /usr/local/tempphp/php-3.0.7/php -f test2.php3 Breakpoint 1, PDF_get_info () at p_basic.c:96 96 info = (PDF_info *) PDF_malloc(sizeof(PDF_info), "PDF_get_info"); (gdb) next 98 info->binary_mode = false; (gdb) print info $1 = (PDF_info *) 0xe73c0 (gdb) print *info $2 = {binary_mode = 0, required_compatibility = PDF1_0, error_handler = 0, Keywords = 0x0, Subject = 0x0, ModDate = 0x0, Title = 0x0, CreationDate = 0x0, Creator = 0x0, Producer = 0x0, Author = 0x0, fontpath = 0x0} (gdb) next 99 info->required_compatibility= PDF1_1; (gdb) next 102 info->Keywords = NULL; (gdb) next 103 info->Subject = NULL; (gdb) next 104 info->ModDate = NULL; (gdb) next 105 info->Title = NULL; (gdb) next 106 info->CreationDate = NULL; (gdb) next 107 info->Creator = NULL; (gdb) print *info $3 = {binary_mode = 0, required_compatibility = PDF1_1, error_handler = 0, Keywords = 0x0, Subject = 0x0, ModDate = 0x0, Title = 0x0, CreationDate = 0x0, Creator = 0x0, Producer = 0x0, Author = 0x0, fontpath = 0x0} (gdb) next 108 info->Producer = NULL; (gdb) next 109 info->Author = NULL; (gdb) next 111 info->error_handler = pdf_default_error_handler; (gdb) print *info $4 = {binary_mode = 0, required_compatibility = PDF1_1, error_handler = 0, Keywords = 0x0, Subject = 0x0, ModDate = 0x0, Title = 0x0, CreationDate = 0x0, Creator = 0x0, Producer = 0x0, Author = 0x0, fontpath = 0x0} (gdb) next Program received signal SIGSEGV, Segmentation fault. 0x5917b in PDF_get_info () at p_basic.c:111 111 info->error_handler = pdf_default_error_handler; (gdb) print info $5 = (PDF_info *) 0xe73c0 (gdb) print *info $6 = {binary_mode = 0, required_compatibility = PDF1_1, error_handler = 0, Keywords = 0x0, Subject = 0x0, ModDate = 0x0, Title = 0x0, CreationDate = 0x0, Creator = 0x0, Producer = 0x0, Author = 0x0, fontpath = 0x0} (gdb) quit The program is running. Quit anyway (and kill it)? (y or n) y bash-2.02# BUT, if I set the value inside gdb, it works... bash-2.02# gdb php GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... (gdb) list p_basic.c:110 105 info->Title = NULL; 106 info->CreationDate = NULL; 107 info->Creator = NULL; 108 info->Producer = NULL; 109 info->Author = NULL; 110 111 info->error_handler = pdf_default_error_handler; 112 113 info->fontpath = PDF_DEFAULT_FONT_PATH; 114 return info; (gdb) break 110 Breakpoint 1 at 0x59178: file p_basic.c, line 110. (gdb) run -f test2.php3 Starting program: /usr/local/tempphp/php-3.0.7/php -f test2.php3 Breakpoint 1, PDF_get_info () at p_basic.c:111 111 info->error_handler = pdf_default_error_handler; (gdb) print info $1 = (PDF_info *) 0xe73c0 (gdb) print *info $2 = {binary_mode = 0, required_compatibility = PDF1_1, error_handler = 0, Keywords = 0x0, Subject = 0x0, ModDate = 0x0, Title = 0x0, CreationDate = 0x0, Creator = 0x0, Producer = 0x0, Author = 0x0, fontpath = 0x0} (gdb) print pdf_default_error_handler $3 = {void (int, char *, char *)} 0x58e44 (gdb) set info->error_handler = pdf_default_error_handler (gdb) print *info $4 = {binary_mode = 0, required_compatibility = PDF1_1, error_handler = 0x58e44 , Keywords = 0x0, Subject = 0x0, ModDate = 0x0, Title = 0x0, CreationDate = 0x0, Creator = 0x0, Producer = 0x0, Author = 0x0, fontpath = 0x0} (gdb) jump 112 Continuing at 0x59186. Program exited normally. (gdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 9:33:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (Postfix) with ESMTP id 5D6E1152EC for ; Mon, 15 Mar 1999 09:33:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA13276; Mon, 15 Mar 1999 09:26:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903151726.JAA13276@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wes Peters Cc: Andrew Gallatin , Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Mon, 15 Mar 1999 09:01:47 MST." <36ED2EEB.E4A0DDCE@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 09:26:38 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess I should take a look at your software and get a card or two > in for testing. I'd like to see what we can do between two Tigon > equipped systems with a Xylan switch in the middle. Most of our > testing on our Gigabit modules so far has been done with a SmartBits > packet generator, but I don't really believe the numbers until I've > seen some real host-generated data streams. Heh. It would be quite funky if we were able to generate bits fast enough to become your preferred host platform for host traffic generation. That would almost mandate some words from you we could use for bragging purposes. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Mar 15 10:12: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 81CE315410 for ; Mon, 15 Mar 1999 10:10:44 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id NAA03039; Mon, 15 Mar 1999 13:08:58 -0500 (EST) Date: Mon, 15 Mar 1999 13:08:58 -0500 (EST) From: Chuck Robey To: Steve Passe Cc: hackers@FreeBSD.ORG Subject: Re: power-off without halt In-Reply-To: <199903151655.JAA28147@Ilsa.StevesCafe.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, 15 Mar 1999, Steve Passe wrote: > Hi, > > We are looking at using FreeBSD as an "embedded OS" inside a line > of instruments we are building. I think I have a handle on all the > issues except how to cleanly handle shutdown where there is no > console, and thus no way to send a 'halt' command. The requirement > is that the user can merely turn off the power, nothing more required. > > I can modify the disk setup, kernel/util code as needed, I just need some > idea for a workable solution. Has anyone delt with this problem before? Interesting. What kind of use is made of local disk? Could you use local disk read only, and just use a mfs partition to work out of? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 10:12:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 430061541B for ; Mon, 15 Mar 1999 10:11:22 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id NAA26892 for ; Mon, 15 Mar 1999 13:16:02 -0500 (EST) Message-Id: <199903151816.NAA26892@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 15 Mar 1999 13:05:30 -0500 To: hackers@freebsd.org From: Dennis Subject: changing consoles == lost data Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is happening when I hit ALT-F2, ALT-F3 etc to switch screens? I've noticed that at with high speed data (in this case 45Mb/s) I can generate overruns by switching screens...is it disabling interrupts for a long period? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 10:32:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtprtp.nortel.com (smtprtp.NortelNetworks.com [192.122.117.66]) by hub.freebsd.org (Postfix) with ESMTP id 22F88154E9 for ; Mon, 15 Mar 1999 10:32:27 -0800 (PST) (envelope-from mmercer@nortelnetworks.com) Received: from zrtpd004.us.nortel.com (actually nrtpd004) by smtprtp.nortel.com; Mon, 15 Mar 1999 13:31:21 -0500 Received: from zrtpd00n.us.nortel.com ([47.156.175.67]) by zrtpd004.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id GRAQY5TT; Mon, 15 Mar 1999 13:31:21 -0500 Received: from brtphb42.us.nortel.com by zrtpd00n.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id 1WMNXYTW; Mon, 15 Mar 1999 13:31:19 -0500 Message-ID: <36ED51F8.92075F22@nortelnetworks.com> Date: Mon, 15 Mar 1999 13:31:20 -0500 From: "Michael Mercer" Reply-To: "Michael Mercer" , mmercer@ipass.net Organization: Nortel X-Mailer: Mozilla 4.5C-CCK-MCD [en] (X11; I; HP-UX B.10.20 9000/778) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: I have some spare time. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Orig: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey peoples, I have some spare time and would like to work on a relatively small project. Any ideas???? Thanks Michael Mercer mmercer@ipass.net -- - Smile!! It makes people wonder what you're up to! - Michael E. Mercer Alumni - Fayetteville State University - Nortel - Research Triangle Park - mmercer@nortel.ca - Work - mmercer@ipass.net - Personal - mercer@sequent.uncfsu.edu - School - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 10:35:27 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 D225914BE4 for ; Mon, 15 Mar 1999 10:35:22 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA15418; Tue, 16 Mar 1999 03:34:17 +0900 (JST) Message-ID: <36ED501F.414D95F0@newsguy.com> Date: Tue, 16 Mar 1999 03:23:27 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith Cc: Andrzej Bialecki , Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC References: <199903150255.SAA09228@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I've actually been talking to David Filo about tunables, and I think > I have a better model for them in the works. It should make it > possible to just about completely eliminate param.c (some > statically-sized items may need to be fixed up). Ouch... You do that, and I'll expel the tunables to their own, to be written by someone else, man page! :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 10:44:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 10ADD14D74 for ; Mon, 15 Mar 1999 10:44:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA01410; Mon, 15 Mar 1999 10:44:01 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 10:44:01 -0800 (PST) From: Matthew Dillon Message-Id: <199903151844.KAA01410@apollo.backplane.com> To: Steve Passe Cc: hackers@FreeBSD.ORG Subject: Re: power-off without halt References: <199903151655.JAA28147@Ilsa.StevesCafe.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : : We are looking at using FreeBSD as an "embedded OS" inside a line :of instruments we are building. I think I have a handle on all the :issues except how to cleanly handle shutdown where there is no :console, and thus no way to send a 'halt' command. The requirement :is that the user can merely turn off the power, nothing more required. : : I can modify the disk setup, kernel/util code as needed, I just need some :idea for a workable solution. Has anyone delt with this problem before? : :-- :Steve Passe | powered by :smp@csn.net | Symmetric MultiProcessor FreeBSD Well, physically speaking you can't power off a machine that may be writing to its disk. If it is in the middle of a write, you *will* lose sectors to hard errors. So, typically, the best way to deal with this sort of situation is to mount the disk read-only and never write to it. Or to not have a disk at all. Or to use a pcmcia type flash disk. -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 Mon Mar 15 10:57: 5 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 2664214FA4 for ; Mon, 15 Mar 1999 10:56:29 -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 2.12 #1) id 10McUN-0001KC-00; Mon, 15 Mar 1999 20:53:23 +0200 From: Sheldon Hearn To: "Michael Mercer" , mmercer@ipass.net Cc: freebsd-hackers@freebsd.org Subject: Re: I have some spare time. In-reply-to: Your message of "Mon, 15 Mar 1999 13:31:20 EST." <36ED51F8.92075F22@nortelnetworks.com> Date: Mon, 15 Mar 1999 20:53:23 +0200 Message-ID: <5095.921524003@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Mar 1999 13:31:20 EST, "Michael Mercer" wrote: > I have some spare time and would like to work on a relatively > small project. Any ideas???? Yep, do some reading. :-) Specifically, have a look at chapter 19 of the FreeBSD handbook, entitled "Contributing to FreeBSD". Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 11: 1:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id 17CC1152F3 for ; Mon, 15 Mar 1999 11:00:30 -0800 (PST) (envelope-from ad@psn.ie) Received: from vmunix.psn.ie ([194.106.150.252]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10McUk-00009D-00 for hackers@freebsd.org; Mon, 15 Mar 1999 18:53:46 +0000 Received: from localhost.psn.ie ([127.0.0.1] helo=localhost) by vmunix.psn.ie with esmtp (Exim 2.10 #1) id 10McVm-00007T-00 for hackers@FreeBSD.org; Mon, 15 Mar 1999 18:54:50 +0000 Date: Mon, 15 Mar 1999 18:54:50 +0000 (GMT) From: Andy Doran To: hackers@FreeBSD.org Subject: fxp driver causing lockup 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 Hi all, I've got weird problem with an Intel Etherexpress Pro 100. The cards work fine, in fact great, with most of my FreeBSD boxes, all of which run the 3.x branch updated weekly over cvsup. The trouble is, when I do an 'ifconfig fxp0 $some_address' on one particular machine (a Tulip P-II, real junk) the machine locks up. The keyboard still works (i.e. can toggle numlock light), and trying to switch to another VT causes the machine to generate a never ending beep. I guess it's getting stuck at spl???() somewhere. Setting the media type works, and the card works fine on other machines. I've tried changing the slot, and using a generic 3.x kernel too, but no luck. A 2.2.6 kernel works fine, no lockups. This card shares an IRQ with a 3c905 and a S3 ViRGE/GX2. Unfortunately I can't hack at this because it's a production box, and has to be up 24/7 almost always. Any ideas? Thanks, Andy. ------------------------------------------------------ Andy Doran, ad@psn.ie Consulting & network engineering ad@NetBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 11: 2:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B638814CE1 for ; Mon, 15 Mar 1999 11:02:37 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA28152; Mon, 15 Mar 1999 10:52:47 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpde28147; Mon Mar 15 18:52:39 1999 Message-ID: <36ED56F3.5656AEC7@whistle.com> Date: Mon, 15 Mar 1999 10:52:35 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Matthew Dillon Cc: Steve Passe , hackers@FreeBSD.ORG Subject: Re: power-off without halt References: <199903151655.JAA28147@Ilsa.StevesCafe.com> <199903151844.KAA01410@apollo.backplane.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: > > :Hi, > : > : We are looking at using FreeBSD as an "embedded OS" inside a line > :of instruments we are building. I think I have a handle on all the > :issues except how to cleanly handle shutdown where there is no > :console, and thus no way to send a 'halt' command. The requirement > :is that the user can merely turn off the power, nothing more required. > : > : I can modify the disk setup, kernel/util code as needed, I just need some > :idea for a workable solution. Has anyone delt with this problem before? > : > :-- > :Steve Passe | powered by > :smp@csn.net | Symmetric MultiProcessor FreeBSD > > Well, physically speaking you can't power off a machine that may > be writing to its disk. If it is in the middle of a write, you > *will* lose sectors to hard errors. > > So, typically, the best way to deal with this sort of situation is > to mount the disk read-only and never write to it. Or to not have a > disk at all. Or to use a pcmcia type flash disk. > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message look at : http://www.whistle.com/ I can guide you on a lot of the issues as we've had to handle them.... julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 11: 8:34 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 2303E15396 for ; Mon, 15 Mar 1999 11:08:26 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA21303; Mon, 15 Mar 1999 20:07:59 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903151907.UAA21303@freebsd.dk> Subject: Re: power-off without halt In-Reply-To: <199903151655.JAA28147@Ilsa.StevesCafe.com> from Steve Passe at "Mar 15, 1999 9:55:54 am" To: smp@csn.net (Steve Passe) Date: Mon, 15 Mar 1999 20:07:59 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Steve Passe wrote: > Hi, > > We are looking at using FreeBSD as an "embedded OS" inside a line > of instruments we are building. I think I have a handle on all the > issues except how to cleanly handle shutdown where there is no > console, and thus no way to send a 'halt' command. The requirement > is that the user can merely turn off the power, nothing more required. > > I can modify the disk setup, kernel/util code as needed, I just need some > idea for a workable solution. Has anyone delt with this problem before? Use a small circuit that gets the power off switch signal, pulls NMI which shutdown the system, and after a sufficient timemout pulls the power.. Nice and easy, and if the system hangs it will just be shut off after the timeout.... KISS at work again :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 11:42:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 4183E14FA9 for ; Mon, 15 Mar 1999 11:42:12 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id MAA20523; Mon, 15 Mar 1999 12:41:42 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903151941.MAA20523@panzer.plutotech.com> Subject: Re: power-off without halt In-Reply-To: <199903151844.KAA01410@apollo.backplane.com> from Matthew Dillon at "Mar 15, 1999 10:44: 1 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Mon, 15 Mar 1999 12:41:41 -0700 (MST) Cc: smp@csn.net, hackers@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 Matthew Dillon wrote... > :Hi, > : > : We are looking at using FreeBSD as an "embedded OS" inside a line > :of instruments we are building. I think I have a handle on all the > :issues except how to cleanly handle shutdown where there is no > :console, and thus no way to send a 'halt' command. The requirement > :is that the user can merely turn off the power, nothing more required. > : > : I can modify the disk setup, kernel/util code as needed, I just need some > :idea for a workable solution. Has anyone delt with this problem before? > : > :-- > :Steve Passe | powered by > :smp@csn.net | Symmetric MultiProcessor FreeBSD > > Well, physically speaking you can't power off a machine that may > be writing to its disk. If it is in the middle of a write, you > *will* lose sectors to hard errors. > > So, typically, the best way to deal with this sort of situation is > to mount the disk read-only and never write to it. Or to not have a > disk at all. Or to use a pcmcia type flash disk. SGI boxes have a neat feature (or at least they did when I did IRIX work a few years ago). They have a "soft" power off switch. You hit the switch, and it safely shuts down the machine. Don't ATX power supplies have some sort of soft power-off capability? How about tying a "power" button on the front panel of this device to a switch that would tell the machine to halt itself and then power off? From looking at the ATX power supply specs: http://www.teleport.com/~atx/spec/atxps09.pdf It looks like there is a signal that tells the power supply to power itself off. However, there's also a "standby" 5V power lead that is always active when the power supply is plugged in. That's what allows things like wake on LAN to work. It looks like the pieces are there. What you want, I suppose, is a motherboard that can intercept the power switch signal, generate an interrupt, and then wait for some feedback from the OS before sending the signal on to shut down the power. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 11:52:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id E7EFC15410 for ; Mon, 15 Mar 1999 11:52:12 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id TAA79415; Mon, 15 Mar 1999 19:51:23 GMT Message-ID: <36ED64BB.6454E97F@tdx.co.uk> Date: Mon, 15 Mar 1999 19:51:23 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Matthew Dillon , smp@csn.net, hackers@FreeBSD.ORG Subject: Re: power-off without halt References: <199903151941.MAA20523@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > Don't ATX power supplies have some sort of soft power-off capability? > How about tying a "power" button on the front panel of this device to a > switch that would tell the machine to halt itself and then power off? > > It looks like the pieces are there. What you want, I suppose, is a > motherboard that can intercept the power switch signal, generate an > interrupt, and then wait for some feedback from the OS before sending the > signal on to shut down the power. They do... Both my boxes here do it while running Win'95/98... If you want to switch them off instantly, no questions asked - you have to hold the on/off button for 4 seconds. If you just tap the same button Win'95/98 shuts down, then switches the machine off... Quite handy I guess :-) (Except more often than not the reason for wanting to switch off the machine is that Win'9X has crashed, beyond seeing the switch being thrown :-) (In which case a 4 second extended press kills it dead... :-) -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 12: 2:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 21D7615599 for ; Mon, 15 Mar 1999 12:02:09 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA02187; Mon, 15 Mar 1999 12:01:44 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 12:01:44 -0800 (PST) From: Matthew Dillon Message-Id: <199903152001.MAA02187@apollo.backplane.com> To: "Kenneth D. Merry" Cc: smp@csn.net, hackers@FreeBSD.ORG Subject: Re: power-off without halt References: <199903151941.MAA20523@panzer.plutotech.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Matthew Dillon wrote... :> :Hi, :> : :> : We are looking at using FreeBSD as an "embedded OS" inside a line :> :of instruments we are building. I think I have a handle on all the :> :issues except how to cleanly handle shutdown where there is no :> :console, and thus no way to send a 'halt' command. The requirement :> :is that the user can merely turn off the power, nothing more required. :> : :> : I can modify the disk setup, kernel/util code as needed, I just need some :> :idea for a workable solution. Has anyone delt with this problem before? :> : :> :-- :> :Steve Passe | powered by :> :smp@csn.net | Symmetric MultiProcessor FreeBSD :> :> Well, physically speaking you can't power off a machine that may :> be writing to its disk. If it is in the middle of a write, you :> *will* lose sectors to hard errors. :> :> So, typically, the best way to deal with this sort of situation is :> to mount the disk read-only and never write to it. Or to not have a :> disk at all. Or to use a pcmcia type flash disk. : :SGI boxes have a neat feature (or at least they did when I did IRIX work a :few years ago). They have a "soft" power off switch. You hit the switch, :and it safely shuts down the machine. : :Don't ATX power supplies have some sort of soft power-off capability? :How about tying a "power" button on the front panel of this device to a :switch that would tell the machine to halt itself and then power off? : :>From looking at the ATX power supply specs: : :http://www.teleport.com/~atx/spec/atxps09.pdf : :It looks like there is a signal that tells the power supply to power itself :off. However, there's also a "standby" 5V power lead that is always active :when the power supply is plugged in. That's what allows things like wake :on LAN to work. : :It looks like the pieces are there. What you want, I suppose, is a :motherboard that can intercept the power switch signal, generate an :interrupt, and then wait for some feedback from the OS before sending the :signal on to shut down the power. : :Ken :-- :Kenneth Merry :ken@plutotech.com This sort of approach doesn't work well in practice. The problem you have to deal with is not so much the user hitting the power switch, but either the user unplugging the system from the wall or a real honest to god power failure occuring. After thinking about it a bit, the best way to solve this sort of problem is to put a monitor on the AC input and then use big honking capacitors on the diode bridge going into the switching power supply. This to hold the line voltage up long enough for the computer to finish writing to the disk when the plug is pulled. If you are trying to use off the shelf parts, you have to locate a switching power supply that has these features. You probably do not want to try to build such a beast yourself ( unless you *like* going through the UL approval process ), nor can you legally hack an existing but not-quite-right power supply. Depending on the current required by the system and the size of the caps, you should be able to get as much as 100mS of good power. e.g. IT=CV, T=CV/I. Assume 60W @ 110V yields half an amp. The caps on the diode bridge will probably level off at 50V or so and the switching regulator will be able to regulate down to, say, 20V. So, for example: T=CV/I T=(1000uF * 20V)/500mA = 40 mS of good power after AC failure. -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 Mon Mar 15 12:41:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 163C915033 for ; Mon, 15 Mar 1999 12:41:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA02388; Mon, 15 Mar 1999 12:41:35 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 12:41:35 -0800 (PST) From: Matthew Dillon Message-Id: <199903152041.MAA02388@apollo.backplane.com> To: "Kenneth D. Merry" , smp@csn.net, hackers@FreeBSD.ORG Subject: Re: power-off without halt References: <199903151941.MAA20523@panzer.plutotech.com> <199903152001.MAA02187@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : e.g. IT=CV, T=CV/I. Assume 60W @ 110V yields half an amp. The caps on : the diode bridge will probably level off at 50V or so and the switching : regulator will be able to regulate down to, say, 20V. So, for example: : : T=CV/I T=(1000uF * 20V)/500mA = 40 mS of good power after AC failure. Oops. that should be 30V. 50V-20V = 30V. T=CV/I T=(1000uF * 30V)/500mA = 60 mS of good power after AC failure. -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 Mon Mar 15 13: 3:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 7B65214BE4 for ; Mon, 15 Mar 1999 13:03:15 -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.8.8/8.8.8) with SMTP id OAA15842; Mon, 15 Mar 1999 14:02:57 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA01477; Mon, 15 Mar 1999 14:02:44 -0700 Date: Mon, 15 Mar 1999 14:02:44 -0700 Message-Id: <199903152102.OAA01477@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: changing consoles == lost data In-Reply-To: <199903151816.NAA26892@etinc.com> References: <199903151816.NAA26892@etinc.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What is happening when I hit ALT-F2, ALT-F3 etc to switch screens? > I've noticed that at with high speed data (in this case 45Mb/s) I can > generate overruns by switching screens...is it disabling interrupts > for a long period? Yes, for the num-lock/caps-lock LED's. This (apparently) requires disabling interrupts for a (relatively) long period of time. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 13:14:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 3690D14CC2 for ; Mon, 15 Mar 1999 13:14:12 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id QAA25818; Mon, 15 Mar 1999 16:13:21 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id QAA08351; Mon, 15 Mar 1999 16:13:04 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id QAA50381; Mon, 15 Mar 1999 16:13:03 -0500 (EST) Date: Mon, 15 Mar 1999 16:13:03 -0500 (EST) From: Thomas David Rivers Message-Id: <199903152113.QAA50381@lakes.dignus.com> To: dillon@apollo.backplane.com, ken@plutotech.com Subject: Re: power-off without halt Cc: hackers@FreeBSD.ORG, smp@csn.net In-Reply-To: <199903151941.MAA20523@panzer.plutotech.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Matthew Dillon wrote... > > :Hi, > > : > > : We are looking at using FreeBSD as an "embedded OS" inside a line > > :of instruments we are building. I think I have a handle on all the > > :issues except how to cleanly handle shutdown where there is no > > :console, and thus no way to send a 'halt' command. The requirement > > :is that the user can merely turn off the power, nothing more required. > > : > > : I can modify the disk setup, kernel/util code as needed, I just need some > > :idea for a workable solution. Has anyone delt with this problem before? > > : > > :-- > > :Steve Passe | powered by > > :smp@csn.net | Symmetric MultiProcessor FreeBSD > > > > Well, physically speaking you can't power off a machine that may > > be writing to its disk. If it is in the middle of a write, you > > *will* lose sectors to hard errors. > > > > So, typically, the best way to deal with this sort of situation is > > to mount the disk read-only and never write to it. Or to not have a > > disk at all. Or to use a pcmcia type flash disk. > > SGI boxes have a neat feature (or at least they did when I did IRIX work a > few years ago). They have a "soft" power off switch. You hit the switch, > and it safely shuts down the machine. > I believe you can make pressing -- on the console do the same thing (or close to it) on FreeBSD. It's not a "switch" but it's close... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 14:10: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B7C8157D4 for ; Mon, 15 Mar 1999 14:09:42 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from jehovah (jehovah.technokratis.com [207.139.115.248]) by oracle.dsuper.net (Delphi 1.3/8.6.9) with SMTP id RAA07956; Mon, 15 Mar 1999 17:08:58 -0500 (EST) Message-ID: <004301be6f31$0b028df0$0100000a@jehovah.technokratis.com> Reply-To: "Bosko Milekic" From: "Bosko Milekic" To: Cc: Subject: Re: thread and socket Date: Mon, 15 Mar 1999 17:13:21 -0500 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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :in multithreaded app is recvfrom only waiting for data, but cannot finish :with EAGAIN error, when I set SO_RCVTIMEO. I need stop recv function after :timeout. in the non threaded version rcv is finish after timeout (no data :is received) , but in multi threaded ver doesn't stop and still is waiting :for data. any data is not comming and ercvfrom is still wiating. WHY????? :thanks. :honza : : :On Sun, 14 Mar 1999, Bosko Milekic wrote: : :> :> I've had a little trouble understanding you... :-) :> :> Here's an excerpt from the man page, though... if this isn't what you were :> looking for, please clarify a bit... :> :> --snip-- :> In the non-threaded library getsockopt() is implemented as the :> getsockopt syscall. :> :> In the threaded library, the getsockopt syscall is assembled to _thread_sys_getsockopt() :> and getsockopt() is implemented as a function which locks s for read and :> write, then calls _thread_sys_getsockopt(). :> Before returning, getsockopt() unlocks s. :> --snip-- :> :> Regards, :> Bosko. :> :> -- :> Bosko Milekic http://www.supernet.ca/~bmilekic/ :> Delphi SuperNet voice: (+1) 514 281-7500 fax: (+1) 514 281-6599 :> PGP Key available upon request. :> : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 14:26:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B96A1526B for ; Mon, 15 Mar 1999 14:24:10 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from jehovah (jehovah.technokratis.com [207.139.115.248]) by oracle.dsuper.net (Delphi 1.3/8.6.9) with SMTP id RAA25669; Mon, 15 Mar 1999 17:23:26 -0500 (EST) Message-ID: <005001be6f33$0f817470$0100000a@jehovah.technokratis.com> Reply-To: "Bosko Milekic" From: "Bosko Milekic" To: "FreeBsd" Cc: Subject: Re: thread and socket Date: Mon, 15 Mar 1999 17:27:49 -0500 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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You'll have to excuse my previous post. (whoopsy). :-) The reason you may be having this problem may be related to the fact that the global integer 'errno' that you are checking is not really 'thread-safe.' The copy of the code you are running contains only one global int errno, and when you check for it in the thread (e.g. when it's re-enterant), there is a problem. Stevens proposes saving the initial value of 'errno' before going elsewhere. You would declare another int (e.g. saveerrno) and do something like: saveerrno = errno; (and then go ahead with your function(s) in the thread) I gave you as an example the global value 'errno,' but you should check any functions you call in threads and make sure that they are thread-safe... I am not very proficient with threads, but I can see an alternative to your problem (if you are still having it). Instead of having your thread go non-blocking, just allow it to block, the kernel will just run some other thread until their is data ready for the blocked function... in your main copy of the code, you can set your own timer which, after expiry, checks whether or not a global buffer has been filled (the buffer would only be filled if recvfrom() returns), and if it hasn't, it can kill the thread, knowing that there was no data to be read... Regards, Bosko M. ____________________________________________________________________________ Bosko Milekic bmilekic@oracle.dsuper.net http://www.dsuper.net/~bmilekic/ Delphi SuperNet +1.888.787.3768 http://www.supernet.ca/ -----Original Message----- From: FreeBsd To: Bosko Milekic Cc: freebsd-hackers@FreeBSD.ORG Date: Monday, March 15, 1999 4:19 AM Subject: Re: thread and socket :in multithreaded app is recvfrom only waiting for data, but cannot finish :with EAGAIN error, when I set SO_RCVTIMEO. I need stop recv function after :timeout. in the non threaded version rcv is finish after timeout (no data :is received) , but in multi threaded ver doesn't stop and still is waiting :for data. any data is not comming and ercvfrom is still wiating. WHY????? :thanks. :honza : : :On Sun, 14 Mar 1999, Bosko Milekic wrote: : :> :> I've had a little trouble understanding you... :-) :> :> Here's an excerpt from the man page, though... if this isn't what you were :> looking for, please clarify a bit... :> :> --snip-- :> In the non-threaded library getsockopt() is implemented as the :> getsockopt syscall. :> :> In the threaded library, the getsockopt syscall is assembled to _thread_sys_getsockopt() :> and getsockopt() is implemented as a function which locks s for read and :> write, then calls _thread_sys_getsockopt(). :> Before returning, getsockopt() unlocks s. :> --snip-- :> :> Regards, :> Bosko. :> :> -- :> Bosko Milekic http://www.supernet.ca/~bmilekic/ :> Delphi SuperNet voice: (+1) 514 281-7500 fax: (+1) 514 281-6599 :> PGP Key available upon request. :> : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 15: 4:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 3922F14F62 for ; Mon, 15 Mar 1999 15:04:32 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.1) with ESMTP id AAA02700; Tue, 16 Mar 1999 00:02:41 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Tue, 16 Mar 1999 00:02:41 +0100 (CET) From: Leif Neland X-Sender: leifn@arnold.neland.dk To: Steve Passe Cc: hackers@FreeBSD.ORG Subject: Re: power-off without halt In-Reply-To: <199903151655.JAA28147@Ilsa.StevesCafe.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, 15 Mar 1999, Steve Passe wrote: > Hi, > > We are looking at using FreeBSD as an "embedded OS" inside a line > of instruments we are building. I think I have a handle on all the > issues except how to cleanly handle shutdown where there is no > console, and thus no way to send a 'halt' command. The requirement > is that the user can merely turn off the power, nothing more required. > Could you use a "soft power off" ? An "off" pushbutton, wired to NMI, which triggered a shutdown, and then turned off a relay? leif@neland.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 17:19:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id D238915162 for ; Mon, 15 Mar 1999 17:19:11 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.8.8) with ESMTP id BAA01673; Tue, 16 Mar 1999 01:17:37 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA03090; Tue, 16 Mar 1999 01:17:04 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903160117.BAA03090@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug White Cc: hackers@FreeBSD.ORG Subject: Re: Will IPFW pass GRE packets? In-reply-to: Your message of "Fri, 12 Mar 1999 16:33:16 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Mar 1999 01:17:03 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hello ... > > I wanted to check if IPFW will pass GRE packets in a standard config from > 3.0. I'm trying to use the patched natd to translate PPTP packets and > natd isn't seeing them (from what I can tell). Is there anything special > I should do to make sure IP proto 47 packets are getting in and out? > > Thanks for any hints... natd in -current now supports (transports) pptp, as does ppp. > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 18:16:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9CFE714DA7 for ; Mon, 15 Mar 1999 18:16:45 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id VAA24377 for ; Mon, 15 Mar 1999 21:16:27 -0500 (EST) Message-Id: <199903160216.VAA24377@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: evil maxusers Date: Mon, 15 Mar 1999 21:16:26 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is evil abuot large maxusers? We have a crashing server (Pentium II-400) with maxusers set to 320. In a previous email to -hackers that I have since lost :I it was mentioned that you could lower maxusers, and the, by hand, up the MBUFs and NPROCs in the config file. However I have grepped the entire kernel source tree, and I can see that MAXUSERS is only used to set MBUFs and NPROCS (and other things derive from there, suich as MAXFILES). Why therefore will MAXUSERS=320 crash my system, while setting MAXUSERS to 64, and adjusting MBUFs and NPROCS by hand will not? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 19:33:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id 4A64015100 for ; Mon, 15 Mar 1999 19:33:34 -0800 (PST) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.9.3/8.9.3) id WAA06493 for freebsd-hackers@FreeBSD.ORG; Mon, 15 Mar 1999 22:33:16 -0500 (EST) (envelope-from sjr) Message-Id: <199903160333.WAA06493@istari.home.net> Date: Mon, 15 Mar 1999 22:33:16 -0500 (EST) From: "Stephen J. Roznowski" Subject: Use of "register" in code To: freebsd-hackers@FreeBSD.ORG 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 been looking at merging some NetBSD fixes for games, and I noticed that they have removed the "register" declaration from (at least) this section of the code tree. Are these register declarations useful, or are they just "historical artifacts"? If they are just historical artifacts, should they be removed? Thanks, -- Stephen J. Roznowski (sjr@home.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 19:50: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B30ED14F96 for ; Mon, 15 Mar 1999 19:50:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA05543; Mon, 15 Mar 1999 19:49:45 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 19:49:45 -0800 (PST) From: Matthew Dillon Message-Id: <199903160349.TAA05543@apollo.backplane.com> To: "Stephen J. Roznowski" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code References: <199903160333.WAA06493@istari.home.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I've been looking at merging some NetBSD fixes for games, and I noticed :that they have removed the "register" declaration from (at least) this :section of the code tree. : :Are these register declarations useful, or are they just "historical :artifacts"? If they are just historical artifacts, should they be :removed? : :Thanks, :-- :Stephen J. Roznowski (sjr@home.net) The register declarations are useless historical artifacts. -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 Mon Mar 15 20:18:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id AB09414C3C for ; Mon, 15 Mar 1999 20:18:05 -0800 (PST) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id PAA02535 for ; Tue, 16 Mar 1999 15:17:45 +1100 (EDT) Received: from areilly.bpc-users.org (CPE-24-192-50-137.nsw.bigpond.net.au [24.192.50.137]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id PAA14998 for ; Tue, 16 Mar 1999 15:17:44 +1100 (EDT) Received: (qmail 40189 invoked by uid 1000); 16 Mar 1999 04:17:44 -0000 From: "Andrew Reilly" Message-ID: <19990316151744.A39973@reilly.home> Date: Tue, 16 Mar 1999 15:17:44 +1100 To: Matthew Dillon , "Stephen J. Roznowski" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code References: <199903160333.WAA06493@istari.home.net> <199903160349.TAA05543@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199903160349.TAA05543@apollo.backplane.com>; from Matthew Dillon on Mon, Mar 15, 1999 at 07:49:45PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 07:49:45PM -0800, Matthew Dillon wrote: > :I've been looking at merging some NetBSD fixes for games, and I noticed > :that they have removed the "register" declaration from (at least) this > :section of the code tree. > : > :Are these register declarations useful, or are they just "historical > :artifacts"? If they are just historical artifacts, should they be > :removed? > : > :Thanks, > :-- > :Stephen J. Roznowski (sjr@home.net) > > The register declarations are useless historical artifacts. Why do you say that? "register" in a declaration has a specific semantic meaning that isn't (to my knowledge) duplicated by any other language mechanism, and that is "this variable does not exist in the memory space, and so _cannot_ be de-referenced with "&" or modified by an asignment through a pointer." Register pointer variables and temporaries are very important for preventing C compilers from producing pessimistic inner loop code. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 20:23:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 974D9150BB for ; Mon, 15 Mar 1999 20:23:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA02703; Mon, 15 Mar 1999 20:16:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903160416.UAA02703@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrew Reilly" Cc: Matthew Dillon , "Stephen J. Roznowski" , freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code In-reply-to: Your message of "Tue, 16 Mar 1999 15:17:44 +1100." <19990316151744.A39973@reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 20:16:52 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Mar 15, 1999 at 07:49:45PM -0800, Matthew Dillon wrote: > > :I've been looking at merging some NetBSD fixes for games, and I noticed > > :that they have removed the "register" declaration from (at least) this > > :section of the code tree. > > : > > :Are these register declarations useful, or are they just "historical > > :artifacts"? If they are just historical artifacts, should they be > > :removed? > > : > > :Thanks, > > :-- > > :Stephen J. Roznowski (sjr@home.net) > > > > The register declarations are useless historical artifacts. > > Why do you say that? "register" in a declaration has a specific > semantic meaning that isn't (to my knowledge) duplicated by any > other language mechanism, and that is "this variable does not exist > in the memory space, and so _cannot_ be de-referenced with "&" or > modified by an asignment through a pointer." Register pointer > variables and temporaries are very important for preventing C > compilers from producing pessimistic inner loop code. That's not what 'register' means, and unfortunately the use of 'register' by code authors doesn't help as they're not privy to the actual layout of the code at the point where register allocation is performed. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Mar 15 20:32:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1D6CF14C3C for ; Mon, 15 Mar 1999 20:32:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA05835; Mon, 15 Mar 1999 20:31:41 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 20:31:41 -0800 (PST) From: Matthew Dillon Message-Id: <199903160431.UAA05835@apollo.backplane.com> To: "Andrew Reilly" Cc: "Stephen J. Roznowski" , freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code References: <199903160333.WAA06493@istari.home.net> <199903160349.TAA05543@apollo.backplane.com> <19990316151744.A39973@reilly.home> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> : :> :Thanks, :> :-- :> :Stephen J. Roznowski (sjr@home.net) :> :> The register declarations are useless historical artifacts. : :Why do you say that? "register" in a declaration has a specific :semantic meaning that isn't (to my knowledge) duplicated by any :other language mechanism, and that is "this variable does not exist :in the memory space, and so _cannot_ be de-referenced with "&" or :modified by an asignment through a pointer." Register pointer :variables and temporaries are very important for preventing C :compilers from producing pessimistic inner loop code. : :-- :Andrew Firstly, that is not what register means. Secondly, all modern C compilers that I know about, including one I wrote years ago, can trivially detect the stack locality of a variable and put it in a register as part of standard optimizations. It's one of the *easiest* optimizations a C compiler can do, in fact. Some compilers will add a little weight to the potential optimization if you use the 'register' keyword, but modern compilers tend to do a better job without the manual weighting. -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 Mon Mar 15 20:52:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 02C32150AE for ; Mon, 15 Mar 1999 20:52:18 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id XAA05838; Mon, 15 Mar 1999 23:51:27 -0500 (EST) (envelope-from luoqi) Date: Mon, 15 Mar 1999 23:51:27 -0500 (EST) From: Luoqi Chen Message-Id: <199903160451.XAA05838@lor.watermarkgroup.com> To: crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: evil maxusers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What is evil abuot large maxusers? We have a crashing server (Pentium II-400) > with maxusers set to 320. In a previous email to -hackers that I have since > lost :I it was mentioned that you could lower maxusers, and the, by hand, > up the MBUFs and NPROCs in the config file. However I have grepped the > entire kernel source tree, and I can see that MAXUSERS is only used to > set MBUFs and NPROCS (and other things derive from there, suich as > MAXFILES). Why therefore will MAXUSERS=320 crash my system, while setting > MAXUSERS to 64, and adjusting MBUFs and NPROCS by hand will not? > > -- > David Cross > Did you look at the config-generated files in /sys/compile/*? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 20:58:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id E480E15143 for ; Mon, 15 Mar 1999 20:58:19 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id XAA26217; Mon, 15 Mar 1999 23:57:57 -0500 (EST) Message-Id: <199903160457.XAA26217@cs.rpi.edu> To: Luoqi Chen Cc: crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: evil maxusers In-Reply-To: Message from Luoqi Chen of "Mon, 15 Mar 1999 23:51:27 EST." <199903160451.XAA05838@lor.watermarkgroup.com> Date: Mon, 15 Mar 1999 23:57:57 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I looked in /usr/src/sys/compile/*/*. A grep -i of that directory structure shows that the only references to maxusers is in the kernel itself (2 error messages, and I have the INCLUDE_CONFIG_FILE option on). and then in param.c where it twaeks NPROC NMBCLUSTERS and NSFBUFS. Other than that no references to "-i" maxusers at all. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 21: 6: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 1649A15100 for ; Mon, 15 Mar 1999 21:06:05 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-71-82.atl.bellsouth.net [209.214.71.82]) by mail0.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id AAA28478; Tue, 16 Mar 1999 00:05:21 -0500 (EST) Received: from localhost (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id XAA60228; Mon, 15 Mar 1999 23:56:21 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) To: fkittred@mail.gwi.net Cc: wghicks@bellsouth.net, freebsd-hackers@freebsd.org Subject: Re: Gigabit ethernet -- what am I doing wrong? In-Reply-To: Your message of "Mon, 15 Mar 1999 08:48:02 -0500" <199903151348.IAA23796@mail.gwi.net> References: <199903151348.IAA23796@mail.gwi.net> X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990315235620N.wghicks@wghicks.bellsouth.net> Date: Mon, 15 Mar 1999 23:56:20 -0500 From: W Gerald Hicks X-Dispatcher: imput version 980905(IM100) Lines: 33 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Fletcher E Kittredge > On Sun, 14 Mar 1999 21:59:44 -0500 W Gerald Hicks wrote: > > Erm... Depends on what one wants to do with it :) > > > > I believe certain market segments would welcome a Gigabit > > Ethernet subsystem on a Rambus with huge memory buffers. > > Hum, the only use of such cards would be PC routers? That's a pretty narrow category :) No, there are quite a few new and previously inconceivable applications emerging to soak up the bandwidth we've gained. > You are talking with a builder/maintainer of PC routers :) > > Having said that, our market niche is *way* small. I don't think this > is a profitable niche. I think that one would be building so few > cards, the cost would be so great per card that it would be cheaper to > buy a Cisco. There are many hidden costs to > developing/building/testing/maintaining/operating PC routers and > Ciscos are already probably cheaper in the long run. I disagree. There are quite a few places where Ciscos just don't fit and people needing solutions are willing to pay for them. Besides, conceding the whole networking market to Cisco isn't good either is it? The niche market is alive and well. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 21: 9:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 14BFA150B8 for ; Mon, 15 Mar 1999 21:09:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA06242; Mon, 15 Mar 1999 21:09:10 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 21:09:10 -0800 (PST) From: Matthew Dillon Message-Id: <199903160509.VAA06242@apollo.backplane.com> To: "Andrew Reilly" , "Stephen J. Roznowski" , freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code References: <199903160333.WAA06493@istari.home.net> <199903160349.TAA05543@apollo.backplane.com> <19990316151744.A39973@reilly.home> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : ::> : ::> :Thanks, ::> :-- ::> :Stephen J. Roznowski (sjr@home.net) ::> ::> The register declarations are useless historical artifacts. :: ::Why do you say that? "register" in a declaration has a specific ::semantic meaning that isn't (to my knowledge) duplicated by any ::other language mechanism, and that is "this variable does not exist ::in the memory space, and so _cannot_ be de-referenced with "&" or ::modified by an asignment through a pointer." Register pointer ::variables and temporaries are very important for preventing C ::compilers from producing pessimistic inner loop code. :: ::-- ::Andrew : : Firstly, that is not what register means. Secondly, all modern C : compilers that I know about, including one I wrote years ago, can : trivially detect the stack locality of a variable and put it in a : register as part of standard optimizations. It's one of the *easiest* : optimizations a C compiler can do, in fact. : : Some compilers will add a little weight to the potential optimization : if you use the 'register' keyword, but modern compilers tend to do a : better job without the manual weighting. : : -Matt : Matthew Dillon : Let me extend this with another example: Protection against aliasing is not usually an issue with stack variables. On the otherhand, it is something that would be much more useful with structural fields or globals. Try putting the 'register' keyword in front of a structural field or global and you will wind up with a fist full of fatal compiler errors. I don't know a single programmer who uses 'register' to mean 'alias protection'. -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 Mon Mar 15 21:17:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id EA2F31507C for ; Mon, 15 Mar 1999 21:17:44 -0800 (PST) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA06281 for ; Tue, 16 Mar 1999 16:17:24 +1100 (EDT) Received: from areilly.bpc-users.org (CPE-24-192-50-137.nsw.bigpond.net.au [24.192.50.137]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id QAA05059 for ; Tue, 16 Mar 1999 16:17:22 +1100 (EDT) Received: (qmail 40606 invoked by uid 1000); 16 Mar 1999 05:17:21 -0000 Message-ID: <19990316051721.40605.qmail@areilly.bpc-users.org> From: "Andrew Reilly" Date: Tue, 16 Mar 1999 16:17:20 +1100 (EST) Subject: Re: Use of "register" in code To: dillon@apollo.backplane.com Cc: andrew@lake.com.au, sjr@home.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199903160431.UAA05835@apollo.backplane.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon said: > Firstly, that is not what register means. Well, I'm not a language lawyer, but it's certainly been my experience. Even the version of gcc shipped as cc with FreeBSD will say foo.c:3: warning: address of register variable `i' requested if you try something like: {register int i; int *p; p = & i;} > Secondly, all modern C > compilers that I know about, including one I wrote years ago, can > trivially detect the stack locality of a variable and put it in a > register as part of standard optimizations. It's one of the *easiest* > optimizations a C compiler can do, in fact. Naturally. You'd hope so. But if your routine takes the address of _any_ auto variable, and hands that to a function or writes to some run-time computed index of it, then the compiler has to assume that any of the other auto variables in the stack frame could have been modified, and so it has to re-fetch any auto variables after such a write. It doesn't have to do that for register variables. > Some compilers will add a little weight to the potential optimization > if you use the 'register' keyword, but modern compilers tend to do a > better job without the manual weighting. One old compiler I've used won't ever put a variable into a register unless you tell it to, but neither example has a bearing on whether "register" has a specific meaning wrt aliasing. The closest reference I've found on the net is http://www.lysator.liu.se/c/rat/c5.html#3-5 3.5.1, which says: " Because the address of a register variable cannot be taken, objects of storage class register effectively exist in a space distinct from other objects. (Functions occupy yet a third address space). This makes them candidates for optimal placement, the usual reason for declaring registers, but it also makes them candidates for more aggressive optimization. The practice of representing register variables as wider types (as when register char is quietly changed to register int) is no longer acceptable. " which seems to back up my assertion. In any case, what does taking the register keyword out buy you? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 21:27: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 2829A1509A for ; Mon, 15 Mar 1999 21:25:47 -0800 (PST) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA01995 for ; Tue, 16 Mar 1999 16:25:27 +1100 (EDT) Received: from areilly.bpc-users.org (CPE-24-192-50-137.nsw.bigpond.net.au [24.192.50.137]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id QAA07606 for ; Tue, 16 Mar 1999 16:25:25 +1100 (EDT) Received: (qmail 40663 invoked by uid 1000); 16 Mar 1999 05:25:24 -0000 Message-ID: <19990316052524.40662.qmail@areilly.bpc-users.org> From: "Andrew Reilly" Date: Tue, 16 Mar 1999 16:25:23 +1100 (EST) Subject: Re: Use of "register" in code To: dillon@apollo.backplane.com Cc: andrew@lake.com.au, sjr@home.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199903160509.VAA06242@apollo.backplane.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon said: > Let me extend this with another example: Protection against aliasing > is not usually an issue with stack variables. Of course it is. It's one of the principle reasons that Fortran can still generate tighter inner loop code than straight-forward C. The handbook of numerical C code says in big letters: fetch to register temporaries if a value is to be re-used, and use register variables for all pointers and indices. > On the otherhand, it is > something that would be much more useful with structural fields > or globals. Not sure why you would want that. Gcc has tweaks to allow you to put globals in specific machine registers, but that's hardly standard C or useful. > I don't know a single programmer who uses 'register' to mean 'alias > protection'. Well, you've met one now :-) -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 21:28:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3E59D1509E for ; Mon, 15 Mar 1999 21:28:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA06458; Mon, 15 Mar 1999 21:27:52 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 21:27:52 -0800 (PST) From: Matthew Dillon Message-Id: <199903160527.VAA06458@apollo.backplane.com> To: "Andrew Reilly" Cc: andrew@lake.com.au, sjr@home.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code References: <19990316051721.40605.qmail@areilly.bpc-users.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Secondly, all modern C :> compilers that I know about, including one I wrote years ago, can :> trivially detect the stack locality of a variable and put it in a :> register as part of standard optimizations. It's one of the *easiest* :> optimizations a C compiler can do, in fact. : :Naturally. You'd hope so. But if your routine takes the address of :_any_ auto variable, and hands that to a function or writes to some :run-time computed index of it, then the compiler has to assume that any :of the other auto variables in the stack frame could have been modified, :and so it has to re-fetch any auto variables after such a write. It :doesn't have to do that for register variables. No, only the auto variable that you took the address of. If an array or structure, the entire array or structure is put on a real stack. Other auto variables are left uneffected. While it is true that in the olden days people would take the address of one auto variable in order to reference another by indexing it, in modern days the alignment and reordering optimizations made by compilers pretty much nixes such uses on auto variables. Such uses are considered 'bad code' these days, so compilers have no problem assuming that other auto variables can remain optimized. :> Some compilers will add a little weight to the potential optimization :> if you use the 'register' keyword, but modern compilers tend to do a :> better job without the manual weighting. : :One old compiler I've used won't ever put a variable into a register :unless you tell it to, but neither example has a bearing on whether :"register" has a specific meaning wrt aliasing. : :The closest reference I've found on the net is http://www.lysator.liu.se/c/rat/c5.html#3-5 :3.5.1, which says: : :" :Because the address of a register variable cannot be taken, objects of storage :class register effectively exist in a space distinct from other objects. :(Functions occupy yet a third address space). This makes them candidates for :optimal placement, the usual reason for declaring registers, but it also makes :them candidates for more aggressive optimization. : :The practice of representing register variables as wider types (as when register :char is quietly changed to register int) is no longer acceptable. :" : :which seems to back up my assertion. : :In any case, what does taking the register keyword out buy you? : :-- :Andrew A lot of the older kernel code used 'register' to optimize for a specific processor or compiler - usually the VAX. As kernel code started to migrate to other processors, such optimizations have historically produced *WORSE* code on the other processors. So people stopped using 'register' and started expecting compilers to optimize it themselves. For example, on an intel processor with only a handful of registers, declaring 8 auto's as register and actually expecting the compiler to do something with that is counter productive. These days, 'register' is considered more of a nuisance that obscures the readability of the code then anything else. Hence people have started ripping out the keyword from code. The only reason it hasn't been ripped out more quickly is because it adds garbage to the CVS diff's which complicates the lives of people who try to sync code up ( such as device drivers ) across platforms. This is why you do not see anyone doing any wholesale removal of 'register' from existing source trees. It is removed more slowly, as people work on other things in the kernel. -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 Mon Mar 15 21:34:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id CC4681509E for ; Mon, 15 Mar 1999 21:31:48 -0800 (PST) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA20874 for ; Tue, 16 Mar 1999 16:31:28 +1100 (EDT) Received: from areilly.bpc-users.org (CPE-24-192-50-137.nsw.bigpond.net.au [24.192.50.137]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id QAA09778 for ; Tue, 16 Mar 1999 16:31:26 +1100 (EDT) Received: (qmail 40723 invoked by uid 1000); 16 Mar 1999 05:31:26 -0000 Message-ID: <19990316053126.40722.qmail@areilly.bpc-users.org> From: "Andrew Reilly" Date: Tue, 16 Mar 1999 16:31:26 +1100 (EST) Subject: Re: Use of "register" in code To: mike@smith.net.au Cc: andrew@lake.com.au, dillon@apollo.backplane.com, sjr@home.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199903160416.UAA02703@dingo.cdrom.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith said: > That's not what 'register' means, I don't have a copy of the standard. Would you mind quoting the relevant bit for us, please? > and unfortunately the use of > 'register' by code authors doesn't help as they're not privy to the > actual layout of the code at the point where register allocation is > performed. I'm not sure that I understand that clause. Are you suggesting that the use of "register" in declarations is harmful, or just that gcc doesn't feel like doing anything useful with it? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 21:40:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id CA5CE14DE5 for ; Mon, 15 Mar 1999 21:40:52 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id VAA17718; Mon, 15 Mar 1999 21:39:59 -0800 (PST) Message-Id: <199903160539.VAA17718@lestat.nas.nasa.gov> To: "Andrew Reilly" Cc: mike@smith.net.au, dillon@apollo.backplane.com, sjr@home.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 15 Mar 1999 21:39:58 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Mar 1999 16:31:26 +1100 (EST) "Andrew Reilly" wrote: > Mike Smith said: > > That's not what 'register' means, > > I don't have a copy of the standard. Would you mind quoting the > relevant bit for us, please? Uhh... "register" isn't in Standard C, is it? -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 21:43:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 758DB14EEE for ; Mon, 15 Mar 1999 21:43:50 -0800 (PST) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA28940 for ; Tue, 16 Mar 1999 16:43:30 +1100 (EDT) Received: from areilly.bpc-users.org (CPE-24-192-50-137.nsw.bigpond.net.au [24.192.50.137]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id QAA13670 for ; Tue, 16 Mar 1999 16:43:27 +1100 (EDT) Received: (qmail 40787 invoked by uid 1000); 16 Mar 1999 05:43:26 -0000 Message-ID: <19990316054325.40786.qmail@areilly.bpc-users.org> From: "Andrew Reilly" Date: Tue, 16 Mar 1999 16:43:25 +1100 (EST) Subject: Re: Use of "register" in code To: dillon@apollo.backplane.com Cc: andrew@lake.com.au, sjr@home.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199903160527.VAA06458@apollo.backplane.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon said: > No, only the auto variable that you took the address of. If an array or > structure, the entire array or structure is put on a real stack. Other > auto variables are left uneffected. > > While it is true that in the olden days people would take the address of > one auto variable in order to reference another by indexing it, in modern > days the alignment and reordering optimizations made by compilers pretty > much nixes such uses on auto variables. Such uses are considered > 'bad code' these days, so compilers have no problem assuming that other > auto variables can remain optimized. Fair enough. I was under the impression that the standard or the compilers had been written to avoid breakage of that "bad code", and so therefore had to be pessimistic. If that's not the case, and they can get away with making those optimisations anyway, then that's good. I've had to use some pretty ordinary compilers. They still exist, and are still shipped with new systems. > specific processor or compiler - usually the VAX. As kernel code started > to migrate to other processors, such optimizations have historically > produced *WORSE* code on the other processors. So people stopped using > 'register' and started expecting compilers to optimize it themselves. But how is using 'register' with gcc in FreeBSD going to make performance _worse_, given that gcc is quite happy to move register variables to and from the stack? I'll shut up now. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 21:44: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 9B5EA14F8E for ; Mon, 15 Mar 1999 21:44:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA03070; Mon, 15 Mar 1999 21:36:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903160536.VAA03070@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrew Reilly" Cc: mike@smith.net.au, dillon@apollo.backplane.com, sjr@home.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code In-reply-to: Your message of "Tue, 16 Mar 1999 16:31:26 +1100." <19990316053126.40722.qmail@areilly.bpc-users.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 21:36:26 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > and unfortunately the use of > > 'register' by code authors doesn't help as they're not privy to the > > actual layout of the code at the point where register allocation is > > performed. > > I'm not sure that I understand that clause. Are you suggesting that > the use of "register" in declarations is harmful, or just that gcc > doesn't feel like doing anything useful with it? No, I'm suggesting that it's not helpful for a code author to use the register qualifier as they're in less of a position than the compiler to decide which variables should best be assigned register storage. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Mar 15 21:46: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox1.ucsd.edu (mailbox1.ucsd.edu [132.239.1.53]) by hub.freebsd.org (Postfix) with ESMTP id 8A48D1516B for ; Mon, 15 Mar 1999 21:45:56 -0800 (PST) (envelope-from rjdawes@physics.ucsd.edu) Received: from physics.ucsd.edu (huntington.ucsd.edu [132.239.73.96]) by mailbox1.ucsd.edu (8.9.1a/8.9.1) with SMTP id VAA05700; Mon, 15 Mar 1999 21:45:37 -0800 (PST) Received: from localhost by physics.ucsd.edu (SMI-8.6/SMI-SVR4) id VAA20024; Mon, 15 Mar 1999 21:43:57 -0800 Date: Mon, 15 Mar 1999 21:43:56 -0800 (PST) From: "Richard J. Dawes" X-Sender: rjdawes@huntington Reply-To: Richard Dawes To: Matthew Dillon Cc: Andrew Reilly , "Stephen J. Roznowski" , freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code In-Reply-To: <199903160509.VAA06242@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 Mon, 15 Mar 1999, Matthew Dillon wrote: > Date: Mon, 15 Mar 1999 21:09:10 -0800 (PST) > From: Matthew Dillon > To: Andrew Reilly , > "Stephen J. Roznowski" , freebsd-hackers@FreeBSD.ORG > Subject: Re: Use of "register" in code > > > : > : > ::> : > ::> :Thanks, > ::> :-- > ::> :Stephen J. Roznowski (sjr@home.net) > ::> > ::> The register declarations are useless historical artifacts. > :: > ::Why do you say that? "register" in a declaration has a specific > ::semantic meaning that isn't (to my knowledge) duplicated by any > ::other language mechanism, and that is "this variable does not exist > ::in the memory space, and so _cannot_ be de-referenced with "&" or > ::modified by an asignment through a pointer." Register pointer > ::variables and temporaries are very important for preventing C > ::compilers from producing pessimistic inner loop code. > :: > ::-- > ::Andrew > : > : Firstly, that is not what register means. Secondly, all modern C > : compilers that I know about, including one I wrote years ago, can > : trivially detect the stack locality of a variable and put it in a > : register as part of standard optimizations. It's one of the *easiest* > : optimizations a C compiler can do, in fact. > : > : Some compilers will add a little weight to the potential optimization > : if you use the 'register' keyword, but modern compilers tend to do a > : better job without the manual weighting. > : > : -Matt > : Matthew Dillon > : > > Let me extend this with another example: Protection against aliasing > is not usually an issue with stack variables. On the otherhand, it is > something that would be much more useful with structural fields > or globals. > > Try putting the 'register' keyword in front of a structural field or > global and you will wind up with a fist full of fatal compiler errors. > > I don't know a single programmer who uses 'register' to mean 'alias > protection'. I agree. Of course, there might not have been optimizing compilers available when Stephen's games were written (the ones from the ancient BSD games collection?) Now, the "register" specifier in userland code can be eliminated without a second thought. Andrew may well be refering to a semantic he learned that might have been in use in that former, perhaps pre-ANSI, day. However, is 'register' not used to indicate candidacy for register allo- cation when (in some rare instance) you don't trust a compiler's optimi- zations? Isn't that one reason gcc offers "-O0"? (I'm sure what level is the default.) In that context, deeming 'register' to be a "useless historical artifact" may be stating the case in terms that are too strong. I don't like to put my God hat on very often, but it's nice to know the option of doing so is available should it be necessary. ======================================== Richard J. Dawes rdawes@ucsd.edu ======================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 22: 4:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox1.ucsd.edu (mailbox1.ucsd.edu [132.239.1.53]) by hub.freebsd.org (Postfix) with ESMTP id B09EF14C24 for ; Mon, 15 Mar 1999 22:04:14 -0800 (PST) (envelope-from rjdawes@physics.ucsd.edu) Received: from physics.ucsd.edu (huntington.ucsd.edu [132.239.73.96]) by mailbox1.ucsd.edu (8.9.1a/8.9.1) with SMTP id WAA07184; Mon, 15 Mar 1999 22:03:55 -0800 (PST) Received: from localhost by physics.ucsd.edu (SMI-8.6/SMI-SVR4) id WAA20089; Mon, 15 Mar 1999 22:02:16 -0800 Date: Mon, 15 Mar 1999 22:02:15 -0800 (PST) From: "Richard J. Dawes" X-Sender: rjdawes@huntington Reply-To: Richard Dawes To: Andrew Reilly Cc: dillon@apollo.backplane.com, sjr@home.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code In-Reply-To: <19990316052524.40662.qmail@areilly.bpc-users.org> 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, 16 Mar 1999, Andrew Reilly wrote: > Of course it is. It's one of the principle reasons that Fortran can > still generate tighter inner loop code than straight-forward C. The > handbook of numerical C code says in big letters: fetch to register > temporaries if a value is to be re-used, and use register variables for > all pointers and indices. Umm, are you refering to "Numerical Recipes in C"? That tome is well- known for its out-of-date C advice, not to mention obsolete algorithms. Just a tip. Sorry for going off-topic. ======================================== Richard J. Dawes rdawes@ucsd.edu ======================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 22: 9:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 5FB4714DB9 for ; Mon, 15 Mar 1999 22:09:22 -0800 (PST) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA19835 for ; Tue, 16 Mar 1999 17:09:02 +1100 (EDT) Received: from areilly.bpc-users.org (CPE-24-192-50-137.nsw.bigpond.net.au [24.192.50.137]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id RAA22211 for ; Tue, 16 Mar 1999 17:09:01 +1100 (EDT) Received: (qmail 41099 invoked by uid 1000); 16 Mar 1999 06:09:00 -0000 Message-ID: <19990316060900.41098.qmail@areilly.bpc-users.org> From: "Andrew Reilly" Date: Tue, 16 Mar 1999 17:09:00 +1100 (EST) Subject: Re: Use of "register" in code To: rdawes@ucsd.edu Cc: dillon@apollo.backplane.com, sjr@home.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard J. Dawes said: > On Tue, 16 Mar 1999, Andrew Reilly wrote: > >> Of course it is. It's one of the principle reasons that Fortran can >> still generate tighter inner loop code than straight-forward C. The >> handbook of numerical C code says in big letters: fetch to register >> temporaries if a value is to be re-used, and use register variables for >> all pointers and indices. > > Umm, are you refering to "Numerical Recipes in C"? That tome is well- > known for its out-of-date C advice, not to mention obsolete algorithms. > > Just a tip. Sorry for going off-topic. No, just my own accumulated numerical C lore. I don't own a copy of Numerical Recipes in C, mostly because every time I've looked something up in someone else's copy the code was awful. Looks like my accumulated C lore needs some updating. Thanks to everyone who's pointed out the error of my ways... -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 22:40:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id A4E2615063 for ; Mon, 15 Mar 1999 22:39:24 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id RAA17539 for ; Tue, 16 Mar 1999 17:10:10 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA26611; Tue, 16 Mar 1999 17:08:55 +0930 Date: Tue, 16 Mar 1999 17:08:55 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: hackers@freebsd.org Subject: VMWare 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 Check out www.vmware.com - this is a product which allows concurrent execution of multiple operating systems on x86, by running under a "host" OS which manages one or more "guest" OSes and presents them with their own private virtual machine (like some of the old mainframes). Currently the only host OS version is for Linux (still in beta), and Windows NT and FreeBSD host versions are in development (I have it on good authority that the FreeBSD version will be released soon). FreeBSD isn't listed on the website, but one of my friends is involved in the beta program and assures me it's coming. On the Guest OS side, they claim support for {Free,Net,Open}BSD, Linux, NT, Win9x, DOS, BeOS, and Solaris 7. Cost for the full version is $300, although for non-commercial and student use it's $99. My friend has been raving about the quality of this product - it certainly does look promising. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 15 23:58:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 17745150EE for ; Mon, 15 Mar 1999 23:58:33 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id XAA73639; Mon, 15 Mar 1999 23:58:07 -0800 (PST) (envelope-from obrien) Date: Mon, 15 Mar 1999 23:58:07 -0800 From: "David O'Brien" To: Andrew Reilly Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code Message-ID: <19990315235807.A73567@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903160527.VAA06458@apollo.backplane.com> <19990316054325.40786.qmail@areilly.bpc-users.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990316054325.40786.qmail@areilly.bpc-users.org>; from Andrew Reilly on Tue, Mar 16, 1999 at 04:43:25PM +1100 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 16, 1999 at 04:43:25PM +1100, Andrew Reilly wrote: > But how is using 'register' with gcc in FreeBSD going to make > performance _worse_, given that gcc is quite happy to move register > variables to and from the stack? Possibly you should take this up on comp.compilers (or comp.std.c). This discussion is much more applicable there than freebsd-hackers. Please study the aggressive optimizations that a modern compiler does and you will realize that the resulting code looks *nothing* like what you would imagine if you "hand compiled" it. Back in the days of the Small C compiler (with only a peephole optimizer), "register" was useful to do some manual optimizations. But no longer. There is a nice ACM Survey paper on compiler optimizations you should read. I can provide the referenced tomorrow when I get to my lab. There is also a new text book on compiler optimizations that came out last year (and used in a grad class here) that would also answer your questions on why "register" is useless today. I can also provide a reference to that tomorrow. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 0:14:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 037F814FA3 for ; Tue, 16 Mar 1999 00:14:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA06956; Tue, 16 Mar 1999 00:14:30 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 00:14:30 -0800 (PST) From: Matthew Dillon Message-Id: <199903160814.AAA06956@apollo.backplane.com> To: "Andrew Reilly" Cc: andrew@lake.com.au, sjr@home.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code References: <19990316054325.40786.qmail@areilly.bpc-users.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I've had to use some pretty ordinary compilers. They still exist, and :are still shipped with new systems. : :> specific processor or compiler - usually the VAX. As kernel code started :> to migrate to other processors, such optimizations have historically :> produced *WORSE* code on the other processors. So people stopped using :> 'register' and started expecting compilers to optimize it themselves. : :But how is using 'register' with gcc in FreeBSD going to make :performance _worse_, given that gcc is quite happy to move register :variables to and from the stack? : :I'll shut up now. : :-- :Andrew I doubt it would make performance worse. I think GCC basically just ignores it for IA32. The general trend in programming these days is to not use 'register' ( for reasons already outlined ), except in certain extreme cases. If you are doing small systems work, it's a different story. But for most mainstream coding 'register' is out. -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 Tue Mar 16 0:52:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C19B414F45 for ; Tue, 16 Mar 1999 00:48:49 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA19976; Tue, 16 Mar 1999 00:42:20 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdP19950; Tue Mar 16 08:42:08 1999 Date: Tue, 16 Mar 1999 00:41:43 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Kris Kennaway Cc: hackers@FreeBSD.ORG Subject: Re: VMWare 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 The coolest thing would be to be able to run an OS under the control of another copy of itself fro single stepping etc. A bit like the 2 machine debugging, but with one machine.. julian On Tue, 16 Mar 1999, Kris Kennaway wrote: > Check out www.vmware.com - this is a product which allows concurrent execution > of multiple operating systems on x86, by running under a "host" OS which > manages one or more "guest" OSes and presents them with their own private > virtual machine (like some of the old mainframes). > > Currently the only host OS version is for Linux (still in beta), and Windows > NT and FreeBSD host versions are in development (I have it on good authority > that the FreeBSD version will be released soon). FreeBSD isn't listed on the > website, but one of my friends is involved in the beta program and assures me > it's coming. > > On the Guest OS side, they claim support for {Free,Net,Open}BSD, Linux, NT, > Win9x, DOS, BeOS, and Solaris 7. > > Cost for the full version is $300, although for non-commercial and student use > it's $99. My friend has been raving about the quality of this product - it > certainly does look promising. > > Kris > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. > > > > 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 Tue Mar 16 0:59:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8B0551514E for ; Tue, 16 Mar 1999 00:59:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id AAA73848; Tue, 16 Mar 1999 00:58:54 -0800 (PST) (envelope-from obrien) Date: Tue, 16 Mar 1999 00:58:54 -0800 From: "David O'Brien" To: Jason Thorpe Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code Message-ID: <19990316005854.B73567@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903160539.VAA17718@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903160539.VAA17718@lestat.nas.nasa.gov>; from Jason Thorpe on Mon, Mar 15, 1999 at 09:39:58PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 09:39:58PM -0800, Jason Thorpe wrote: > Uhh... "register" isn't in Standard C, is it? ANSI X3.159-1989: 3.1.1 Keywords -------------- "register" listed 3.5.1 Storage-Class Specifiers ------------------------------ A declaration of an identifier for an object with storage-class specifier "register" suggests that access to the object be as fast as possible. The extent to which such suggestions are effective is implementation-defined.(footnote 58) (footnote 58) The implementation may treat any "register" declaration simply as an "auto" declaration. However, whether or not addressable storage is actually used, the address of any part of an object declared with storage-class specifier "register" may not be computed, either explicitly (by use of the unary "&" operator as discussed in 3.3.3.2) or implicitly (by converting an array name to a pointer as discussed in 3.2.2.1). Thus the only operator that can be applied to an array declared with storage-class specifier "register" is "sizeof". -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 1:13:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id E602514D1E for ; Tue, 16 Mar 1999 01:13:19 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 5264 invoked by uid 1001); 16 Mar 1999 09:12:59 +0000 (GMT) To: julian@whistle.com Cc: kkennawa@physics.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: VMWare From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 16 Mar 1999 00:41:43 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 16 Mar 1999 10:12:59 +0100 Message-ID: <5262.921575579@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The coolest thing would be to be able to run an OS under the control of > another copy of itself fro single stepping etc. > > A bit like the 2 machine debugging, but with one machine.. Shades of VM/CMS. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 1:30:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id 0D64714CD1 for ; Tue, 16 Mar 1999 01:30:40 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 18994 invoked by uid 1000); 16 Mar 1999 09:29:54 -0000 Date: Tue, 16 Mar 1999 10:29:54 +0100 From: Andreas Braukmann To: hackers@FreeBSD.ORG Subject: Re: VMWare Message-ID: <19990316102954.B501@paert.tse-online.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Kris Kennaway on Tue, Mar 16, 1999 at 05:08:55PM +0930 Organization: TSE TeleService GmbH Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just a few minutes before I read your mail, I had contacted vmware (ok, ... the sales department ;) ) regarding the future availability of their product for FreeBSD (as the host-platform). On Tue, Mar 16, 1999 at 05:08:55PM +0930, Kris Kennaway wrote: > that the FreeBSD version will be released soon). FreeBSD isn't listed on the > website, but one of my friends is involved in the beta program and assures me > it's coming. Meanwhile I got their answer :(. He stated, that they are no plans for FreeBSD as a host-platform as a matter of fact. And now, ... I'm very, very, very sad ... as a matter of fact. But I will definitely buy the NT hosted version as soon as it becomes available. Andreas -- : TSE TeleService GmbH : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 5:45:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gwi.net (mail.gwi.net [204.120.68.142]) by hub.freebsd.org (Postfix) with ESMTP id B474D1540C for ; Tue, 16 Mar 1999 05:43:24 -0800 (PST) (envelope-from fkittred@mail.gwi.net) Received: from mail.gwi.net (fkittred@localhost [127.0.0.1]) by mail.gwi.net (8.8.5/8.8.7) with ESMTP id IAA28283; Tue, 16 Mar 1999 08:42:06 -0500 (EST) Message-Id: <199903161342.IAA28283@mail.gwi.net> To: Wes Peters Cc: Matthew Dillon , Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@freebsd.org Reply-To: Matthew Dillon Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Mon, 15 Mar 1999 08:58:07 MST." <36ED2E0F.6B0028DB@softweyr.com> Date: Tue, 16 Mar 1999 08:42:05 -0500 From: Fletcher E Kittredge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Mar 1999 08:58:07 -0700 Wes Peters wrote: > > Tell that to Alcatel, who just agreed to pay $2 billion for us. > > > P.S. I hope to be one of your first customers! > > You're about 5 years too late for that. See http://www.xylan.com/ for > the full poop. You'll specifically want to look at the Omni Switch/ > Router and the 2-port GSX Gigabit Ethernet card. Some of the $2 billion should go to your web server department :) That URL is unreachable(see below). I am really looking forward to reading your specs when the server[s] come back on the net. regards, fletcher P.S. it appears your main nameserver is down too? usr/local/archive/webmaster>ping www.xylan.com PING webster.xylan.com (208.8.0.251): 56 data bytes 64 bytes from 208.8.0.251: icmp_seq=0 ttl=241 time=165.195 ms 64 bytes from 208.8.0.251: icmp_seq=1 ttl=241 time=145.79 ms 64 bytes from 208.8.0.251: icmp_seq=3 ttl=241 time=149.238 ms 64 bytes from 208.8.0.251: icmp_seq=4 ttl=241 time=149.801 ms ^C --- webster.xylan.com ping statistics --- 5 packets transmitted, 4 packets received, 20% packet loss round-trip min/avg/max = 145.79/152.506/165.195 ms /usr/local/archive/webmaster>telnet www.xylan.com 80 Trying 208.8.0.251... telnet: Unable to connect to remote host: Connection refused /usr/local/archive/webmaster>telnet www.xylan.com 443 Trying 208.8.0.251... (timeout) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 6:23:27 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 0F3BF1526B for ; Tue, 16 Mar 1999 06:23:25 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA04748; Tue, 16 Mar 1999 23:23:16 +0900 (JST) Message-ID: <36EE54E1.40572320@newsguy.com> Date: Tue, 16 Mar 1999 21:56:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Steve Passe Cc: hackers@FreeBSD.ORG Subject: Re: power-off without halt References: <199903151655.JAA28147@Ilsa.StevesCafe.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Passe wrote: > > We are looking at using FreeBSD as an "embedded OS" inside a line > of instruments we are building. I think I have a handle on all the > issues except how to cleanly handle shutdown where there is no > console, and thus no way to send a 'halt' command. The requirement > is that the user can merely turn off the power, nothing more required. > > I can modify the disk setup, kernel/util code as needed, I just need some > idea for a workable solution. Has anyone delt with this problem before? Steve, this problem might be similar to the one of a UPS-backed unit. In such systems, it is common to have a signal being sent from the UPS to the computer, so that the computer will shutdown before the UPS batteries run out. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 6:23:37 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 7B8AB1529D for ; Tue, 16 Mar 1999 06:23:26 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA04652; Tue, 16 Mar 1999 23:22:57 +0900 (JST) Message-ID: <36EE2085.A0FAAE76@newsguy.com> Date: Tue, 16 Mar 1999 18:12:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Andrew Reilly Cc: dillon@apollo.backplane.com, sjr@home.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Use of "register" in code References: <19990316052524.40662.qmail@areilly.bpc-users.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Reilly wrote: > > Not sure why you would want that. Gcc has tweaks to allow you to put > globals in specific machine registers, but that's hardly standard C or > useful. Not exactly hardly useful, if you work with virtual machines. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 6:24: 5 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 A5A3015365 for ; Tue, 16 Mar 1999 06:24:02 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA04797; Tue, 16 Mar 1999 23:23:26 +0900 (JST) Message-ID: <36EE5B76.3C467B7B@newsguy.com> Date: Tue, 16 Mar 1999 22:24:06 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: sthaug@nethelp.no Cc: julian@whistle.com, kkennawa@physics.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: VMWare References: <5262.921575579@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > > > The coolest thing would be to be able to run an OS under the control of > > another copy of itself fro single stepping etc. > > > > A bit like the 2 machine debugging, but with one machine.. > > Shades of VM/CMS. What do you mean by "shades"? :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 6:39:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 2FB4C1514E for ; Tue, 16 Mar 1999 06:39:48 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id HAA14741; Tue, 16 Mar 1999 07:39:43 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EE6D2F.E6D9227F@softweyr.com> Date: Tue, 16 Mar 1999 07:39:43 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Andy Doran Cc: hackers@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andy Doran wrote: > > Hi all, > I've got weird problem with an Intel Etherexpress Pro 100. The cards work > fine, in fact great, with most of my FreeBSD boxes, all of which run > the 3.x branch updated weekly over cvsup. > > The trouble is, when I do an 'ifconfig fxp0 $some_address' on one > particular machine (a Tulip P-II, real junk) the machine locks up. The > keyboard still works (i.e. can toggle numlock light), and trying to switch > to another VT causes the machine to generate a never ending beep. I guess > it's getting stuck at spl???() somewhere. > > Setting the media type works, and the card works fine on other > machines. I've tried changing the slot, and using a generic 3.x kernel > too, but no luck. A 2.2.6 kernel works fine, no lockups. This card shares > an IRQ with a 3c905 and a S3 ViRGE/GX2. > > Unfortunately I can't hack at this because it's a production box, and has > to be up 24/7 almost always. Any ideas? I've seen the same problem on a Toshiba Equuium with on-board Pro 100+. The failure happens when the first DMA in the attach routine never completes. I'll be looking into it this week; I finally have some time to debug this problem and two other network cards for when it the machine has to work. I've saved a couple of recent messages about BIOS not initializing PCI cards; I'm wondering if that might be the cause of the problem. This machine worked fine with 2.2.x, so I'll be looking at what changed between 2.2.7 and 3.0/3.1. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 7:12: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 9689315698 for ; Tue, 16 Mar 1999 07:10:52 -0800 (PST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id AAA02610 for ; Wed, 17 Mar 1999 00:01:47 +0900 (JST) Message-Id: <199903161501.AAA02610@shidahara1.planet.sci.kobe-u.ac.jp> To: freebsd-hackers@freebsd.org Subject: ACPI Table Reader Date: Wed, 17 Mar 1999 00:01:46 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I wrote ACPI table reader. The code is at http://www.planet.sci.kobe-u.ac.jp/~takawata/acpi/ see document in the archive. I noticed (probably) bugs in current kernel. I already submited it in i386/10587 and i386/10485. (i386/10485 may not be bug.) I already post about for in freebsd-tech-jp@jp.freebsd.org . But this is newer version than I announced. File signature is updated: MD5 Hash of the archive is MD5 (acpi.tar.gz) = 50300bfcc9278a0a365b56a049ddcef5 The sigature of the archive signed with my PGP key is -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: lntvbI6jmbJdrT79BJjXqonvHHi/6v+N iQCVAwUANu3umF632uaGoujtAQHPSQP/WJ7dNmseFcUT1If4UVTc4z8zcGdrsAUU iIkPzohUj2dBOMv/CgplCYwbLXoGwtCAN0nnmAcCnfDb/D2nJi0Ln4PeX6CqfmO6 pQ5qwvzAHZpWrHVX8nYEwDJa/AYpjRoBq4rTZvQH6+D/Wv7ef0OEOC0SXOEDoffi AvVTBLf3x3c= =frxZ -----END PGP SIGNATURE----- Thanks in advance for your feedback. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 7:29:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 6B2DF14E00 for ; Tue, 16 Mar 1999 07:29:38 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id IAA14844; Tue, 16 Mar 1999 08:29:01 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EE78BC.1AA3B0BB@softweyr.com> Date: Tue, 16 Mar 1999 08:29:00 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Andrew Gallatin , Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903151726.JAA13276@dingo.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: > > > I guess I should take a look at your software and get a card or two > > in for testing. I'd like to see what we can do between two Tigon > > equipped systems with a Xylan switch in the middle. Most of our > > testing on our Gigabit modules so far has been done with a SmartBits > > packet generator, but I don't really believe the numbers until I've > > seen some real host-generated data streams. > > Heh. It would be quite funky if we were able to generate bits fast > enough to become your preferred host platform for host traffic > generation. You already are our favorite host platform for IP testing; I setup our test network with FreeBSD hosts at both ends of the lab. ;^) For pure packet generation, it's hard to beat a SmartBits (if you can afford the price). > That would almost mandate some words from you we could use for bragging > purposes. 8) Maybe I'll write a Daemon News article? We need to get some of the GigEth cards working first, though. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 8:48:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id AF76D152E8 for ; Tue, 16 Mar 1999 08:48:47 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA14560; Tue, 16 Mar 1999 11:52:45 -0500 (EST) Date: Tue, 16 Mar 1999 11:52:44 -0500 (EST) From: Alfred Perlstein To: Julian Elischer Cc: Kris Kennaway , hackers@FreeBSD.ORG Subject: Re: VMWare 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 Tue, 16 Mar 1999, Julian Elischer wrote: > The coolest thing would be to be able to run an OS under the control of > another copy of itself fro single stepping etc. > > A bit like the 2 machine debugging, but with one machine.. > I wonder how to hook up remote gdb to it? :) It'd be nice to trash a virtual machine instead of my workstation when i try things... -Alfred > julian > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 10:16: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 942DC1537E for ; Tue, 16 Mar 1999 10:16:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA11214; Tue, 16 Mar 1999 10:15:40 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 10:15:40 -0800 (PST) From: Matthew Dillon Message-Id: <199903161815.KAA11214@apollo.backplane.com> To: "Daniel C. Sobral" Cc: sthaug@nethelp.no, julian@whistle.com, kkennawa@physics.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: VMWare References: <5262.921575579@verdi.nethelp.no> <36EE5B76.3C467B7B@newsguy.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :sthaug@nethelp.no wrote: :> :> > The coolest thing would be to be able to run an OS under the control of :> > another copy of itself fro single stepping etc. :> > :> > A bit like the 2 machine debugging, but with one machine.. :> :> Shades of VM/CMS. : :What do you mean by "shades"? :-) : :-- :Daniel C. Sobral (8-DCS) :dcs@newsguy.com :dcs@freebsd.org With VM/CMS you could build virtual machines inside virtual machines inside virtual machines, and so forth. -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 Tue Mar 16 11:30:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id B7CD114D92 for ; Tue, 16 Mar 1999 11:30:47 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 29247 invoked from network); 16 Mar 1999 19:30:27 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 16 Mar 1999 19:30:27 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.3/8.9.1) id OAA08492; Tue, 16 Mar 1999 14:30:18 -0500 (EST) Message-Id: <199903161930.OAA08492@y.dyson.net> Subject: Re: Use of "register" in code In-Reply-To: <199903160814.AAA06956@apollo.backplane.com> from Matthew Dillon at "Mar 16, 99 00:14:30 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 16 Mar 1999 14:30:18 -0500 (EST) Cc: andrew@lake.com.au, sjr@home.net, freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Matthew Dillon said: > :I've had to use some pretty ordinary compilers. They still exist, and > :are still shipped with new systems. > : > :> specific processor or compiler - usually the VAX. As kernel code started > :> to migrate to other processors, such optimizations have historically > :> produced *WORSE* code on the other processors. So people stopped using > :> 'register' and started expecting compilers to optimize it themselves. > : > :But how is using 'register' with gcc in FreeBSD going to make > :performance _worse_, given that gcc is quite happy to move register > :variables to and from the stack? > : > :I'll shut up now. > : > :-- > :Andrew > > I doubt it would make performance worse. I think GCC basically just > ignores it for IA32. > It does ignore it. The justification is because the compiler knows more about temporaries and other usage than the programmer. Most of the time (but not all of the time), that is true. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 12:23:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (Postfix) with ESMTP id EF6141536E for ; Tue, 16 Mar 1999 12:23:13 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id NAA01135 for ; Tue, 16 Mar 1999 13:31:42 -0700 (MST) Message-Id: <199903162031.NAA01135@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: hackers@FreeBSD.ORG Subject: Re: power-off without halt In-reply-to: Your message of "Tue, 16 Mar 1999 21:56:01 +0900." <36EE54E1.40572320@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Mar 1999 13:31:42 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Steve Passe wrote: > > > > We are looking at using FreeBSD as an "embedded OS" inside a line > > of instruments we are building. I think I have a handle on all the > > issues except how to cleanly handle shutdown where there is no > > console, and thus no way to send a 'halt' command. The requirement > > is that the user can merely turn off the power, nothing more required. > > > > I can modify the disk setup, kernel/util code as needed, I just need some > > idea for a workable solution. Has anyone delt with this problem before? First, I want to thank everyone for the useful replies I received on this, over 30 so far! Several people have suggested a UPS based solution. This is to look like an instrument, ie a small black box. Not enough room for a UPS internally, and nothing to prevent a user from unplugging it. The ideas about honker caps for ~60-100ms uptime might be workable. The ideas along the lines of an MFS based working partition, with everything else mounted readonly also has merit. I'll be back after mulling this over some more... thanx again, -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 13:36: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 4F5111505C for ; Tue, 16 Mar 1999 13:35:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA00853; Tue, 16 Mar 1999 13:26:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903162126.NAA00853@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wes Peters Cc: Mike Smith , Andrew Gallatin , Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "Tue, 16 Mar 1999 08:29:00 MST." <36EE78BC.1AA3B0BB@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Mar 1999 13:26:06 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Heh. It would be quite funky if we were able to generate bits fast > > enough to become your preferred host platform for host traffic > > generation. > > You already are our favorite host platform for IP testing; I setup > our test network with FreeBSD hosts at both ends of the lab. ;^) > For pure packet generation, it's hard to beat a SmartBits (if you > can afford the price). > > > That would almost mandate some words from you we could use for bragging > > purposes. 8) > > Maybe I'll write a Daemon News article? We need to get some of the > GigEth cards working first, though. Bill just posted some ttcp numbers; over 600Mbps on TCP, over 800Mbps on UDP. Not too shabby for raw throughput. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 16 13:53:21 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 1294114E00 for ; Tue, 16 Mar 1999 13:53:18 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id VAA79973; Tue, 16 Mar 1999 21:52:59 GMT 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 OAA04845; Tue, 16 Mar 1999 14:52:42 -0700 (MST) Message-Id: <199903162152.OAA04845@harmony.village.org> To: Steve Passe Subject: Re: power-off without halt Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 16 Mar 1999 13:31:42 MST." <199903162031.NAA01135@Ilsa.StevesCafe.com> References: <199903162031.NAA01135@Ilsa.StevesCafe.com> Date: Tue, 16 Mar 1999 14:52:42 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903162031.NAA01135@Ilsa.StevesCafe.com> Steve Passe writes: : The ideas along the lines of an MFS based working partition, with everything : else mounted readonly also has merit. I'll be back after mulling this over : some more... If you have a serial interface free, you could have a button that would send a break over that line and then some small time later remove power from the system. Also, ATA flash card support in FreeBSD[*] is on the horizon which might offer some interesting possibilites as well. It might be fast enough to sync the unwritten data to quickly enough if you could somehow get an interrupt that says that power is failing and you have n mS before it is gone. Warner P.S. One can use ATA flash cards right now on FreeBSD by connecting them directly to the "IDE" bus, since they are just disks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 14:39:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 8C99915584 for ; Tue, 16 Mar 1999 14:38:47 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id RAA14610 for ; Tue, 16 Mar 1999 17:38:28 -0500 (EST) Message-Id: <199903162238.RAA14610@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: KVA size changes in 3.1-stable Date: Tue, 16 Mar 1999 17:38:27 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have been experiencing some problems with a 3.1-stable machine with 192M of RAM and 900M swap. The crashes seem to be related to NFS, but it is very eratic (oh, did I mention maxusers is 320?). Needless to say, we think the problem may be the KVA problem that has walked arround here abit lately. I have the patches from Tor Egge. I noticed that some of the patches are optional. For example, we don't need to make a change to pmap.h since we can do the same with 'options "NKPDE=126"'. However there are also changes to the kernel's load address (0xf0100000 -> 0xe0100000). Are these changes mandatory as well? (I am assuming they are, but we don't want to make changes to source files that CVS is going to blast.). -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 16: 5:28 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 D8D1114C8E for ; Tue, 16 Mar 1999 16:05:22 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA29959; Wed, 17 Mar 1999 10:34:48 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [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: Wed, 17 Mar 1999 10:34:48 +1030 (CST) From: "Daniel O'Connor" To: Alfred Perlstein Subject: Re: VMWare Cc: hackers@FreeBSD.ORG, Kris Kennaway , Julian Elischer Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Mar-99 Alfred Perlstein wrote: > > A bit like the 2 machine debugging, but with one machine.. > I wonder how to hook up remote gdb to it? :) > It'd be nice to trash a virtual machine instead of my workstation > when i try things... Well, VMWare virtualises serial ports, so maybe you can map a virtual serial port to a file :) Either that or have a null modem connected to 2 serial ports on your computer :) (ie one is used by the virtual OS, and the other by the real OS) --- 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 Tue Mar 16 16:11:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 0A3DD151C9 for ; Tue, 16 Mar 1999 16:11:23 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA20187; Tue, 16 Mar 1999 16:10:53 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 16:10:53 -0800 (PST) From: Matthew Dillon Message-Id: <199903170010.QAA20187@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable References: <199903162238.RAA14610@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :We have been experiencing some problems with a 3.1-stable machine with 192M :of RAM and 900M swap. The crashes seem to be related to NFS, but it is :very eratic (oh, did I mention maxusers is 320?). Needless to say, we :think the problem may be the KVA problem that has walked arround here abit :lately. I have the patches from Tor Egge. I noticed that some of the :patches are optional. For example, we don't need to make a change to pmap.h :since we can do the same with 'options "NKPDE=126"'. However there are also :changes to the kernel's load address (0xf0100000 -> 0xe0100000). Are these :changes mandatory as well? (I am assuming they are, but we don't want to make :changes to source files that CVS is going to blast.). : :-- :David Cross Before you get into that mess with -stable, I suggest reducing your 'maxusers' kernel config to 128 or less. If it is already 128 or less, then the KVA problem is unlikely to be the cause of your problem. Certainly if your maxusers is 64 or less, the KVA problem can't be the cause of your problem. ( Also presuming you are using the default and not overriding NMBCLUSTERS and NBUFS, etc...). The first thing you do when you get a problem is try to rule things out. Patching comes later. -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 Tue Mar 16 16:44:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 6A42C1518D for ; Tue, 16 Mar 1999 16:44:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@ken.cs.rpi.edu [128.213.4.10]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id TAA16397; Tue, 16 Mar 1999 19:44:32 -0500 (EST) Message-Id: <199903170044.TAA16397@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: KVA size changes in 3.1-stable In-Reply-To: Message from Matthew Dillon of "Tue, 16 Mar 1999 16:10:53 PST." <199903170010.QAA20187@apollo.backplane.com> Date: Tue, 16 Mar 1999 19:44:31 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have pretty much ruled out everything else. No 2 of the crashes are ever the same, it is only this machine, and the only difference between this machine and other machines that are rock solid (48+ days uptime), is that this machine has the high maxusers. It is required that this machine has a high maxusers as it is used for shell access for students writing programs. Are there any problems with incorperating Tor's changes into 3.1-STABLE? If so please speak, as that is exactly what I am doing now. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 17: 1:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from if.scientech.com (eaglerock.if.scientech.com [198.60.85.3]) by hub.freebsd.org (Postfix) with ESMTP id E265815160 for ; Tue, 16 Mar 1999 17:01:27 -0800 (PST) (envelope-from cmott@scientech.com) Received: from localhost (cmott@localhost) by if.scientech.com (8.9.2/8.8.7) with ESMTP id SAA22549; Tue, 16 Mar 1999 18:00:35 -0700 (MST) X-Authentication-Warning: if.scientech.com: cmott owned process doing -bs Date: Tue, 16 Mar 1999 18:00:35 -0700 (MST) From: Charles Mott To: Steve Passe Cc: hackers@FreeBSD.org Subject: Re: power-off without halt In-Reply-To: <199903162031.NAA01135@Ilsa.StevesCafe.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 Tue, 16 Mar 1999, Steve Passe wrote: > Several people have suggested a UPS based solution. This is to look like > an instrument, ie a small black box. Not enough room for a UPS internally, > and nothing to prevent a user from unplugging it. The ideas about > honker caps for ~60-100ms uptime might be workable. > > The ideas along the lines of an MFS based working partition, with everything > else mounted readonly also has merit. I'll be back after mulling this over > some more... > > thanx again, > -- > Steve Passe | powered by > smp@csn.net | Symmetric MultiProcessor FreeBSD Would running from a ram disk be feasible? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 17:22:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 10666151FA for ; Tue, 16 Mar 1999 17:22:07 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id CAA18296; Wed, 17 Mar 1999 02:21:45 +0100 (CET) (envelope-from des) To: Andreas Klemm Cc: Rob Snow , Amancio Hasty , Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <001b01be6e10$08061120$03e48486@dympna.com> <19990314142436.A1292@titan.klemm.gtn.com> From: Dag-Erling Smorgrav Date: 17 Mar 1999 02:21:44 +0100 In-Reply-To: Andreas Klemm's message of "Sun, 14 Mar 1999 14:24:37 +0100" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Klemm writes: > AFAIK "zero copy tcp/ip" went into 3.1 and 4.0. Thanks to David > Greenman who implemented and tested this on ftp.cdrom.com. > (I hope I got the credits right ;-) No, that's only zero-copy transmission of files over stream sockets. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 17:38:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8C4DE150A6; Tue, 16 Mar 1999 17:38:52 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id CAA18655; Wed, 17 Mar 1999 02:37:09 +0100 (CET) (envelope-from des) To: Ruslan Ermilov Cc: dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall References: <19990313200150.A83040@relay.ucb.crimea.ua> <199903131819.TAA29395@rt2.synx.com> <19990314162419.A10242@relay.ucb.crimea.ua> From: Dag-Erling Smorgrav Date: 17 Mar 1999 02:37:09 +0100 In-Reply-To: Ruslan Ermilov's message of "Sun, 14 Mar 1999 16:24:19 +0200" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov writes: > On Sat, Mar 13, 1999 at 07:11:19PM +0100, Remy Nonnenmacher wrote: > > On 13 Mar, Ruslan Ermilov wrote: > > > It seems that such "fast forwardable" packets, when passed from > > > ether_input(), for example, just simply bypass all firewall checks. > > > Am I right? > > you are. > It's a big security leak... > David, was it supposed by design (that such packets bypass firewall)? The whole point with fast forwarding is shortening the data path. This includes not running packets through the firewall. This is precisely why it's an option, and is not on by default. After all, if it had no disadvantages or side effects, there'd be no reason *not* to use it, right? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 18: 3:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 915E9151D6 for ; Tue, 16 Mar 1999 18:02:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA21057; Tue, 16 Mar 1999 18:02:35 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 18:02:35 -0800 (PST) From: Matthew Dillon Message-Id: <199903170202.SAA21057@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: KVA size changes in 3.1-stable References: <199903170044.TAA16397@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :We have pretty much ruled out everything else. No 2 of the crashes are ever :the same, it is only this machine, and the only difference between this :machine and other machines that are rock solid (48+ days uptime), is that :this machine has the high maxusers. It is required that this machine :has a high maxusers as it is used for shell access for students writing :programs. : :Are there any problems with incorperating Tor's changes into 3.1-STABLE? If :so please speak, as that is exactly what I am doing now. :-- :David Cross I'm not sure if the 3.x bootblocks & /boot stuff can handle the relocated kernel. If not, you would have to use 4.x bootblocks and /boot stuff ( which should work under both 3.x and 4.x ). Otherwise, it should work under 3.x. -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 Tue Mar 16 18:20:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A66BF15160 for ; Tue, 16 Mar 1999 18:20:41 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id DAA19702; Wed, 17 Mar 1999 03:20:16 +0100 (CET) (envelope-from des) To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: evil maxusers References: <199903160216.VAA24377@cs.rpi.edu> From: Dag-Erling Smorgrav Date: 17 Mar 1999 03:20:15 +0100 In-Reply-To: "David E. Cross"'s message of "Mon, 15 Mar 1999 21:16:26 -0500" Message-ID: Lines: 41 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" writes: > What is evil abuot large maxusers? We have a crashing server (Pentium II-400) > with maxusers set to 320. In a previous email to -hackers that I have since > lost :I it was mentioned that you could lower maxusers, and the, by hand, > up the MBUFs and NPROCs in the config file. However I have grepped the > entire kernel source tree, and I can see that MAXUSERS is only used to > set MBUFs and NPROCS (and other things derive from there, suich as > MAXFILES). Why therefore will MAXUSERS=320 crash my system, while setting > MAXUSERS to 64, and adjusting MBUFs and NPROCS by hand will not? Because mbufs eat memory, and the kernel has a limited address space. If I'm not mistaken, setting maxusers to 320 eats up to 90 MB in mbuf clusters alone, which is almost half the kernel address space. The kernel address space was increased to 1 GB a few days ago.If you're running 4.0 (on a production server? I hope not), update your sources and rebuild. If you're running 3.1, you can try to apply those patches by hand, or wait for them to be MFCed. If you're running 2.x, all bets are off. dg 1999/03/11 10:28:47 PST Modified files: sys/i386/conf Makefile.i386 kernel.script sys/i386/include pmap.h Log: Increased kernel virtual address space to 1GB. NOTE: You MUST have fixed bootblocks in order to boot the kernel after this! Also note that this change breaks BSDI BSD/OS compatibility. Also increased default NKPT to 17 so that FreeBSD can boot on machines with >=2GB of RAM. Booting on machines with exactly 4GB requires other patches, not included. Revision Changes Path 1.141 +2 -2 src/sys/i386/conf/Makefile.i386 1.2 +1 -1 src/sys/i386/conf/kernel.script 1.59 +4 -4 src/sys/i386/include/pmap.h DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 18:23:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 869A915248 for ; Tue, 16 Mar 1999 18:23:40 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id DAA19771; Wed, 17 Mar 1999 03:23:17 +0100 (CET) (envelope-from des) To: Matthew Dillon Cc: "Daniel C. Sobral" , sthaug@nethelp.no, julian@whistle.com, kkennawa@physics.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: VMWare References: <5262.921575579@verdi.nethelp.no> <36EE5B76.3C467B7B@newsguy.com> <199903161815.KAA11214@apollo.backplane.com> From: Dag-Erling Smorgrav Date: 17 Mar 1999 03:23:16 +0100 In-Reply-To: Matthew Dillon's message of "Tue, 16 Mar 1999 10:15:40 -0800 (PST)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > :sthaug@nethelp.no wrote: > :> > The coolest thing would be to be able to run an OS under the control of > :> > another copy of itself fro single stepping etc. > :> Shades of VM/CMS. > :What do you mean by "shades"? :-) > With VM/CMS you could build virtual machines inside virtual machines inside > virtual machines, and so forth. Who says it won't work with VMWare? In fact, I'd be disappointed if it didn't - it'd mean VMWare isn't complete. Think of it in the same terms as of a general Turing machine. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 18:27:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 4E4D2152B0 for ; Tue, 16 Mar 1999 18:26:13 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id SAA01082; Tue, 16 Mar 1999 18:24:53 -0800 (PST) Message-Id: <199903170224.SAA01082@implode.root.com> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable In-reply-to: Your message of "Tue, 16 Mar 1999 18:02:35 PST." <199903170202.SAA21057@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 16 Mar 1999 18:24:52 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >:We have pretty much ruled out everything else. No 2 of the crashes are ever >:the same, it is only this machine, and the only difference between this >:machine and other machines that are rock solid (48+ days uptime), is that >:this machine has the high maxusers. It is required that this machine >:has a high maxusers as it is used for shell access for students writing >:programs. >: >:Are there any problems with incorperating Tor's changes into 3.1-STABLE? If >:so please speak, as that is exactly what I am doing now. >:-- >:David Cross > > I'm not sure if the 3.x bootblocks & /boot stuff can handle the > relocated kernel. If not, you would have to use 4.x bootblocks and > /boot stuff ( which should work under both 3.x and 4.x ). Otherwise, > it should work under 3.x. The boot problem is only with ELF kernels, so another solution is to build the kernel in a.out format ("KERNFORMAT= aout" in /etc/make.conf). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 18:37: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D0F1914FEB for ; Tue, 16 Mar 1999 18:36:50 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id DAA20142; Wed, 17 Mar 1999 03:36:29 +0100 (CET) (envelope-from des) To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable References: <199903162238.RAA14610@cs.rpi.edu> From: Dag-Erling Smorgrav Date: 17 Mar 1999 03:36:28 +0100 In-Reply-To: "David E. Cross"'s message of "Tue, 16 Mar 1999 17:38:27 -0500" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" writes: > However there are also > changes to the kernel's load address (0xf0100000 -> 0xe0100000). Are these > changes mandatory as well? This is part of what's needed to increase the kernel address space, which is necessary to support configurations with large amounts of RAM and/or large vvalues of maxusers. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 18:52: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m2-6-dbn.dial-up.net [196.34.155.70]) by hub.freebsd.org (Postfix) with ESMTP id A6B9D14F05 for ; Tue, 16 Mar 1999 18:50:26 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id EAA11926; Wed, 17 Mar 1999 04:47:39 +0200 (SAT) From: Robert Nordier Message-Id: <199903170247.EAA11926@ceia.nordier.com> Subject: Re: KVA size changes in 3.1-stable In-Reply-To: <199903170202.SAA21057@apollo.backplane.com> from Matthew Dillon at "Mar 16, 99 06:02:35 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 17 Mar 1999 04:47:34 +0200 (SAT) Cc: crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 > :We have pretty much ruled out everything else. No 2 of the crashes are ever > :the same, it is only this machine, and the only difference between this > :machine and other machines that are rock solid (48+ days uptime), is that > :this machine has the high maxusers. It is required that this machine > :has a high maxusers as it is used for shell access for students writing > :programs. > : > :Are there any problems with incorperating Tor's changes into 3.1-STABLE? If > :so please speak, as that is exactly what I am doing now. > :-- > :David Cross > > I'm not sure if the 3.x bootblocks & /boot stuff can handle the > relocated kernel. If not, you would have to use 4.x bootblocks and > /boot stuff ( which should work under both 3.x and 4.x ). Otherwise, > it should work under 3.x. > > -Matt > Matthew Dillon > Either lot should work fine: there've been no required changes in that area. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 18:59:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id DF57515235 for ; Tue, 16 Mar 1999 18:59:31 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA18794; Tue, 16 Mar 1999 18:54:52 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdY18789; Wed Mar 17 02:54:42 1999 Message-ID: <36EF196F.41C67EA6@whistle.com> Date: Tue, 16 Mar 1999 18:54:39 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Matthew Dillon , "Daniel C. Sobral" , sthaug@nethelp.no, kkennawa@physics.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: VMWare References: <5262.921575579@verdi.nethelp.no> <36EE5B76.3C467B7B@newsguy.com> <199903161815.KAA11214@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Matthew Dillon writes: > > :sthaug@nethelp.no wrote: > > :> > The coolest thing would be to be able to run an OS under the control of > > :> > another copy of itself fro single stepping etc. > > :> Shades of VM/CMS. > > :What do you mean by "shades"? :-) > > With VM/CMS you could build virtual machines inside virtual machines inside > > virtual machines, and so forth. > > Who says it won't work with VMWare? In fact, I'd be disappointed if it > didn't - it'd mean VMWare isn't complete. Think of it in the same > terms as of a general Turing machine. They say it won't work.. In their FAQ or somewhere.. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 19:51:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 1289814F4C for ; Tue, 16 Mar 1999 19:51:38 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@ken.cs.rpi.edu [128.213.4.10]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id WAA19489; Tue, 16 Mar 1999 22:51:01 -0500 (EST) Message-Id: <199903170351.WAA19489@cs.rpi.edu> To: Robert Nordier Cc: dillon@apollo.backplane.com (Matthew Dillon), crossd@cs.rpi.edu, freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: KVA size changes in 3.1-stable In-Reply-To: Message from Robert Nordier of "Sat, 17 Mar 1999 04:47:34 +0200." <199903170247.EAA11926@ceia.nordier.com> Date: Tue, 16 Mar 1999 22:50:59 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG AUGH! I compiled the /boot/loader from the 4.0 tree CVS-ed a couple of hours ago (we have our own copy which periodically syncs with cvsup.freebsd.org). I tell it to boot *any* kernel, and it just *hangs* (caps lock/scroll lock still works, but nothing else.)... Normally a /boot/loader startup looks something like: /-\|kernel /-\|/... etc you get the idea. this one looks like: /-\|/ (and hangs here) Any ideas? (It doesn't matter which kernel I am trying to boot relocated or not :I ) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 20: 4: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 0D03314EBA for ; Tue, 16 Mar 1999 20:03:53 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id XAA45673; Tue, 16 Mar 1999 23:01:39 -0500 (EST) Date: Tue, 16 Mar 1999 23:01:39 -0500 (EST) From: Chuck Robey To: "David E. Cross" Cc: Robert Nordier , Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable In-Reply-To: <199903170351.WAA19489@cs.rpi.edu> 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, 16 Mar 1999, David E. Cross wrote: > AUGH! > > I compiled the /boot/loader from the 4.0 tree CVS-ed a couple of hours ago > (we have our own copy which periodically syncs with cvsup.freebsd.org). I > tell it to boot *any* kernel, and it just *hangs* (caps lock/scroll lock > still works, but nothing else.)... Normally a /boot/loader startup looks > something like: > /-\|kernel /-\|/... etc you get the idea. > > this one looks like: > > /-\|/ (and hangs here) How long since you last used disklabel to update your bootblocks? Old ones will do that (they did for me, using 2.2.6 bootblocks a while back). ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 20:57:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.38]) by hub.freebsd.org (Postfix) with ESMTP id A1AA514BCE; Tue, 16 Mar 1999 20:56:56 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id WAA55971; Tue, 16 Mar 1999 22:55:22 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 16 Mar 1999 22:55:18 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: chat@freebsd.org Subject: Re: Use of "register" in code X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14063.12923.464399.183283@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I doubt it would make performance worse. I think GCC basically just > > ignores it for IA32. > It does ignore it. This is categorically wrong. GCC does not ignore "register" declarations. It honors the ANSI standard C semantics for register-qualified types in at least some circumstances, even without supplying -ansi or -pedantic options. I just tried it. > ... the compiler knows more > about temporaries and other usage than the programmer. Most of the time > (but not all of the time), that is true. This is certainly correct, but is beside the point, which illustrates the danger of the "register" keyword: Even experienced expert users who have not specialized in compilers or language semantics are decieved by the fact that the semantics of "register" in the ANSI dialect bear only a passing relationship to the ordinary technical use of the English word. I would like to make several points which this discussion has obscured to date: Firstly, removing "register" declarations from a program can cause correct code to become incorrect code. This is true, not only of ANSI C, but of the GNU C 2 series compilers, as well as other significant current compilers, such as Microsoft and SunPro. Secondly, producing such code is not easy, and it is very unlikely that any given use of the keyword in the source base will meet the necessary conditions to demonstrate this fact. Thirdly, most instances of the keyword are not intentionally being used to produce ANSI semantics. Instead, the author's intention was to effect the manual optimization of K & R's "register" keyword. It is this intention which is justifiably belittled by the majority of commentators in this thread. Finally, David O'Brien's quote from ANSI X3.159-1989 proves that Andrew O'Rielly's characterization of the meaning of "register" is fair and justified. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 21:31:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0AC45150B8; Tue, 16 Mar 1999 21:31:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA12122; Tue, 16 Mar 1999 21:30:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Andrzej Bialecki Cc: Ruslan Ermilov , sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-reply-to: Your message of "Mon, 15 Mar 1999 17:00:32 +0100." Date: Tue, 16 Mar 1999 21:30:59 -0800 Message-ID: <12120.921648659@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is ERRATA.TXT correct? > > Probably not. Don't speculate like this - tell me exactly what's wrong with it instead. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 21:31:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BD55D15126 for ; Tue, 16 Mar 1999 21:31:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA12111; Tue, 16 Mar 1999 21:30:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Ruslan Ermilov Cc: Sheldon Hearn , FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-reply-to: Your message of "Mon, 15 Mar 1999 12:25:08 +0200." <19990315122508.A9370@relay.ucb.crimea.ua> Date: Tue, 16 Mar 1999 21:30:40 -0800 Message-ID: <12109.921648640@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to your ERRATA entry, these changes are saved to /kernel.config. No, according to the errata 3.1 *erroneously* put its values there. This was identified as a bug in that same errata entry. The kget function in sysinstall is what writes the file out. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 21:37:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 30E8815005 for ; Tue, 16 Mar 1999 21:37:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA12178; Tue, 16 Mar 1999 21:37:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-reply-to: Your message of "Sun, 14 Mar 1999 18:21:38 +0200." <35437.921428498@axl.noc.iafrica.com> Date: Tue, 16 Mar 1999 21:37:56 -0800 Message-ID: <12176.921649076@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Cost: > Annoy the people who have large memory configurations and who > don't build custom kernels. Too high. The fact that we got royally screwed in a magazine comparison test is what *made* David add the >64MB check in the first place. People with broken server-class hardware like this should fix it, not band-aid it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 21:40:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D422A14EC0 for ; Tue, 16 Mar 1999 21:40:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA12198; Tue, 16 Mar 1999 21:40:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Mark J. Taylor" Cc: Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-reply-to: Your message of "Sun, 14 Mar 1999 13:19:05 EST." Date: Tue, 16 Mar 1999 21:40:34 -0800 Message-ID: <12196.921649234@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For our NetMAX product (shameless plug: http://www.netmax.com/), > which is 2.2.7+ based (we're working on a 3.1 version), we've > added two additional boot options: > 1) -M always perform speculative memory probe > 2) -m never perform speculative memory probe Now there's an idea, though I'd go a little further: Why not add a new variable to the 3-stage loader so you could simply say: boot> set maxmem=64M boot> load /kernel boot> boot (etc) To set the memory size to some exact value (which you might know better than the probe). This strikes me as far more general and easy to understand as well. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 22:12:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 083F214C94 for ; Tue, 16 Mar 1999 22:12:22 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id HAA25561; Wed, 17 Mar 1999 07:12:03 +0100 (CET) (envelope-from des) To: Dag-Erling Smorgrav Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: evil maxusers References: <199903160216.VAA24377@cs.rpi.edu> From: Dag-Erling Smorgrav Date: 17 Mar 1999 07:12:02 +0100 In-Reply-To: Dag-Erling Smorgrav's message of "17 Mar 1999 03:20:15 +0100" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Because mbufs eat memory, and the kernel has a limited address space. > If I'm not mistaken, setting maxusers to 320 eats up to 90 MB in mbuf > clusters alone, which is almost half the kernel address space. Foo, I made a braino. Mbuf clusters are 16 mbufs long, not 16 kB (or rather, they're 2048 bytes long which happens to be 16 times the size of a regular mbuf) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 22:20:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id ACE9F15038 for ; Tue, 16 Mar 1999 22:20:31 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id BAA29977; Wed, 17 Mar 1999 01:20:05 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA12891; Wed, 17 Mar 1999 01:20:04 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id BAA54317; Wed, 17 Mar 1999 01:20:03 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199903170620.BAA54317@bb01f39.unx.sas.com> Subject: Re: fxp driver causing lockup In-Reply-To: From Wes Peters at "Mar 16, 1999 7:39:43 am" To: wes@softweyr.com (Wes Peters), freebsd-hackers@freebsd.org Date: Wed, 17 Mar 1999 01:20:03 -0500 (EST) Cc: sascht@unx.sas.com (Charles Tudor) 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 Hi, I beleive you are correct. The following code fragment from if_fxp.c is the lockup: /* * Start the config command/DMA. */ fxp_scb_wait(sc); CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); /* ...and wait for it to complete. */ while (!(cbp->cb_status & FXP_CB_STATUS_C)); according to doc at Dell's website (they have a machine with this problem), the bios is not enabling dma on the adapter board. I beleive the person I copied on this mail can provide the precise web page that documents this. According to them, it is possible to discreetly turn on dma on the adapter. This is were someone with the appropriate doc needs to jump in... Basically, the driver needs to check that dma is enabled and enable it if not. Just my 0.02 cents, John > Andy Doran wrote: > > > > Hi all, > > I've got weird problem with an Intel Etherexpress Pro 100. The cards work > > fine, in fact great, with most of my FreeBSD boxes, all of which run > > the 3.x branch updated weekly over cvsup. > > > > The trouble is, when I do an 'ifconfig fxp0 $some_address' on one > > particular machine (a Tulip P-II, real junk) the machine locks up. The > > keyboard still works (i.e. can toggle numlock light), and trying to switch > > to another VT causes the machine to generate a never ending beep. I guess > > it's getting stuck at spl???() somewhere. > > > > Setting the media type works, and the card works fine on other > > machines. I've tried changing the slot, and using a generic 3.x kernel > > too, but no luck. A 2.2.6 kernel works fine, no lockups. This card shares > > an IRQ with a 3c905 and a S3 ViRGE/GX2. > > > > Unfortunately I can't hack at this because it's a production box, and has > > to be up 24/7 almost always. Any ideas? > > I've seen the same problem on a Toshiba Equuium with on-board Pro 100+. > The failure happens when the first DMA in the attach routine never > completes. I'll be looking into it this week; I finally have some time > to debug this problem and two other network cards for when it the machine > has to work. > > I've saved a couple of recent messages about BIOS not initializing PCI > cards; I'm wondering if that might be the cause of the problem. This > machine worked fine with 2.2.x, so I'll be looking at what changed > between 2.2.7 and 3.0/3.1. > > - -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://www.softweyr.com/~softweyr wes@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 Tue Mar 16 22:40:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.38]) by hub.freebsd.org (Postfix) with ESMTP id 544F315038 for ; Tue, 16 Mar 1999 22:40:14 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id AAA56674; Wed, 17 Mar 1999 00:38:47 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 17 Mar 1999 00:38:46 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: hackers@freebsd.org Subject: imgact_interp X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14063.19540.330930.620154@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote a kld module to invoke java on class files. I'd like to generalize it before send-pr'ing it. However, I'm new at this sort of thing, and don't know how to best send registrations to the module. To allow an interpreter I to interpret files matching N bytes of magic M, I would like to send the module , but since M may contain nuls, I can't really use sysctls (the hammer I know), unless I were to escape the nuls somehow, which seems grotty. I could add a well-known secondary magic file, or a syntactic extension to /etc/magic, but those seems kludgy as well. How should this properly be done? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 23:18:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 335571510B for ; Tue, 16 Mar 1999 23:18:16 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id AAA16526; Wed, 17 Mar 1999 00:18:34 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EF5749.2B1A8D21@softweyr.com> Date: Wed, 17 Mar 1999 00:18:33 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "John W. DeBoskey" Cc: freebsd-hackers@freebsd.org, Charles Tudor Subject: Re: fxp driver causing lockup References: <199903170620.BAA54317@bb01f39.unx.sas.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John W. DeBoskey" wrote: > > Hi, > > I beleive you are correct. The following code fragment from > if_fxp.c is the lockup: > > /* > * Start the config command/DMA. > */ > fxp_scb_wait(sc); > CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); > /* ...and wait for it to complete. */ > while (!(cbp->cb_status & FXP_CB_STATUS_C)); Yup, that's it. I initially tracked this down under 3.0, but moved the machine back to 2.2.7 because I needed it to get work done. I've now stuffed two 3c905Bs into it for my main and test network, and can play with the Pro 100B without losing a network connection. > according to doc at Dell's website (they have a machine with this > problem), the bios is not enabling dma on the adapter board. I beleive > the person I copied on this mail can provide the precise web page > that documents this. > > According to them, it is possible to discreetly turn on dma on > the adapter. This is were someone with the appropriate doc needs > to jump in... > > Basically, the driver needs to check that dma is enabled and > enable it if not. Any hints as to how to do that? I've got the machine, the lockups, and a (little) bit of driver knowlege. Plus a fair bit of tenacity. The Linux 2.2 driver exhibits the same problem on these machines, so I can either share the fix with them or just convince them to upgrade to FreeBSD once I get this nailed. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 23:49: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B3CC14D33; Tue, 16 Mar 1999 23:48:24 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id JAA91975; Wed, 17 Mar 1999 09:45:30 +0200 (EET) (envelope-from ru) Date: Wed, 17 Mar 1999 09:45:30 +0200 From: Ruslan Ermilov To: Dag-Erling Smorgrav Cc: dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall Message-ID: <19990317094530.A91937@relay.ucb.crimea.ua> Mail-Followup-To: Dag-Erling Smorgrav , dg@FreeBSD.ORG, hackers@FreeBSD.ORG References: <19990313200150.A83040@relay.ucb.crimea.ua> <199903131819.TAA29395@rt2.synx.com> <19990314162419.A10242@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Dag-Erling Smorgrav on Wed, Mar 17, 1999 at 02:37:09AM +0100 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 17, 1999 at 02:37:09AM +0100, Dag-Erling Smorgrav wrote: > Ruslan Ermilov writes: > > On Sat, Mar 13, 1999 at 07:11:19PM +0100, Remy Nonnenmacher wrote: > > > On 13 Mar, Ruslan Ermilov wrote: > > > > It seems that such "fast forwardable" packets, when passed from > > > > ether_input(), for example, just simply bypass all firewall checks. > > > > Am I right? > > > you are. > > It's a big security leak... > > David, was it supposed by design (that such packets bypass firewall)? > > The whole point with fast forwarding is shortening the data path. This > includes not running packets through the firewall. This is precisely > why it's an option, and is not on by default. After all, if it had no > disadvantages or side effects, there'd be no reason *not* to use it, > right? > Agreed. One thing I thought of. Why it is not documented anywhere? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 23:56: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from helen.CS.Berkeley.EDU (helen.CS.Berkeley.EDU [128.32.131.251]) by hub.freebsd.org (Postfix) with ESMTP id 13D7515255 for ; Tue, 16 Mar 1999 23:56:06 -0800 (PST) (envelope-from jmacd@helen.CS.Berkeley.EDU) Received: (from jmacd@localhost) by helen.CS.Berkeley.EDU (8.9.1a/8.9.1) id XAA06558; Tue, 16 Mar 1999 23:55:47 -0800 (PST) Message-ID: <19990316235547.14559@helen.CS.Berkeley.EDU> Date: Tue, 16 Mar 1999 23:55:47 -0800 From: Josh MacDonald To: freebsd-hackers@freebsd.org Subject: SCSI Tape (HP SureStore T20) trouble Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I reported trouble with this tape drive under 3.0-RELEASE a while ago and was told to try 3.1, so I did. Now I am using 3.1-STABLE as of today. I'm still having trouble, but different trouble. The HP SureStore T20 uses a QIC-3220 format (Travan TR-5) minicartridge (10G uncompressed capacity). The manual says it has a sustained data transfer rate of 1M/s and a burst rate of 3M/s. sa0 at ncr0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers And I can run dump, and the mt commands. 'mt status' reports: Mode Density Blocksize bpi Compression Current: 0x47 512 bytes 0 unsupported ---------available modes--------- 0: 0x47 512 bytes 0 unsupported 1: 0x47 512 bytes 0 unsupported 2: 0x47 512 bytes 0 unsupported 3: 0x47 512 bytes 0 unsupported --------------------------------- Current Driver State: at rest. I ran dump to see if it really works, and dump reports no errors, but there are console messages. DUMP: Date of this level 0 dump: Tue Mar 16 23:42:42 1999 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rda0s2a (/) to /dev/nrsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 26417 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 26407 tape blocks on 1 volumes(s) DUMP: finished in 58 seconds, throughput 455 KBytes/sec DUMP: level 0 dump on Tue Mar 16 23:42:42 1999 DUMP: Closing /dev/nrsa0 DUMP: DUMP IS DONE The console reads: (sa0:ncr0:0:5:0): SPACE. CDB: 11 1 ff ff ff 0 (sa0:ncr0:0:5:0): ILLEGAL REQUEST asc:2c,0 (sa0:ncr0:0:5:0): Command sequence error (sa0:ncr0:0:5:0): unable to backspace over one of double filemarks at EOD- opting for safety and it rewinds the tape even though I opened the nrsa0 device (which supposedly does NOT rewind). I am able to restore from the dump, but it seems broken that it does not rewind. Also, the drive says it supports hardware compression, but 'mt status' says it is unsupported. Does anyone know whats the trouble with either of these problems? -josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 16 23:59:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C137F1520E; Tue, 16 Mar 1999 23:59:12 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id IAA28144; Wed, 17 Mar 1999 08:58:10 +0100 (CET) (envelope-from des) To: Ruslan Ermilov Cc: Dag-Erling Smorgrav , dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall References: <19990313200150.A83040@relay.ucb.crimea.ua> <199903131819.TAA29395@rt2.synx.com> <19990314162419.A10242@relay.ucb.crimea.ua> <19990317094530.A91937@relay.ucb.crimea.ua> From: Dag-Erling Smorgrav Date: 17 Mar 1999 08:58:09 +0100 In-Reply-To: Ruslan Ermilov's message of "Wed, 17 Mar 1999 09:45:30 +0200" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov writes: > Why it is not documented anywhere? Why isn't most of FreeBSD documented anywhere? or How much are you willing to pay someone to do the work? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 0: 2:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id F2B0F14C88; Wed, 17 Mar 1999 00:01:50 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id JAA96201; Wed, 17 Mar 1999 09:59:40 +0200 (EET) (envelope-from ru) Date: Wed, 17 Mar 1999 09:59:40 +0200 From: Ruslan Ermilov To: "Jordan K. Hubbard" Cc: Andrzej Bialecki , sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings Message-ID: <19990317095940.B91937@relay.ucb.crimea.ua> Mail-Followup-To: "Jordan K. Hubbard" , Andrzej Bialecki , sheldonh@FreeBSD.ORG, FreeBSD Hackers References: <12120.921648659@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <12120.921648659@zippy.cdrom.com>; from Jordan K. Hubbard on Tue, Mar 16, 1999 at 09:30:59PM -0800 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 16, 1999 at 09:30:59PM -0800, Jordan K. Hubbard wrote: > > > Is ERRATA.TXT correct? > > > > Probably not. > > Don't speculate like this - tell me exactly what's wrong with it instead. > Like you said, the kget function only available in sysinstall. Exactly: there is no way to save kernel changes after installation. I mean, you reboot your system, make some changes in UserConfig, and then... how do you save these changes? The only way I see is to MFC `kget' into RELENG_3, and make entries for it in /etc/rc. Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 0:13:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 2B0881530E; Wed, 17 Mar 1999 00:12:25 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id KAA99153; Wed, 17 Mar 1999 10:11:25 +0200 (EET) (envelope-from ru) Date: Wed, 17 Mar 1999 10:11:25 +0200 From: Ruslan Ermilov To: Dag-Erling Smorgrav Cc: dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall Message-ID: <19990317101125.C91937@relay.ucb.crimea.ua> Mail-Followup-To: Dag-Erling Smorgrav , dg@FreeBSD.ORG, hackers@FreeBSD.ORG References: <19990313200150.A83040@relay.ucb.crimea.ua> <199903131819.TAA29395@rt2.synx.com> <19990314162419.A10242@relay.ucb.crimea.ua> <19990317094530.A91937@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Dag-Erling Smorgrav on Wed, Mar 17, 1999 at 08:58:09AM +0100 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 17, 1999 at 08:58:09AM +0100, Dag-Erling Smorgrav wrote: > Ruslan Ermilov writes: > > Why it is not documented anywhere? > > Why isn't most of FreeBSD documented anywhere? > > or > > How much are you willing to pay someone to do the work? > Well, OK. Could you, _please_, document it in the inet.4 manpage, section ``MIB VARIABLES'', or ask dg@freebsd.org to do it? Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 0:20:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7EA4815335; Wed, 17 Mar 1999 00:20:44 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id JAA28666; Wed, 17 Mar 1999 09:17:52 +0100 (CET) (envelope-from des) To: Ruslan Ermilov Cc: Dag-Erling Smorgrav , dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall References: <19990313200150.A83040@relay.ucb.crimea.ua> <199903131819.TAA29395@rt2.synx.com> <19990314162419.A10242@relay.ucb.crimea.ua> <19990317094530.A91937@relay.ucb.crimea.ua> <19990317101125.C91937@relay.ucb.crimea.ua> From: Dag-Erling Smorgrav Date: 17 Mar 1999 09:17:51 +0100 In-Reply-To: Ruslan Ermilov's message of "Wed, 17 Mar 1999 10:11:25 +0200" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov writes: > On Wed, Mar 17, 1999 at 08:58:09AM +0100, Dag-Erling Smorgrav wrote: > > Ruslan Ermilov writes: > > > Why it is not documented anywhere? > > Why isn't most of FreeBSD documented anywhere? > > or > > How much are you willing to pay someone to do the work? > Well, OK. > Could you, _please_, document it in the inet.4 manpage, > section ``MIB VARIABLES'', or ask dg@freebsd.org to do it? You missed my point. You asked why it wasn't documented, and my questions were intended to make you understand why. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 0:46:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id F25A415204; Wed, 17 Mar 1999 00:44:07 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id KAA07590; Wed, 17 Mar 1999 10:41:57 +0200 (EET) (envelope-from ru) Date: Wed, 17 Mar 1999 10:41:57 +0200 From: Ruslan Ermilov To: Dag-Erling Smorgrav Cc: dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall Message-ID: <19990317104157.A4028@relay.ucb.crimea.ua> Mail-Followup-To: Dag-Erling Smorgrav , dg@FreeBSD.ORG, hackers@FreeBSD.ORG References: <19990313200150.A83040@relay.ucb.crimea.ua> <199903131819.TAA29395@rt2.synx.com> <19990314162419.A10242@relay.ucb.crimea.ua> <19990317094530.A91937@relay.ucb.crimea.ua> <19990317101125.C91937@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Dag-Erling Smorgrav on Wed, Mar 17, 1999 at 09:17:51AM +0100 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 17, 1999 at 09:17:51AM +0100, Dag-Erling Smorgrav wrote: > Ruslan Ermilov writes: > > On Wed, Mar 17, 1999 at 08:58:09AM +0100, Dag-Erling Smorgrav wrote: > > > Ruslan Ermilov writes: > > > > Why it is not documented anywhere? > > > Why isn't most of FreeBSD documented anywhere? > > > or > > > How much are you willing to pay someone to do the work? > > Well, OK. > > Could you, _please_, document it in the inet.4 manpage, > > section ``MIB VARIABLES'', or ask dg@freebsd.org to do it? > > You missed my point. You asked why it wasn't documented, and my > questions were intended to make you understand why. > So, do you mean you won't document anything you won't be paid for? This is probably Microsoft's way, not FreeBSD's. I work with FreeBSD for 3+ years, and contribute to it for free... I just complained why David didn't document this feature when it was committed. Unfortunately, there was no response from him. Probably, he's very busy now. So, I ask _you_ to document this feature for others... not for me. I already understand how it does work. When someone introduces a new feature, how others will know about it? Without documenting it, the only way for them is to read the commitlogs or wait until someone tells them about this feature. Later, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 1:13:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from send101.yahoomail.com (send101.yahoomail.com [205.180.60.87]) by hub.freebsd.org (Postfix) with SMTP id 8A054150A3 for ; Wed, 17 Mar 1999 01:13:27 -0800 (PST) (envelope-from thallgren@yahoo.com) Message-ID: <19990317091302.28660.rocketmail@send101.yahoomail.com> Received: from [131.116.188.217] by send101.yahoomail.com; Wed, 17 Mar 1999 01:13:02 PST Date: Wed, 17 Mar 1999 01:13:02 -0800 (PST) From: Tommy Hallgren Subject: VMWare on FreeBSD (Fwd: Re: Question about host OS) To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-2089018456-921661982=:10079" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-2089018456-921661982=:10079 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline note: forwarded msg attached. I suggest that you mail sales@vmware.com and ask them about a FreeBSD version, if you'are prepared to buy one. == Regards, Tommy Hallgren Briljantg. 31, SE-421 49, Göteborg Tel.: 031 - 770 5232 (Work: Telia Prosoft) Tel.: 0709 - 312 404 (GSM) Tel.: 031 - 47 65 28 (Home) _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com --0-2089018456-921661982=:10079 Content-Type: message/rfc822 X-Apparently-To: thallgren@yahoo.com via mdd103.yahoomail.com Received: from unknown (HELO geneva.vmware.com) (209.220.69.160) by mta109.yahoomail.com with SMTP; 16 Mar 1999 13:05:26 -0800 Received: from admin (palo-alto.vmware.com [209.220.69.218]) by geneva.vmware.com (8.8.7/8.8.5) with SMTP id NAA16592; Tue, 16 Mar 1999 13:03:40 -0800 Message-ID: <01f501be6ff1$49696d00$da45dcd1@admin.vmware.com> From: "VJ Richey" To: "Tommy Hallgren" , Subject: Re: Question about host OS Date: Tue, 16 Mar 1999 13:09:31 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Content-Length: 983 Dear Tommy, Thank you for your interest in VMware. We currently do not have plans for FreeBSD support as a host operating system. It should run fine as a Guest Operating System within a Virtual Platform Environment. I have however noted your inquiry as a request for support as a Host Operating System. Sincerely, V.J. Richey -----Original Message----- From: Tommy Hallgren To: sales@vmware.com Date: Tuesday, March 16, 1999 5:04 AM Subject: Question about host OS >Hi! > >I'm wondering if/when a FreeBSD version of the host-OS version will be >available. > >(see www.freebsd.org for more info about FreeBSD) > >Regards, > > > > >== >Regards, Tommy Hallgren >Briljantg. 31, SE-421 49, Göteborg >Tel.: 031 - 770 5232 (Work: Telia Prosoft) >Tel.: 0709 - 312 404 (GSM) >Tel.: 031 - 47 65 28 (Home) > > >_________________________________________________________ >DO YOU YAHOO!? >Get your free @yahoo.com address at http://mail.yahoo.com --0-2089018456-921661982=:10079-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 2:34:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 3789214E5D for ; Wed, 17 Mar 1999 02:34:20 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id KAA77522; Wed, 17 Mar 1999 10:33:53 GMT (envelope-from joe) Date: Wed, 17 Mar 1999 10:33:53 +0000 From: Josef Karthauser To: sales@vmware.com Subject: Re: VMWare on FreeBSD (Fwd: Re: Question about host OS) Message-ID: <19990317103352.C62508@pavilion.net> References: <19990317091302.28660.rocketmail@send101.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990317091302.28660.rocketmail@send101.yahoomail.com>; from Tommy Hallgren on Wed, Mar 17, 1999 at 01:13:02AM -0800 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, We're very interested in your VMware platform and eagerly await it's full release. Unfortunately you don't appear to support our platform as a host operating system. We're a large FreeBSD house in the UK and are very interested in running your product in this host environment. Please can you provide us with a time scale for supporting this platform. If you require any technical help with this please let us know. As you're probably aware FreeBSD has a very strong development team, and though we've not got as much PR in the field as the Linux camps we do have a very strong user-ship among professionals. You may wish to check out http://www.uk.freebsd.org/commercial/ to verify this. I greatly look forward to your response, and your support of FreeBSD. Regards, Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 3:57: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 088A6153D5; Wed, 17 Mar 1999 03:55:58 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA96186; Wed, 17 Mar 1999 03:53:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Ruslan Ermilov Cc: Andrzej Bialecki , sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-reply-to: Your message of "Wed, 17 Mar 1999 09:59:40 +0200." <19990317095940.B91937@relay.ucb.crimea.ua> Date: Wed, 17 Mar 1999 03:53:00 -0800 Message-ID: <96184.921671580@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm talking about ERRATA.TXT here. > On Tue, Mar 16, 1999 at 09:30:59PM -0800, Jordan K. Hubbard wrote: > > > > Is ERRATA.TXT correct? > > > > > > Probably not. > > > > Don't speculate like this - tell me exactly what's wrong with it instead. > > > > Like you said, the kget function only available in sysinstall. > Exactly: there is no way to save kernel changes after installation. > I mean, you reboot your system, make some changes in UserConfig, > and then... how do you save these changes? > > The only way I see is to MFC `kget' into RELENG_3, and make > entries for it in /etc/rc. > > > Cheers, > -- > Ruslan Ermilov Sysadmin and DBA of the > ru@ucb.crimea.ua United Commercial Bank > +380.652.247.647 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 4:28:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (Postfix) with ESMTP id 1562114F16 for ; Wed, 17 Mar 1999 04:28:19 -0800 (PST) (envelope-from brandon@ice.cold.org) Received: (from brandon@localhost) by ice.cold.org (8.8.8/8.8.5) id FAA01292 for freebsd-hackers@freeBSD.org; Wed, 17 Mar 1999 05:28:00 -0700 (MST) Date: Wed, 17 Mar 1999 05:28:00 -0700 From: Brandon Gillespie To: freebsd-hackers@freeBSD.org Subject: global Makefile(s) BINDIR inconsistency with DESTDIR Message-ID: <19990317052800.A1102@ice.cold.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary=9amGYk9869ThD9tj; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 2.2.8-RELEASE X-PGP-Public-Key: http://www.roguetrader.com/~brandon/brandon@roguetrader_com.pubkey Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Forgive me if this is incorrect, but there appears to be a major inconsistency in the use of ${BINDIR} througout the heirarchy, in regard to ${DESTDIR} and installation. I am not fully certain what the role of BINDIR is, but it appears people are also using it as a destination install directory--without at least prefixing ${DESTDIR}. I am trying to build a 4.0/CURRENT tree and install it onto a jaz drive (or really any alternate drive)--so I can boot it without effecting the stability of the primary OS due to my changes. I am building it ala: make buildworld && make DESTDIR=/jaz installworld Everything is fine, except for not everything pays attention to DESTDIR. The problem is that BINDIR is not defined using DESTDIR, which is OK, but then in some cases people use it as if it should. If you doubt, cd to your source directory and type: fgrep BINDIR */*/Makefile This probably would not have been a problem, but i am low on space on my root partition, and when one of the things (dhclient) was installing into /sbin instead of ${DESTDIR}/sbin, it filled up /. Suggested fix? I suppose we (I?) can scan the source for all offending usages, which I am willing to do if this is really a problem. My suggestion would be to make a DESTBIN which is simply defined at the same time as BINDIR, as ${DESTDIR}${BINDIR}. If it is a prob, I can submit a bug report. -Brandon Gillespie --9amGYk9869ThD9tj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: a61IgqP/JDdU0jmFq9aoYd/zYsBk6Zot iQA/AwUBNu+fz0v5XoQiMgn6EQLH8gCgzDuGwgThxdwYAFxkm3bdigSegWMAn2FL V8ZE2vxIhJYUHxPnwCfb3tP1 =dOBs -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 4:31:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7A8AA1541C for ; Wed, 17 Mar 1999 04:31:46 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id EAA17781; Wed, 17 Mar 1999 04:31:03 -0800 Date: Wed, 17 Mar 1999 04:31:02 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Josh MacDonald Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI Tape (HP SureStore T20) trouble In-Reply-To: <19990316235547.14559@helen.CS.Berkeley.EDU> 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 > > (sa0:ncr0:0:5:0): SPACE. CDB: 11 1 ff ff ff 0 > (sa0:ncr0:0:5:0): ILLEGAL REQUEST asc:2c,0 > (sa0:ncr0:0:5:0): Command sequence error > (sa0:ncr0:0:5:0): unable to backspace over one of double filemarks at EOD- opting for safety > > and it rewinds the tape even though I opened the nrsa0 device (which > supposedly does NOT rewind). I am able to restore from the dump, but > it seems broken that it does not rewind. Also, the drive says it supports (I'm sure you mean "It is broken that it rewinds") > hardware compression, but 'mt status' says it is unsupported. Does > anyone know whats the trouble with either of these problems? There are actually three problems here: Problem #1: The driver apparently has a problem backspacing over a filemark. This indicates to me that this should be treated as if it were a QIC drive that only has one filemark at EOD. Frankly, I would have loved to enforce only one filemark at EOD for all except 1/2" reel drives, but folks shot that down months ago. Fix: Quirk the drive to have the SA_QUIRK_1FM. Problem #2: When this failed, the driver tried to eject the tape. Well, that doesn't work for a lot of drives. This has been discussed on this list quite a bit recently. Fix: I proposed a change that will not have the drive rewind, but will disallow further writes until either a rewind, eject, or a space to EOD is performed. This fix is in progress. If I didn't have a 100 degree fever, it'd probably be done some time in the next day or so. Problem #3: Compression is being reported as the driver tried to use some 'standard' means to enable compression. Unfortunately, the method chosen is for a mode page that's in SCSI-3, not for SCSI-2. Fix: use the Device Configuration page first and then try the Date Compression page). However, this may not always guarantee compression if compression is enabled via some drive specific mechanism, e.g. a density code. A manual for this device may have this information. Passing that information back to someone to fold into the driver will be appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 4:33:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 345DE1524F for ; Wed, 17 Mar 1999 04:33:12 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id EAA17786; Wed, 17 Mar 1999 04:32:48 -0800 Date: Wed, 17 Mar 1999 04:32:47 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Josh MacDonald Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI Tape (HP SureStore T20) trouble - More- In-Reply-To: <19990316235547.14559@helen.CS.Berkeley.EDU> 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 Oh- btw- what does the manual say about this miniqic in terms of what the supported fixed record sizes are? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 8:18: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (Postfix) with ESMTP id 63EFE14BF3 for ; Wed, 17 Mar 1999 08:17:58 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id IAA19582; Wed, 17 Mar 1999 08:50:33 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id IAA05575; Wed, 17 Mar 1999 08:50:02 -0600 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id IAA20156; Wed, 17 Mar 1999 08:50:01 -0600 (CST) Date: Wed, 17 Mar 1999 08:50:01 -0600 (CST) From: Jonathan Lemon Message-Id: <199903171450.IAA20156@free.pcs> To: tony@dell.com, freebsd-hackers@freebsd.org Subject: Re: Proposal: Define MAXMEM in GENERIC X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >At 01:20 PM 3/14/99 -0600, Jonathan Lemon wrote: >>>p.s. FreeBSD seems to prefer E801h over E820h. I'd like to see it >>> the other way around, since you could gain almost 64 KB of >>> extra memory in some cases. >> >>Not true, if you're referring to the VM86 memory probe. It tries >>INT 15h, AX=E820, then INT 15h, AX=E801, then INT 15h, AX=88, in >>that order. > >Sorry about that. I have all three of the BIOS functions in my >box, but I still see this: > >BIOS basemem: 639K, extmem: 64512K (from 0xe801 call) > >so I made an assumption. I did say it *seems* to prefer E801h. Actually, it appears that you are right, the E820 call was broken by an earlier commit (circa September), and hasn't worked since. I just sync-ed up to current yesterday and found this out. Once this is fixed, I think that the VM86 code should become mandatory, and the entire "speculative memory probe" should just disappear. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 8:43:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 88D3815116 for ; Wed, 17 Mar 1999 08:43:14 -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.8.8/8.8.8) with SMTP id JAA04218; Wed, 17 Mar 1999 09:41:23 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA10150; Wed, 17 Mar 1999 09:41:09 -0700 Date: Wed, 17 Mar 1999 09:41:09 -0700 Message-Id: <199903171641.JAA10150@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: "Mark J. Taylor" , Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-Reply-To: <12196.921649234@zippy.cdrom.com> References: <12196.921649234@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > For our NetMAX product (shameless plug: http://www.netmax.com/), > > which is 2.2.7+ based (we're working on a 3.1 version), we've > > added two additional boot options: > > 1) -M always perform speculative memory probe > > 2) -m never perform speculative memory probe > > Now there's an idea, though I'd go a little further: Why not add a new > variable to the 3-stage loader so you could simply say: > > boot> set maxmem=64M > boot> load /kernel > boot> boot > (etc) > > To set the memory size to some exact value (which you might know > better than the probe). This strikes me as far more general and easy > to understand as well. I would think a Forth hacker could do this, given that the flags to the npx device can be used to specify the amount of memory in the system. (Although, I could find it documented anywhere obvious when I went looking for it in the man pages.) /sys/i386/isa/npx.c: revision 1.32 date: 1996/11/11 20:39:03; author: bde; state: Exp; lines: +47 -13 ... Added a boot-time way to set the memory size (iosiz in config, iosize in userconfig for npx0). ... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 8:58: 4 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 5B6F314C29 for ; Wed, 17 Mar 1999 08:57:56 -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 2.12 #1) id 10NJcx-000Jzc-00; Wed, 17 Mar 1999 18:57:07 +0200 From: Sheldon Hearn To: Brandon Gillespie Cc: freebsd-hackers@freeBSD.org Subject: Re: global Makefile(s) BINDIR inconsistency with DESTDIR In-reply-to: Your message of "Wed, 17 Mar 1999 05:28:00 MST." <19990317052800.A1102@ice.cold.org> Date: Wed, 17 Mar 1999 18:57:06 +0200 Message-ID: <76855.921689826@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999 05:28:00 MST, Brandon Gillespie wrote: > If it is a prob, I can submit a bug report. It is a problem. 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 Mar 17 9:46:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 0535215515 for ; Wed, 17 Mar 1999 09:45:23 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id DDBF018C7; Wed, 17 Mar 1999 18:45:20 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id D73C94988; Wed, 17 Mar 1999 18:45:20 +0100 (CET) Date: Wed, 17 Mar 1999 18:45:19 +0100 (CET) From: Andrzej Bialecki To: "Jordan K. Hubbard" Cc: "Mark J. Taylor" , Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-Reply-To: <12196.921649234@zippy.cdrom.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 Tue, 16 Mar 1999, Jordan K. Hubbard wrote: > > For our NetMAX product (shameless plug: http://www.netmax.com/), > > which is 2.2.7+ based (we're working on a 3.1 version), we've > > added two additional boot options: > > 1) -M always perform speculative memory probe > > 2) -m never perform speculative memory probe > > Now there's an idea, though I'd go a little further: Why not add a new > variable to the 3-stage loader so you could simply say: > > boot> set maxmem=64M > boot> load /kernel > boot> boot > (etc) Ehm... That's exactly what I suggested. See Mike's reply earlier in this thread. 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 Wed Mar 17 10:10:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bozeman.pwrh.com (bozeman.vlt.com [199.201.184.209]) by hub.freebsd.org (Postfix) with ESMTP id 591E815339 for ; Wed, 17 Mar 1999 10:10:14 -0800 (PST) (envelope-from ptacek@pwrh.com) Received: from pwrh.com (ptacek.pwrh.com [172.22.2.77]) by bozeman.pwrh.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id FFBLRHG0; Wed, 17 Mar 1999 11:14:18 -0700 Message-ID: <36EFEFF3.FA2CB789@pwrh.com> Date: Wed, 17 Mar 1999 11:09:55 -0700 From: ptacek Organization: Powerhouse Tech X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: KLD compile links? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have recently converted an existing LKM that we had to a KLD format. It seems to up and running now, however if I try and compile in a different directory it fails. The directory I did my development in was: /usr/src/sys/modules/vlc However previously we used /usr/src/lkm/vlc as our directory and I would like to continue to use that directory ( for now at least ) to keep the install instructions similar. I believe that a link created in the compile directory ( @ ) is being set incorrectly. In the directories that work it points to /usr/src/sys and in the directories where it doesn't work it is pointing to /usr/src. How is this link set, and why would it be different in different directories. If I manually include the /usr/src/sys directory with a -I/usr/src/sys it works fine, so I am pretty sure this is my problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 10:21:13 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 D4A9C14C84 for ; Wed, 17 Mar 1999 10:21:09 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA28396; Thu, 18 Mar 1999 03:20:46 +0900 (JST) Message-ID: <36EFEA9E.ED8DFF5@newsguy.com> Date: Thu, 18 Mar 1999 02:47:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC References: <12176.921649076@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > Cost: > > Annoy the people who have large memory configurations and who > > don't build custom kernels. > > Too high. The fact that we got royally screwed in a magazine > comparison test is what *made* David add the >64MB check in the first > place. People with broken server-class hardware like this should fix > it, not band-aid it. Hear! Hear! It's not the people with *working* hardware that should get the short end! -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 10:21:15 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 4CB05152B7 for ; Wed, 17 Mar 1999 10:21:12 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA28361; Thu, 18 Mar 1999 03:20:33 +0900 (JST) Message-ID: <36EFE66D.5654E3F2@newsguy.com> Date: Thu, 18 Mar 1999 02:29:17 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "David E. Cross" Cc: Robert Nordier , Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable References: <199903170351.WAA19489@cs.rpi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The old loader is backed to /boot/loader.old, if you use normal installation procedure. So, interrupt the second stage, and boot the old loader (or the kernel directly, actually). I'm not entirely sure, but 4.0 loader might be depending on /sys/sys/linker.h. "David E. Cross" wrote: > > AUGH! > > I compiled the /boot/loader from the 4.0 tree CVS-ed a couple of hours ago > (we have our own copy which periodically syncs with cvsup.freebsd.org). I > tell it to boot *any* kernel, and it just *hangs* (caps lock/scroll lock > still works, but nothing else.)... Normally a /boot/loader startup looks > something like: > /-\|kernel /-\|/... etc you get the idea. > > this one looks like: > > /-\|/ (and hangs here) > > Any ideas? > (It doesn't matter which kernel I am trying to boot relocated or not :I ) > -- > David Cross > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 10:21:16 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 CA5C914C84 for ; Wed, 17 Mar 1999 10:21:14 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA28404; Thu, 18 Mar 1999 03:20:50 +0900 (JST) Message-ID: <36EFEAE7.5028D72F@newsguy.com> Date: Thu, 18 Mar 1999 02:48:23 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: "Mark J. Taylor" , Sheldon Hearn , hackers@FreeBSD.org Subject: Re: Proposal: Define MAXMEM in GENERIC References: <12196.921649234@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > For our NetMAX product (shameless plug: http://www.netmax.com/), > > which is 2.2.7+ based (we're working on a 3.1 version), we've > > added two additional boot options: > > 1) -M always perform speculative memory probe > > 2) -m never perform speculative memory probe > > Now there's an idea, though I'd go a little further: Why not add a new > variable to the 3-stage loader so you could simply say: > > boot> set maxmem=64M > boot> load /kernel > boot> boot > (etc) > > To set the memory size to some exact value (which you might know > better than the probe). This strikes me as far more general and easy > to understand as well. The speculative memory probe flags is still a good idea. And the default should be the VM86 stuff (if it is compiled in). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 10:42:50 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 24D551556A for ; Wed, 17 Mar 1999 10:42:47 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA29453; Thu, 18 Mar 1999 03:42:44 +0900 (JST) Message-ID: <36EFF74A.F42597F4@newsguy.com> Date: Thu, 18 Mar 1999 03:41:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: hackers@freebsd.org Subject: volatile question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From aio.h: typedef struct aiocb { int aio_fildes; /* File descriptor */ off_t aio_offset; /* File offset for I/O */ volatile void *aio_buf; /* I/O buffer in process space */ ^^^^^^^^^^^^^^^^^^^^^^^ size_t aio_nbytes; /* Number of bytes for I/O */ struct sigevent aio_sigevent; /* Signal to deliver */ int aio_lio_opcode; /* LIO opcode */ int aio_reqprio; /* Request priority -- ignored */ struct __aiocb_private _aiocb_private; } aiocb_t; Is the volatile keyword in the right position? Shouldn't it be void* volatile aio_buf? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 11:23:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m1-38-dbn.dial-up.net [196.34.155.38]) by hub.freebsd.org (Postfix) with ESMTP id 9E92A14BCD for ; Wed, 17 Mar 1999 11:22:59 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA00398; Wed, 17 Mar 1999 21:19:35 +0200 (SAT) From: Robert Nordier Message-Id: <199903171919.VAA00398@ceia.nordier.com> Subject: Re: KVA size changes in 3.1-stable In-Reply-To: from Chuck Robey at "Mar 16, 99 11:01:39 pm" To: chuckr@mat.net (Chuck Robey) Date: Wed, 17 Mar 1999 21:19:33 +0200 (SAT) Cc: crossd@cs.rpi.edu, rnordier@nordier.com, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Chuck Robey wrote: > On Tue, 16 Mar 1999, David E. Cross wrote: > > > AUGH! > > > > I compiled the /boot/loader from the 4.0 tree CVS-ed a couple of hours ago > > (we have our own copy which periodically syncs with cvsup.freebsd.org). I > > tell it to boot *any* kernel, and it just *hangs* (caps lock/scroll lock > > still works, but nothing else.)... Normally a /boot/loader startup looks > > something like: > > /-\|kernel /-\|/... etc you get the idea. > > > > this one looks like: > > > > /-\|/ (and hangs here) > > How long since you last used disklabel to update your bootblocks? Old > ones will do that (they did for me, using 2.2.6 bootblocks a while > back). I'm really skeptical that the loader problems you experienced had anything directly to do with the 2.2.6 bootblocks. I have a machine here, still running 2.2.5-RELEASE, and regularly test loader on it. To double-check, I just upgraded the bootblocks to 2.2.6, and loader works fine. Because loader runs under BTX, the protected mode environment passed by the bootblocks is completely torn down, and the machine is brought back to real address mode before BTX starts. So I just can't relate to this kind of cause producing this kind of effect. To answer David's original question, I don't know of anything likely to cause loader to behave this way. I think Daniel's suggestion, made elsewhere, of trying /boot/loader.old would help in establishing whether the problem is in the new code, or whether something in the environment has changed and is causing problems. However, I'll try the latest loader, once today's make world finishes here. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 11:37: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5B7A114D3A for ; Wed, 17 Mar 1999 11:36:59 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA47616; Wed, 17 Mar 1999 14:34:32 -0500 (EST) Date: Wed, 17 Mar 1999 14:34:32 -0500 (EST) From: Chuck Robey To: Robert Nordier Cc: crossd@cs.rpi.edu, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable In-Reply-To: <199903171919.VAA00398@ceia.nordier.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, 17 Mar 1999, Robert Nordier wrote: > Chuck Robey wrote: > > > On Tue, 16 Mar 1999, David E. Cross wrote: > > > > > AUGH! > > > > > > I compiled the /boot/loader from the 4.0 tree CVS-ed a couple of hours ago > > > (we have our own copy which periodically syncs with cvsup.freebsd.org). I > > > tell it to boot *any* kernel, and it just *hangs* (caps lock/scroll lock > > > still works, but nothing else.)... Normally a /boot/loader startup looks > > > something like: > > > /-\|kernel /-\|/... etc you get the idea. > > > > > > this one looks like: > > > > > > /-\|/ (and hangs here) > > > > How long since you last used disklabel to update your bootblocks? Old > > ones will do that (they did for me, using 2.2.6 bootblocks a while > > back). > > I'm really skeptical that the loader problems you experienced had > anything directly to do with the 2.2.6 bootblocks. I have a machine > here, still running 2.2.5-RELEASE, and regularly test loader on > it. To double-check, I just upgraded the bootblocks to 2.2.6, and > loader works fine. I'm not an expert on that part, but I followed instructions I had from Mike (I was aware that a screwup could wreck my machine, so I was very careful) and the first time, it refused to boot the elf kernel. I booted the aout one, got more advice, did the disklabel, tried it again with no further changes, and it worked. Perhaps you're right, it's something else, but you can probably see why I think like I do. I'm not going to go stick the old bootblocks back .... is it possible that something since has changed with the bootblocks, so that the failure I saw wouldn't even occur any more? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 11:47:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id E91DF15610 for ; Wed, 17 Mar 1999 11:47:17 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA47649; Wed, 17 Mar 1999 14:45:13 -0500 (EST) Date: Wed, 17 Mar 1999 14:45:13 -0500 (EST) From: Chuck Robey To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: volatile question In-Reply-To: <36EFF74A.F42597F4@newsguy.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, 18 Mar 1999, Daniel C. Sobral wrote: > >From aio.h: > > typedef struct aiocb { > int aio_fildes; /* File descriptor */ > off_t aio_offset; /* File offset for I/O */ > volatile void *aio_buf; /* I/O buffer in process > space */ > ^^^^^^^^^^^^^^^^^^^^^^^ > size_t aio_nbytes; /* Number of bytes for I/O > */ > struct sigevent aio_sigevent; /* Signal to deliver */ > int aio_lio_opcode; /* LIO opcode */ > int aio_reqprio; /* Request priority -- > ignored */ > struct __aiocb_private _aiocb_private; > } aiocb_t; > > Is the volatile keyword in the right position? Shouldn't it be void* > volatile aio_buf? H&S pages 74-75: that code is right. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 11:51:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 543881527C for ; Wed, 17 Mar 1999 11:51:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA31589; Wed, 17 Mar 1999 11:50:45 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Mar 1999 11:50:45 -0800 (PST) From: Matthew Dillon Message-Id: <199903171950.LAA31589@apollo.backplane.com> To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: volatile question References: <36EFF74A.F42597F4@newsguy.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :typedef struct aiocb { : int aio_fildes; /* File descriptor */ : off_t aio_offset; /* File offset for I/O */ : volatile void *aio_buf; /* I/O buffer in process :space */ : ^^^^^^^^^^^^^^^^^^^^^^^ : :Is the volatile keyword in the right position? Shouldn't it be void* :volatile aio_buf? It depends whether you want a pointer to volatile data, or whether you want a volatile pointer to normal data. volatile void *aio_buf; normal pointer to volatile data void * volatile aio_buf; volatile pointer to normal data volatile void * volatile aio_buf; volatile pointer to volatile data -Matt Matthew Dillon :-- :Daniel C. Sobral (8-DCS) :dcs@newsguy.com :dcs@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 Mar 17 13:20:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 1B570152EA for ; Wed, 17 Mar 1999 13:19:53 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id QAA07438; Wed, 17 Mar 1999 16:19:04 -0500 (EST) Message-Id: <199903172119.QAA07438@cs.rpi.edu> To: "Daniel C. Sobral" Cc: "David E. Cross" , Robert Nordier , Matthew Dillon , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: KVA size changes in 3.1-stable In-Reply-To: Message from "Daniel C. Sobral" of "Thu, 18 Mar 1999 02:29:17 +0900." <36EFE66D.5654E3F2@newsguy.com> Date: Wed, 17 Mar 1999 16:19:03 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The old loader is backed to /boot/loader.old, if you use normal > installation procedure. > > So, interrupt the second stage, and boot the old loader (or the > kernel directly, actually). > > I'm not entirely sure, but 4.0 loader might be depending on > /sys/sys/linker.h. I built the 4.0 loader as follows: mkdir /tmp/loader cd /tmp/loader cvs -d /exports/disk1/cvs/FreeBSD/ncvs checkout src/sys cd src/sys/boot make cd i386/loader (some of those paths maybe of, I am doing this from memory ;) cp /boot/loader /boot/loader.good cp loader /boot/loader /bin/sync (x3) I then reboot the system, and it dies as I said. Some additional information is that I put the new loader on a floppy, and booted that. entering "boot disk1s1a:kernel" would give me an error that it could not find the file. "boot disk1s1a:COPYRIGHT" gave me the same error ;). Eventually I set currdev and rootdev to disk1s1a: and I was able to boot the kernel, it got as far as: kernel.kva text=.... [......] and then locked (this time the keyboard did not respond and I needed to hit the reset button. when boot/loader came up this time (again off of floppy), I told it to boot disk1s1a:boot/loader.good (after setting currdev and rootdev again). and from there I told it to boot the old/non-relocated kernel. I have been running that kernel since, but I would greatly enjoy running the relocated kernel with larger KVA :) As somone perviously asked, I did read the CVS log, and made changes to the listed files (with the exceptions to the ones I could modify with 'options "NKPT=17"' and 'options "NKPDE=254"'.) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 13:27:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from marlin.corp.gulf.net (marlin.corp.gulf.net [198.69.72.17]) by hub.freebsd.org (Postfix) with ESMTP id A219615266 for ; Wed, 17 Mar 1999 13:27:25 -0800 (PST) (envelope-from scott@marlin.corp.gulf.net) Received: from localhost (scott@localhost) by marlin.corp.gulf.net (8.9.1a/8.9.1) with SMTP id PAA05672 for ; Wed, 17 Mar 1999 15:26:54 -0600 (CST) Date: Wed, 17 Mar 1999 15:26:53 -0600 (CST) From: Scott Madley To: freebsd-hackers@freebsd.org Subject: unsubscribe 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 unsubscribe _____ | ___| Scott Madley | |___ ____ ____ _______ ______ Gulf Coast Internet Company |___ | __| |__ __|_ __| http://www.gulf.net ___| | |__| | | | | | | scott@corp.gulf.net |_____|____|____| |_| |_| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 13:31:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from niobe.ewox.org (ppp007.uio.no [129.240.240.8]) by hub.freebsd.org (Postfix) with ESMTP id 5BBCF14C0A for ; Wed, 17 Mar 1999 13:31:10 -0800 (PST) (envelope-from des@niobe.ewox.org) Received: (from des@localhost) by niobe.ewox.org (8.9.3/8.9.1) id WAA26407; Wed, 17 Mar 1999 22:29:08 +0100 (CET) (envelope-from des) To: Dag-Erling Smorgrav Cc: freebsd-hackers@freebsd.org Subject: Re: YP bogons in src/lib/libc/gen/getpwent.c References: <86ww0f24hw.fsf@niobe.ewox.org> From: Dag-Erling Smorgrav Date: 17 Mar 1999 22:29:08 +0100 In-Reply-To: Dag-Erling Smorgrav's message of "17 Mar 1999 22:25:15 +0100" Message-ID: <86vhfz24bf.fsf@niobe.ewox.org> Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Here's an untested patch: Strike "untested". I linked Apache with a patched getpwent.c, and it works just fine now. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 13:31:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from niobe.ewox.org (ppp007.uio.no [129.240.240.8]) by hub.freebsd.org (Postfix) with ESMTP id 10F331554E for ; Wed, 17 Mar 1999 13:31:10 -0800 (PST) (envelope-from des@niobe.ewox.org) Received: (from des@localhost) by niobe.ewox.org (8.9.3/8.9.1) id WAA26038; Wed, 17 Mar 1999 22:25:16 +0100 (CET) (envelope-from des) To: freebsd-hackers@freebsd.org Subject: YP bogons in src/lib/libc/gen/getpwent.c From: Dag-Erling Smorgrav Date: 17 Mar 1999 22:25:15 +0100 Message-ID: <86ww0f24hw.fsf@niobe.ewox.org> Lines: 61 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a problem in the yp routines in src/lib/libc/gen/getpwent.c which results in the malfunction of Apache (and possibly other getpwent() consumers) on NIS clients. The problem seems to arise when the getpw*() functions are called both before and after dropping privileges and forking. The first call to getpw*() causes _ypinitdb() to set _gotmaster to YP_HAVE_MASTER. This causes subsequent _getyppass() calls to attempt to access the master.passwd.byname map, which will fail after Apache has dropped privileges and forked, because the children need to rebind, but don't have permission to bind to a privileged port. The bug does not occur in debug mode (httpd -X) because Apache does not fork, so it keeps using the original socket, which is bound to a privileged port. Proposed solution: if _getyppass() fails and _gotmaster != YP_HAVE_NONE, retry with mastermap = map. If that succeeds, set _gotmaster to YP_HAVE_NONE and proceed. If not, return 0 as usual. Here's an untested patch: Index: src/lib/libc/gen/getpwent.c =================================================================== RCS file: /home/ncvs/src/lib/libc/gen/getpwent.c,v retrieving revision 1.48 diff -u -r1.48 getpwent.c --- getpwent.c 1998/12/17 16:31:02 1.48 +++ getpwent.c 1999/03/17 21:22:35 @@ -747,14 +747,21 @@ return 0; } - sprintf(mastermap,"%s",map); - if (_gotmaster == YP_HAVE_MASTER) sprintf(mastermap,"master.%s", map); + else + sprintf(mastermap,"%s",map); if(yp_match(_pw_yp_domain, (char *)&mastermap, name, strlen(name), - &result, &resultlen)) - return 0; + &result, &resultlen)) { + if (_gotmaster != YP_HAVE_MASTER) + return 0; + sprintf(mastermap,"%s",map); + if (yp_match(_pw_yp_domain, (char *)&mastermap, + name, strlen(name), &result, &resultlen)) + return 0; + _gotmaster = YP_HAVE_NONE; + } if (!_pw_stepping_yp) { s = strchr(result, ':'); It might also make sense to export a function which completely resets the getpwent() code (i.e. sets _yp_enabled to -1, _gotmaster to YP_HAVE_NONE, etc.) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 13:33:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id AFA9C1556D for ; Wed, 17 Mar 1999 13:33:55 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 9449 invoked by uid 1001); 17 Mar 1999 21:33:35 +0000 (GMT) To: crossd@cs.rpi.edu Cc: dcs@newsguy.com, rnordier@nordier.com, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 17 Mar 1999 16:19:03 -0500" References: <199903172119.QAA07438@cs.rpi.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 17 Mar 1999 22:33:35 +0100 Message-ID: <9447.921706415@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I built the 4.0 loader as follows: > mkdir /tmp/loader > cd /tmp/loader > cvs -d /exports/disk1/cvs/FreeBSD/ncvs checkout src/sys > cd src/sys/boot > make > cd i386/loader > (some of those paths maybe of, I am doing this from memory ;) > cp /boot/loader /boot/loader.good > cp loader /boot/loader > /bin/sync (x3) > > I then reboot the system, and it dies as I said. > > Some additional information is that I put the new loader on a floppy, and > booted that. entering "boot disk1s1a:kernel" would give me an error that > it could not find the file. "boot disk1s1a:COPYRIGHT" gave me the same > error ;). Eventually I set currdev and rootdev to disk1s1a: and I was able to > boot the kernel, it got as far as: > kernel.kva text=.... [......] > > and then locked (this time the keyboard did not respond and I needed to hit the > reset button. when boot/loader came up this time (again off of floppy), I > told it to boot disk1s1a:boot/loader.good (after setting currdev and rootdev > again). and from there I told it to boot the old/non-relocated kernel. I > have been running that kernel since, but I would greatly enjoy running the > relocated kernel with larger KVA :) > > As somone perviously asked, I did read the CVS log, and made changes to the > listed files (with the exceptions to the ones I could modify with > 'options "NKPT=17"' and 'options "NKPDE=254"'.) My experience, after trying this today: It worked fine here. What I did, on a 3.1-STABLE system (Compaq Proliant 3000), was: - Use the dg patched conf/Makefile.i386 conf/kernel.script include/pmap.h from 4.0-CURRENT. - Build new kernel, attempt to boot. Stops in loader with an error message I didn't write down, unfortunately. (But this was expected - dg's commit message explicitly mentioned the need for new boot blocks.) - Install boot1 boot2 loader from a 4.0-CURRENT system - these had been generated during a "make buildworld" on March first. And presto, it booted. Been running fine for 6 hours so far. The reason I wanted the larger KVA is that this machine has 576 MB memory, and I'm wondering if some unexplained hangs and reboots we've had could be due to the KVA size. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 13:43:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 5B9FB15376 for ; Wed, 17 Mar 1999 13:43:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id QAA08106; Wed, 17 Mar 1999 16:43:15 -0500 (EST) Message-Id: <199903172143.QAA08106@cs.rpi.edu> To: sthaug@nethelp.no Cc: crossd@cs.rpi.edu, dcs@newsguy.com, rnordier@nordier.com, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: KVA size changes in 3.1-stable In-Reply-To: Message from sthaug@nethelp.no of "Wed, 17 Mar 1999 22:33:35 +0100." <9447.921706415@verdi.nethelp.no> Date: Wed, 17 Mar 1999 16:43:15 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I built the 4.0 loader as follows: > > mkdir /tmp/loader > > cd /tmp/loader > > cvs -d /exports/disk1/cvs/FreeBSD/ncvs checkout src/sys > > cd src/sys/boot > > make > > cd i386/loader > > (some of those paths maybe of, I am doing this from memory ;) > > cp /boot/loader /boot/loader.good > > cp loader /boot/loader > > /bin/sync (x3) > > > > I then reboot the system, and it dies as I said. > > > > Some additional information is that I put the new loader on a floppy, and > > booted that. entering "boot disk1s1a:kernel" would give me an error that > > it could not find the file. "boot disk1s1a:COPYRIGHT" gave me the same > > error ;). Eventually I set currdev and rootdev to disk1s1a: and I was able to > > boot the kernel, it got as far as: > > kernel.kva text=.... [......] > > > > and then locked (this time the keyboard did not respond and I needed to hit the > > reset button. when boot/loader came up this time (again off of floppy), I > > told it to boot disk1s1a:boot/loader.good (after setting currdev and rootdev > > again). and from there I told it to boot the old/non-relocated kernel. I > > have been running that kernel since, but I would greatly enjoy running the > > relocated kernel with larger KVA :) > > > > As somone perviously asked, I did read the CVS log, and made changes to the > > listed files (with the exceptions to the ones I could modify with > > 'options "NKPT=17"' and 'options "NKPDE=254"'.) > > My experience, after trying this today: It worked fine here. What I did, > on a 3.1-STABLE system (Compaq Proliant 3000), was: > > - Use the dg patched conf/Makefile.i386 conf/kernel.script include/pmap.h > from 4.0-CURRENT. > - Build new kernel, attempt to boot. Stops in loader with an error message > I didn't write down, unfortunately. (But this was expected - dg's commit > message explicitly mentioned the need for new boot blocks.) > - Install boot1 boot2 loader from a 4.0-CURRENT system - these had been > generated during a "make buildworld" on March first. > > And presto, it booted. Been running fine for 6 hours so far. The reason > I wanted the larger KVA is that this machine has 576 MB memory, and I'm > wondering if some unexplained hangs and reboots we've had could be due > to the KVA size. Ok... I think I will stop causing spam to -hackers over this. I had been using 3.1-stable's boot1/boot2 with the 4.0 boot loader (and assumed it was OK, I thought once /boot/loader took over, it was working). I will pound on this myself for awhile and see where it goes. I would like to make the request that the KVA changes be brought back into the -stable kerenel :) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 13:54:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m2-2-dbn.dial-up.net [196.34.155.66]) by hub.freebsd.org (Postfix) with ESMTP id 747FA15619 for ; Wed, 17 Mar 1999 13:53:32 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA02196; Wed, 17 Mar 1999 23:50:49 +0200 (SAT) From: Robert Nordier Message-Id: <199903172150.XAA02196@ceia.nordier.com> Subject: Re: KVA size changes in 3.1-stable In-Reply-To: from Chuck Robey at "Mar 17, 99 02:34:32 pm" To: chuckr@mat.net (Chuck Robey) Date: Wed, 17 Mar 1999 23:50:46 +0200 (SAT) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (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 [Cc trimmed] > > > How long since you last used disklabel to update your bootblocks? Old > > > ones will do that (they did for me, using 2.2.6 bootblocks a while > > > back). > > > > I'm really skeptical that the loader problems you experienced had > > anything directly to do with the 2.2.6 bootblocks. I have a machine > > here, still running 2.2.5-RELEASE, and regularly test loader on > > it. To double-check, I just upgraded the bootblocks to 2.2.6, and > > loader works fine. > > I'm not an expert on that part, but I followed instructions I had from > Mike (I was aware that a screwup could wreck my machine, so I was very > careful) and the first time, it refused to boot the elf kernel. I > booted the aout one, got more advice, did the disklabel, tried it again > with no further changes, and it worked. Perhaps you're right, it's > something else, but you can probably see why I think like I do. Sure, it's known as "jumping to conclusions". :-) > I'm not going to go stick the old bootblocks back .... is it possible > that something since has changed with the bootblocks, so that the > failure I saw wouldn't even occur any more? I suppose loader may have changed in some small way that is nevertheless significant. There's always the possibility that some benign bug may have become less than benign in unusual circumstances that the particular bootblocks contributed to. The explanation just doesn't fit either the theory, or most of the data points here. That doesn't mean the explanation is wrong, just that it will tend to be *regarded* as wrong. :-) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 14:22:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 3EBAF152FE for ; Wed, 17 Mar 1999 14:22:23 -0800 (PST) (envelope-from sascht@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id RAA00582; Wed, 17 Mar 1999 17:21:59 -0500 (EST) Received: from loki.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03266; Wed, 17 Mar 1999 17:21:58 -0500 From: Charles Tudor Received: by loki.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA00704; Wed, 17 Mar 1999 17:21:57 -0500 Message-Id: <199903172221.AA00704@loki.unx.sas.com> Subject: Re: fxp driver causing lockup To: wes@softweyr.com (Wes Peters) Date: Wed, 17 Mar 1999 17:21:57 -0500 (EST) Cc: jwd@unx.sas.com, freebsd-hackers@freebsd.org, sascht@unx.sas.com In-Reply-To: <36EF5749.2B1A8D21@softweyr.com> from "Wes Peters" at Mar 17, 99 00:18:33 am X-Mailer: ELM [version 2.4 PL23] 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 > > "John W. DeBoskey" wrote: > > > > Hi, > > > > I beleive you are correct. The following code fragment from > > if_fxp.c is the lockup: > > > > /* > > * Start the config command/DMA. > > */ > > fxp_scb_wait(sc); > > CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); > > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); > > /* ...and wait for it to complete. */ > > while (!(cbp->cb_status & FXP_CB_STATUS_C)); > > Yup, that's it. I initially tracked this down under 3.0, but moved the > machine back to 2.2.7 because I needed it to get work done. I've now > stuffed two 3c905Bs into it for my main and test network, and can play > with the Pro 100B without losing a network connection. > > > according to doc at Dell's website (they have a machine with this > > problem), the bios is not enabling dma on the adapter board. I beleive > > the person I copied on this mail can provide the precise web page > > that documents this. > > > > According to them, it is possible to discreetly turn on dma on > > the adapter. This is were someone with the appropriate doc needs > > to jump in... > > > > Basically, the driver needs to check that dma is enabled and > > enable it if not. > > Any hints as to how to do that? I've got the machine, the lockups, > and a (little) bit of driver knowlege. Plus a fair bit of tenacity. > The Linux 2.2 driver exhibits the same problem on these machines, so I > can either share the fix with them or just convince them to upgrade > to FreeBSD once I get this nailed. ;^) > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://www.softweyr.com/~softweyr wes@softweyr.com > I am trying to contact Intel to see if I can get the information needed to fix the problem. I will let you know if I receive the information. Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 15:33: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D26BF1532C; Wed, 17 Mar 1999 15:32:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA98700; Wed, 17 Mar 1999 15:32:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Ruslan Ermilov Cc: Dag-Erling Smorgrav , dg@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ipflow and ipfirewall In-reply-to: Your message of "Wed, 17 Mar 1999 10:41:57 +0200." <19990317104157.A4028@relay.ucb.crimea.ua> Date: Wed, 17 Mar 1999 15:32:08 -0800 Message-ID: <98698.921713528@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just complained why David didn't document this feature when it > was committed. Unfortunately, there was no response from him. > Probably, he's very busy now. So, I ask _you_ to document this > feature for others... not for me. I already understand how it > does work. I think the point he was trying to really make (it's always fun watching non-native speakers argue in English :-) is that any arbitrary value of "you" is *always* too busy, so if you really want it to happen the best way is to submit the diffs or full docs or whatever. As you yourself just pointed out, you understand how it works and that makes you an ideal candidate to document it when others are clearly too busy to do so. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 16:47:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 8459C14D2A; Wed, 17 Mar 1999 16:47:12 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA19636; Wed, 17 Mar 1999 16:46:20 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA21911; Wed, 17 Mar 1999 16:46:20 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id RAA01113; Wed, 17 Mar 1999 17:46:17 -0700 Message-ID: <36F04CD0.B0D46F3B@softweyr.com> Date: Wed, 17 Mar 1999 17:46:08 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Spengler , hackers@freebsd.org, jkh@freebsd.org Subject: Re: fxp driver causing lockup References: <199903172356.RAA14113@us.networkcs.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 Spengler wrote: > Wes Peters said: > > "John W. DeBoskey" wrote: > > > > > > Hi, > > > > > > I beleive you are correct. The following code fragment from > > > if_fxp.c is the lockup: > > > > > > /* > > > * Start the config command/DMA. > > > */ > > > fxp_scb_wait(sc); > > > CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); > > > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); > > > /* ...and wait for it to complete. */ > > > while (!(cbp->cb_status & FXP_CB_STATUS_C)); > > > > Yup, that's it. I initially tracked this down under 3.0, but moved the > > machine back to 2.2.7 because I needed it to get work done. I've now > > stuffed two 3c905Bs into it for my main and test network, and can play > > with the Pro 100B without losing a network connection. > > There was a FreeBSD 2.2.x -> 3.x change in which the driver is now responsible > for setting the PCI busmaster enable bit. This may (or not) be your problem. > In the fxp_attach() function, you should insert the following before doing > the pci_map_mem() call: > > u_long val; > > val = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); > val |= (PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN); > pci_conf_write(config_id, PCI_COMMAND_STATUS_REG, val); > > Hope this helps! It did, it's working fine now. Here's the diff vs. 3.1-RELEASE: *** if_fxp.c.orig Wed Mar 17 17:06:51 1999 --- if_fxp.c Wed Mar 17 17:23:09 1999 *************** *** 98,103 **** --- 98,104 ---- #include /* for DELAY */ #include + #include /* for PCIM_CMD_xxx */ #include #include *************** *** 523,528 **** --- 524,530 ---- vm_offset_t pbase; struct ifnet *ifp; int s; + u_long val; sc = malloc(sizeof(struct fxp_softc), M_DEVBUF, M_NOWAIT); if (sc == NULL) *************** *** 531,536 **** --- 533,545 ---- callout_handle_init(&sc->stat_ch); s = splimp(); + + /* + * Enable bus mastering. + */ + val = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); + val |= (PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN); + pci_conf_write(config_id, PCI_COMMAND_STATUS_REG, val); /* * Map control/status registers. Can a couple of other hackers with EEPro 100's try this out to make sure it doesn't accidentally break anything else? If not, I'll commit it tomorrow. Thanks a TON, Mike. Now I can rip that second XL out of this machine and upgrade my other machine to 3.1 also. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 16:55: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m2-2-dbn.dial-up.net [196.34.155.66]) by hub.freebsd.org (Postfix) with ESMTP id A6197152B7 for ; Wed, 17 Mar 1999 16:54:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id CAA03803; Thu, 18 Mar 1999 02:51:32 +0200 (SAT) From: Robert Nordier Message-Id: <199903180051.CAA03803@ceia.nordier.com> Subject: Re: KVA size changes in 3.1-stable In-Reply-To: <199903172143.QAA08106@cs.rpi.edu> from "David E. Cross" at "Mar 17, 99 04:43:15 pm" To: crossd@cs.rpi.edu (David E. Cross) Date: Thu, 18 Mar 1999 02:51:30 +0200 (SAT) Cc: sthaug@nethelp.no, crossd@cs.rpi.edu, dcs@newsguy.com, rnordier@nordier.com, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 > > My experience, after trying this today: It worked fine here. What I did, > > on a 3.1-STABLE system (Compaq Proliant 3000), was: > > > > - Use the dg patched conf/Makefile.i386 conf/kernel.script include/pmap.h > > from 4.0-CURRENT. > > - Build new kernel, attempt to boot. Stops in loader with an error message > > I didn't write down, unfortunately. (But this was expected - dg's commit > > message explicitly mentioned the need for new boot blocks.) > > - Install boot1 boot2 loader from a 4.0-CURRENT system - these had been > > generated during a "make buildworld" on March first. > > > > And presto, it booted. Been running fine for 6 hours so far. The reason > > I wanted the larger KVA is that this machine has 576 MB memory, and I'm > > wondering if some unexplained hangs and reboots we've had could be due > > to the KVA size. > > Ok... I think I will stop causing spam to -hackers over this. I had been using > 3.1-stable's boot1/boot2 with the 4.0 boot loader (and assumed it was OK, I > thought once /boot/loader took over, it was working). I will pound on this > myself for awhile and see where it goes. Just as info: there are absolutely no differences (source code or binaries) between the -stable and -current boot1/boot2. I've been keeping the code identical deliberately. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 18:26:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bulls.mei.co.jp (bulls.mei.co.jp [202.224.189.102]) by hub.freebsd.org (Postfix) with ESMTP id A58BF15264 for ; Wed, 17 Mar 1999 18:26:35 -0800 (PST) (envelope-from takamune@avrl.mei.co.jp) Received: by bulls.mei.co.jp (8.9.1/3.7W) with ESMTP id LAA21426; Thu, 18 Mar 1999 11:25:31 +0900 (JST) Received: by dodgers.mei.co.jp (8.9.1/3.7W) with SMTP id LAA05345; Thu, 18 Mar 1999 11:25:30 +0900 (JST) Received: by avrlgate1.avrl.mei.co.jp (8.6.10+2.4W/3.3W3-avrl3.0) id LAA29340; Thu, 18 Mar 1999 11:25:29 +0900 To: brandon@roguetrader.com Cc: freebsd-hackers@freeBSD.org Subject: Re: global Makefile(s) BINDIR inconsistency with DESTDIR From: Kazu TAKAMUNE In-Reply-To: Your message of "Wed, 17 Mar 1999 05:28:00 -0700" <19990317052800.A1102@ice.cold.org> References: <19990317052800.A1102@ice.cold.org> X-Mailer: xcite1.27> Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990318112439P.takamune@avrl.mei.co.jp> Date: Thu, 18 Mar 1999 11:24:39 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 9 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Wed, 17 Mar 1999 05:28:00 -0700 >>>>> brandon@roguetrader.com(Brandon Gillespie) said: Brandon> If it is a prob, I can submit a bug report. I reported the same problem in bin/10615 the day before yesterday. --- With best regards. Kazu TAKAMUNE takamune@avrl.mei.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 18:27:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 7FC691529A for ; Wed, 17 Mar 1999 18:27:36 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id UAA12493; Wed, 17 Mar 1999 20:27:06 -0600 (CST) Date: Wed, 17 Mar 1999 20:27:05 -0600 From: "Matthew D. Fuller" To: Nate Williams Cc: hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC Message-ID: <19990317202705.X25217@futuresouth.com> References: <12196.921649234@zippy.cdrom.com> <199903171641.JAA10150@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199903171641.JAA10150@mt.sri.com>; from Nate Williams on Wed, Mar 17, 1999 at 09:41:09AM -0700 X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Trim, trim, trim on the CC's] On Wed, Mar 17, 1999 at 09:41:09AM -0700, a little birdie told me that Nate Williams remarked > > I would think a Forth hacker could do this, given that the flags to the > npx device can be used to specify the amount of memory in the system. > (Although, I could find it documented anywhere obvious when I went > looking for it in the man pages.) > > /sys/i386/isa/npx.c: > revision 1.32 > date: 1996/11/11 20:39:03; author: bde; state: Exp; lines: +47 -13 > ... > Added a boot-time way to set the memory size (iosiz in config, iosize in > userconfig for npx0). > ... Note that the one time I tried this (admittedly, way back in 2.1.{5|6} days) it didn't work. That was on a Compaq (doncha LOVE 'em? ;) with that weird Compaq motherboard/chipset or something which meant that without an explicit MAXMEM, it wouldn't detect over 16 meg, and I didn't have the space to build a kernel. --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 20:17:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (Postfix) with ESMTP id 1F57E15032 for ; Wed, 17 Mar 1999 20:17:14 -0800 (PST) (envelope-from joe@monk.via.net) Received: (from joe@localhost) by monk.via.net (8.8.8/8.8.8) id UAA09443 for hackers@freebsd.org; Wed, 17 Mar 1999 20:16:54 -0800 (PST) (envelope-from joe) From: Joe McGuckin Message-Id: <199903180416.UAA09443@monk.via.net> Date: Wed, 17 Mar 1999 20:16:54 -0800 (PST) To: hackers@freebsd.org Subject: Repeated 'lockmgr: locking against myself' panics on 3.1-RELEASE (fwd) X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.1, Users set to 500, 512M ram. Approx 5 to 7 minutes after rebooting, the system will panic. Sorry, I don't have anymore info. Turning USERS down to 400 seems to have fixed the problem. Has anyone else seen this problem? Thanks, Joe Joe McGuckin ViaNet Communications 1235 Pear Ave, Suite 107 Mountain View, CA 90403 Phone: 650-969-2203 Cell: 415-710-4894 Fax: 650-969-2124 Joe McGuckin ViaNet Communications 1235 Pear Ave, Suite 107 Mountain View, CA 90403 Phone: 650-969-2203 Cell: 415-710-4894 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 20:55:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox1.ucsd.edu (mailbox1.ucsd.edu [132.239.1.53]) by hub.freebsd.org (Postfix) with ESMTP id 58D3214C43 for ; Wed, 17 Mar 1999 20:55:10 -0800 (PST) (envelope-from rjdawes@physics.ucsd.edu) Received: from physics.ucsd.edu (huntington.ucsd.edu [132.239.73.96]) by mailbox1.ucsd.edu (8.9.1a/8.9.1) with SMTP id UAA10506; Wed, 17 Mar 1999 20:54:51 -0800 (PST) Received: from localhost by physics.ucsd.edu (SMI-8.6/SMI-SVR4) id UAA00347; Wed, 17 Mar 1999 20:53:12 -0800 Date: Wed, 17 Mar 1999 20:53:12 -0800 (PST) From: "Richard J. Dawes" X-Sender: rjdawes@huntington Reply-To: Richard Dawes To: "Matthew D. Fuller" Cc: hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-Reply-To: <19990317202705.X25217@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 Hello, all! I have belatedly started reading this thread, and I am mystified as to what is meant by "broken" hardware (which I take it is shipped that way?), with regard to memory. What exactly is broken? Do some cheapo motherboards use specific chips that are bad at managing memory? I guess what I'm asking is if this problem is well-defined, and, if so, some pointers on further information would greatly be appreci- ated. (My quick perusal of HARDWARE.TXT produced nothing.) Thanks! --Rich [P.S. -- Just occurred to me, maybe this should be posted to -hardware?] ======================================== Richard J. Dawes rdawes@ucsd.edu ======================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 21: 8:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 135E015374 for ; Wed, 17 Mar 1999 21:08:51 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id XAA22508; Wed, 17 Mar 1999 23:08:23 -0600 (CST) Date: Wed, 17 Mar 1999 23:08:23 -0600 From: "Matthew D. Fuller" To: Richard Dawes Cc: hackers@FreeBSD.ORG Subject: Broken memory (was Re: Proposal: Define MAXMEM in GENERIC) Message-ID: <19990317230822.Y25217@futuresouth.com> References: <19990317202705.X25217@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Richard J. Dawes on Wed, Mar 17, 1999 at 08:53:12PM -0800 X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 17, 1999 at 08:53:12PM -0800, a little birdie told me that Richard J. Dawes remarked > Hello, all! > I have belatedly started reading this thread, and I am mystified > as to what is meant by "broken" hardware (which I take it is shipped > that way?), with regard to memory. What exactly is broken? Do some > cheapo motherboards use specific chips that are bad at managing memory? > I guess what I'm asking is if this problem is well-defined, and, > if so, some pointers on further information would greatly be appreci- > ated. (My quick perusal of HARDWARE.TXT produced nothing.) I suspect it's not a -hackers topic as such, but as long as it's here I'll leave it until somebody bites my head off. This was a Compaq Presario 9232, shipped with 16 megs of RAM and a P120. Bought it (on closeout) in August '96. I've seen this with the vast majority (I'm tempted to say all, but I'll err on the side of caution) of Compaq's I've seen exhibit this, even up through some 3.0 SNAP's from mid last year (I think). Define MAXMEM, you're golden. Don't, it'll only detect 16 megs. I don't know if the npx0 trick works on the later versions; I've always had space/etc to do custom kernels since then, so I haven't bothered. But under 2.1.6 I could never get it to recognize the full 24; only the first 16. > ======================================== > Richard J. Dawes rdawes@ucsd.edu > ======================================== --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 21:34:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 3192014CA3 for ; Wed, 17 Mar 1999 21:34:13 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id AAA24072; Thu, 18 Mar 1999 00:39:04 -0500 (EST) Date: Thu, 18 Mar 1999 00:39:02 -0500 (EST) From: Alfred Perlstein To: Joe McGuckin Cc: hackers@FreeBSD.ORG Subject: Re: Repeated 'lockmgr: locking against myself' panics on 3.1-RELEASE (fwd) In-Reply-To: <199903180416.UAA09443@monk.via.net> 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, 17 Mar 1999, Joe McGuckin wrote: > > > > 3.1, Users set to 500, 512M ram. Approx 5 to 7 minutes after rebooting, > the system will panic. Sorry, I don't have anymore info. > > Turning USERS down to 400 seems to have fixed the problem. > > Has anyone else seen this problem? Yes, everyone, it really isn't a problem though, check the mailing lists for more verbose advice, but for a safe bet, keep MAXUSERS less than 128. -Alfred > > Thanks, > > Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 22: 7:43 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 6FBC7150B4 for ; Wed, 17 Mar 1999 22:06:55 -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 2.12 #1) id 10NVwa-000KU4-00; Thu, 18 Mar 1999 08:06:12 +0200 From: Sheldon Hearn To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Serve working hardware first (was Define MAXMEM in GENERIC) In-reply-to: Your message of "Thu, 18 Mar 1999 02:47:10 +0900." <36EFEA9E.ED8DFF5@newsguy.com> Date: Thu, 18 Mar 1999 08:06:12 +0200 Message-ID: <78743.921737172@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Mar 1999 02:47:10 +0900, "Daniel C. Sobral" wrote: > Hear! Hear! It's not the people with *working* hardware that should > get the short end! Hi Daniel, That's certainly a reasonable statement. I agree with you, for whatever that's worth. However, my impression has always been that the priority in GENERIC is to make sure as many people as possible can boot FreeBSD. The only case I can think of right now that supports this impression is the disabled probe for 32 bit multi-sector transfers in the IDE driver. Do we have a fixed goal with GENERIC, or have things fuzzied out over the years? Ciao, Sheldon. [Reply Subjects should not include the (was Define MAXMEM in GENERIC) ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 23: 7:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from stevie.loop.com (stevie-inet.loop.com [207.211.60.71]) by hub.freebsd.org (Postfix) with ESMTP id A0FB214D15 for ; Wed, 17 Mar 1999 23:07:32 -0800 (PST) (envelope-from icimjs@loop.com) Received: from knobel (p15.hwts13.loop.net [207.211.62.180]) by stevie.loop.com (8.9.1/8.9.1) with SMTP id XAA14539 for ; Wed, 17 Mar 1999 23:07:41 -0800 (PST) Message-Id: <3.0.5.32.19990317230615.015a8aa0@pop.loop.com> X-Sender: icimjs@pop.loop.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 17 Mar 1999 23:06:15 -0800 To: freebsd-hackers@freebsd.org From: Elan Subject: Re: VMWare In-Reply-To: <199903161815.KAA11214@apollo.backplane.com> References: <5262.921575579@verdi.nethelp.no> <36EE5B76.3C467B7B@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, if you are a software developer, use single stepping when you debug code and plan to use Vmware, please let mailto:tech_info@vmware.com know that you will want to use single stepping under Vmware for debugging purposes. According to info on their website, single stepping is currently not supported (setting break points, however, is) and according to information I got from their tech_info guy, they haven't decided whether to include that feature. It appears to depend on whether they get enough requests for it! TIA, Elan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 17 23:34:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bbcc.ctc.edu (bbcc.ctc.edu [134.39.180.254]) by hub.freebsd.org (Postfix) with ESMTP id 7F38814C57 for ; Wed, 17 Mar 1999 23:34:28 -0800 (PST) (envelope-from chris@bbcc.ctc.edu) Received: from localhost (chris@localhost) by bbcc.ctc.edu (8.8.8/8.6.12) with SMTP id XAA09173; Wed, 17 Mar 1999 23:26:38 -0800 (PST) Date: Wed, 17 Mar 1999 23:26:37 -0800 (PST) From: Chris Coleman To: "Matthew D. Fuller" Cc: Richard Dawes , hackers@FreeBSD.ORG Subject: Re: Broken memory (was Re: Proposal: Define MAXMEM in GENERIC) In-Reply-To: <19990317230822.Y25217@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 I am having this problem now with my Compaq presario 9564. I am runnig 2.2.6 and it only detects 16 meg and I have 24 in there. I thought it might have been because the memory I added was not "Compaq" memory or something like that. I will define MAXMEM and fix this tonite. :-) -Chris On Wed, 17 Mar 1999, Matthew D. Fuller wrote: > On Wed, Mar 17, 1999 at 08:53:12PM -0800, a little birdie told me > that Richard J. Dawes remarked > > Hello, all! > > I have belatedly started reading this thread, and I am mystified > > as to what is meant by "broken" hardware (which I take it is shipped > > that way?), with regard to memory. What exactly is broken? Do some > > cheapo motherboards use specific chips that are bad at managing memory? > > I guess what I'm asking is if this problem is well-defined, and, > > if so, some pointers on further information would greatly be appreci- > > ated. (My quick perusal of HARDWARE.TXT produced nothing.) > > I suspect it's not a -hackers topic as such, but as long as it's here > I'll leave it until somebody bites my head off. > This was a Compaq Presario 9232, shipped with 16 megs of RAM and a P120. > Bought it (on closeout) in August '96. I've seen this with the vast > majority (I'm tempted to say all, but I'll err on the side of caution) of > Compaq's I've seen exhibit this, even up through some 3.0 SNAP's from mid > last year (I think). Define MAXMEM, you're golden. Don't, it'll only > detect 16 megs. I don't know if the npx0 trick works on the later > versions; I've always had space/etc to do custom kernels since then, so I > haven't bothered. But under 2.1.6 I could never get it to recognize the > full 24; only the first 16. > > > ======================================== > > Richard J. Dawes rdawes@ucsd.edu > > ======================================== > > > > --- > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > | Matthew Fuller http://www.over-yonder.net/ | > * fullermd@futuresouth.com fullermd@over-yonder.net * > | UNIX Systems Administrator Specializing in FreeBSD | > * FutureSouth Communications ISPHelp ISP Consulting * > | "The only reason I'm burning my candle at both ends, | > * is because I haven't figured out how to light the * > | middle yet" | > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > > > 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 Mar 18 0:10:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles193.castles.com [208.214.165.193]) by hub.freebsd.org (Postfix) with ESMTP id 3C9881538F for ; Thu, 18 Mar 1999 00:10:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA00640; Thu, 18 Mar 1999 00:04:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903180804.AAA00640@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable In-reply-to: Your message of "Tue, 16 Mar 1999 19:44:31 EST." <199903170044.TAA16397@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Mar 1999 00:04:41 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We have pretty much ruled out everything else. No 2 of the crashes are ever > the same, it is only this machine, and the only difference between this > machine and other machines that are rock solid (48+ days uptime), is that > this machine has the high maxusers. It is required that this machine > has a high maxusers as it is used for shell access for students writing > programs. > > Are there any problems with incorperating Tor's changes into 3.1-STABLE? If > so please speak, as that is exactly what I am doing now. What aspect of "maxusers" is actually required for your students? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 18 0:55:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id B50AA14C2B for ; Thu, 18 Mar 1999 00:55:41 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id IAA74484 for hackers@freebsd.org; Thu, 18 Mar 1999 08:55:22 GMT (envelope-from joe) Date: Thu, 18 Mar 1999 08:55:22 +0000 From: Josef Karthauser To: hackers@freebsd.org Subject: [christiane@vmware.com: RE: VMWare on FreeBSD (Fwd: Re: Question about host OS)] Message-ID: <19990318085522.A74171@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've received a prompt reply from VMWare. Perhaps more lobbying will convince them ! Joe ----- Forwarded message from Christiane Holtzman ----- From: Christiane Holtzman Reply-To: "christiane@vmware.com" To: "'VJ Richey'" Cc: "'joe@pavilion.net'" Subject: RE: VMWare on FreeBSD (Fwd: Re: Question about host OS) Date: Wed, 17 Mar 1999 15:10:55 -0800 Organization: VMware X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Joe, Thank you for your email and interest in VMware. Unfortunately we currently do not have plans to support FreeBSD as a host operating system. We will support FreeBSD as a guest operating system. We have noted you request of FreeBSD host support in case we review this in the future. BTW our current Linux beta should run FreeBSD 2.2.8 (and probably other2.2.x) as a *guest* OS with a Linux host. FreeBSD 3.0 or 3.1 will not run in this current beta release. We have 3.1 running here and need to release some changes to our software to support it, hopefully this will happen sometime soon as we refresh the beta release. I have however noted your inquiry as a request for that support. Sincerely, Christiane Holtzman VMware, Inc. On Wednesday, March 17, 1999 10:25 AM, VJ Richey [SMTP:vj@vmware.com] wrote: > > -----Original Message----- > From: Josef Karthauser > To: sales@vmware.com > Date: Wednesday, March 17, 1999 2:34 AM > Subject: Re: VMWare on FreeBSD (Fwd: Re: Question about host OS) > > > >Hello, > > > >We're very interested in your VMware platform and eagerly await > >it's full release. Unfortunately you don't appear to support our > >platform as a host operating system. We're a large FreeBSD house > >in the UK and are very interested in running your product in this > >host environment. > > > >Please can you provide us with a time scale for supporting this > >platform. If you require any technical help with this please let us > >know. > >As you're probably aware FreeBSD has a very strong development > >team, and though we've not got as much PR in the field as the Linux > >camps we do have a very strong user-ship among professionals. You > >may wish to check out http://www.uk.freebsd.org/commercial/ to > >verify this. > > > >I greatly look forward to your response, and your support of FreeBSD. > > > > > >Regards, > >Joe > >-- > >Josef Karthauser FreeBSD: How many times have you booted today? > >Technical Manager Viagra for your server (http://www.uk.freebsd.org) > >Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, > joe@tao.org.uk] ----- End forwarded message ----- -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 1:24: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id AFFE215524 for ; Thu, 18 Mar 1999 01:24:03 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.8.8) with ESMTP id JAA46177 for ; Thu, 18 Mar 1999 09:23:42 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA09320 for ; Thu, 18 Mar 1999 08:26:06 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903180826.IAA09320@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.org Subject: dgm (Digiboard PC/Xem) - candidate for removal ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Mar 1999 08:26:06 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there anyone out there that's willing to run some probe code for me with an installed digiboard that currently uses the dgm driver in -current or -stable ? The dgm & dgb drivers are almost the same, and I'd like to merge them and clean up the result. I can't unless I can figure out how to distinguish PC/Xi boards (I've got one of these) from PC/Xem boards (I haven't got one of these). If nobody can help, I suspect dgm will have to go and I'll concentrate on tidying up the dgb driver with PC/Xi support only. TIA. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 4:37: 0 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 9B08714C83 for ; Thu, 18 Mar 1999 04:36:50 -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 2.12 #1) id 10Nc2I-000LDj-00 for hackers@freebsd.org; Thu, 18 Mar 1999 14:36:30 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: login_cap(3) waxing or waning? Date: Thu, 18 Mar 1999 14:36:29 +0200 Message-ID: <81574.921760589@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I've added the following command-line option to ftpd(8): -n If /var/run/nologin does not exist, also check for the specified file and, if it exists, display it and exit. I need this work-around because ftpd does not honour the login_cap(3) capabilities ``nologin'' and ``ignorenologin''. I would have preferred to add the following to login.conf(5): ftp:\ :nologin=/var/run/nologin.ftp:\ :tc=default: Is login_cap going to be around long enough for it to be worthwhile investing time in teaching ftpd to respect its ``nologin'' and ``ignorelogin'' capabilities? The alternative is for me to man-handle ftpd into testing for /var/run/nologin.curname, but if login_cap is going to stick around, I'd like to do this properly. As an aside, is curname (see ftpd.c:755) restricted to 10 characters instead of MAXLOGNAME for reasons instrinsic to the FTP protocol, or was it simply not updated when MAXLOGNAME was born? Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 5:59: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pegasus.freibergnet.de (pegasus.freibergnet.de [194.123.255.9]) by hub.freebsd.org (Postfix) with ESMTP id 616AE15495 for ; Thu, 18 Mar 1999 05:58:28 -0800 (PST) (envelope-from holm@pegasus.freibergnet.de) Received: (from holm@localhost) by pegasus.freibergnet.de (8.9.3/8.9.1) id OAA35637; Thu, 18 Mar 1999 14:56:52 +0100 (CET) (envelope-from holm) Date: Thu, 18 Mar 1999 14:56:52 +0100 From: Holm Tiffe To: Brian Somers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dgm (Digiboard PC/Xem) - candidate for removal ? Message-ID: <19990318145652.B35553@pegasus.freibergnet.de> Reply-To: holm@freibergnet.de References: <199903180826.IAA09320@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95i In-Reply-To: <199903180826.IAA09320@keep.lan.Awfulhak.org>; from Brian Somers on Thu, Mar 18, 1999 at 08:26:06AM +0000 Organization: FreibergNet Internet Services X-Phone: +49-3731-781279 X-Fax: +49-3731-781377 X-PGP-fingerprint: 86 EC A5 63 B5 28 78 13 8B FC E9 09 04 6E 86 FC Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > Hi, > > Is there anyone out there that's willing to run some probe code for > me with an installed digiboard that currently uses the dgm driver in > -current or -stable ? I have an Digiboard PC/Xe if this makes sense here. Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 8: 7: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 8F45F1508C for ; Thu, 18 Mar 1999 08:00:01 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA21997 for ; Thu, 18 Mar 1999 11:04:02 -0500 (EST) Message-Id: <199903181604.LAA21997@etinc.com> X-Sender: dennis@etinc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 18 Mar 1999 10:52:56 -0500 To: hackers@freebsd.org From: Dennis Subject: NFS - Will it ever be fixed? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NFS continues, after many many years, to virtually lock up systems when the server goes away and anything on it is in the path. If you try to dismount it locks up also. Is there a way around the 3 hour waiting period (it seems) for the system to realize that the server is gone? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 8:34:24 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 819EB14E09 for ; Thu, 18 Mar 1999 08:34:15 -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 2.12 #1) id 10NfjX-000M0e-00; Thu, 18 Mar 1999 18:33:23 +0200 From: Sheldon Hearn To: Dennis Cc: hackers@freebsd.org Subject: Re: NFS - Will it ever be fixed? In-reply-to: Your message of "Thu, 18 Mar 1999 10:52:56 EST." <199903181604.LAA21997@etinc.com> Date: Thu, 18 Mar 1999 18:33:23 +0200 Message-ID: <84607.921774803@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Mar 1999 10:52:56 EST, Dennis wrote: > Is there a way around the 3 hour waiting period (it seems) for the system > to realize that the server is gone? There certainly is. Read the info(1) page for amd (am-utils). Specifically, see ``intr'' and ``soft'' under: Mount Maps -> Location Format -> Mount Options -> opts Option As an aside, the tone of your post wasn't called for. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 8:48: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 4BCC714E34 for ; Thu, 18 Mar 1999 08:47:52 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.8.8) with ESMTP id QAA58692; Thu, 18 Mar 1999 16:47:31 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA01588; Thu, 18 Mar 1999 16:35:34 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903181635.QAA01588@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: holm@freibergnet.de Cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: dgm (Digiboard PC/Xem) - candidate for removal ? In-reply-to: Your message of "Thu, 18 Mar 1999 14:56:52 +0100." <19990318145652.B35553@pegasus.freibergnet.de> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-10506572080" Date: Thu, 18 Mar 1999 16:35:34 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_-10506572080 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable > Brian Somers wrote: > = > > Hi, > > = > > Is there anyone out there that's willing to run some probe code for = > > me with an installed digiboard that currently uses the dgm driver in = > > -current or -stable ? > = > I have an Digiboard PC/Xe if this makes sense here. Great. Is it currently identified by the dgm driver (rather than the = dgb driver) ? If so, can you apply this patch and tell me what the = boot messages say ? TIA. > Holm > -- = > FreibergNet Systemhaus GbR Holm Tiffe * Administration, Developme= nt > Systemhaus f=FCr Daten- und Netzwerktechnik phone +49 3731 78= 1279 > Unternehmensgruppe Liebscher & Partner fax +49 3731 7813= 77 > D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.d= e/ -- = Brian Don't _EVER_ lose your sense of humour ! --==_Exmh_-10506572080 Content-Type: application/x-patch ; name="dgm.patch" Content-Description: dgm.patch Content-Disposition: attachment; filename="dgm.patch" Index: dgm.c =================================================================== RCS file: /home/ncvs/src/sys/gnu/i386/isa/dgm.c,v retrieving revision 1.7 diff -u -r1.7 dgm.c --- dgm.c 1999/01/30 12:17:32 1.7 +++ dgm.c 1999/02/13 21:37:14 @@ -239,25 +239,25 @@ static speed_t dgmdefaultrate = TTYDEF_SPEED; static struct speedtab dgmspeedtab[] = { - 0, FEP_B0, /* old (sysV-like) Bx codes */ - 50, FEP_B50, - 75, FEP_B75, - 110, FEP_B110, - 134, FEP_B134, - 150, FEP_B150, - 200, FEP_B200, - 300, FEP_B300, - 600, FEP_B600, - 1200, FEP_B1200, - 1800, FEP_B1800, - 2400, FEP_B2400, - 4800, FEP_B4800, - 9600, FEP_B9600, - 19200, FEP_B19200, - 38400, FEP_B38400, - 57600, (FEP_FASTBAUD|FEP_B50), /* B50 & fast baud table */ - 115200, (FEP_FASTBAUD|FEP_B110), /* B100 & fast baud table */ - -1, -1 + { 0, FEP_B0 }, /* old (sysV-like) Bx codes */ + { 50, FEP_B50 }, + { 75, FEP_B75 }, + { 110, FEP_B110 }, + { 134, FEP_B134 }, + { 150, FEP_B150 }, + { 200, FEP_B200 }, + { 300, FEP_B300 }, + { 600, FEP_B600 }, + { 1200, FEP_B1200 }, + { 1800, FEP_B1800 }, + { 2400, FEP_B2400 }, + { 4800, FEP_B4800 }, + { 9600, FEP_B9600 }, + { 19200, FEP_B19200 }, + { 38400, FEP_B38400 }, + { 57600, (FEP_FASTBAUD|FEP_B50) }, /* B50 & fast baud table */ + { 115200, (FEP_FASTBAUD|FEP_B110) }, /* B100 & fast baud table */ + { -1, -1 } }; static struct dbgflagtbl @@ -382,7 +382,9 @@ { struct dgm_softc *sc= &dgm_softc[dev->id_unit]; int i, v; +#ifdef DGB_DEBUG int unit=dev->id_unit; +#endif sc->unit=dev->id_unit; sc->port=dev->id_iobase; @@ -417,8 +419,15 @@ /* check type of card and get internal memory characteristics */ v=inb(sc->port); + + if (!(v & 0x1)) { + int second; - printf("dgm%d: PC/Xem\n",dev->id_unit); + outb(sc->port, 1); + second = inb(sc->port); + printf("dgm%d: PC/Xem (type %d, %d)\n",dev->id_unit, v, second); + } else + printf("dgm%d: PC/Xem (type %d)\n",dev->id_unit, v); sc->type=PCXEM; sc->mem_seg=0x8000; @@ -659,8 +668,6 @@ shrinkmem=0; } -/* HERE */ - port->txptr=mem+( ((bc->tseg)<<4) & 0x7FFF ); port->rxptr=mem+( ((bc->rseg)<<4) & 0x7FFF ); port->txwin=FEPWIN | ((bc->tseg)>>11); @@ -1886,7 +1893,6 @@ setwin(sc,0); head=bc->tin & wmask; -/*HERE*/ do { tail=bc->tout; } while (tail != bc->tout); tail=bc->tout & wmask; @@ -2105,7 +2111,4 @@ SYSINIT(dgmdev,SI_SUB_DRIVERS,SI_ORDER_MIDDLE+CDEV_MAJOR,dgm_drvinit,NULL) -int fi(){ - return 0; -} #endif /* NDGM > 0 */ --==_Exmh_-10506572080-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 12: 0:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id 55E771527B for ; Thu, 18 Mar 1999 12:00:21 -0800 (PST) (envelope-from ad@psn.ie) Received: from vmunix.psn.ie ([194.106.150.252]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10NiXL-00009c-00; Thu, 18 Mar 1999 19:32:59 +0000 Received: from localhost.psn.ie ([127.0.0.1] helo=localhost) by vmunix.psn.ie with esmtp (Exim 2.10 #1) id 10NiYM-00005I-00; Thu, 18 Mar 1999 19:34:02 +0000 Date: Thu, 18 Mar 1999 19:34:02 +0000 (GMT) From: Andy Doran To: Wes Peters Cc: Mike Spengler , hackers@freebsd.org Subject: Re: fxp driver causing lockup In-Reply-To: <36F04CD0.B0D46F3B@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 > > There was a FreeBSD 2.2.x -> 3.x change in which the driver is now responsible > > for setting the PCI busmaster enable bit. This may (or not) be your problem. > > In the fxp_attach() function, you should insert the following before doing > > the pci_map_mem() call: > > > > u_long val; > > > > val = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); > > val |= (PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN); > > pci_conf_write(config_id, PCI_COMMAND_STATUS_REG, val); > > > > Hope this helps! Thanks to all who helped out. I'll give this a shot tomorrow and let you know how it goes. Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 12:34:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from send1e.yahoomail.com (send1e.yahoomail.com [205.180.60.64]) by hub.freebsd.org (Postfix) with SMTP id 929B114CB8 for ; Thu, 18 Mar 1999 12:34:31 -0800 (PST) (envelope-from byteryder_98@yahoo.com) Message-ID: <19990318203246.637.rocketmail@send1e.yahoomail.com> Received: from [4.17.19.37] by send1e; Thu, 18 Mar 1999 12:32:46 PST Date: Thu, 18 Mar 1999 12:32:46 -0800 (PST) From: Byte Ryder Subject: Re: ipflow and ipfirewall To: Dag-Erling Smorgrav , Ruslan Ermilov Cc: Dag-Erling Smorgrav , dg@FreeBSD.ORG, hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---Dag-Erling Smorgrav wrote: > > Ruslan Ermilov writes: > > On Wed, Mar 17, 1999 at 08:58:09AM +0100, Dag-Erling Smorgrav wrote: > > > Ruslan Ermilov writes: > > > > Why it is not documented anywhere? > > > Why isn't most of FreeBSD documented anywhere? > > > or > > > How much are you willing to pay someone to do the work? > > Well, OK. > > Could you, _please_, document it in the inet.4 manpage, > > section ``MIB VARIABLES'', or ask dg@freebsd.org to do it? > > You missed my point. You asked why it wasn't documented, and my > questions were intended to make you understand why. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > I Don't understand why Ruslan can't post an addendum to the manpages. Nor do I begin to understand the "procedures" around the maintenance of this Public? software. Should I be reading the FAQ? _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 13:20:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 0D5FD14BF4; Thu, 18 Mar 1999 13:20:15 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id WAA76350; Thu, 18 Mar 1999 22:19:53 +0100 (CET) (envelope-from des) To: Byte Ryder Cc: questions@FreeBSD.ORG Subject: Re: ipflow and ipfirewall References: <19990318203246.637.rocketmail@send1e.yahoomail.com> From: Dag-Erling Smorgrav Date: 18 Mar 1999 22:19:52 +0100 In-Reply-To: Byte Ryder's message of "Thu, 18 Mar 1999 12:32:46 -0800 (PST)" Message-ID: Lines: 26 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to -questions] Byte Ryder writes: > I Don't understand why Ruslan can't post an addendum > to the manpages. Of course he can. > Nor do I begin to understand > the "procedures" around the maintenance of this > Public? software. FreeBSD is not "public software". It is developed by a group of individuals, partially supported by a number of private companies. Anyone can suggest changes, but only a relatively few people can commit them. There are currently a little less than 150 committers. > Should I be reading the FAQ? The answer to that is *always* "yes". DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 13:38:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak.texar.com (pak.texar.com [207.112.49.1]) by hub.freebsd.org (Postfix) with ESMTP id 8BBFB14EB5 for ; Thu, 18 Mar 1999 13:38:49 -0800 (PST) (envelope-from dseg@pak.texar.com) Received: (from dseg@localhost) by pak.texar.com (8.8.8/8.8.3) id QAA25519; Thu, 18 Mar 1999 16:39:49 -0500 (EST) Date: Thu, 18 Mar 1999 16:39:49 -0500 (EST) From: Dan Seguin To: freebsd-hackers@freebsd.org Subject: KLD extern calls 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 Hi all. Is it possible to make calls to std libs from within a KLD? For example, getpwuid()? If so, how does one link it in? I've tried ld by hand (specifying -lc), but get "bad exec format" when trying to load it. Otherwise, it just refuses to load, claiming "undefined symbol getpwuid". This is not limited to the abovementioned call. Any ideas, knowledge, help is appreciated. Dan Seguin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 13:42: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles114.castles.com [208.214.165.114]) by hub.freebsd.org (Postfix) with ESMTP id 9C7A4154DE for ; Thu, 18 Mar 1999 13:41:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA03345; Thu, 18 Mar 1999 13:35:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903182135.NAA03345@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dan Seguin Cc: freebsd-hackers@freebsd.org Subject: Re: KLD extern calls In-reply-to: Your message of "Thu, 18 Mar 1999 16:39:49 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Mar 1999 13:35:24 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is it possible to make calls to std libs from within a KLD? For example, > getpwuid()? If so, how does one link it in? I've tried ld by hand > (specifying -lc), but get "bad exec format" when trying to load it. > Otherwise, it just refuses to load, claiming "undefined symbol getpwuid". > This is not limited to the abovementioned call. Any ideas, knowledge, > help is appreciated. No. KLDs execute within the kernel, not in userspace. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 18 13:43:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox1.ucsd.edu (mailbox1.ucsd.edu [132.239.1.53]) by hub.freebsd.org (Postfix) with ESMTP id F18941550F for ; Thu, 18 Mar 1999 13:43:42 -0800 (PST) (envelope-from rjdawes@physics.ucsd.edu) Received: from physics.ucsd.edu (huntington.ucsd.edu [132.239.73.96]) by mailbox1.ucsd.edu (8.9.1a/8.9.1) with SMTP id NAA13274; Thu, 18 Mar 1999 13:43:23 -0800 (PST) Received: from localhost by physics.ucsd.edu (SMI-8.6/SMI-SVR4) id NAA03562; Thu, 18 Mar 1999 13:41:43 -0800 Date: Thu, 18 Mar 1999 13:41:43 -0800 (PST) From: "Richard J. Dawes" X-Sender: rjdawes@huntington Reply-To: Richard Dawes To: Chris Coleman Cc: "Matthew D. Fuller" , hackers@FreeBSD.ORG Subject: Re: Broken memory (was Re: Proposal: Define MAXMEM in GENERIC) 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 Hmm. So what about the that stuff about machines with >64 MB? Poor m/b design? (Just curious -- what m/b does the Presario have?) Thanks. --Rich On Wed, 17 Mar 1999, Chris Coleman wrote: > Date: Wed, 17 Mar 1999 23:26:37 -0800 (PST) > From: Chris Coleman > To: "Matthew D. Fuller" > Cc: Richard Dawes , hackers@FreeBSD.ORG > Subject: Re: Broken memory (was Re: Proposal: Define MAXMEM in GENERIC) > > I am having this problem now with my Compaq presario 9564. I am runnig > 2.2.6 and it only detects 16 meg and I have 24 in there. I thought it > might have been because the memory I added was not "Compaq" memory or > something like that. I will define MAXMEM and fix this tonite. :-) > > -Chris > > On Wed, 17 Mar 1999, Matthew D. Fuller wrote: > > > On Wed, Mar 17, 1999 at 08:53:12PM -0800, a little birdie told me > > that Richard J. Dawes remarked > > > Hello, all! > > > I have belatedly started reading this thread, and I am mystified > > > as to what is meant by "broken" hardware (which I take it is shipped > > > that way?), with regard to memory. What exactly is broken? Do some > > > cheapo motherboards use specific chips that are bad at managing memory? > > > I guess what I'm asking is if this problem is well-defined, and, > > > if so, some pointers on further information would greatly be appreci- > > > ated. (My quick perusal of HARDWARE.TXT produced nothing.) > > > > I suspect it's not a -hackers topic as such, but as long as it's here > > I'll leave it until somebody bites my head off. > > This was a Compaq Presario 9232, shipped with 16 megs of RAM and a P120. > > Bought it (on closeout) in August '96. I've seen this with the vast > > majority (I'm tempted to say all, but I'll err on the side of caution) of > > Compaq's I've seen exhibit this, even up through some 3.0 SNAP's from mid > > last year (I think). Define MAXMEM, you're golden. Don't, it'll only > > detect 16 megs. I don't know if the npx0 trick works on the later > > versions; I've always had space/etc to do custom kernels since then, so I > > haven't bothered. But under 2.1.6 I could never get it to recognize the > > full 24; only the first 16. > > > > > ======================================== > > > Richard J. Dawes rdawes@ucsd.edu > > > ======================================== > > > > > > > > --- > > > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > > | Matthew Fuller http://www.over-yonder.net/ | > > * fullermd@futuresouth.com fullermd@over-yonder.net * > > | UNIX Systems Administrator Specializing in FreeBSD | > > * FutureSouth Communications ISPHelp ISP Consulting * > > | "The only reason I'm burning my candle at both ends, | > > * is because I haven't figured out how to light the * > > | middle yet" | > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > > > > > > 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 > ======================================== Richard J. Dawes rdawes@ucsd.edu ======================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 13:45: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak.texar.com (pak.texar.com [207.112.49.1]) by hub.freebsd.org (Postfix) with ESMTP id E43E514DB4 for ; Thu, 18 Mar 1999 13:44:45 -0800 (PST) (envelope-from dseg@pak.texar.com) Received: (from dseg@localhost) by pak.texar.com (8.8.8/8.8.3) id QAA25535; Thu, 18 Mar 1999 16:45:31 -0500 (EST) Date: Thu, 18 Mar 1999 16:45:31 -0500 (EST) From: Dan Seguin To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: KLD extern calls In-Reply-To: <199903182135.NAA03345@dingo.cdrom.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, 18 Mar 1999, Mike Smith wrote: > > > > Is it possible to make calls to std libs from within a KLD? For example, > > getpwuid()? If so, how does one link it in? I've tried ld by hand > > (specifying -lc), but get "bad exec format" when trying to load it. > > Otherwise, it just refuses to load, claiming "undefined symbol getpwuid". > > This is not limited to the abovementioned call. Any ideas, knowledge, > > help is appreciated. > > No. KLDs execute within the kernel, not in userspace. > I feared as much. I thought maybe there was some kind of "bridge". Thanks for your help. Dan Seguin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 14:24:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 61A5414C0B for ; Thu, 18 Mar 1999 14:24:50 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id XAA08990; Thu, 18 Mar 1999 23:24:20 +0100 (CET) (envelope-from olli) Date: Thu, 18 Mar 1999 23:24:20 +0100 (CET) From: Oliver Fromme Message-Id: <199903182224.XAA08990@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Erorr: isa_dmainit(2, 1024) failed Cc: alc@cs.rice.edu Newsgroups: list.freebsd-hackers Organization: Administration Heim 3 Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alan Cox wrote in list.freebsd-hackers: > Please try the following simpler patch. It should accomplish > the same thing as Tor's patch. > > Replace the TAILQ_INSERT_TAIL in vm_page_startup (in vm_page.c) > with a TAILQ_INSERT_HEAD. That fixes kern/9515. I'd like to ask to commit that patch and close kern/9515. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 16: 3: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 66B8214E2C; Thu, 18 Mar 1999 16:03:01 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id BAA78555; Fri, 19 Mar 1999 01:02:34 +0100 (CET) (envelope-from des) To: Wes Peters Cc: Mike Spengler , hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: <199903172356.RAA14113@us.networkcs.com> <36F04CD0.B0D46F3B@softweyr.com> From: Dag-Erling Smorgrav Date: 19 Mar 1999 01:02:34 +0100 In-Reply-To: Wes Peters's message of "Wed, 17 Mar 1999 17:46:08 -0700" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > It did, it's working fine now. Here's the diff vs. 3.1-RELEASE: > [...] Hmm, I wonder if this will fix the "freeze while probing fxp0" bug as well. ISTR that's what's keeping FreeBSD out of IBM's list of recommended operating systems for the Netfinity. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 16: 6:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9C6C115541 for ; Thu, 18 Mar 1999 16:06:10 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id BAA78592; Fri, 19 Mar 1999 01:05:43 +0100 (CET) (envelope-from des) To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: NFS - Will it ever be fixed? References: <199903181604.LAA21997@etinc.com> From: Dag-Erling Smorgrav Date: 19 Mar 1999 01:05:43 +0100 In-Reply-To: Dennis's message of "Thu, 18 Mar 1999 10:52:56 -0500" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis writes: > NFS continues, after many many years, to virtually lock up systems > when the server goes away and anything on it is in the path. If you > try to dismount it locks up also. That's a feature, and it can easily be turned off. "Users continue, after many years, to refuse to read documentation, and blame their incompetence on the OS and its developers...." DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 17: 8: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id D702214F17 for ; Thu, 18 Mar 1999 17:07:54 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10NnmH-00042r-00; Fri, 19 Mar 1999 07:08:45 +0600 Date: Fri, 19 Mar 1999 07:08:45 +0600 (ALMT) From: Boris Popov To: Dan Seguin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KLD extern calls 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 Thu, 18 Mar 1999, Dan Seguin wrote: > Is it possible to make calls to std libs from within a KLD? For example, > getpwuid()? If so, how does one link it in? I've tried ld by hand No, you can't use stdlibs call without a user process. The simplest way is to create daemon which will call KLD via syscall. This call should sleep on entry. Whenever KLD want to call stdlib's function it should fill necessary arguments, wakeup sleeping call which will pass them back to daemon and receive reply via the same syscall. Of course, you should define a simple protocol between daemon and KLD and avoid mess with request/reply. The same goal can be achieved via socket interface. -- | Boris Popov | http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 18: 2:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 03D6015583 for ; Thu, 18 Mar 1999 18:02:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA42974; Thu, 18 Mar 1999 18:01:34 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Mar 1999 18:01:34 -0800 (PST) From: Matthew Dillon Message-Id: <199903190201.SAA42974@apollo.backplane.com> To: Oliver Fromme Cc: freebsd-hackers@FreeBSD.ORG, alc@cs.rice.edu Subject: Re: Erorr: isa_dmainit(2, 1024) failed References: <199903182224.XAA08990@dorifer.heim3.tu-clausthal.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Alan Cox wrote in list.freebsd-hackers: : > Please try the following simpler patch. It should accomplish : > the same thing as Tor's patch. : > : > Replace the TAILQ_INSERT_TAIL in vm_page_startup (in vm_page.c) : > with a TAILQ_INSERT_HEAD. : :That fixes kern/9515. :I'd like to ask to commit that patch and close kern/9515. : :Regards : Oliver : :-- :Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany :(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) Seems reasonable to me. Be sure to comment the reason for adding to the head instead of the tail, Alan. -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 Mar 18 19:50:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id EDBE8150A3 for ; Thu, 18 Mar 1999 19:50:26 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id WAA02769 for hackers@freebsd.org; Thu, 18 Mar 1999 22:56:53 -0500 From: Bill Paul Message-Id: <199903190356.WAA02769@skynet.ctr.columbia.edu> Subject: Gigabit ethernet revisited To: hackers@freebsd.org Date: Thu, 18 Mar 1999 22:56:52 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2436 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I'm still trying to squeeze the best possible performance out of the Tigon 2, but I've run into a bottleneck that I can't seem to sort out. First of all, transmission speed seems just fine: with jumbo frames enabled, I can blast 8K UDP packets at 840Mbps. (With the normal 1500byte MTU, I can get around 630Mbps. This is all without checksum offloading.) The problem is on the receive side. When I send all these UDP packets, the receiving host drops about 30% of them. Now, I know what you're going to say: UDP is unreliable, blah blah. But this is going through a single fiber patch from one host to another, so there's really nowhere for frames to get lost, assuming nice fast transfers between the NIC and the host. What seems to be happening is that while PCI read performance (transfering from host to NIC) is very good, PCI write performance (transfering from NIC to host) sucks. At the very least, it's about half what I think it should be. The nic stats counters show quite a few nicDmaWriteRingFull and nicNoMoreWrDMADescriptors errors, which means that the NIC is receiving the frames but the bus isn't transfering them to the host fast enough. The machines I'm using now are Dell Precision 410 workstations, each with one 450Mhz Pentium II CPU, 128MB of RAM and Intel 82443BX PCI chipsets. The manual says that there are certain things you have to do to insure that PCI Write and Invalidate is turned on, which I think I'm doing correctly. The 'write and invalidate' bit seems to be set in the PCI command register. I don't have a PCI bus analyzer so I'm sort of in the dark. I don't think I've done anything to horribly pessimize the receive handling code. I'm starting to run out of things to try. The latest driver revision is at http://www.freebsd.org/~wpaul/Alteon/3.0/tigon.tar.gz. The manuals for the Tigon chip are at http://www.alteon.com/support/openkits. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 19:52: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 2AD72154C1; Thu, 18 Mar 1999 19:51:45 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id UAA21187; Thu, 18 Mar 1999 20:51:22 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36F1C9B9.257D9269@softweyr.com> Date: Thu, 18 Mar 1999 20:51:21 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: <199903172356.RAA14113@us.networkcs.com> <36F04CD0.B0D46F3B@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 Dag-Erling Smorgrav wrote: > > Wes Peters writes: > > It did, it's working fine now. Here's the diff vs. 3.1-RELEASE: > > [...] > > Hmm, I wonder if this will fix the "freeze while probing fxp0" bug as > well. ISTR that's what's keeping FreeBSD out of IBM's list of > recommended operating systems for the Netfinity. I haven't seen any freezes while *probing* the fxp, but they may not really know the difference. The hang happened in the *attach*, when the user (or system) ifconfig's the interface up. Do you have any details, or a contact I can email? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 18 20: 5:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 09A5B15561; Thu, 18 Mar 1999 20:05:40 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id FAA81789; Fri, 19 Mar 1999 05:05:16 +0100 (CET) (envelope-from des) To: Wes Peters Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: <199903172356.RAA14113@us.networkcs.com> <36F04CD0.B0D46F3B@softweyr.com> <36F1C9B9.257D9269@softweyr.com> From: Dag-Erling Smorgrav Date: 19 Mar 1999 05:05:15 +0100 In-Reply-To: Wes Peters's message of "Thu, 18 Mar 1999 20:51:21 -0700" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > Dag-Erling Smorgrav wrote: > > Wes Peters writes: > > > It did, it's working fine now. Here's the diff vs. 3.1-RELEASE: > > > [...] > > Hmm, I wonder if this will fix the "freeze while probing fxp0" bug as > > well. ISTR that's what's keeping FreeBSD out of IBM's list of > > recommended operating systems for the Netfinity. > I haven't seen any freezes while *probing* the fxp, but they may not > really know the difference. The hang happened in the *attach*, when > the user (or system) ifconfig's the interface up. Do you have any > details, or a contact I can email? No, I've never had trouble with the fxp driver. It's something I saw mentioned on one of the lists - either -advocacy or -chat. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 20:25:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 7E94D14E88; Thu, 18 Mar 1999 20:25:25 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id VAA21268; Thu, 18 Mar 1999 21:24:55 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36F1D196.C7E58624@softweyr.com> Date: Thu, 18 Mar 1999 21:24:54 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: <199903172356.RAA14113@us.networkcs.com> <36F04CD0.B0D46F3B@softweyr.com> <36F1C9B9.257D9269@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 Dag-Erling Smorgrav wrote: > > Wes Peters writes: > > Dag-Erling Smorgrav wrote: > > > Wes Peters writes: > > > > It did, it's working fine now. Here's the diff vs. 3.1-RELEASE: > > > > [...] > > > > > > Hmm, I wonder if this will fix the "freeze while probing fxp0" bug as > > > well. ISTR that's what's keeping FreeBSD out of IBM's list of > > > recommended operating systems for the Netfinity. > > > > I haven't seen any freezes while *probing* the fxp, but they may not > > really know the difference. The hang happened in the *attach*, when > > the user (or system) ifconfig's the interface up. Do you have any > > details, or a contact I can email? > > No, I've never had trouble with the fxp driver. It's something I saw > mentioned on one of the lists - either -advocacy or -chat. Mike, I saw something in the -chat archives where you were beating up Brett Glass (always fun) w.r.t. problems with the NetFinity. You mention the "initialising fxp0 hangs" bug. Do you think this might have been the problem? Mine was on a Toshiba 7000S with on-board EEPro 100+; it was failing during the attach due to not having bus mastering turned on. Do you know anyone at IBM that can give this patch a try on a NetFinity with onboard EEPro 100 to see if it fixes the problem? If not, if they are willing to ship me a system for a few weeks I'm willing to beat on it until I get it working. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 18 20:30:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id A9B9C14E78 for ; Thu, 18 Mar 1999 20:30:12 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: (qmail 14056 invoked from network); 19 Mar 1999 04:29:53 -0000 Received: from nathan.enteract.com (dscheidt@207.229.143.6) by thor.enteract.com with SMTP; 19 Mar 1999 04:29:53 -0000 Date: Thu, 18 Mar 1999 22:29:35 -0600 (CST) From: David Scheidt To: hackers@FreeBSD.org Subject: Re: fxp driver causing lockup 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 19 Mar 1999, Dag-Erling Smorgrav wrote: : :Wes Peters writes: :> I haven't seen any freezes while *probing* the fxp, but they may not :> really know the difference. The hang happened in the *attach*, when :> the user (or system) ifconfig's the interface up. Do you have any :> details, or a contact I can email? : :No, I've never had trouble with the fxp driver. It's something I saw :mentioned on one of the lists - either -advocacy or -chat. The machine on my desk at work had this problem trying to install 3.0-RELEASE via NFS. The hang occurred at ifconfig up time, not boot time. I was worried that I wouldn't be able to use FreeBSD because of it. Not getting my constant unix fix would be a bad thing. The machine is a Compaq EN PII-350. Interestingly, it happened with my machine, but not with a cow-orkers which is exactly the same. (By actual inspection, not by model.) David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 21:26:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 202C415038 for ; Thu, 18 Mar 1999 21:25:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA44097; Thu, 18 Mar 1999 21:25:12 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Mar 1999 21:25:12 -0800 (PST) From: Matthew Dillon Message-Id: <199903190525.VAA44097@apollo.backplane.com> To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited References: <199903190356.WAA02769@skynet.ctr.columbia.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :it's about half what I think it should be. The nic stats counters :show quite a few nicDmaWriteRingFull and nicNoMoreWrDMADescriptors :errors, which means that the NIC is receiving the frames but the :bus isn't transfering them to the host fast enough. : :The machines I'm using now are Dell Precision 410 workstations, each :with one 450Mhz Pentium II CPU, 128MB of RAM and Intel 82443BX PCI :chipsets. It sounds like the DMA is working fine, but the host computer is not able to drain the receive ring ( which I presume is the 'write ring' ) quickly enough. Your current code appears to allocate a sufficient number of buffers, but your ti_refill_rx_rings() optimization is suspect... you do not call it until you have *COMPLETELY* drained the RX ring of packets. What happens if new packets are streaming in faster then you can drain them? You will completely exhaust your RX ring before you reallocate it's buffers. I would also suggest figuring out *exactly* why you are getting the error message... i.e. is the RX ring actually completely used up as of the time the error occurs? -Matt Matthew Dillon :http://www.freebsd.org/~wpaul/Alteon/3.0/tigon.tar.gz. The manuals :for the Tigon chip are at http://www.alteon.com/support/openkits. : :-Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 21:27:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 525BB14E60 for ; Thu, 18 Mar 1999 21:27:28 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id XAA24289 for ; Thu, 18 Mar 1999 23:27:09 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id XAA94607 for freebsd-hackers@freebsd.org; Thu, 18 Mar 1999 23:27:09 -0600 (CST) Date: Thu, 18 Mar 1999 23:27:08 -0600 From: Alan Cox To: freebsd-hackers@freebsd.org Subject: Re: Erorr: isa_dmainit(2, 1024) failed Message-ID: <19990318232708.A89403@nonpc.cs.rice.edu> References: <199903182224.XAA08990@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199903182224.XAA08990@dorifer.heim3.tu-clausthal.de>; from Oliver Fromme on Thu, Mar 18, 1999 at 11:24:20PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 18, 1999 at 11:24:20PM +0100, Oliver Fromme wrote: > > That fixes kern/9515. > I'd like to ask to commit that patch and close kern/9515. > It's a hack, and not a real solution to the underlying problem, but it won't break anything that we (John, David, Matt, me, etc.) can think of ... so I've committed it to -current. -stable will follow in a few days. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 22:38: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 6099F14EDC for ; Thu, 18 Mar 1999 22:38:01 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA21524; Thu, 18 Mar 1999 23:37:36 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36F1F0B0.F8F79F22@softweyr.com> Date: Thu, 18 Mar 1999 23:37:36 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: David Scheidt Cc: hackers@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > > On 19 Mar 1999, Dag-Erling Smorgrav wrote: > > : > :Wes Peters writes: > :> I haven't seen any freezes while *probing* the fxp, but they may not > :> really know the difference. The hang happened in the *attach*, when > :> the user (or system) ifconfig's the interface up. Do you have any > :> details, or a contact I can email? > : > :No, I've never had trouble with the fxp driver. It's something I saw > :mentioned on one of the lists - either -advocacy or -chat. > > The machine on my desk at work had this problem trying to install 3.0-RELEASE > via NFS. The hang occurred at ifconfig up time, not boot time. I was > worried that I wouldn't be able to use FreeBSD because of it. Not getting > my constant unix fix would be a bad thing. The machine is a Compaq EN PII-350. > Interestingly, it happened with my machine, but not with a cow-orkers which > is exactly the same. (By actual inspection, not by model.) Booting it under Windows, disabling the interface, then booting to FreeBSD will probably bring it up. On the other hand, if you have kernel sources on-line, applying the patch will fix the problem so it'll work under FreeBSD without the intervention of MS-Virus. I'll send the patch in a separate message, it's already been posted to several of the mailing lists. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 18 23:25:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pegasus.freibergnet.de (pegasus.freibergnet.de [194.123.255.9]) by hub.freebsd.org (Postfix) with ESMTP id 6B8DB14D02 for ; Thu, 18 Mar 1999 23:25:24 -0800 (PST) (envelope-from holm@pegasus.freibergnet.de) Received: (from holm@localhost) by pegasus.freibergnet.de (8.9.3/8.9.1) id IAA37097; Fri, 19 Mar 1999 08:23:43 +0100 (CET) (envelope-from holm) Date: Fri, 19 Mar 1999 08:23:43 +0100 From: Holm Tiffe To: Brian Somers Cc: holm@freibergnet.de, freebsd-hackers@FreeBSD.ORG Subject: Re: dgm (Digiboard PC/Xem) - candidate for removal ? Message-ID: <19990319082343.A37059@pegasus.freibergnet.de> Reply-To: holm@freibergnet.de References: <19990318145652.B35553@pegasus.freibergnet.de> <199903181635.QAA01588@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95i In-Reply-To: <199903181635.QAA01588@keep.lan.Awfulhak.org>; from Brian Somers on Thu, Mar 18, 1999 at 04:35:34PM +0000 Organization: FreibergNet Internet Services X-Phone: +49-3731-781279 X-Fax: +49-3731-781377 X-PGP-fingerprint: 86 EC A5 63 B5 28 78 13 8B FC E9 09 04 6E 86 FC Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > Brian Somers wrote: > > > > > Hi, > > > > > > Is there anyone out there that's willing to run some probe code for > > > me with an installed digiboard that currently uses the dgm driver in > > > -current or -stable ? > > > > I have an Digiboard PC/Xe if this makes sense here. > > Great. Is it currently identified by the dgm driver (rather than the > dgb driver) ? Currently it is working using the the dgb driver, I'll try to build a kernel with the dgm driver using your patches over the weekend (since this board is in my home machine). You hear from me, Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 18 23:41:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id D625614DFA; Thu, 18 Mar 1999 23:41:35 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id AAA21668; Fri, 19 Mar 1999 00:41:15 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36F1FF9B.1CD96ACB@softweyr.com> Date: Fri, 19 Mar 1999 00:41:15 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: sos@freebsd.org Cc: hackers@freebsd.org Subject: wst driver status Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How is the wst driver these days? I've just noticed the OnStream ADR drives, which support 15GB uncompressed on a single cartridge. They offer this system with an IDE interface at $299, and a SCSI-2 version at $599. I need a backup system and don't have SCSI in the machine, so if there is any hope at all of having the IDE version work, I think I'll grab one. http://www.onstream.com/adr CDW and MicroWarehouse both have this in stock and shipping for the advertised price, $299, so it appears to be real. I didn't see any- thing like technical information on their web site, but I've just emailed their "System Builders" contact, Frank Woodward, about getting detailed specs. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 19 0:11:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 0F2CB15151 for ; Fri, 19 Mar 1999 00:10:20 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id AAA36424 for ; Fri, 19 Mar 1999 00:08:34 -0800 (PST) Date: Fri, 19 Mar 1999 00:08:33 -0800 (PST) From: Julian Elischer To: hackers@freebsd.org Subject: Exctracting stuff from PRs 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 Sometimes people submit code in a PR (in fact we encourage this). Unfortunatly they often include the code as an attachment, so it appears in the PR database as some 'encoded' form of data. If we could get teh PR gatabase to send these mailing back out as mail again we'd be able to extract the file susing mail agents, however the only this we can do is run edit-pr and the web interface. neither of which knows how to handle MIME enclosures. How do other people cope with this? For a trivial example.. see misc/8139. this has submissions in the audit trail, with the headers Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable so there are funny things in the source like "if [ "${1}X" =3D "X" ]" but one could extract it buy hand and edit it correct. But I've seen people submitting them with 'Base64' and other similar unreadable encodings. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 0:26:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles356.castles.com [208.214.167.56]) by hub.freebsd.org (Postfix) with ESMTP id CB70514C15 for ; Fri, 19 Mar 1999 00:26:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA04832; Fri, 19 Mar 1999 00:20:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903190820.AAA04832@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wes Peters Cc: hackers@FreeBSD.ORG Subject: Re: fxp driver causing lockup In-reply-to: Your message of "Thu, 18 Mar 1999 21:24:54 MST." <36F1D196.C7E58624@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Mar 1999 00:20:46 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike, I saw something in the -chat archives where you were beating up > Brett Glass (always fun) w.r.t. problems with the NetFinity. You > mention the "initialising fxp0 hangs" bug. Do you think this might > have been the problem? Mine was on a Toshiba 7000S with on-board > EEPro 100+; it was failing during the attach due to not having bus > mastering turned on. Anyone's guess, but the symptoms match. > Do you know anyone at IBM that can give this patch a try on a NetFinity > with onboard EEPro 100 to see if it fixes the problem? If not, if they > are willing to ship me a system for a few weeks I'm willing to beat on > it until I get it working. Anyone with a Netfinity 3000 or 3500 with the onboard fxp is invited to try this; failing that I guess it's almost time to take another day down to San Mateo and go through their rack again. I wouldn't mind a better chance of supporting the AMD PC-NET PCI parts though; they use them too... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Fri Mar 19 0:27:26 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 2104514DAB; Fri, 19 Mar 1999 00:27:23 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA30428; Fri, 19 Mar 1999 09:26:59 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903190826.JAA30428@freebsd.dk> Subject: Re: wst driver status In-Reply-To: <36F1FF9B.1CD96ACB@softweyr.com> from Wes Peters at "Mar 19, 1999 0:41:15 am" To: wes@softweyr.com (Wes Peters) Date: Fri, 19 Mar 1999 09:26:58 +0100 (CET) Cc: sos@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Wes Peters wrote: > How is the wst driver these days? I've just noticed the OnStream ADR > drives, which support 15GB uncompressed on a single cartridge. They > offer this system with an IDE interface at $299, and a SCSI-2 version > at $599. I need a backup system and don't have SCSI in the machine, > so if there is any hope at all of having the IDE version work, I > think I'll grab one. > > http://www.onstream.com/adr > > CDW and MicroWarehouse both have this in stock and shipping for the > advertised price, $299, so it appears to be real. I didn't see any- > thing like technical information on their web site, but I've just > emailed their "System Builders" contact, Frank Woodward, about getting > detailed specs. If it follows the ATAPI spec it should just work, but that remains to be tested. There is hope that I'll get my hands on one though, if that succeeds I'll make it work :) -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 Mar 19 0:33:56 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 0036F15609 for ; Fri, 19 Mar 1999 00:33:36 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id TAA20203; Fri, 19 Mar 1999 19:02:24 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [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: Fri, 19 Mar 1999 19:02:23 +1030 (CST) From: "Daniel O'Connor" To: Julian Elischer Subject: RE: Exctracting stuff from PRs Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Mar-99 Julian Elischer wrote: > If we could get teh PR gatabase to send these mailing back out as mail > again we'd be able to extract the file susing mail agents, however > the only this we can do is run edit-pr and the web interface. > neither of which knows how to handle MIME enclosures. > > How do other people cope with this? > > For a trivial example.. see misc/8139. this has submissions in the audit > trail, with the headers > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > so there are funny things in the source like > "if [ "${1}X" =3D "X" ]" > but one could extract it buy hand and edit it correct. > But I've seen people submitting them with 'Base64' > and other similar unreadable encodings. You could try getting your mail reader to process it.. I haven't tried, but it should deal with the MIME'ness of message in question. --- 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 Fri Mar 19 4: 0:17 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 68B791559C for ; Fri, 19 Mar 1999 04:00:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA04951; Fri, 19 Mar 1999 21:00:08 +0900 (JST) Message-ID: <36F2397A.24363F1B@newsguy.com> Date: Fri, 19 Mar 1999 20:48:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Julian Elischer , hackers@freebsd.org Subject: Re: Exctracting stuff from PRs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Sometimes people submit code in a PR (in fact we encourage this). > Unfortunatly they often include the code as an attachment, > so it appears in the PR database as some 'encoded' form of data. > > If we could get teh PR gatabase to send these mailing back out as mail > again we'd be able to extract the file susing mail agents, however > the only this we can do is run edit-pr and the web interface. > neither of which knows how to handle MIME enclosures. > > How do other people cope with this? As it was once pointed out to me, you can cvsup them. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 4:42:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tpg.tpg.edu.ee (vee-gw.tpg.edu.ee [193.40.40.139]) by hub.freebsd.org (Postfix) with ESMTP id 1B4E0156A0 for ; Fri, 19 Mar 1999 04:41:45 -0800 (PST) (envelope-from igor_f@tpg.edu.ee) Received: from andrei (andrei.tpg.edu.ee [193.40.51.114]) by tpg.tpg.edu.ee (8.8.8/8.8.8) with SMTP id OAA11848 for ; Fri, 19 Mar 1999 14:44:36 +0200 (EET) (envelope-from igor_f@tpg.edu.ee) Message-ID: <000b01be7206$4b79db40$723328c1@andrei> From: "Igor Feklin" To: Subject: SUBSCRIBE Date: Fri, 19 Mar 1999 14:44:56 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01BE7217.0E4A09A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0008_01BE7217.0E4A09A0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Thank You! ------=_NextPart_000_0008_01BE7217.0E4A09A0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
Thank=20 You!
------=_NextPart_000_0008_01BE7217.0E4A09A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 4:56:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id C037F14FDD for ; Fri, 19 Mar 1999 04:56:06 -0800 (PST) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.9.3/8.9.3) id HAA02053 for freebsd-hackers@FreeBSD.ORG; Fri, 19 Mar 1999 07:55:47 -0500 (EST) (envelope-from sjr) Message-Id: <199903191255.HAA02053@istari.home.net> Date: Fri, 19 Mar 1999 07:55:47 -0500 (EST) From: "Stephen J. Roznowski" Subject: Re: Use of "register" in code To: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199903160333.WAA06493@istari.home.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Mar, I asked: > I've been looking at merging some NetBSD fixes for games, and I noticed > that they have removed the "register" declaration from (at least) this > section of the code tree. > > Are these register declarations useful, or are they just "historical > artifacts"? If they are just historical artifacts, should they be > removed? Apparently, the consensus is that these are just historical artifacts... What is the opinion on removing these? (If I send in a PR with the changes would it get committed?) Thanks, -SR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 5: 3:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id 400F914E78 for ; Fri, 19 Mar 1999 05:03:48 -0800 (PST) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.9.3/8.9.3) id IAA02072 for freebsd-hackers@FreeBSD.ORG; Fri, 19 Mar 1999 08:03:29 -0500 (EST) (envelope-from sjr) Message-Id: <199903191303.IAA02072@istari.home.net> Date: Fri, 19 Mar 1999 08:03:29 -0500 (EST) From: "Stephen J. Roznowski" Subject: Conversion to ANSI C To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the NetBSD mailing lists, there is a discussion about converting their source code to ANSI (vice K&R), see: http://mail-index.netbsd.org/tech-misc/1999/03/ Are there any thoughts about following this? -- Stephen J. Roznowski (sjr@home.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 5:41: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C9DE514F97 for ; Fri, 19 Mar 1999 05:41:03 -0800 (PST) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port18.netsvr1.cst.vastnet.net [207.252.73.18]) by etinc.com (8.8.8/8.6.9) with SMTP id IAA03806; Fri, 19 Mar 1999 08:39:17 -0500 (EST) Message-Id: <199903191339.IAA03806@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 19 Mar 1999 08:51:41 -0500 To: Dag-Erling Smorgrav From: Dennis Subject: Re: NFS - Will it ever be fixed? Cc: hackers@FreeBSD.ORG In-Reply-To: References: <199903181604.LAA21997@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:05 AM 3/19/99 +0100, Dag-Erling Smorgrav wrote: >Dennis writes: >> NFS continues, after many many years, to virtually lock up systems >> when the server goes away and anything on it is in the path. If you >> try to dismount it locks up also. > >That's a feature, and it can easily be turned off. > >"Users continue, after many years, to refuse to read documentation, >and blame their incompetence on the OS and its developers...." > >DES Any clues on how? Docs on nfsd and mountd dont seem to mention anything. Incompetence is a function of available information. Dennis ------------------------------------------------------------------------- http://www.etinc.com T1/T3 boards for FreeBSD and Linux Bandwidth Management for FreeBSD and BSD/OS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 5:59:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from europa.salford.ac.uk (europa.salford.ac.uk [146.87.3.2]) by hub.freebsd.org (Postfix) with SMTP id 2B652153A1 for ; Fri, 19 Mar 1999 05:58:32 -0800 (PST) (envelope-from M.S.Powell@ais.salford.ac.uk) Received: (qmail 29507 invoked by alias); 19 Mar 1999 13:57:28 -0000 Received: (qmail 29500 invoked from network); 19 Mar 1999 13:57:27 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by europa.salford.ac.uk with SMTP; 19 Mar 1999 13:57:27 -0000 Received: (qmail 33206 invoked by alias); 19 Mar 1999 13:57:21 -0000 Delivered-To: catchall-freebsd-hackers@freebsd.org Received: (qmail 33197 invoked by uid 141); 19 Mar 1999 13:57:21 -0000 Date: Fri, 19 Mar 1999 13:57:21 +0000 (GMT) From: Mark Powell To: freebsd-hackers@freebsd.org Subject: Re: NFS - Will it ever be fixed? 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 In article <7ctk6q$6t9$1@ananke.salford.ac.uk>, Dennis wrote: >At 01:05 AM 3/19/99 +0100, Dag-Erling Smorgrav wrote: >>Dennis writes: >>> NFS continues, after many many years, to virtually lock up systems >>> when the server goes away and anything on it is in the path. If you >>> try to dismount it locks up also. >> >>That's a feature, and it can easily be turned off. >> >>"Users continue, after many years, to refuse to read documentation, >>and blame their incompetence on the OS and its developers...." > >Any clues on how? > >Docs on nfsd and mountd dont seem to mention anything. You haven't looked at 'man mount_nfs' for all those years? Just to confuse the issue and to show it's not FreeBSD specific, from Solaris 2.6 'man mount_nfs': ... soft|hard Return an error if the server does not respond, or continue the retry request until the server responds. The default value is hard. ... intr|nointr Allow (do not allow) keyboard interrupts to kill a process that is hung while waiting for a response on a hard-mounted file system. The default is intr. ... Thus, something like "rw,bg,soft,intr" as your nfs options may help with FreeBSD's broken NFS (sic). Mark Powell - System Administrator (UNIX) - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 6: 9:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id CF3F0155EE for ; Fri, 19 Mar 1999 06:09:34 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA03718; Fri, 19 Mar 1999 09:15:54 -0500 From: Bill Paul Message-Id: <199903191415.JAA03718@skynet.ctr.columbia.edu> Subject: Re: Gigabit ethernet revisited To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 19 Mar 1999 09:15:53 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199903190525.VAA44097@apollo.backplane.com> from "Matthew Dillon" at Mar 18, 99 09:25:12 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3429 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > :it's about half what I think it should be. The nic stats counters > :show quite a few nicDmaWriteRingFull and nicNoMoreWrDMADescriptors > :errors, which means that the NIC is receiving the frames but the > :bus isn't transfering them to the host fast enough. > : > :The machines I'm using now are Dell Precision 410 workstations, each > :with one 450Mhz Pentium II CPU, 128MB of RAM and Intel 82443BX PCI > :chipsets. > > It sounds like the DMA is working fine, but the host computer > is not able to drain the receive ring ( which I presume is the > 'write ring' ) quickly enough. No, I don't think that's it. I think the DMA isn't going fast enough. The 'WriteRing' in question is a ring of DMA descriptors inside the NIC, which the firmware is supposed to be managing. There's also a DmaReadRing for the transmit side. > Your current code appears to allocate a sufficient number of buffers, > but your ti_refill_rx_rings() optimization is suspect... you do not > call it until you have *COMPLETELY* drained the RX ring of packets. > What happens if new packets are streaming in faster then you can drain > them? You will completely exhaust your RX ring before you reallocate > it's buffers. There are a couple of tuning parameters that control when the NIC will interrupt the host to check the receive ring: ti_rx_coal_ticks and ti_rx_max_coal_bds. The former is the number of microseconds that can elapse before the NIC will be forced to interrupt, and the latter is the number of descriptors to wait to be accumulated before generating an interrupt. Right now, I set things for 500 microseconds and 64 buffer descriptors, and in my tests this usually results in buffers being DMAed in chunks of 16 or so. (I addedm some instrumentation to check this.) So I don't think the RX ring is getting anywhere near drained. For giggles, I cranked thinks up so that it DMA'ed a couple hundred a shot before interrupting and it was still too slow, and that was with all 512 entries in the receive ring filled up. > I would also suggest figuring out *exactly* why you are getting the > error message... i.e. is the RX ring actually completely used up as of > the time the error occurs? The firmware source code is somewhat... opaque. But basically it means that the NIC has received frames and wants to queue them onto the DMA write ring, but that ring is already full. In other words, the MAC part of the NIC is getting the all the frames and wants to get them into the host, but the DMA is proceeding so slowly that it can't move them all and has to drop some. I'm not discounting the possibility that the receive handler is botching things somehow, but I don't think the problem is lack of space in the receive ring. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 6:23:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 0713615208 for ; Fri, 19 Mar 1999 06:23:29 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id PAA89428; Fri, 19 Mar 1999 15:23:06 +0100 (CET) (envelope-from des) To: Dennis Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: NFS - Will it ever be fixed? References: <199903181604.LAA21997@etinc.com> <199903191339.IAA03806@etinc.com> From: Dag-Erling Smorgrav Date: 19 Mar 1999 15:23:05 +0100 In-Reply-To: Dennis's message of "Fri, 19 Mar 1999 08:51:41 -0500" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis writes: > Any clues on how? > > Docs on nfsd and mountd dont seem to mention anything. You're looking at the wrong man pages. You want the man pages for the *client*, not for the server. The client is mount_nfsd. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 6:46:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 5A12C15151 for ; Fri, 19 Mar 1999 06:46:22 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id HAA22332; Fri, 19 Mar 1999 07:45:50 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36F2631E.5D968EEB@softweyr.com> Date: Fri, 19 Mar 1999 07:45:50 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Dennis , hackers@FreeBSD.ORG Subject: Re: NFS - Will it ever be fixed? References: <199903181604.LAA21997@etinc.com> <199903191339.IAA03806@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Dennis writes: > > Any clues on how? > > > > Docs on nfsd and mountd dont seem to mention anything. > > You're looking at the wrong man pages. You want the man pages for the > *client*, not for the server. The client is mount_nfsd. I can recommend a copy of O'Reilly's book on "Administering NFS and NIS" at this point as well. While the commands are not *exactly* correct for FreeBSD, the administration tips and general information about how NFS works and how to use it effectively are invaluable for newbies. That and a careful reading of the man pages to figure out how to do what they recommon on FreeBSD should help a lot. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 19 6:51:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id A9F7914EDD; Fri, 19 Mar 1999 06:51:40 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id HAA22336; Fri, 19 Mar 1999 07:49:16 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36F263EB.EF936E5@softweyr.com> Date: Fri, 19 Mar 1999 07:49:15 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?S=F8ren?= Schmidt Cc: sos@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: wst driver status References: <199903190826.JAA30428@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Søren Schmidt" wrote: > > It seems Wes Peters wrote: > > How is the wst driver these days? I've just noticed the OnStream ADR > > drives, which support 15GB uncompressed on a single cartridge. They > > offer this system with an IDE interface at $299, and a SCSI-2 version > > at $599. I need a backup system and don't have SCSI in the machine, > > so if there is any hope at all of having the IDE version work, I > > think I'll grab one. > > > > http://www.onstream.com/adr > > > > CDW and MicroWarehouse both have this in stock and shipping for the > > advertised price, $299, so it appears to be real. I didn't see any- > > thing like technical information on their web site, but I've just > > emailed their "System Builders" contact, Frank Woodward, about getting > > detailed specs. > > If it follows the ATAPI spec it should just work, but that remains to > be tested. There is hope that I'll get my hands on one though, if > that succeeds I'll make it work :) If I buy one and it doesn't work, I'll be glad to send it to you along with whatever doco I can get my hands on. If you've got a channel to get a free one, by all means don't let me stop you! ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 19 6:58:27 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 A350A14DCA; Fri, 19 Mar 1999 06:58:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA31337; Fri, 19 Mar 1999 15:57:49 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903191457.PAA31337@freebsd.dk> Subject: Re: wst driver status In-Reply-To: <36F263EB.EF936E5@softweyr.com> from Wes Peters at "Mar 19, 1999 7:49:15 am" To: wes@softweyr.com (Wes Peters) Date: Fri, 19 Mar 1999 15:57:49 +0100 (CET) Cc: sos@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Wes Peters wrote: > "Søren Schmidt" wrote: > > > > It seems Wes Peters wrote: > > > How is the wst driver these days? I've just noticed the OnStream ADR > > > drives, which support 15GB uncompressed on a single cartridge. They > > > offer this system with an IDE interface at $299, and a SCSI-2 version > > > at $599. I need a backup system and don't have SCSI in the machine, > > > so if there is any hope at all of having the IDE version work, I > > > think I'll grab one. > > > > > > http://www.onstream.com/adr > > > > > > CDW and MicroWarehouse both have this in stock and shipping for the > > > advertised price, $299, so it appears to be real. I didn't see any- > > > thing like technical information on their web site, but I've just > > > emailed their "System Builders" contact, Frank Woodward, about getting > > > detailed specs. > > > > If it follows the ATAPI spec it should just work, but that remains to > > be tested. There is hope that I'll get my hands on one though, if > > that succeeds I'll make it work :) > > If I buy one and it doesn't work, I'll be glad to send it to you along > with whatever doco I can get my hands on. If you've got a channel to > get a free one, by all means don't let me stop you! ;^) I might have, its not settled yet, but if that fails, and there is problems with it, I'll take you up on that offer :) -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 Mar 19 7: 4:58 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 9B2D414DCA for ; Fri, 19 Mar 1999 07:04:51 -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 2.12 #1) id 10O0oV-000NjV-00; Fri, 19 Mar 1999 17:03:55 +0200 From: Sheldon Hearn To: Dennis Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: NFS - Will it ever be fixed? In-reply-to: Your message of "Fri, 19 Mar 1999 08:51:41 EST." <199903191339.IAA03806@etinc.com> Date: Fri, 19 Mar 1999 17:03:55 +0200 Message-ID: <91232.921855835@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Mar 1999 08:51:41 EST, Dennis wrote: > Docs on nfsd and mountd dont seem to mention anything. > > Incompetence is a function of available information. Hi Dennis, The information is available. Have a look at /usr/share/doc/smm/06.nfs/paper.ascii.gz, particularly section 3, entitled "Dealing with Hung Servers". Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 7:16:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from exchange.worldmediaco.net (unknown [207.252.122.245]) by hub.freebsd.org (Postfix) with ESMTP id 1C36914D81 for ; Fri, 19 Mar 1999 07:16:45 -0800 (PST) (envelope-from cwatson@WorldMediaCo.net) Received: by EXCHANGE with Internet Mail Service (5.5.2232.9) id ; Fri, 19 Mar 1999 09:15:27 -0600 Message-ID: <81936838EBB9D2118647006008C0A387C684@EXCHANGE> From: "Watson, chris" To: "'freebsd-hackers@freebsd.org'" Subject: Found a driver for IDT's ATM nicstar driver. Date: Fri, 19 Mar 1999 09:15:25 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found this while searching for something else FreeBSD related. Do we support the IDT Nicstar ATM card. If not these people have a driver available for FreeBSD and it's under a BSD license. http://www.pluris.com/~dave/nicstar/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 9:39:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D7DE714D02 for ; Fri, 19 Mar 1999 09:39:42 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA59302; Fri, 19 Mar 1999 09:39:14 -0800 (PST) (envelope-from dillon) Date: Fri, 19 Mar 1999 09:39:14 -0800 (PST) From: Matthew Dillon Message-Id: <199903191739.JAA59302@apollo.backplane.com> To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited References: <199903191415.JAA03718@skynet.ctr.columbia.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :No, I don't think that's it. I think the DMA isn't going fast enough. :The 'WriteRing' in question is a ring of DMA descriptors inside the :NIC, which the firmware is supposed to be managing. There's also a :DmaReadRing for the transmit side. :.. :> Your current code appears to allocate a sufficient number of buffers, :> but your ti_refill_rx_rings() optimization is suspect... you do not :> call it until you have *COMPLETELY* drained the RX ring of packets. :> What happens if new packets are streaming in faster then you can drain :> them? You will completely exhaust your RX ring before you reallocate :> it's buffers. : :There are a couple of tuning parameters that control when the NIC :will interrupt the host to check the receive ring: ti_rx_coal_ticks and :ti_rx_max_coal_bds. The former is the number of microseconds that can :elapse before the NIC will be forced to interrupt, and the latter is :the number of descriptors to wait to be accumulated before generating :an interrupt. Right now, I set things for 500 microseconds and 64 :buffer descriptors, and in my tests this usually results in buffers :being DMAed in chunks of 16 or so. (I addedm some instrumentation to :check this.) So I don't think the RX ring is getting anywhere near :drained. Hmm. I definitely think there's a bug due to not repopulating buffers from inside your receive interrupt packet processing loop, but it may not be the cause of this bug. If the NIC is unable to complete DMA quickly enough, perhaps the burst parameters can be tweaked. The PC certainly should be able to do DMA writes to memory at the PCI bus speed! Ok, lets see... what about these: Read Max DMA parameter Write Max DMA parameter Minimum DMA parameter PCI Latency Timer / system PCI latency timer At a guess, I think you would want: Read Max DMA parameter 16 Write Max DMA parameter 128 Minimum DMA parameter 128 PCI Latency Timer relatively high for this board ( if you have a per-board choice, you may not ) :write ring, but that ring is already full. In other words, the MAC :part of the NIC is getting the all the frames and wants to get them :into the host, but the DMA is proceeding so slowly that it can't move :them all and has to drop some. : :I'm not discounting the possibility that the receive handler is botching :things somehow, but I don't think the problem is lack of space in the :receive ring. : :-Bill -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 Mar 19 9:51:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 42F0E14EE6; Fri, 19 Mar 1999 09:49:52 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2232.9) id ; Fri, 19 Mar 1999 10:49:32 -0700 Message-ID: <64003B21ECCAD11185C500805F31EC03022B5EF3@houston.matchlogic.com> From: Charles Randall To: freebsd-questions@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: RE: 3.1: Link with static a.out lib? Date: Fri, 19 Mar 1999 10:49:32 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've Cc'd freebsd-hackers in an attempt to reach a wider audience. With the help of Michael E. Mercer [mmercer@ipass.net] I'm now using gcc's "-aout" option (which appears to be undocumented) but I still get the following message when compiling on 3.1R, % gcc -aout test.c libInOldAoutFormat.a ld: crt0.o: No such file or directory Again, 1. Is this possible? 2. Are there instructions for doing this? Thanks, Charles > -----Original Message----- > From: Charles Randall > Sent: Wednesday, March 17, 1999 11:37 AM > To: 'freebsd-questions@freebsd.org' > Subject: 3.1: Link with static a.out lib? > > I have a 3rd-party static library in a.out format for > FreeBSD 2.2.2. This works fine on FreeBSD 2.2.8. > > However, because of the a.out->elf conversion, I'm having problems > linking this into a program when building on FreeBSD 3.1. > > 1. Is this possible? > 2. Are there instructions for doing this available somewhere? > > Thanks, > Charles > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 10:16:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id BD257150A3 for ; Fri, 19 Mar 1999 10:15:53 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id NAA25554; Fri, 19 Mar 1999 13:15:28 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id NAA07603; Fri, 19 Mar 1999 13:15:03 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 19 Mar 1999 13:15:03 -0500 (EST) To: Matthew Dillon Cc: Bill Paul , hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited In-Reply-To: <199903191739.JAA59302@apollo.backplane.com> References: <199903191415.JAA03718@skynet.ctr.columbia.edu> <199903191739.JAA59302@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14066.37142.414291.953962@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > Hmm. I definitely think there's a bug due to not repopulating buffers > from inside your receive interrupt packet processing loop, but it may > not be the cause of this bug. Insufficient Rx buffer descriptors isn't the cause of this. If it were, we'd be seeing the firmware complaining about nicNoMoreRxBDs, rather than nicDmaWriteRingFull. > If the NIC is unable to complete DMA quickly enough, perhaps the burst > parameters can be tweaked. The PC certainly should be able to do DMA > writes to memory at the PCI bus speed! I agree that the pci tuning parameters are the best candidates for optimization. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 10:46: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C0F7614FFF for ; Fri, 19 Mar 1999 10:45:49 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id KAA56110; Fri, 19 Mar 1999 10:41:58 -0800 (PST) Message-ID: <36F29A75.41C67EA6@whistle.com> Date: Fri, 19 Mar 1999 10:41:57 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: "Daniel O'Connor" Cc: hackers@FreeBSD.ORG Subject: Re: Exctracting stuff from PRs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > You could try getting your mail reader to process it.. I haven't tried, but it > should deal with the MIME'ness of message in question. It's not when it's mail, but when you go to examine the bug report, from the database, you discover that the bug patch is not directly usable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 11:11:43 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 A66B115078 for ; Fri, 19 Mar 1999 11:11:41 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id NAA01908; Fri, 19 Mar 1999 13:11:14 -0600 (CST) Date: Fri, 19 Mar 1999 13:11:14 -0600 (CST) From: Steve Price To: Julian Elischer Cc: "Daniel O'Connor" , hackers@FreeBSD.ORG Subject: Re: Exctracting stuff from PRs In-Reply-To: <36F29A75.41C67EA6@whistle.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, 19 Mar 1999, Julian Elischer wrote: # Daniel O'Connor wrote: # > # # > You could try getting your mail reader to process it.. I haven't tried, but it # > should deal with the MIME'ness of message in question. # # # It's not when it's mail, but when you go to examine the bug report, # from the database, you discover that the bug patch is not directly # usable. As some kind soul once suggested to me, you can always use ports/converters/mpack to extract the MIME bits. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 11:33:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sierrahill.com (unknown [209.198.135.2]) by hub.freebsd.org (Postfix) with ESMTP id E15321514D for ; Fri, 19 Mar 1999 11:33:35 -0800 (PST) (envelope-from rjoe@sierrahill.com) Received: (from rjoe@localhost) by sierrahill.com (8.8.8/8.8.8) id NAA10411; Fri, 19 Mar 1999 13:38:44 -0600 (CST) (envelope-from rjoe) From: Joe Schwartz Message-Id: <199903191938.NAA10411@sierrahill.com> Subject: 3.1 adduser -batch gone? To: freebsd-hackers@freebsd.org Date: Fri, 19 Mar 1999 13:38:44 -0600 (CST) Cc: rjoe@sierrahill.com ( Joe Schwartz ) X-Mailer: ELM [version 2.4 PL23] 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 Folks, I'm migrating an ISP's NT e-mail server to FreeBSD 3.1. They've provided user info including: login ID, full name, passwd I've set up the script using my FreeBSD 2.8 system to create the adduser script which looks like: adduser -batch test4 '' '' 'MR. TEST' qwerty7 Works great on 2.8 and creates a record like this: test4:$1$Yk404UY5$vsmNN4Ah1sLVZyHX.NEok1:1024:15::0:0:MR. TEST:/home/test4:/bin/ csh. I tried running he script on the 3.1 machine and got a: '-batch no longer supported' error message. I was originally going to use 'pw', but not not understand how to use it to set a passwd. Am I overlooking this option? HELP, I don't want to do this by hand and could sure use some advice on how to programatically make these users. Thanks, Joe S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 13:13:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (Postfix) with ESMTP id A1C2814F30 for ; Fri, 19 Mar 1999 13:13:27 -0800 (PST) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.9.1a/8.9.1) with SMTP id NAA09627; Fri, 19 Mar 1999 13:13:11 -0800 (PST) Date: Fri, 19 Mar 1999 13:13:11 -0800 (PST) From: Dan Busarow To: Joe Schwartz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 3.1 adduser -batch gone? In-Reply-To: <199903191938.NAA10411@sierrahill.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, 19 Mar 1999, Joe Schwartz wrote: > I'm migrating an ISP's NT e-mail server to FreeBSD 3.1. They've > provided user info including: > > login ID, full name, passwd > > I've set up the script using my FreeBSD 2.8 system to create the > adduser script which looks like: > > adduser -batch test4 '' '' 'MR. TEST' qwerty7 > > Works great on 2.8 and creates a record like this: > > test4:$1$Yk404UY5$vsmNN4Ah1sLVZyHX.NEok1:1024:15::0:0:MR. TEST:/home/test4:/bin/ > csh. > > > I tried running he script on the 3.1 machine and got a: > > '-batch no longer supported' error message. > > I was originally going to use 'pw', but not not understand > how to use it to set a passwd. Am I overlooking this option? Looks like I'll be migrating my adduser scripts too :) This seems to work # echo qwerty7 | pw useradd test4 -c "MR TEST" -h 0 -h is the magic Dan -- Dan Busarow 949 443 4172 Dana Point Communications, Inc. dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 14: 0:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id 7A4F9156F7 for ; Fri, 19 Mar 1999 14:00:30 -0800 (PST) (envelope-from ad@psn.ie) Received: from vmunix.psn.ie ([194.106.150.252]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10O6Qe-0000s4-00; Fri, 19 Mar 1999 21:03:41 +0000 Received: from localhost.psn.ie ([127.0.0.1] helo=localhost) by vmunix.psn.ie with esmtp (Exim 2.10 #1) id 10O6Rg-00004K-00; Fri, 19 Mar 1999 21:04:44 +0000 Date: Fri, 19 Mar 1999 21:04:44 +0000 (GMT) From: Andy Doran To: Joe Schwartz Cc: freebsd-hackers@freebsd.org Subject: Re: 3.1 adduser -batch gone? In-Reply-To: <199903191938.NAA10411@sierrahill.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 Take a look at: http://www.psn.ie/users/ad/psntools It's in need of a major rewrite and release under BSD license, but works well as it is. If you have questions mail psntools-users@psn.ie. Andy. > Folks, > > I'm migrating an ISP's NT e-mail server to FreeBSD 3.1. They've > provided user info including: > > login ID, full name, passwd > > I've set up the script using my FreeBSD 2.8 system to create the > adduser script which looks like: > > adduser -batch test4 '' '' 'MR. TEST' qwerty7 > > Works great on 2.8 and creates a record like this: > > test4:$1$Yk404UY5$vsmNN4Ah1sLVZyHX.NEok1:1024:15::0:0:MR. TEST:/home/test4:/bin/ > csh. > > > I tried running he script on the 3.1 machine and got a: > > '-batch no longer supported' error message. > > I was originally going to use 'pw', but not not understand > how to use it to set a passwd. Am I overlooking this option? > > HELP, I don't want to do this by hand and could sure use some > advice on how to programatically make these users. > > Thanks, > > Joe S. > > > > > > 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 Mar 19 14:13: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C7D2E14ED5 for ; Fri, 19 Mar 1999 14:12:55 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id RAA34406; Fri, 19 Mar 1999 17:14:16 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: Date: Fri, 19 Mar 1999 17:13:06 -0500 To: Julian Elischer , hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Exctracting stuff from PRs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:08 AM -0800 3/19/99, Julian Elischer wrote: > Sometimes people submit code in a PR (in fact we encourage this). > Unfortunately they often include the code as an attachment, > so it appears in the PR database as some 'encoded' form of data. When I went to use 'send-pr' for a problem, I was surprised that send-pr itself does not have a parameter for "sample file" or some-such. If it did, then you would have some control of what format that enclosure arrived in. I was going to suggest that at the time, but then I thought "Hey, I could write a sample implementation, and thus I would be doing more than just asking someone else to do work". Of course, I only think of it when I'm *doing* a send-pr, and so far I've never remembered to actually sit down and write a change to the send-pr script. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 14:14:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 4DA45157AE for ; Fri, 19 Mar 1999 14:14:01 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id OAA13607; Fri, 19 Mar 1999 14:13:06 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA19635; Fri, 19 Mar 1999 14:13:05 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id PAA14407; Fri, 19 Mar 1999 15:13:02 -0700 Message-ID: <36F2CBE9.1934E6F1@softweyr.com> Date: Fri, 19 Mar 1999 15:12:57 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Joe Schwartz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 3.1 adduser -batch gone? References: <199903191938.NAA10411@sierrahill.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Schwartz wrote: > > > Folks, > > I'm migrating an ISP's NT e-mail server to FreeBSD 3.1. They've > provided user info including: > > login ID, full name, passwd > > I've set up the script using my FreeBSD 2.8 system to create the > adduser script which looks like: > > adduser -batch test4 '' '' 'MR. TEST' qwerty7 > > Works great on 2.8 and creates a record like this: > > test4:$1$Yk404UY5$vsmNN4Ah1sLVZyHX.NEok1:1024:15::0:0:MR. TEST:/home/test4:/bin/ > csh. > > > I tried running he script on the 3.1 machine and got a: > > '-batch no longer supported' error message. > > I was originally going to use 'pw', but not not understand > how to use it to set a passwd. Am I overlooking this option? > > HELP, I don't want to do this by hand and could sure use some > advice on how to programatically make these users. Look at the -h option. This prevents you from passing the password on the command line, where it can be viewed by other users. This seems to work entirely adequately: pw useradd foobar -u 2525 -h 0 <; Fri, 19 Mar 1999 14:21:08 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.8.8) with ESMTP id WAA12421; Fri, 19 Mar 1999 22:20:45 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA04670; Fri, 19 Mar 1999 09:59:09 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903190959.JAA04670@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: holm@freibergnet.de Cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: dgm (Digiboard PC/Xem) - candidate for removal ? In-reply-to: Your message of "Fri, 19 Mar 1999 08:23:43 +0100." <19990319082343.A37059@pegasus.freibergnet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 19 Mar 1999 09:59:09 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The dgm driver won't work at all if your card currently works under = the dgb driver.... I'll keep your name though and maybe ask you to = test the end result... Thanks. > Brian Somers wrote: > = > > > Brian Somers wrote: > > > = > > > > Hi, > > > > = > > > > Is there anyone out there that's willing to run some probe code f= or = > > > > me with an installed digiboard that currently uses the dgm driver= in = > > > > -current or -stable ? > > > = > > > I have an Digiboard PC/Xe if this makes sense here. > > = > > Great. Is it currently identified by the dgm driver (rather than the= = > > dgb driver) ? = > = > Currently it is working using the the dgb driver, I'll try to build > a kernel with the dgm driver using your patches over the weekend > (since this board is in my home machine). > = > You hear from me, > = > Holm > -- = > FreibergNet Systemhaus GbR Holm Tiffe * Administration, Developme= nt > Systemhaus f=FCr Daten- und Netzwerktechnik phone +49 3731 78= 1279 > Unternehmensgruppe Liebscher & Partner fax +49 3731 7813= 77 > D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.d= e/ -- = Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 14:44:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id AB42515BBC for ; Fri, 19 Mar 1999 14:44:14 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id B7B8918C2; Fri, 19 Mar 1999 23:44:16 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id B6D2649B9; Fri, 19 Mar 1999 23:44:16 +0100 (CET) Date: Fri, 19 Mar 1999 23:44:16 +0100 (CET) From: Andrzej Bialecki To: Wes Peters Cc: hackers@freebsd.org Subject: Re: fxp driver causing lockup In-Reply-To: <36F1D196.C7E58624@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 On Thu, 18 Mar 1999, Wes Peters wrote: > > > I haven't seen any freezes while *probing* the fxp, but they may not > > > really know the difference. The hang happened in the *attach*, when > > > the user (or system) ifconfig's the interface up. Do you have any > > > details, or a contact I can email? > > > > No, I've never had trouble with the fxp driver. It's something I saw > > mentioned on one of the lists - either -advocacy or -chat. > > Mike, I saw something in the -chat archives where you were beating up > Brett Glass (always fun) w.r.t. problems with the NetFinity. You > mention the "initialising fxp0 hangs" bug. Do you think this might > have been the problem? Mine was on a Toshiba 7000S with on-board > EEPro 100+; it was failing during the attach due to not having bus > mastering turned on. Hmmm... I'm coming somewhat late to this thread, but I had exactly the same problems with fxp0 on IBM's PC 300PL workstation. However, I was able to "fix" it by turning ON the Eth. card in BIOS setup :-) It just happened to be disabled before. Funny thing, though - normally, when you disable the card in the BIOS, FreeBSD can't even discover it. Here it finds it, but then it wedges the system... 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 Fri Mar 19 15:10:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from redbox.venux.net (redbox.venux.net [216.47.238.10]) by hub.freebsd.org (Postfix) with ESMTP id 319CA154D9 for ; Fri, 19 Mar 1999 15:10:11 -0800 (PST) (envelope-from matthew@venux.net) Received: from thunder (net177138.hcv.com [209.153.177.138]) by redbox.venux.net (Postfix) with SMTP for id E1DF62E20A; Fri, 19 Mar 1999 18:11:04 -0500 (EST) Message-Id: <4.1.19990319180111.00af0140@mail.venux.net> X-Sender: mhagerty@mail.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 19 Mar 1999 18:09:56 -0500 To: freebsd-hackers@freebsd.org From: Matthew Hagerty Subject: PThread level in 3.1-R Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, What pthreads version is 3.1-Release based on? I recall that 2.2.x was pthreads level 4 and that there was work in progress to bring it up to level 10. Has that happened and is there some where on the web page that tells me so I don't have to bother the list? Thanks, Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 16:40:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id CE92614FC2 for ; Fri, 19 Mar 1999 16:40:26 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id QAA68735 for ; Fri, 19 Mar 1999 16:30:06 -0800 (PST) Message-ID: <36F2EC0D.237C228A@whistle.com> Date: Fri, 19 Mar 1999 16:30:05 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: [Fwd: !! Emergency !! FreeBSD 3.1 on IBM Netfinity 5000 Server] Content-Type: multipart/mixed; boundary="------------4487EB717DE145182F1CF0FB" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------4487EB717DE145182F1CF0FB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit did everybody get this? I'd have thought it would have had more comment.. julian --------------4487EB717DE145182F1CF0FB Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-Path: Received: from whistle.com (whistle.whistle.com [207.76.205.131]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA57504 for ; Fri, 19 Mar 1999 11:16:14 -0800 (PST) From: hawkkuan@tw.ibm.com Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA23350 for ; Fri, 19 Mar 1999 11:16:13 -0800 (PST) Received: from gatekeeper.whistle.com( 207.76.204.2) by whistle.com via smap (V2.0) id xma023340; Fri, 19 Mar 99 11:15:49 -0800 Received: (from smap@localhost) by gatekeeper.whistle.com (8.8.8/8.8.7) id LAA20269 for ; Fri, 19 Mar 1999 11:15:48 -0800 (PST) (envelope-from hawkkuan@tw.ibm.com) Received: from mail2.sol.net( 206.55.64.73) by gatekeeper.whistle.com via smap (V2.0) id xma020257; Fri, 19 Mar 99 11:15:34 -0800 Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by mail2.sol.net (8.8.8/8.8.8/SNNS-1.02) with ESMTP id NAA08803 for ; Fri, 19 Mar 1999 13:15:27 -0600 (CST) Received: by hub.freebsd.org (Postfix) id 0134615566; Fri, 19 Mar 1999 10:32:01 -0800 (PST) Delivered-To: julian@freebsd.org Received: from ausmtp01.au.ibm.com (ausmtp01.au.ibm.COM [202.135.136.97]) by hub.freebsd.org (Postfix) with ESMTP id 0945114F7B; Fri, 19 Mar 1999 10:30:43 -0800 (PST) (envelope-from hawkkuan@tw.ibm.com) Received: from f03n05e.au.ibm.com (f03n05s.au.ibm.com [9.185.166.73]) by ausmtp01.au.ibm.com (1.0.0) with ESMTP id FAA33444; Sat, 20 Mar 1999 05:26:10 +1100 Received: from tw.ibm.com (f06n09s [9.185.166.69]) by f03n05e.au.ibm.com (8.8.7/8.8.7) with SMTP id FAA39862; Sat, 20 Mar 1999 05:29:08 +1100 Received: by tw.ibm.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 48256739.00658A46 ; Sat, 20 Mar 1999 02:29:05 +0800 X-Lotus-FromDomain: IBMTW To: freebsdteam@tw.ibm.com Cc: kenc@tw.ibm.com Message-ID: <48256739.00658833.00@tw.ibm.com> Date: Sat, 20 Mar 1999 02:26:02 +0800 Subject: !! Emergency !! FreeBSD 3.1 on IBM Netfinity 5000 Server Mime-Version: 1.0 Content-type: text/plain; charset=big5 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mail2.sol.net id NAA08803 Dear Freebsd core team and developers, Recenlty IBM Taiwan had a large project to prompt FreeBSD in Taiwan elementary school. We use 600 sets IBM Netfinity 5000 server in this project. We had some problems with IBM Netfinity 5000 with FreeBSD, The most important is that there is 2 set of PCI bridge of Netfinity 5000. When I installed the netfinity 5000 and use "dmesg" command. System can regonized all chip set on mainboard, include 2 PCI bridge chip set and 1 PCI-ISA bridge. =3D=3D=3D=3D IBM Netfinity 5000 Bus Architecture =3D=3D=3D=3D PCI bus 0 connected with on board AIC-7895, S3 Video chip & AMD 79cXXX NIC and only "1" free PCI slot. PCI bus 1 connected with 4 PCI slots , 2 of them are PCI/ISA share slot. =3D=3D=3D=3D=3D=3D The most problems we meet =3D=3D=3D=3D=3D=3D All adaptor (we try Intel Ether express pro) only can be regonized o= n PCI bus 0 , but no matter what we have tried, we can't install any adaptor on PCI bus 1 slots!! Could you help us!! We really wonna prompt FreeBSD on Taiwan market. It need all your help for this!! Is there anyone tried install FreeBSD on multi PCI bus system(most mid-high end PC server desgined not just for 1 PCI bridge but more than 2 or 3 PCI bridge= )? Please help us!! Best Regards, Hawk Kuan =A9x=AE=B6=B5=D8 Sales Specialist , PSG, IBM Taiwan, 206, Sec.1 Keelung Rd, Taipei, Taiwa= n, R.O.C. Tel:886-2-2725-9522, Pager:0959-316961, Mobile: 0936-945920 Notes ID: Hawk JH Kuan/Taiwan/IBM , E-Mail: hawkkuan@tw.ibm.com --------------4487EB717DE145182F1CF0FB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 16:40:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id F1792151B2 for ; Fri, 19 Mar 1999 16:40:33 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id QAA68943; Fri, 19 Mar 1999 16:35:50 -0800 (PST) Message-ID: <36F2ED64.6201DD56@whistle.com> Date: Fri, 19 Mar 1999 16:35:48 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: hawkkuan@tw.ibm.com Cc: hackers@freebsd.org Subject: Re: !! Emergency !! FreeBSD 3.1 on IBM Netfinity 5000 Server References: <48256739.00658833.00@tw.ibm.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 hawkkuan@tw.ibm.com wrote: > > Dear Freebsd core team and developers, The first thing you should do is send the contents of the 'dmesg' command, after booting with -v. It should be sent to -hackers.. there was some problem in your mail message so that I could not see what group you sent it to, so I have CC'd it to hackers. (often -questions would be correct but I agree that it is more appropriate in THIS case for -hackers) julian > > Recenlty IBM Taiwan had a large project to prompt FreeBSD in Taiwan > elementary > school. We use 600 sets IBM Netfinity 5000 server in this project. > > We had some problems with IBM Netfinity 5000 with FreeBSD, The most > important > is that there is 2 set of PCI bridge of Netfinity 5000. When I installed > the netfinity 5000 and > use "dmesg" command. System can regonized all chip set on mainboard, > include 2 PCI bridge > chip set and 1 PCI-ISA bridge. > > ==== IBM Netfinity 5000 Bus Architecture ==== > > PCI bus 0 connected with on board AIC-7895, S3 Video chip & AMD > 79cXXX NIC and > only "1" free PCI slot. > > PCI bus 1 connected with 4 PCI slots , 2 of them are PCI/ISA share > slot. > > ====== The most problems we meet ====== > > All adaptor (we try Intel Ether express pro) only can be regonized on > PCI bus 0 , but > no matter what we have tried, we can't install any adaptor on PCI bus 1 > slots!! > > Could you help us!! We really wonna prompt FreeBSD on Taiwan market. > It need all > your help for this!! > > Is there anyone tried install FreeBSD on multi PCI bus system(most > mid-high end PC > server desgined not just for 1 PCI bridge but more than 2 or 3 PCI bridge)? > > Please help us!! > > Best Regards, > > Hawk Kuan ©x®¶µØ > Sales Specialist , PSG, IBM Taiwan, 206, Sec.1 Keelung Rd, Taipei, Taiwan, > R.O.C. > Tel:886-2-2725-9522, Pager:0959-316961, Mobile: 0936-945920 > Notes ID: Hawk JH Kuan/Taiwan/IBM , E-Mail: hawkkuan@tw.ibm.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 17:26:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id CD24F1509B for ; Fri, 19 Mar 1999 17:26:25 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA04463; Fri, 19 Mar 1999 20:32:45 -0500 From: Bill Paul Message-Id: <199903200132.UAA04463@skynet.ctr.columbia.edu> Subject: Re: Gigabit ethernet revisited To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 19 Mar 1999 20:32:44 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199903191739.JAA59302@apollo.backplane.com> from "Matthew Dillon" at Mar 19, 99 09:39:14 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4270 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > Hmm. I definitely think there's a bug due to not repopulating buffers > from inside your receive interrupt packet processing loop, but it may > not be the cause of this bug. > > If the NIC is unable to complete DMA quickly enough, perhaps the burst > parameters can be tweaked. The PC certainly should be able to do DMA > writes to memory at the PCI bus speed! > > Ok, lets see... what about these: > > Read Max DMA parameter > Write Max DMA parameter > Minimum DMA parameter > PCI Latency Timer / system PCI latency timer > > At a guess, I think you would want: > > Read Max DMA parameter 16 > Write Max DMA parameter 128 > Minimum DMA parameter 128 > PCI Latency Timer relatively high for this board > ( if you have a per-board choice, > you may not ) Well, as it turns out, at least in this particular instance, the problem was solved by setting the write max value to zero, which is unlimited. My machine has an 82443BX chipset, which is supposed to allow an unlimited burst size. The manual also says that it uses zero for the read and write max values in the sample driver because this works best on most systems. So now, I'm not having problems with a PCI bottleneck anymore. When I to a 'ttcp -s -n10000 -u -t ' the receiving host receives all the packets (as evidenced by netstat -in) and there are no more nicDmaWriteRingFull errors. However, the ttcp -r -s -u that's waiting on the receive side still does not get all the data. This is what was confusing me: I wasn't checking the udp stats with netstat -s and comparing them to netstat -in. I was observing lost packets even when I had the PCI configuration done right, but for a completely different reason. Netstat -s reports that all the UDP datagrams are received (they get as far as udp_input()) but a large percentage of them are dropped 'due to full socket buffers' (i.e. sbappendaddr() doesn't return 0). (Now I know what's going to happen here. Somebody's going to glibly suggest increasing the socket buffer size. I tried that, by increasing the value of kern.ipc.maxsockbuf. It didn't make any difference. If somebody wants to suggest something along these lines, don't do it in a vague and hand-waving fashion. Before you make the suggestion, try to do it yourself. Make a note of exactly what you do. See if it actually has a positive effect on the problem. _Then_ explain _exactly_ what you did so that I can duplicate it.) The receiving host is under heavy interrupt load. Andrew Gallatin has said to me that this is a classic case of livelock, where the system is so busy processing interrupts that nothing else is getting done. In this case, the NIC is dutifully DMAing all the packets to the host and the driver is queing them all to ether_input(), but this is happening so often that the other parts of the kernel aren't getting a chance to process the packets in time, so the queues fill up and packets get dropped. This is another problem that I'm not sure how to solve. It sounds to me like dealing with this involves changing things outside of the driver itself. In order to handle everything within the driver, it would have to be able to tell when the various input queues are full, which I think would require lots of protocol specific that should be somewhere else. I have tried adjusting the 'rx_coal_ticks' value a bit and it does help to increase it, however it can't cure the problem completely. Increasing rx_coal_ticks too much (in conjunction with rx_max_coal_bds) can introduce a lot of latency, which creates other problems. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 17:35:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles228.castles.com [208.214.165.228]) by hub.freebsd.org (Postfix) with ESMTP id 8505315027 for ; Fri, 19 Mar 1999 17:35:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA07762; Fri, 19 Mar 1999 17:29:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903200129.RAA07762@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul Cc: dillon@apollo.backplane.com (Matthew Dillon), hackers@freebsd.org Subject: Re: Gigabit ethernet revisited In-reply-to: Your message of "Fri, 19 Mar 1999 20:32:44 EST." <199903200132.UAA04463@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Mar 1999 17:29:44 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (Now I know what's going to happen here. Somebody's going to glibly > suggest increasing the socket buffer size. I tried that, by increasing > the value of kern.ipc.maxsockbuf. It didn't make any difference. If > somebody wants to suggest something along these lines, don't do it in > a vague and hand-waving fashion. Before you make the suggestion, try > to do it yourself. Make a note of exactly what you do. See if it actually > has a positive effect on the problem. _Then_ explain _exactly_ what you > did so that I can duplicate it.) I told you to wind up the socket's receive buffer size with the approproate socket option in the user app. I don't know what the _real_ "right" answer is for UDP. For TCP, you can try setting the pipe size for the route to tweak the socket buffers. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Fri Mar 19 17:51:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6482F15352 for ; Fri, 19 Mar 1999 17:51:04 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id RAA71046; Fri, 19 Mar 1999 17:49:03 -0800 (PST) Message-ID: <36F2FE8E.7566F4CF@whistle.com> Date: Fri, 19 Mar 1999 17:49:02 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Bill Paul Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited References: <199903200132.UAA04463@skynet.ctr.columbia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: > > The receiving host is under heavy interrupt load. Andrew Gallatin has > said to me that this is a classic case of livelock, where the system > is so busy processing interrupts that nothing else is getting done. > In this case, the NIC is dutifully DMAing all the packets to the host > and the driver is queing them all to ether_input(), but this is happening > so often that the other parts of the kernel aren't getting a chance to > process the packets in time, so the queues fill up and packets get dropped. I think Andrew might be right.. it could well be livelock. Matt Thomas implemented a solution for the 100mb dec cards when 100 was fast. I think that the de drivers responded to the interrupt and immediatly did SCHEDNETISR() to schedule the rest of the driver that was running at a lower priority. I don't know if the if_de driver still does that but is could be worth a look. The other problem may be that there is just not enough PCI bus left for all the cycles needed for the processor to clear out the queue. (no wait that doesn't make sense because that would be memory bus bandwidth.. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 19 20:13:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id F06BD14E9F for ; Fri, 19 Mar 1999 20:13:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA16399; Fri, 19 Mar 1999 20:13:07 -0800 (PST) (envelope-from dillon) Date: Fri, 19 Mar 1999 20:13:07 -0800 (PST) From: Matthew Dillon Message-Id: <199903200413.UAA16399@apollo.backplane.com> To: Julian Elischer Cc: Bill Paul , hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited References: <199903200132.UAA04463@skynet.ctr.columbia.edu> <36F2FE8E.7566F4CF@whistle.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Bill Paul wrote: :> :> The receiving host is under heavy interrupt load. Andrew Gallatin has :> said to me that this is a classic case of livelock, where the system :> is so busy processing interrupts that nothing else is getting done. :> In this case, the NIC is dutifully DMAing all the packets to the host :> and the driver is queing them all to ether_input(), but this is happening :... : :I think Andrew might be right.. :it could well be livelock. : :Matt Thomas implemented a solution for the 100mb dec cards :when 100 was fast. I think that the de drivers responded to the :interrupt and immediatly did SCHEDNETISR() to schedule the rest of Hey cool, at least the hardware problem has been solved! On the livelock thingy -- well, one way to find out is to use ipfw to throw away the packets, and then do a 'systat -vm 1' to see where the cpu's time is being sent and how much cpu is being used. I'm guessing between 50% and 70% of the cpu is being eaten with the packets going into an ipfw bitbucket. Each memory read or write represents around 85 MBytes/sec. The DMA counts as one. The read() system call counts as two ( because it must read from one memory location and write to another ) -- this puts us perilously close to the memory bandwidth limit of the cpu when you count all the other garbage going on that's breaking up the L1 cache. :julian -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 Mar 19 22: 8:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 30C8414CAF for ; Fri, 19 Mar 1999 22:08:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id WAA38098; Fri, 19 Mar 1999 22:06:35 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903200606.WAA38098@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Julian Elischer , Bill Paul , hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited In-reply-to: Your message of "Fri, 19 Mar 1999 20:13:07 PST." <199903200413.UAA16399@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Mar 1999 22:06:35 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that David Greeman quoted 2 gigabytes/sec memory bandwith for the Xeon processor with whatever chipset he was using. Cheers, Amancio > :Bill Paul wrote: > :> > :> The receiving host is under heavy interrupt load. Andrew Gallatin has > :> said to me that this is a classic case of livelock, where the system > :> is so busy processing interrupts that nothing else is getting done. > :> In this case, the NIC is dutifully DMAing all the packets to the host > :> and the driver is queing them all to ether_input(), but this is happening > :... > : > :I think Andrew might be right.. > :it could well be livelock. > : > :Matt Thomas implemented a solution for the 100mb dec cards > :when 100 was fast. I think that the de drivers responded to the > :interrupt and immediatly did SCHEDNETISR() to schedule the rest of > > Hey cool, at least the hardware problem has been solved! > > On the livelock thingy -- well, one way to find out is to use ipfw > to throw away the packets, and then do a 'systat -vm 1' to see where > the cpu's time is being sent and how much cpu is being used. > > I'm guessing between 50% and 70% of the cpu is being eaten with the > packets going into an ipfw bitbucket. > > Each memory read or write represents around 85 MBytes/sec. The DMA counts > as one. The read() system call counts as two ( because it must read from > one memory location and write to another ) -- this puts us perilously > close to the memory bandwidth limit of the cpu when you count all the > other garbage going on that's breaking up the L1 cache. > > :julian > > -Matt > Matthew Dillon > > > > > 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 Sat Mar 20 0: 7:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id D30D615087 for ; Sat, 20 Mar 1999 00:06:55 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id AAA12975; Sat, 20 Mar 1999 00:04:22 -0800 (PST) Message-Id: <199903200804.AAA12975@implode.root.com> To: Amancio Hasty Cc: Matthew Dillon , Julian Elischer , Bill Paul , hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited In-reply-to: Your message of "Fri, 19 Mar 1999 22:06:35 PST." <199903200606.WAA38098@rah.star-gate.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 20 Mar 1999 00:04:22 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I think that David Greeman quoted 2 gigabytes/sec memory bandwith for >the Xeon processor with whatever chipset he was using. That was Intel's claim when using 8-way interleaved, 50ns EDO memory (which is how this machine is configured). I think whoever said that at Intel was wrong, however. It doesn't seem to be as fast as even 1 GB/second. I'm actually getting lower transmit numbers than Bill is for the equivilent tests, on a machine that should be much faster than Bill's, and that's another mystery we've been trying to resolve. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project > > Cheers, > Amancio > >> :Bill Paul wrote: >> :> >> :> The receiving host is under heavy interrupt load. Andrew Gallatin has >> :> said to me that this is a classic case of livelock, where the system >> :> is so busy processing interrupts that nothing else is getting done. >> :> In this case, the NIC is dutifully DMAing all the packets to the host >> :> and the driver is queing them all to ether_input(), but this is happening >> :... >> : >> :I think Andrew might be right.. >> :it could well be livelock. >> : >> :Matt Thomas implemented a solution for the 100mb dec cards >> :when 100 was fast. I think that the de drivers responded to the >> :interrupt and immediatly did SCHEDNETISR() to schedule the rest of >> >> Hey cool, at least the hardware problem has been solved! >> >> On the livelock thingy -- well, one way to find out is to use ipfw >> to throw away the packets, and then do a 'systat -vm 1' to see where >> the cpu's time is being sent and how much cpu is being used. >> >> I'm guessing between 50% and 70% of the cpu is being eaten with the >> packets going into an ipfw bitbucket. >> >> Each memory read or write represents around 85 MBytes/sec. The DMA counts >> as one. The read() system call counts as two ( because it must read from >> one memory location and write to another ) -- this puts us perilously >> close to the memory bandwidth limit of the cpu when you count all the >> other garbage going on that's breaking up the L1 cache. >> >> :julian >> >> -Matt >> Matthew Dillon >> >> >> >> >> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 0:29:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id E30AF1504A for ; Sat, 20 Mar 1999 00:28:59 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA68510; Sat, 20 Mar 1999 08:31:35 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 20 Mar 1999 08:31:35 +0000 (GMT) From: Doug Rabson To: Julian Elischer Cc: hawkkuan@tw.ibm.com, hackers@freebsd.org Subject: Re: !! Emergency !! FreeBSD 3.1 on IBM Netfinity 5000 Server In-Reply-To: <36F2ED64.6201DD56@whistle.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, 19 Mar 1999, Julian Elischer wrote: > hawkkuan@tw.ibm.com wrote: > > > > Dear Freebsd core team and developers, > > The first thing you should do is send the contents of the 'dmesg' > command, after booting with -v. > It should be sent to -hackers.. there was some problem in your mail > message so that I could not see what group you sent it to, so I have > CC'd it to hackers. > > (often -questions would be correct but I agree that it is more > appropriate in THIS case for -hackers) Thanks Julian, I was just about to ask for the same information. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 2:14:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from finland.ispro.net.tr (finland.ispro.net.tr [195.174.18.1]) by hub.freebsd.org (Postfix) with ESMTP id 9151E14F5C for ; Sat, 20 Mar 1999 02:14:50 -0800 (PST) (envelope-from yurtesen@ispro.net.tr) Received: from localhost (yurtesen@localhost) by finland.ispro.net.tr (8.9.2/8.9.2) with ESMTP id MAA61637 for ; Sat, 20 Mar 1999 12:14:29 +0200 (EET) (envelope-from yurtesen@ispro.net.tr) Date: Sat, 20 Mar 1999 12:14:29 +0200 (EET) From: Evren Yurtesen X-Sender: yurtesen@localhost To: freebsd-hackers@freebsd.org Subject: adaptec aba-1030 drivers 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 hello, will there be a driver for FreeBSD to support Adaptec ABA-1030 satellite receivers? ( http://www.broadlogic.com/ ) or is it possible to use linux drivers? thanks Evren Yurtesen ISPRO A.S. yurtesen@ispro.net.tr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 6:42: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3BA1B150C5; Sat, 20 Mar 1999 06:41:56 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id PAA16643; Sat, 20 Mar 1999 15:41:35 +0100 (CET) (envelope-from des) To: Charles Randall Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 3.1: Link with static a.out lib? References: <64003B21ECCAD11185C500805F31EC03022B5EF3@houston.matchlogic.com> From: Dag-Erling Smorgrav Date: 20 Mar 1999 15:41:34 +0100 In-Reply-To: Charles Randall's message of "Fri, 19 Mar 1999 10:49:32 -0700" Message-ID: Lines: 22 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charles Randall writes: > With the help of Michael E. Mercer [mmercer@ipass.net] I'm now using gcc's > "-aout" option (which appears to be undocumented) but I still get the > following message when compiling on 3.1R, > > % gcc -aout test.c libInOldAoutFormat.a > ld: crt0.o: No such file or directory > > Again, > > 1. Is this possible? Yes. > 2. Are there instructions for doing this? What you wrote above should be enough. Are you sure your system wasn't built with -DNOAOUT? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 7:57:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ausmtp02.au.ibm.com (ausmtp02.au.ibm.COM [202.135.136.105]) by hub.freebsd.org (Postfix) with ESMTP id F257714DE3; Sat, 20 Mar 1999 07:57:10 -0800 (PST) (envelope-from hawkkuan@tw.ibm.com) Received: from f03n05e.au.ibm.com (f03n05s.au.ibm.com [9.185.166.73]) by ausmtp02.au.ibm.com (1.0.0) with ESMTP id CAA65972; Sun, 21 Mar 1999 02:50:33 +1100 From: hawkkuan@tw.ibm.com Received: from tw.ibm.com (f06n09s [9.185.166.69]) by f03n05e.au.ibm.com (8.8.7/8.8.7) with SMTP id CAA59270; Sun, 21 Mar 1999 02:55:47 +1100 Received: by tw.ibm.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 4825673A.005780A1 ; Sat, 20 Mar 1999 23:55:45 +0800 X-Lotus-FromDomain: IBMTW To: questions@freebsd.org, hackers@freebsd.org Message-ID: <4825673A.00577C58.00@tw.ibm.com> Date: Sat, 20 Mar 1999 11:42:11 +0800 Subject: !! Emergency !! Help FreeBSD 3.0 with IBM Netfinity 5000 Mime-Version: 1.0 Content-type: text/plain; charset=big5 Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Freebsd core team and developers, Recenlty IBM Taiwan had a large project to prompt FreeBSD in Taiwan elementary school. We use 600 sets IBM Netfinity 5000 server in this project. We had some problems with IBM Netfinity 5000 with FreeBSD, The most important is that there is 2 set of PCI bridge of Netfinity 5000. When I installed the netfinity 5000 and use "dmesg" command. System can regonized all chip set on mainboard, include 2 PCI bridge chip set and 1 PCI-ISA bridge. ==== IBM Netfinity 5000 Bus Architecture ==== PCI bus 0 connected with on board AIC-7895, S3 Video chip & AMD 79cXXX NIC and only "1" free PCI slot. PCI bus 1 connected with 4 PCI slots , 2 of them are PCI/ISA share slot. ====== The most problems we meet ====== All adaptor (we try Intel Ether express pro) only can be regonized on PCI bus 0 , but no matter what we have tried, we can't install any adaptor on PCI bus 1 slots!! Could you help us!! We really wonna prompt FreeBSD on Taiwan market. It need all your help for this!! Is there anyone tried install FreeBSD on multi PCI bus system(most mid-high end PC server desgined not just for 1 PCI bridge but more than 2 or 3 PCI bridge)? Please help us!! ====dmesg message======= Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #1: Fri Mar 19 11:11:06 GMT 1999 root@hawk.tw.ibm.com:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz cost 5077 ns Timecounter "TSC" frequency 349181049 Hz cost 147 ns CPU: Pentium II (quarter-micron) (349.18-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 67108864 (65536K bytes) avail memory = 62480384 (61016K bytes) Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x02 on pci0.0.1 ahc0: rev 0x04 int a irq 15 on pci0.6.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x04 int b irq 11 on pci0.6.1 ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs lnc1: rev 0x33 int a irq 15 on pci0.9.0 lnc1: PCnet-FAST+ address 00:04:ac:b8:44:b3 vga0: rev 0x16 int a irq 11 on pci0.10.0 chip2: rev 0x4d on pci0.15.0 ide_pci0: rev 0x4a int a irq 14 on pci0.15.1 ide_pci: controller is simplex, no DMA on secondary channel Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model IntelliMouse, device ID 3 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, dma, iordis wcd0: 2406/5500Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked wdc1 not found at 0x170 wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface ahc0: Someone reset channel A Waiting 15 seconds for SCSI devices to settle Sending WDTR! (probe15:ahc1:0:0:0): Sending SDTR!! pass1 at ahc1 bus 0 target 14 lun 0 pass1: Fixed Processor SCSI2 device pass1: 3.300MB/s transfers changing root device to da0s1a da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) lnc1: Heartbeat error -- SQE test failed lnc1: Loss of carrier during transmit -- Net error? fd0c: hard error reading fsbn 0 (No status) fd0c: hard error reading fsbn 0 (No status) fd0c: hard error reading fsbn 0 (No status) fd0c: hard error writing fsbn 4 of 4-6 (No status) fd0c: hard error writing fsbn 13 of 13-15 (No status) fd0c: hard error writing fsbn 21 (No status) fd0c: hard error writing fsbn 1981 (No status) =========== Best Regards, Hawk Kuan ©x®¶µØ Sales Specialist , PSG, IBM Taiwan, 206, Sec.1 Keelung Rd, Taipei, Taiwan, R.O.C. Tel:886-2-2725-9522, Pager:0959-316961, Mobile: 0936-945920 Notes ID: Hawk JH Kuan/Taiwan/IBM , E-Mail: hawkkuan@tw.ibm.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 8: 9:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from unix1.it-datacntr.louisville.edu (unix1.it-datacntr.louisville.edu [136.165.4.27]) by hub.freebsd.org (Postfix) with ESMTP id C170014F18 for ; Sat, 20 Mar 1999 08:09:10 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from homer.louisville.edu (ktstev01@homer.louisville.edu [136.165.1.20]) by unix1.it-datacntr.louisville.edu (8.8.8/8.8.7) with ESMTP id LAA19602 for ; Sat, 20 Mar 1999 11:08:50 -0500 Received: (from ktstev01@localhost) by homer.louisville.edu (8.8.8/8.8.8) id LAA10974 for freebsd-hackers@freebsd.org; Sat, 20 Mar 1999 11:08:49 -0500 (EST) Message-ID: <19990320110849.B9286@homer.louisville.edu> Date: Sat, 20 Mar 1999 11:08:49 -0500 From: Keith Stevenson To: freebsd-hackers@freebsd.org Subject: FreeBSD on the IBM Netfinity Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For about the next two weeks I have access to an IBM Netfinity 5500 server. (It might be a 5000. I'm not certain.) The Netware/NT administrator who "owns" it has graciously offered it to me for FreeBSD testing. (He's too far behind in his workload to need it right now.) He doesn't care what we install on it as long as he can have it back in working order in two weeks or so. (The poor thing is destined to be an NT server.) My question to all of you (especially the developer types) is what can I do with it in order to assist FreeBSD in supporting on this platform? I'm planning to start by installing 3.1 on Monday. This seems like a good opportunity to get some testing done. What does everyone think? --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 Sat Mar 20 8:18:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 33BB014E52 for ; Sat, 20 Mar 1999 08:18:43 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA09354 for ; Sat, 20 Mar 1999 11:24:32 -0500 (EST) Date: Sat, 20 Mar 1999 11:24:31 -0500 (EST) From: Alfred Perlstein To: hackers@freebsd.org Subject: splimp is overkill? 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 was looking at some networking code recently and noticed something... it seems that splimp has to raised for individual drivers, but splimp blocks out all driver interupts correct? Why not have a function that just locks an individual network driver out of getting interupts instead of the whole slew of drivers? I noticed this looking at sys/net/if_tun.c The QUEUE macros need splimp, but we know what interface we are working on, why not just 'splimp' that ONE interface? Also has anyone given thought to individual driver mbuf pools? Yes, it's sort of evil, but it also reduces the need to lock up the whole network stack. If you can allocate on your own pool of mbufs, instead of a global pool you can avoid blocking the entire networking stack. Now you may ask, well since mbufs "travel around" who gets them when they are freed? well you can maintain high and low watermarks for attempting to distribute or take from other drivers. This isn't a solution, just an idea. This would also help SMP if done properly imo. Comments? If anything flames explaining why this is a bad idea are welcome, I just want to understand more. thank you, Alfred Perlstein - Admin, coder, and admirer of all things BSD. -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 8:21:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8C87B14E6E for ; Sat, 20 Mar 1999 08:21:24 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id RAA17996; Sat, 20 Mar 1999 17:20:58 +0100 (CET) (envelope-from des) To: Keith Stevenson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on the IBM Netfinity References: <19990320110849.B9286@homer.louisville.edu> From: Dag-Erling Smorgrav Date: 20 Mar 1999 17:20:57 +0100 In-Reply-To: Keith Stevenson's message of "Sat, 20 Mar 1999 11:08:49 -0500" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Keith Stevenson writes: > [...] My question to all of you > (especially the developer types) is what can I do with it in order to assist > FreeBSD in supporting on this platform? I'm planning to start by installing > 3.1 on Monday. This seems like a good opportunity to get some testing done. > > What does everyone think? Install 3.1, then upgrade immediately to 4.0 (cvsup + make world). You'll need the sources anyway to be of any help, and 4.0 is where things happen. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 9:24:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 62CE914FD1 for ; Sat, 20 Mar 1999 09:24:05 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id TAA09222; Sat, 20 Mar 1999 19:23:20 +0200 (EET) Date: Sat, 20 Mar 1999 19:23:20 +0200 (EET) From: Narvi To: David Greenman Cc: Amancio Hasty , Matthew Dillon , Julian Elischer , Bill Paul , hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited In-Reply-To: <199903200804.AAA12975@implode.root.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, 20 Mar 1999, David Greenman wrote: > >I think that David Greeman quoted 2 gigabytes/sec memory bandwith for > >the Xeon processor with whatever chipset he was using. > > That was Intel's claim when using 8-way interleaved, 50ns EDO memory (which > is how this machine is configured). I think whoever said that at Intel was > wrong, however. It doesn't seem to be as fast as even 1 GB/second. I'm > actually getting lower transmit numbers than Bill is for the equivilent tests, > on a machine that should be much faster than Bill's, and that's another > mystery we've been trying to resolve. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project Believe only what Stream tells you. Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 9:41:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 0FA4114E5A for ; Sat, 20 Mar 1999 09:41:10 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 27407 invoked by uid 1001); 20 Mar 1999 17:40:50 +0000 (GMT) To: hackers@freebsd.org Subject: On the lighter side (which Linux distribution is best?) From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 20 Mar 1999 18:40:50 +0100 Message-ID: <27405.921951650@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See http://www.userfriendly.org/cartoons/archives/99mar/19990320.html Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 9:42:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id AF11614E70 for ; Sat, 20 Mar 1999 09:42:18 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id MAA11313 for ; Sat, 20 Mar 1999 12:40:50 -0500 (EST) Message-Id: <199903201740.MAA11313@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 20 Mar 1999 12:36:18 -0500 To: hackers@freebsd.org From: Dennis Subject: kernel config setting not being saved Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Changes made at boot with the kernel config utility are not being saved in v3.1R. Is there something that needs to be done manually to save them? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 9:51:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 0025F154D9 for ; Sat, 20 Mar 1999 09:51:16 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id SAA19140; Sat, 20 Mar 1999 18:50:54 +0100 (CET) (envelope-from des) To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: kernel config setting not being saved References: <199903201740.MAA11313@etinc.com> From: Dag-Erling Smorgrav Date: 20 Mar 1999 18:50:54 +0100 In-Reply-To: Dennis's message of "Sat, 20 Mar 1999 12:36:18 -0500" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis writes: > Changes made at boot with the kernel config utility are not > being saved in v3.1R. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 10:36:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 5605514DDE; Sat, 20 Mar 1999 10:35:38 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 24E0018C2; Sat, 20 Mar 1999 19:35:41 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 1D1584990; Sat, 20 Mar 1999 19:35:41 +0100 (CET) Date: Sat, 20 Mar 1999 19:35:38 +0100 (CET) From: Andrzej Bialecki To: Dag-Erling Smorgrav Cc: Dennis , hackers@FreeBSD.ORG, jkh@freebsd.org Subject: Re: kernel config setting not being saved 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 20 Mar 1999, Dag-Erling Smorgrav wrote: > Dennis writes: > > Changes made at boot with the kernel config utility are not > > being saved in v3.1R. > > Which IMHO misses the point to some extent. It's true that changes are written out _during_ _installation_, and put in the wrong place. But then the poor user thinks that this will happen automagically each time he/she boots -c, which is simply not true. So, the errata should be corrected - it's not plainly wrong, but violates POLA. 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 Sat Mar 20 11:34: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from regret.globalserve.net (regret.globalserve.net [209.90.144.72]) by hub.freebsd.org (Postfix) with ESMTP id C91CF14FF0 for ; Sat, 20 Mar 1999 11:33:51 -0800 (PST) (envelope-from dm@regret.globalserve.net) Received: (from dm@localhost) by regret.globalserve.net (8.9.3/8.9.1) id PAA34185 for hackers@freebsd.org; Sat, 20 Mar 1999 15:43:43 GMT (envelope-from dm) Message-ID: <19990320154343.A34085@globalserve.net> Date: Sat, 20 Mar 1999 15:43:43 +0000 From: Dan Moschuk To: hackers@freebsd.org Subject: odd pthreads problem. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I have encounted a small problem that I believe is with pthreads. I have a threaded program that operates under a fair amount of load. When it is started from crontab, the CPU usage jumps to 100%, when it is started from the command line it idles around 3-7%. However, when it is started from the commandline, I get a fairly regular screen dump of "junk" (similar to what you'd see if you cat'd a binary file to stdout). This occurs even when stdout/stderr is redirected to /dev/null. I have gone through my code a few times, and there are *no* instances where it prints to the screen. This has been tested with 2.2.7 and last weeks 4.0-current. Ideas? Regards, -- Dan Moschuk (TFreak!dm@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company "If at first you don't succeed, redefine success" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 12:18:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0C7D614E8C for ; Sat, 20 Mar 1999 12:18:36 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost by bingsun1.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id PAA18704 for ; Sat, 20 Mar 1999 15:18:15 -0500 (EST) X-Authentication-Warning: bingsun1.cc.binghamton.edu: bf20761 owned process doing -bs Date: Sat, 20 Mar 1999 15:18:15 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun1 To: freebsd-hackers@FreeBSD.ORG Subject: Calculation of load average and CCPU_SHIFT 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 am looking into the source code in file vm_meter.c and kern_synch.c of FreeBSD 2.2.8. They use integer multiplication and shift operation to replace the costly float multiplication. The FSCALE and FSHIFT are for this purpose. But I could not understand the usage of CCPU_SHIFT in schedcpu(). Specifically, please explain the following comments in the source code in more detail if possible: -------------------------------------------------------------------- To estimate CCPU_SHIFT for exp(-1/20), the following formula was used: 1 - exp(-1/20) ~= 0.0487 ~= 0.0488 == 1 (fixed pt, *11* bits). Scale factor for scaled integers used to count %cpu time and load averages. The number of CPU 'tick's that map to a unique '%age' can be expressed by the formula (1 / (2 ^ (FSHIFT - 11))). The maximum load average that can be calculated (assuming 32 bits) can be closely approximated using the formula (2 ^ (2 * (16 - FSHIFT))) for (FSHIFT < 15). For the scheduler to maintain a 1:1 mapping of CPU 'tick' to '%age', FSHIFT must be at least 11; this gives us a maximum load average of ~1024. ------------------------------------------------------------------- Any help or hint is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 12:37:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 2659014C10 for ; Sat, 20 Mar 1999 12:37:18 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA02543; Sat, 20 Mar 1999 19:19:26 +0100 From: Luigi Rizzo Message-Id: <199903201819.TAA02543@labinfo.iet.unipi.it> Subject: Re: Calculation of load average and CCPU_SHIFT To: bf20761@binghamton.edu (zhihuizhang) Date: Sat, 20 Mar 1999 19:19:26 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "zhihuizhang" at Mar 20, 99 03:17:56 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 354 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am looking into the source code in file vm_meter.c and kern_synch.c of > FreeBSD 2.2.8. They use integer multiplication and shift operation to > replace the costly float multiplication. The FSCALE and FSHIFT are for it is not only costly (actually, on modern CPUs it is not costly at all!), FPU usage is not allowed in the kernel. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 17:46:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from regret.globalserve.net (regret.globalserve.net [209.90.144.72]) by hub.freebsd.org (Postfix) with ESMTP id 8BD2E14F29 for ; Sat, 20 Mar 1999 17:46:37 -0800 (PST) (envelope-from dm@regret.globalserve.net) Received: (from dm@localhost) by regret.globalserve.net (8.9.3/8.9.1) id VAA37614 for hackers@freebsd.org; Sat, 20 Mar 1999 21:56:27 GMT (envelope-from dm) Message-ID: <19990320215627.A37588@globalserve.net> Date: Sat, 20 Mar 1999 21:56:27 +0000 From: Dan Moschuk To: hackers@freebsd.org Subject: GNOME Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all, Does anyone else experience a lot of coredumping (signal 6) with the latest build of gnome (from the ports)? Regards, -- Dan Moschuk (TFreak!dm@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company "If at first you don't succeed, redefine success" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 18: 4:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id 6824315023 for ; Sat, 20 Mar 1999 18:04:57 -0800 (PST) (envelope-from insane@lunatic.oneinsane.net) Received: (from insane@localhost) by lunatic.oneinsane.net (8.9.2/8.9.2) id SAA77143 for freebsd-hackers@freebsd.org; Sat, 20 Mar 1999 18:04:37 -0800 (PST) (envelope-from insane) Date: Sat, 20 Mar 1999 18:04:37 -0800 From: "Ron 'The InSaNe One' Rosson" To: freebsd-hackers@freebsd.org Subject: Re: GNOME Message-ID: <19990320180437.A77055@lunatic.oneinsane.net> Reply-To: insane@oneinsane.net References: <19990320215627.A37588@globalserve.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990320215627.A37588@globalserve.net>; from Dan Moschuk on Sat, Mar 20, 1999 at 09:56:27PM +0000 X-Operating-System: FreeBSD lunatic.oneinsane.net 3.1-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane-pgp5i.txt X-Uptime: 6:03PM up 3 days, 12:14, 2 users, load averages: 0.07, 0.09, 0.10 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some, here.. just about every applet.. All sig 6. TTFN Ron On Sat, Mar 20, 1999 at 09:56:27PM +0000, Dan Moschuk wrote: > > Hey all, > > Does anyone else experience a lot of coredumping (signal 6) with the latest > build of gnome (from the ports)? > > Regards, > -- > Dan Moschuk (TFreak!dm@globalserve.net) > Senior Systems/Network Administrator > Globalserve Communications Inc., a Primus Canada Company > "If at first you don't succeed, redefine success" > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 18:24:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id E854D150FA for ; Sat, 20 Mar 1999 18:24:17 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id NAA23842 for hackers@FreeBSD.ORG; Sun, 21 Mar 1999 13:23:56 +1100 (EST) Message-ID: <19990321132356.M11159@rf900.physics.usyd.edu.au> Date: Sun, 21 Mar 1999 13:23:56 +1100 From: David Dawes To: hackers@FreeBSD.ORG Subject: Re: !! Emergency !! Help FreeBSD 3.0 with IBM Netfinity 5000 References: <4825673A.00577C58.00@tw.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4825673A.00577C58.00@tw.ibm.com>; from hawkkuan@tw.ibm.com on Sat, Mar 20, 1999 at 11:42:11AM +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 20, 1999 at 11:42:11AM +0800, hawkkuan@tw.ibm.com wrote: > Recenlty IBM Taiwan had a large project to prompt FreeBSD in Taiwan >elementary >school. We use 600 sets IBM Netfinity 5000 server in this project. > > We had some problems with IBM Netfinity 5000 with FreeBSD, The most >important >is that there is 2 set of PCI bridge of Netfinity 5000. When I installed >the netfinity 5000 and >use "dmesg" command. System can regonized all chip set on mainboard, >include 2 PCI bridge >chip set and 1 PCI-ISA bridge. > >==== IBM Netfinity 5000 Bus Architecture ==== > > PCI bus 0 connected with on board AIC-7895, S3 Video chip & AMD >79cXXX NIC and >only "1" free PCI slot. > > PCI bus 1 connected with 4 PCI slots , 2 of them are PCI/ISA share >slot. > >====== The most problems we meet ====== > > > All adaptor (we try Intel Ether express pro) only can be regonized on >PCI bus 0 , but >no matter what we have tried, we can't install any adaptor on PCI bus 1 >slots!! >Probing for devices on PCI bus 0: >chip0: rev 0x04 on pci0.0.0 >chip1: rev 0x02 on pci0.0.1 I guess the problem is multiple host-PCI bridges. This is something we need to deal with at XFree86 too. Is it correct that there is no generic way of handling these? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 19:57:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.dyn.ml.org (pm3-9.ppp.wenet.net [206.15.85.9]) by hub.freebsd.org (Postfix) with ESMTP id 2818C14F48 for ; Sat, 20 Mar 1999 19:57:30 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id TAA66714; Sat, 20 Mar 1999 19:57:17 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 20 Mar 1999 19:57:17 -0800 (PST) From: Alex Zepeda To: Dan Moschuk Cc: hackers@FreeBSD.ORG Subject: Re: GNOME In-Reply-To: <19990320215627.A37588@globalserve.net> 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 > Does anyone else experience a lot of coredumping (signal 6) with the latest > build of gnome (from the ports)? That means an assertion failed. Really this should probably be reported to the Gnome camp. Well, that and the "core" ports should be updated to 1.0.4, and stuff. It seems like the Gnome ports are in a state of flux right now, as not many have been updated to depend on gtk+/glib 1.2... and so incorrectly look for 1.1d (?!?). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 20: 5:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 5E5E214C92; Sat, 20 Mar 1999 20:05:13 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (ts4-11-ppp.ipass.net [207.120.205.11]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id XAA28893; Sat, 20 Mar 1999 23:04:50 -0500 (EST) Message-ID: <36F4707E.E7A6D897@ipass.net> Date: Sat, 20 Mar 1999 23:07:27 -0500 From: "Michael E. Mercer" Reply-To: samit@usa.ltindia.com X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: rfork() Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, This was posted to freebsd-questions with no reply. I tried this and the child process created a core file. I also tried the other options and they seem to work. Just RFPROC and RFMEM DON'T! Thanks, Michael Mercer -------------------- Can any one suggest how to use rfork( RFPROC | RFMEM ); according to the manual, freeBSD supports this and it should create a new process which will share the address space. But what I'm getting is a) It returns only to the parent process with a childID. b) It doesn't go into child part c) 'PS' shows that a child process is active. Code: #include main() { int childId; printf("Parent Process start \n"); if ( (childId = rfork(RFMEM | RFPROC) ) == 0 ) { printf("In Child childId(%d) PId(%d)\n", childId,getpid() ); sleep(4); exit(0); } { char buf[10] = "Samit"; int nRet; printf("Parent process continues with childId(%d) %s,PID(%d)\n", childId, buf,getpid()); sleep(5); } } Output: $ cc test.c $ a.out & $ Parent Process start Parent process continues with childId(10759) Samit,PID(10758) ps PID TT STAT TIME COMMAND 10697 p2 Ss 0:00.07 -sh (sh) 10758 p2 S 0:00.00 a.out 10759 p2 Z 0:00.00 (a.out) 10760 p2 R+ 0:00.00 ps why it is created zombie and it does not execute the code ? --Samit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" 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 Sat Mar 20 20:13: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id F08A6150B2 for ; Sat, 20 Mar 1999 20:12:57 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 1530 invoked from network); 21 Mar 1999 04:12:36 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 21 Mar 1999 04:12:36 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.3/8.9.1) id XAA04326; Sat, 20 Mar 1999 23:12:35 -0500 (EST) Message-Id: <199903210412.XAA04326@y.dyson.net> Subject: Re: rfork() In-Reply-To: <36F4707E.E7A6D897@ipass.net> from "Michael E. Mercer" at "Mar 20, 99 11:07:27 pm" To: samit@usa.ltindia.com Date: Sat, 20 Mar 1999 23:12:35 -0500 (EST) Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Michael E. Mercer said: > Hello, > > This was posted to freebsd-questions with no reply. > I tried this and the child process created a core file. > I also tried the other options and they seem to work. > Just RFPROC and RFMEM DON'T! > rfork(RFMEM) doesn't easily work from C. You need to create an assembly stub. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 20:21:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 60BCB14C92; Sat, 20 Mar 1999 20:21:29 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (ts4-11-ppp.ipass.net [207.120.205.11]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id XAA00437; Sat, 20 Mar 1999 23:20:58 -0500 (EST) Message-ID: <36F47446.E67A7602@ipass.net> Date: Sat, 20 Mar 1999 23:23:34 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: dyson@iquest.net Cc: samit@usa.ltindia.com, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rfork() References: <199903210412.XAA04326@y.dyson.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, With very little experience in assembly, could you or someone else give me a small example? Thanks in advance, Michael Mercer "John S. Dyson" wrote: > > Michael E. Mercer said: > > Hello, > > > > This was posted to freebsd-questions with no reply. > > I tried this and the child process created a core file. > > I also tried the other options and they seem to work. > > Just RFPROC and RFMEM DON'T! > > > rfork(RFMEM) doesn't easily work from C. You need to > create an assembly stub. > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > > 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 Sat Mar 20 20:36:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 5F56F15093 for ; Sat, 20 Mar 1999 20:36:14 -0800 (PST) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 10OZxq-0007gR-00; Sat, 20 Mar 1999 20:35:54 -0800 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id UAA15058; Sat, 20 Mar 1999 20:35:51 -0800 Date: Sat, 20 Mar 1999 20:35:51 -0800 (PST) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: GNOME To: Dan Moschuk Cc: hackers@FreeBSD.ORG 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 > > Does anyone else experience a lot of coredumping (signal 6) with the > > latest build of gnome (from the ports)? I've actually found the 1.0.* versions to be much more stable than the 0.98/99.* versions. > That means an assertion failed. Really this should probably be reported > to the Gnome camp. Well, that and the "core" ports should be updated to > 1.0.4, and stuff. > > It seems like the Gnome ports are in a state of flux right now, as not > many have been updated to depend on gtk+/glib 1.2... and so incorrectly > look for 1.1d (?!?). There is one big problem with the way the ports builds work. When checking dependancies, it isn't always possible to tell when the installed version isn't really up to date. This can be a particular problem with a dependancy tree as deep, complex, and dynamic as the gnome suite. The safest way to handle this is, of course, to track down all of the dependancies of the gnome port (try something like "make clean | sort -u"); pkg_delete all of them; and re-build. But that's usually grossly inconvienient. So, if you don't mind the package database thinking you've got more than one version installed, the second-best approach is to manually check the dependancy tree for each port you want to install, and build them from the bottom up instead of relying on the ports Makefiles to do it for you. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 22: 6:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id 3D50214F7E for ; Sat, 20 Mar 1999 22:06:35 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id AAA51264; Sun, 21 Mar 1999 00:06:15 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma051262; Sun, 21 Mar 99 00:05:46 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id AAA59505; Sun, 21 Mar 1999 00:05:31 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199903210605.AAA59505@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <19990320215627.A37588@globalserve.net> References: <19990320215627.A37588@globalserve.net> Subject: Re: GNOME Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Dan Moschuk Cc: hackers@FreeBSD.ORG Date: Sun, 21 Mar 1999 00:05:31 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 March 1999 at 21:56, Dan Moschuk wrote: > Does anyone else experience a lot of coredumping (signal 6) with the latest > build of gnome (from the ports)? Yes. So far as I can tell, these are gnome bugs. However, I'm still trying to debug them anyway. I think more updates are close ... GNOME 1.0 seems to have been buggy enough to release many 1.0.x versions in rapid succession. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 22: 9: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id 21C4914C28 for ; Sat, 20 Mar 1999 22:09:06 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id AAA51269; Sun, 21 Mar 1999 00:08:45 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma051267; Sun, 21 Mar 99 00:08:36 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id AAA59605; Sun, 21 Mar 1999 00:08:22 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199903210608.AAA59605@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: GNOME Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Alex Zepeda Cc: Dan Moschuk , hackers@FreeBSD.ORG Date: Sun, 21 Mar 1999 00:08:22 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 March 1999 at 19:57, Alex Zepeda wrote: > It seems like the Gnome ports are in a state of flux right now, as not > many have been updated to depend on gtk+/glib 1.2... and so incorrectly > look for 1.1d (?!?). All of the current GNOME ports depend upon the gtk12 and glib12 ports, AFAIK. There are, I think, some GTK ports that are left depending upon 1.1.16 (gtk11-devel port) right now. They should still build, and their respective maintainers will probably update them sooner or later (if they need no major modifications to work with GTK 1.2). Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 22:11:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id CB9CB152E5 for ; Sat, 20 Mar 1999 22:11:07 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id AAA51285; Sun, 21 Mar 1999 00:10:45 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma051283; Sun, 21 Mar 99 00:10:42 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id AAA59688; Sun, 21 Mar 1999 00:10:28 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199903210610.AAA59688@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: GNOME Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: patl@phoenix.volant.org Cc: Dan Moschuk , hackers@FreeBSD.ORG Date: Sun, 21 Mar 1999 00:10:28 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 March 1999 at 20:35, patl@phoenix.volant.org wrote: > There is one big problem with the way the ports builds work. When > checking dependancies, it isn't always possible to tell when the > installed version isn't really up to date. This can be a particular > problem with a dependancy tree as deep, complex, and dynamic as the > gnome suite. They usually work. Where they don't, it would be nice to get a send-pr so the port can be fixed. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 22:15:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.dyn.ml.org (pm3-4.ppp.wenet.net [206.15.85.4]) by hub.freebsd.org (Postfix) with ESMTP id 5E99614BE4 for ; Sat, 20 Mar 1999 22:15:35 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id WAA99984; Sat, 20 Mar 1999 22:15:16 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 20 Mar 1999 22:15:16 -0800 (PST) From: Alex Zepeda To: Jacques Vidrine Cc: Dan Moschuk , hackers@FreeBSD.ORG Subject: Re: GNOME In-Reply-To: <199903210608.AAA59605@spawn.nectar.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 Sun, 21 Mar 1999, Jacques Vidrine wrote: > All of the current GNOME ports depend upon the gtk12 and glib12 > ports, AFAIK. There are, I think, some GTK ports that are left > depending upon 1.1.16 (gtk11-devel port) right now. They should > still build, and their respective maintainers will probably update > them sooner or later (if they need no major modifications to work > with GTK 1.2). Perhaps I picked some bad ports, gmc and balsa. gmc needed a little tweaking (of the patches?!) to get itself built, and works as well as expcted (it doesn't). Balsa OTOH wouldn't even compile. It seems to be wanting version 0.4.9?!? the latest version available from www.balsa.net was 0.4.6.2... even after telling it to depend on Gtk+ 1.2 it wouldn't build. I'm not quite sure what the maintainer was thinking here. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 22:35:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 93CAD14BE7 for ; Sat, 20 Mar 1999 22:34:25 -0800 (PST) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 10OboB-0000zG-00; Sat, 20 Mar 1999 22:34:03 -0800 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id WAA15100; Sat, 20 Mar 1999 22:33:58 -0800 Date: Sat, 20 Mar 1999 22:33:58 -0800 (PST) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: GNOME To: Jacques Vidrine Cc: Dan Moschuk , hackers@FreeBSD.ORG In-Reply-To: <199903210610.AAA59688@spawn.nectar.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 20 March 1999 at 20:35, patl@phoenix.volant.org wrote: > > There is one big problem with the way the ports builds work. When > > checking dependancies, it isn't always possible to tell when the > > installed version isn't really up to date. This can be a particular > > problem with a dependancy tree as deep, complex, and dynamic as the > > gnome suite. > > They usually work. Where they don't, it would be nice to get > a send-pr so the port can be fixed. The problem is that the ports aren't making changes that are visible to the dependancy tests. In some cases it is because a port is changing rapidly enough that it doesn't make sense to bump up a library version number; but in others, the test is for the existance of a file whose name is not expected to change across versions. In general, the updated versions are expected to be backwards compatible. But when they contain significant bug fixes, failing to update them can make the higher-level ports look flakey. These aren't easy things to fix because it isn't at all obvious what the right fix is. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 23:13:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 37A1B150C2 for ; Sat, 20 Mar 1999 23:13:11 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id CAA08119; Sun, 21 Mar 1999 02:18:55 -0500 From: Bill Paul Message-Id: <199903210718.CAA08119@skynet.ctr.columbia.edu> Subject: Re: Gigabit ethernet revisited To: julian@whistle.com (Julian Elischer) Date: Sun, 21 Mar 1999 02:18:53 -0500 (EST) Cc: dillon@apollo.backplane.com, hackers@freebsd.org In-Reply-To: <36F2FE8E.7566F4CF@whistle.com> from "Julian Elischer" at Mar 19, 99 05:49:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3294 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Julian Elischer had to walk into mine and say: > I think Andrew might be right.. > it could well be livelock. > > Matt Thomas implemented a solution for the 100mb dec cards > when 100 was fast. I think that the de drivers responded to the > interrupt and immediatly did SCHEDNETISR() to schedule the rest of > the driver that was running at a lower priority. I don't know if the > if_de driver still does that but is could be worth a look. I took a stab at duplicating this (the code is in the de driver but it's conditional and not enabled by default). I managed to make it work fairly easily, but it doesn't seem to help. I even set the maxsockbuf parameter to a ridiculously large number (20MBytes) and did a -b20000000 with ttcp to have it set the SO_RCVBUF really large, and still the socket buffers filled up (I actually added some debug printf()s to see what happened in sbappendaddr() when sbspace() showed there was no room left and indeed the socket buffer showed up as been filled for several consecutive calls to sbappendaddr().) It seems really strange to me that this can happen: the application should be draining the socket long before 20MB of data accumulates. Let me just see if I understand what happens correctly: - Data arrives at the NIC. - The NIC interrupts. - The driver checks the receive ring and passes the packets to ether_input(). - Ether_input() puts them on a queue and schedules a soft interrupt (netisr). - The netisr eventually causes ip_input() to run. - Ip_input() passes the data to udp_input(). - Udp_input() passes the data to sbappendaddr() and calls sorwakeup(). - Sorwakeup() sets some flags in the socket structure and calls sowakeup(). - Sowakeup() calls wakeup(). - Wakeup() marks the process waiting on the socket as runnable. - The scheduler runs the process so it can receive the data. So, how long after the process is marked runable does the scheduler actually transfer control to the process so that it can handle the received data? Can the process be prevented from running if there are too many interrupts from the NIC? Is there some way to make the scheduler run the process more often (I tried using nice -20 on the receving instance of ttcp; that didn't seem to make a difference)? Has anybody else actually tried to receive data at 600 to 800Mbps speeds on FreeBSD and done it reliably? (Note: I mean actually transmitting UDP packets at, say 80MB/sec and actually receiving _all_ of the transmitted packets on the other side, in the application, at the same speed. No fudging.) Transmit speed doesn't seem to be an issue here, but somehow I get the feeling that the kernel is sabotaging itself on receive. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 20 23:31: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9A1B3150C2 for ; Sat, 20 Mar 1999 23:31:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA09427; Sat, 20 Mar 1999 23:30:42 -0800 (PST) (envelope-from dillon) Date: Sat, 20 Mar 1999 23:30:42 -0800 (PST) From: Matthew Dillon Message-Id: <199903210730.XAA09427@apollo.backplane.com> To: Bill Paul Cc: julian@whistle.com (Julian Elischer), hackers@freebsd.org Subject: Re: Gigabit ethernet revisited References: <199903210718.CAA08119@skynet.ctr.columbia.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :So, how long after the process is marked runable does the scheduler :actually transfer control to the process so that it can handle the :received data? Can the process be prevented from running if there are :too many interrupts from the NIC? Is there some way to make the scheduler :run the process more often (I tried using nice -20 on the receving :instance of ttcp; that didn't seem to make a difference)? Has anybody :else actually tried to receive data at 600 to 800Mbps speeds on FreeBSD :and done it reliably? (Note: I mean actually transmitting UDP packets at, :say 80MB/sec and actually receiving _all_ of the transmitted packets on :the other side, in the application, at the same speed. No fudging.) :Transmit speed doesn't seem to be an issue here, but somehow I get the :feeling that the kernel is sabotaging itself on receive. : :-Bill You need to do the test I suggested sinking the packets into the bit bucket with ipfw. You also need to do a cpu loading test - graph the cpu utilization as displayed by vmstat or 'systat -vm 1' verses the packet load, both going into the bit bucket, or being read by a process. If there is any cpu available, runnable processes will run no matter what the cpu load. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 21 0: 0: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id BF21315135 for ; Sun, 21 Mar 1999 00:00:03 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id XAA47764; Sat, 20 Mar 1999 23:58:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903210758.XAA47764@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com Cc: Matthew Dillon , Julian Elischer , Bill Paul , hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet revisited In-reply-to: Your message of "Sat, 20 Mar 1999 00:04:22 PST." <199903200804.AAA12975@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 20 Mar 1999 23:58:51 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps the manufacturer of the gigabit ethernet chipset or the ethernet gigabit ether board can shine some of light into whats going on ?? Enjoy, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message