From owner-freebsd-stable Sun Aug 8 4:24:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from io.cts.com (io.cts.com [198.68.174.34]) by hub.freebsd.org (Postfix) with ESMTP id 33A0214EBA for ; Sun, 8 Aug 1999 04:24:27 -0700 (PDT) (envelope-from mdavis@cts.com) Received: from VOYAGER (voyager.cts.com [198.68.174.38]) by io.cts.com (8.9.3/8.9.2) with SMTP id EAA00419 for ; Sun, 8 Aug 1999 04:20:38 -0700 (PDT) (envelope-from mdavis@cts.com) From: "Morgan Davis" To: Subject: Removing files in /lost+found causes panic Date: Sun, 8 Aug 1999 04:20:37 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running FreeBSD 3.2-stable (last cvsup/make-world was yesterday, new kernel installed, etc.). A recent fsck after a bad shutdown left several weird files in /lost+found. They look like character or block device files, with random flag attributes and modes. I read the FAQ/handbook items on using chflags to clean up the flags that keep you from removing the files. But when I attempt to remove them, the system panics every time. I tried it in single user mode, no difference. I booted up the Fixit floppy, mounted the drive, and tried again. Same problem. This happens on the root filesystem's lost+found as well as on the /usr filesystem (which is the only one that has softupdates enabled). What is the trick to cleaning out these /lost+found directories without panicing? Thanks. --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 6:14:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id F0B0714DFD for ; Sun, 8 Aug 1999 06:14:55 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Aug 1999 14:13:40 +0100 (BST) Date: Sun, 8 Aug 1999 14:13:39 +0100 From: David Malone To: Morgan Davis Cc: freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic Message-ID: <19990808141339.A51902@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Morgan Davis on Sun, Aug 08, 1999 at 04:20:37AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 08, 1999 at 04:20:37AM -0700, Morgan Davis wrote: > This happens on the root filesystem's lost+found as well as on the /usr > filesystem (which is the only one that has softupdates enabled). With really weird files in lost+found you probably need to use clri to clear the inodes for these weird files. You could probably try something like the following: 1) ls -i and note the inode numbers. 2) boot into single user mode. 3) Do "clri /dev/rda0swhatever 4873928 4287942 37204 ..." where you put in the correct character device and inode numbers 4) Reboot and let fsck clean up the resulting mess. We had this happen ages ago when half of a ccd device keep going away 'cos of confused scsi stuff. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 8:48:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 62C9114DDC for ; Sun, 8 Aug 1999 08:48:31 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-53.dialup.rdu.ipass.net [209.170.132.53]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id LAA24624 for ; Sun, 8 Aug 1999 11:45:38 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id LAA00835 for stable@freebsd.org; Sun, 8 Aug 1999 11:48:16 -0400 (EDT) (envelope-from rhh) Date: Sun, 8 Aug 1999 11:48:16 -0400 From: Randall Hopper To: stable@freebsd.org Subject: (BUG?) Mounting "on top" of another mount Message-ID: <19990808114816.A682@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.2-RELEASE here. I had: > df | grep 32_share /dev/wd1s3e 2031953 1353017 516380 72% /32_share Then I mistakenly did a: > mount /dev/wd0s3e /32_share ^ And it didn't generate an error (!?). I then had: > df | grep 32_share /dev/wd1s3e 2031953 1353017 516380 72% /32_share /dev/wd0s3e 2032623 1169007 701007 63% /32_share Odd things started happening (vi failed, missing directories, etc.), so I rebooted. All is normal now, and nothing lost AFAIK, but that sure was strange. Is this a bug or a feature? Randall E.g. > mount /dev/wd1s1 /abc > mount /dev/wd1s2 /abc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 9:23:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 1991814BE7 for ; Sun, 8 Aug 1999 09:23:05 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 11DVhF-0004BS-00; Sun, 8 Aug 1999 09:21:17 -0700 Date: Sun, 8 Aug 1999 09:21:15 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: David Malone Cc: Morgan Davis , freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic In-Reply-To: <19990808141339.A51902@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, David Malone wrote: > On Sun, Aug 08, 1999 at 04:20:37AM -0700, Morgan Davis wrote: > > > This happens on the root filesystem's lost+found as well as on the /usr > > filesystem (which is the only one that has softupdates enabled). > > With really weird files in lost+found you probably need to use clri > to clear the inodes for these weird files. You could probably try > something like the following: > > 1) ls -i and note the inode numbers. > 2) boot into single user mode. > 3) Do "clri /dev/rda0swhatever 4873928 4287942 37204 ..." > where you put in the correct character device and inode > numbers > 4) Reboot and let fsck clean up the resulting mess. > > We had this happen ages ago when half of a ccd device keep going > away 'cos of confused scsi stuff. > > David. I don't think you should ever need to use clri. The system should only panic if the filesystem is corrupt. If fsck finds serious damage, you should run it again to make sure everything. Chances are the first fsck left some unfixed problems. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 10:56:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 17E9214FA6 for ; Sun, 8 Aug 1999 10:56:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA10180; Sun, 8 Aug 1999 11:54:26 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA01023; Sun, 8 Aug 1999 11:54:15 -0600 (MDT) Message-Id: <199908081754.LAA01023@harmony.village.org> To: tcobb@staff.circle.net Subject: Re: continued crashes with 3.1-Stable Cc: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com In-reply-to: Your message of "Sat, 07 Aug 1999 00:15:38 EDT." <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> References: <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> Date: Sun, 08 Aug 1999 11:54:15 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> tcobb@staff.circle.net writes: : I think the problem is the SMP. I've been having frequent : freezes with SMP under heavy webserver load with 3.2-R, : and 3.2-S. I'm unfortunately led to believe that FreeBSD : SMP is just not ready for primetime. Too bad the $$ we blew : on a dual PIII-550 box. I've seen freezes on -stable from NFS. We use amd, which creates local NFS mounts (mounts where both the client and server are on the same machine). When there are high loads, a deadlock situation can occur where a struct buf buffer is trying to be written out, but fails because of NFS locking. Matt Dillon's help in tracking this down has been invaluable. I'm working on a kludge to keep the deadlock from happening. That might be the cause of your hangs.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 10:57:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 59BAE14F91 for ; Sun, 8 Aug 1999 10:57:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA10202; Sun, 8 Aug 1999 11:55:42 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA01058; Sun, 8 Aug 1999 11:55:31 -0600 (MDT) Message-Id: <199908081755.LAA01058@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: continued crashes with 3.1-Stable Cc: tcobb@staff.circle.net, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com In-reply-to: Your message of "Fri, 06 Aug 1999 22:31:38 PDT." <2602.934003898@localhost> References: <2602.934003898@localhost> Date: Sun, 08 Aug 1999 11:55:31 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <2602.934003898@localhost> "Jordan K. Hubbard" writes: : I wonder why this doesn't happen to Yahoo's SMP boxes then. : They run -stable and would be screaming blue murder if their : webservers were doing the same thing. So, for that matter, : would Hotmail. We run -stable on a SMP boxes at work. We've seen minor annoyances (like times for process not being right, etc), but nothing major. The one bad bug we've found with NFS happens on UP machines too.. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 10:58:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 03D9614F81; Sun, 8 Aug 1999 10:58:06 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA10214; Sun, 8 Aug 1999 11:56:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA01076; Sun, 8 Aug 1999 11:56:19 -0600 (MDT) Message-Id: <199908081756.LAA01076@harmony.village.org> To: tcobb@staff.circle.net Subject: Re: continued crashes with 3.1-Stable Cc: jkh@zippy.cdrom.com, freebsd-smp@FreeBSD.ORG, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 07 Aug 1999 08:28:10 EDT." <307D63ED6749CF11AAE9005004461A5B3FB9@FREYA> References: <307D63ED6749CF11AAE9005004461A5B3FB9@FREYA> Date: Sun, 08 Aug 1999 11:56:19 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <307D63ED6749CF11AAE9005004461A5B3FB9@FREYA> tcobb@staff.circle.net writes: : Unfortunately, our hosting customer who is running a high-end : e-commerce site on this machine isn't excited about being : a testbed, they want a solution that works and stays working. Are you using loopback NFS mounts? If so, there is a bug under heavy load with that... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 11:24:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 90C2614E3C for ; Sun, 8 Aug 1999 11:24:56 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA25860; Sun, 8 Aug 1999 11:22:53 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199908081822.LAA25860@freeway.dcfinc.com> Subject: Re: continued crashes with 3.1-Stable In-Reply-To: from Seth at "Aug 7, 99 02:34:49 pm" To: seth@freebie.dp.ny.frb.org (Seth) Date: Sun, 8 Aug 1999 11:22:53 -0700 (MST) Cc: tcobb@staff.circle.net, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Seth wrote: > Have to disagree. 3.1-R had some problems. 3.2-S works flawlessly, even > under heavy load (big disk I/O and >24 system load averages). This is a > dual Xeon 450, scsi disks off an adaptec 7890, 384 megs RAM. Heavy load? Hah! I laugh at your heavy load. Witness: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= chad@freebie[/home/chad]:21> telnet 138.113.17.2 Trying 138.113.17.2... Connected to stormy.anasazi.com. Escape character is '^]'. UNIX(r) System V Release 4.0 (stormy) login: chad Password: UNIX System V Release 4, 1.1-94d079 Pyramid NILE stormy Copyright (c) 1984 AT&T All Rights Reserved Last login: Fri Jul 30 10:39:42 from freebie.dcfinc.com TERM set to cons25 No mail 11:16am up 72 days, 2:33, 3 users, load average: 126.16, 123.52, 122.47 chad@stormy[/home/chad]:22> logout -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= :-) ;-) :-) -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 12: 1:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id ECD2C14BD6; Sun, 8 Aug 1999 12:01:32 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Sun, 8 Aug 1999 14:55:27 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B3FDF@FREYA> From: tcobb@staff.circle.net To: imp@village.org Cc: jkh@zippy.cdrom.com, freebsd-smp@FreeBSD.ORG, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG Subject: RE: continued crashes with 3.1-Stable Date: Sun, 8 Aug 1999 14:55:26 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not using loopback nfs mounts (though I am using those successfully on other UP machines). I think I've found something that may explain what I'm seeing (the freezes): http://www.hardwarecentral.com/hardwarecentral/reports/881/1 -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Warner Losh [mailto:imp@village.org] > Sent: Sunday, August 08, 1999 1:56 PM > To: tcobb@staff.circle.net > Cc: jkh@zippy.cdrom.com; freebsd-smp@FreeBSD.ORG; > lightningweb@hotmail.com; freebsd-stable@FreeBSD.ORG > Subject: Re: continued crashes with 3.1-Stable > > > In message <307D63ED6749CF11AAE9005004461A5B3FB9@FREYA> > tcobb@staff.circle.net writes: > : Unfortunately, our hosting customer who is running a high-end > : e-commerce site on this machine isn't excited about being > : a testbed, they want a solution that works and stays working. > > Are you using loopback NFS mounts? If so, there is a bug > under heavy > load with that... > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 12: 5:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DA92A14BD6; Sun, 8 Aug 1999 12:05:28 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA10349; Sun, 8 Aug 1999 13:02:14 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA01304; Sun, 8 Aug 1999 13:02:04 -0600 (MDT) Message-Id: <199908081902.NAA01304@harmony.village.org> To: tcobb@staff.circle.net Subject: Re: continued crashes with 3.1-Stable Cc: jkh@zippy.cdrom.com, freebsd-smp@FreeBSD.ORG, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 08 Aug 1999 14:55:26 EDT." <307D63ED6749CF11AAE9005004461A5B3FDF@FREYA> References: <307D63ED6749CF11AAE9005004461A5B3FDF@FREYA> Date: Sun, 08 Aug 1999 13:02:03 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <307D63ED6749CF11AAE9005004461A5B3FDF@FREYA> tcobb@staff.circle.net writes: : I'm not using loopback nfs mounts (though I am using those : successfully on other UP machines). That's an accident waiting to happen. If you are doing anything with a high i/o load, you'll hit a deadlock in the implementation of nfs on -stable only. try creating a 16M-32M file and copying it around a few times. Kills my -stable machines every time... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 14:43:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 40F6E14FA9 for ; Sun, 8 Aug 1999 14:43:10 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Aug 1999 22:41:35 +0100 (BST) Date: Sun, 8 Aug 1999 22:41:35 +0100 From: David Malone To: Tom Cc: Morgan Davis , freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic Message-ID: <19990808224135.A54409@walton.maths.tcd.ie> References: <19990808141339.A51902@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Tom on Sun, Aug 08, 1999 at 09:21:15AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 08, 1999 at 09:21:15AM -0700, Tom wrote: > I don't think you should ever need to use clri. The system should only > panic if the filesystem is corrupt. If fsck finds serious damage, you > should run it again to make sure everything. Chances are the first fsck > left some unfixed problems. I've definitely come up with times where: 1) fsck checks the filesystem and gives it the OK, but it isn't. 2) fsck leaves weird files around in /lost+found which are difficult or impossible to delete. 3) fsck after about 8 runs still goes through the same list of questions and asks to be rerun again. 4) fsck says it doesn't need to be rerun, but if you rerun it it makes more repairs. The first and fourth were a long time ago and I think have been fixed. The second I haven't seen recently, but evidently someone else has. The last has happened to me on 3.2 as recently as a month ago. Clir and fsdb have got me out of these situations. I always run fsck an extra time these days if there was any corruption, just to be safe! David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 14:51:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from io.cts.com (io.cts.com [198.68.174.34]) by hub.freebsd.org (Postfix) with ESMTP id 1370415044 for ; Sun, 8 Aug 1999 14:51:13 -0700 (PDT) (envelope-from mdavis@cts.com) Received: from VOYAGER (voyager.cts.com [198.68.174.38]) by io.cts.com (8.9.3/8.9.2) with SMTP id OAA01256; Sun, 8 Aug 1999 14:49:21 -0700 (PDT) (envelope-from mdavis@cts.com) From: "Morgan Davis" To: "Tom" , "David Malone" Cc: Subject: RE: Removing files in /lost+found causes panic Date: Sun, 8 Aug 1999 14:49:21 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't think you should ever need to use clri. The system should only > panic if the filesystem is corrupt. If fsck finds serious damage, you > should run it again to make sure everything. Chances are the first fsck > left some unfixed problems. > > Tom Tom, fsck has been run several times (multiples in single user mode, with syncs in between, and across several reboots), and shows no problems at all. Yet, any attempt to molest the files in /lost+found initiates an immediate panic. I think the clri method might be the best way, and I'll try that next. SCO has an unlink command that sounds like it does the same thing, only you pass it a file or directory name. Just takes it out and the next fsck cleans up after you. --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 14:51:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id CD99214F9C for ; Sun, 8 Aug 1999 14:51:53 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 11Dapc-00025J-00; Sun, 8 Aug 1999 14:50:16 -0700 Date: Sun, 8 Aug 1999 14:50:13 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: David Malone Cc: Morgan Davis , freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic In-Reply-To: <19990808224135.A54409@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, David Malone wrote: > On Sun, Aug 08, 1999 at 09:21:15AM -0700, Tom wrote: > > > I don't think you should ever need to use clri. The system should only > > panic if the filesystem is corrupt. If fsck finds serious damage, you > > should run it again to make sure everything. Chances are the first fsck > > left some unfixed problems. > > I've definitely come up with times where: > > 1) fsck checks the filesystem and gives it the OK, but it isn't. Yes, but is this a -p", which only does a partial check? If so, that may be what it is supposed to do. > 2) fsck leaves weird files around in /lost+found which are difficult > or impossible to delete. > 3) fsck after about 8 runs still goes through the same list of questions > and asks to be rerun again. > 4) fsck says it doesn't need to be rerun, but if you rerun it it makes > more repairs. A lot of these sound like hardware. Some drives, especially IDE, will just corrupt themselves. Turing off multi-block mode can somtimes help. I have a Maxtor IDE drive (8.4GB) that I can not use with FreeBSD's multi-block mode, as data will be corrupted and fsck will always report errors. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 14:52:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id BCC0F14F58 for ; Sun, 8 Aug 1999 14:52:41 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Aug 1999 22:51:00 +0100 (BST) Date: Sun, 8 Aug 1999 22:50:59 +0100 From: David Malone To: Warner Losh Cc: "Jordan K. Hubbard" , tcobb@staff.circle.net, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Subject: Re: continued crashes with 3.1-Stable Message-ID: <19990808225059.B54409@walton.maths.tcd.ie> References: <2602.934003898@localhost> <199908081755.LAA01058@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908081755.LAA01058@harmony.village.org>; from Warner Losh on Sun, Aug 08, 1999 at 11:55:31AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 08, 1999 at 11:55:31AM -0600, Warner Losh wrote: > In message <2602.934003898@localhost> "Jordan K. Hubbard" writes: > : I wonder why this doesn't happen to Yahoo's SMP boxes then. > : They run -stable and would be screaming blue murder if their > : webservers were doing the same thing. So, for that matter, > : would Hotmail. > > We run -stable on a SMP boxes at work. We've seen minor annoyances > (like times for process not being right, etc), but nothing major. The > one bad bug we've found with NFS happens on UP machines too.. We've found one bug in -stable which we sent Matt a fix for - unfortunately it uncovers another bug, which we sent Matt a workaround for. We've been testing the patches for several months and they have improved the stability of our 3.2 NFS clients alot. The bug is to do with concurrent writes to files and is easier to provoke with a SMP machine. Basically, if you write a program which does lots of short unbuffered writes, and then do a.out > /nfs/file& a.out > /nfs/file& a.out > /nfs/file& a.out > /nfs/file& a.out > /nfs/file& . . . a few times you'll hang the machines. If you try it on -current you'll just panic the machine. You'll also see that it takes *ages* to finish doing these - which is because of the way our buffer locking works. We also have patches which makes UDP based NFS reply with the correct source address, which we're cleaning up. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 15: 6:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A33B01501F for ; Sun, 8 Aug 1999 15:06:44 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Aug 1999 23:04:15 +0100 (BST) To: Tom Cc: David Malone , Morgan Davis , freebsd-stable@freebsd.org, dwmalone@maths.tcd.ie Subject: Re: Removing files in /lost+found causes panic In-reply-to: Your message of "Sun, 08 Aug 1999 14:50:13 PDT." X-Request-Do: Date: Sun, 08 Aug 1999 23:04:15 +0100 From: David Malone Message-ID: <199908082304.aa22521@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've definitely come up with times where: > > > > 1) fsck checks the filesystem and gives it the OK, but it isn't. > > Yes, but is this a -p", which only does a partial check? If so, that > may be what it is supposed to do. No. > A lot of these sound like hardware. Some drives, especially IDE, will > just corrupt themselves. Turing off multi-block mode can somtimes help. > I have a Maxtor IDE drive (8.4GB) that I can not use with FreeBSD's > multi-block mode, as data will be corrupted and fsck will always report > errors. Nothing wrong with the hardware. The first time I had this trouble was when there was a new/revised ahc driver, which sometimes locked up one scsi bus preventing access to one half of a ccd array. Justin fixed stuff in the driver and it's been happy as larry ever since. The filesystem was definitely left in a state that fsck couldn't deal with (probably because some of the writes were still making it to the other disk?) The most recent time I was dump/restoring 3x4GB filesystems onto 3x9GB softupdates filesystems over the network and the machine died 16 minutes before it was done. The target drives are all recent revision Quantum Atlases connected to two Adaptec SCSI controlers. These disks weren't striped, one filesystem per disk. I have two people who watched do about 5 fsck's on one of the disks and it asked me the same things every time after the first. Every time since we've had no trouble with corruption. (We did have one weird problem where 4GB of disk space vanished wile using softupdates over NFS - it didn't show up with quot or du, and even persisted across reboots and fscking. Turning off soft updates and fscking reclaimed it I think). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 15:24:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from io.cts.com (io.cts.com [198.68.174.34]) by hub.freebsd.org (Postfix) with ESMTP id 9C52E14C2E for ; Sun, 8 Aug 1999 15:24:03 -0700 (PDT) (envelope-from mdavis@cts.com) Received: from VOYAGER (voyager.cts.com [198.68.174.38]) by io.cts.com (8.9.3/8.9.2) with SMTP id PAA00291; Sun, 8 Aug 1999 15:22:25 -0700 (PDT) (envelope-from mdavis@cts.com) From: "Morgan Davis" To: "Tom" , "David Malone" Cc: Subject: RE: Removing files in /lost+found causes panic Date: Sun, 8 Aug 1999 15:22:24 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom, thanks for the suggestion to use clri and fsck. This did the trick! David, I have Seagate SCSI drives, so it's not the IDE problem you described. My conclusion is that there is something not right in the kernel if trying to remove a file causes it to panic. Remove should be a lot like what clri and fsck does -- dellocate the inode, update free block map, tie up any loose ends so that that filesystem is stable. Apparently, rm is trying to do more -- perhaps stat the file in some way that is getting tripped up on odd characteristics of the file entry (since it looks like a block or character device, etc.). Since these odd files are not supposed to show up at all, I presume the kernel is assuming that such a situation never occurs and doesn't have to plan for that contingency. --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 16:10:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 00DE415089 for ; Sun, 8 Aug 1999 16:10:14 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 42209 invoked by uid 100); 8 Aug 1999 23:08:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Aug 1999 23:08:21 -0000 Date: Sun, 8 Aug 1999 16:08:20 -0700 (PDT) From: Mike Meyer To: Tom Cc: David Malone , Morgan Davis , freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, Tom wrote: :->Date: Sun, 8 Aug 1999 14:50:13 -0700 (PDT) :->From: Tom :->To: David Malone :->Cc: Morgan Davis , freebsd-stable@freebsd.org :->Subject: Re: Removing files in /lost+found causes panic :-> :->On Sun, 8 Aug 1999, David Malone wrote: :-> :->> On Sun, Aug 08, 1999 at 09:21:15AM -0700, Tom wrote: :->> :->> > I don't think you should ever need to use clri. The system should only :->> > panic if the filesystem is corrupt. If fsck finds serious damage, you :->> > should run it again to make sure everything. Chances are the first fsck :->> > left some unfixed problems. :->> :->> I've definitely come up with times where: :->> :->> 1) fsck checks the filesystem and gives it the OK, but it isn't. :-> :-> Yes, but is this a -p", which only does a partial check? If so, that :->may be what it is supposed to do. :-> :->> 2) fsck leaves weird files around in /lost+found which are difficult :->> or impossible to delete. :->> 3) fsck after about 8 runs still goes through the same list of questions :->> and asks to be rerun again. :->> 4) fsck says it doesn't need to be rerun, but if you rerun it it makes :->> more repairs. :-> :-> A lot of these sound like hardware. Some drives, especially IDE, will :->just corrupt themselves. Turing off multi-block mode can somtimes help. :->I have a Maxtor IDE drive (8.4GB) that I can not use with FreeBSD's :->multi-block mode, as data will be corrupted and fsck will always report :->errors. :-> :-> :->Tom :-> :-> :-> :->To Unsubscribe: send mail to majordomo@FreeBSD.org :->with "unsubscribe freebsd-stable" in the body of the message :-> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 16:10:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (castles523.castles.com [208.214.165.87]) by hub.freebsd.org (Postfix) with ESMTP id BF78615090 for ; Sun, 8 Aug 1999 16:10:13 -0700 (PDT) (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 QAA13667; Sun, 8 Aug 1999 16:02:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908082302.QAA13667@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Morgan Davis" Cc: "Tom" , "David Malone" , freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic In-reply-to: Your message of "Sun, 08 Aug 1999 15:22:24 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Aug 1999 16:02:57 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would, of course, have been _really_nice_ if you actually bothered to give us some details on these files before you nuked them... > Tom, thanks for the suggestion to use clri and fsck. This did the trick! > > David, I have Seagate SCSI drives, so it's not the IDE problem you > described. > > My conclusion is that there is something not right in the kernel if trying > to remove a file causes it to panic. Remove should be a lot like what clri > and fsck does -- dellocate the inode, update free block map, tie up any > loose ends so that that filesystem is stable. Apparently, rm is trying to > do more -- perhaps stat the file in some way that is getting tripped up on > odd characteristics of the file entry (since it looks like a block or > character device, etc.). Since these odd files are not supposed to show up > at all, I presume the kernel is assuming that such a situation never occurs > and doesn't have to plan for that contingency. > > --Morgan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 16:22:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 765B514D97 for ; Sun, 8 Aug 1999 16:22:02 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 42308 invoked by uid 100); 8 Aug 1999 23:20:09 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Aug 1999 23:20:09 -0000 Date: Sun, 8 Aug 1999 16:20:09 -0700 (PDT) From: Mike Meyer To: freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My apologies to all for the missed reply. I think it may be time to find a new mailer; cancel & send in Pine are to close together. :->> 1) fsck checks the filesystem and gives it the OK, but it isn't. :-> Yes, but is this a -p", which only does a partial check? If so, that :->may be what it is supposed to do. On first reading this, my reaction was "-p" stands for "preen", and it does *not* do a partial check! Checking the documentation and code showed that that reaction was in deed correct - if fsck in preen mode checks the disk, it does a complete check - but this is still a valid question, because "-p" checks to see if the disk is marked clean, and skips the rest of the disk in that case. I just want to make sure that nobody thinks that they missing something if they run fsck in preen mode after a crash. They aren't - preen mode is designed for system startup, and so does things quietly, and fixes things that it can safely fix, and runs them in parallel (which was what Chris Torek's "preen" command, from whence this mode gets it's name, did) to take advantage of overlapped IO. ; Sun, 8 Aug 1999 16:31:58 -0700 (PDT) (envelope-from mdavis@cts.com) Received: from VOYAGER (voyager.cts.com [198.68.174.38]) by io.cts.com (8.9.3/8.9.2) with SMTP id QAA00382; Sun, 8 Aug 1999 16:30:14 -0700 (PDT) (envelope-from mdavis@cts.com) From: "Morgan Davis" To: "Mike Smith" Cc: Subject: RE: Removing files in /lost+found causes panic Date: Sun, 8 Aug 1999 16:30:14 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701 In-reply-to: <199908082302.QAA13667@dingo.cdrom.com> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would, of course, have been _really_nice_ if you actually bothered > to give us some details on these files before you nuked them... Sorry, will keep that in mind if it happens again. Getting a clean system back up and running was the main thing on my mind. What steps do you recommend so I can get you the details you need? Not sure if this will be useful, but here's all I can tell you. I became aware of a problem during a tape backup. Dump complained about invalid file references. I stopped the backup when it indicated that the completion time was going to be over 800 hours (normally, it's about an hour). After getting into single user, I ran fsck which found a lot of errors. This put about a dozen files into lost+found directories on two filesystems. The files were mostly small -- between 60 and a couple hundred bytes. They appeared to be from files in /usr/src/contrib and a few in /usr/obj. (Nothing I couldn't restore from a cvsup and a make world). The modes, owner, group, and flags were scrambled nonsense -- there are no files on any healthy system with those attributes. I cleared out all the flags with chflags. I could clear all the modes except the special device type bits (block and character). Any attempt to remove the files resulted in a panic. However, subsequent fsck's would run through everything with no errors (except for the dirty filesystem warning, of course). I booted the FreeBSD install floppies and use the Fixit disk to try to remove the files from there, thinking maybe the fact that they were on the same filesystem as the kernel was the culprit. But after mounting the drives, attempts to remove the files resulted in similar panics. Finally, David Malone's suggestion to use clri + fsck was the magic to clean it all up. --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 8 17: 6:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2917D15032 for ; Sun, 8 Aug 1999 17:06:27 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA11010; Sun, 8 Aug 1999 18:03:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA02388; Sun, 8 Aug 1999 18:02:55 -0600 (MDT) Message-Id: <199908090002.SAA02388@harmony.village.org> To: David Malone Subject: Re: continued crashes with 3.1-Stable Cc: "Jordan K. Hubbard" , tcobb@staff.circle.net, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com In-reply-to: Your message of "Sun, 08 Aug 1999 22:50:59 BST." <19990808225059.B54409@walton.maths.tcd.ie> References: <19990808225059.B54409@walton.maths.tcd.ie> <2602.934003898@localhost> <199908081755.LAA01058@harmony.village.org> Date: Sun, 08 Aug 1999 18:02:55 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990808225059.B54409@walton.maths.tcd.ie> David Malone writes: : We also have patches which makes UDP based NFS reply with the correct : source address, which we're cleaning up. Would you be willing to share this, and other patches with the community? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 0: 8: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id AC30914F39 for ; Mon, 9 Aug 1999 00:07:58 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Aug 1999 08:03:43 +0100 (BST) To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG Subject: Re: continued crashes with 3.1-Stable In-reply-to: Your message of "Sun, 08 Aug 1999 18:02:55 MDT." <199908090002.SAA02388@harmony.village.org> X-Request-Do: Date: Mon, 09 Aug 1999 08:03:43 +0100 From: David Malone Message-ID: <199908090803.aa38073@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <19990808225059.B54409@walton.maths.tcd.ie> David Malone writes: > : We also have patches which makes UDP based NFS reply with the correct > : source address, which we're cleaning up. > > Would you be willing to share this, and other patches with the > community? We posted a crude form of them to one of the mailing lists not so long ago - we discovered that the nfsd patch was a bit rough and so Ian Dowse is cleaning them up. I'd say Ian will file a PR within the next week or so. I'm off to see the eclipse this week, and if Ian hasn't had a chance to look at sending them in I'll do it when I get back again. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 0:55:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from volodya.prime.net.ua (volodya.prime.net.ua [195.64.229.17]) by hub.freebsd.org (Postfix) with ESMTP id 706EB15240 for ; Mon, 9 Aug 1999 00:55:40 -0700 (PDT) (envelope-from andyo@prime.net.ua) Received: from prime.net.ua (localhost [127.0.0.1]) by volodya.prime.net.ua (8.9.3/8.8.8) with ESMTP id KAA08935; Mon, 9 Aug 1999 10:53:57 +0300 (EEST) (envelope-from andyo@prime.net.ua) Message-ID: <37AE890E.6DF5CB40@prime.net.ua> Date: Mon, 09 Aug 1999 10:53:52 +0300 From: "Andy V. Oleynik" Organization: M-Info X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en, ru, uk MIME-Version: 1.0 To: Nick Martin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Several Bugs (or maybe Features) (looks like known bug , see PR) References: <19990805052951.A72463@caerbanog.nimlabs.org> <19990806203429.A2789@dblab.ece.ntua.gr> <37AB31B6.872AFD8B@prime.net.ua> <19990807130016.H442@neglekt.lwhs.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See Poul-Henning Kamp's msg below: >Subject: > Re: kern/12022: System clock timewarps > Date: > Thu, 17 Jun 1999 13:43:26 +0200 > From: > Poul-Henning Kamp > To: > "Andy V. Oleynik" > CC: > freebsd-bugs@FreeBSD.ORG >The TSC doesn't (always) work on K5/model0 I committed a fix for this >to -current recently. >Try to remove/comment out this line in i386/isa/clock.c: > init_timecounter(&tsc_timecounter); I disabled TSC timecounter by reinitializing tsc_present variable into 0 after it initializes into 1. >In message <199906170720.AAA28120@freefall.freebsd.org>, "Andy V. Oleynik" writes: >The following reply was made to PR kern/12022; it has been noted by GNATS. > >From: "Andy V. Oleynik" >To: freebsd-gnats-submit@freebsd.org, dwhite@pond.net >Cc: >Subject: Re: kern/12022: System clock timewarps >Date: Thu, 17 Jun 1999 09:55:20 +0300 > > I have 2 boxes at work: > 1. Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 90040111 Hz > CPU: AMD K5 model 0 (90.04-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x501 Stepping=1 > Features=0x3bf > (BIOS reports: AMD-k5-PR90 CPU, > Award Modular BIOS v4.51PG, > Award P&P BIOS extension v1.0A, > M/B 580VPX-ITE8661-2A5LDL1CC-0) > 2. > Sorry, I can't give Timecounters strings 'cos I've removed 3.2-S and > > installed 2.2.8-R on this PC due the clock bug. > CPU: AMD K5 model 0 (74.54-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x501 Stepping=1 > Features=0x3bf > (BIOS reports: AMD-k5-PR75 CPU, > Award Modular BIOS v4.51PG release > 03/03/1997S, > Award P&P BIOS extension v1.0A, > M/B I430VX-02071997C-00) > Timecounters on 1st PC: > Jun 14 09:58:28 volodya /kernel: Timecounter "i8254" frequency > 1193182 Hz > Jun 14 09:58:28 volodya /kernel: Timecounter "TSC" frequency > 90040208 Hz Nick Martin wrote: > On Fri, Aug 06, 1999 at 10:04:23PM +0300, Andrej V. Olejnik@caerbanog (Andy V. Oleynik) wrote: > > Could U pleas send ur dmesg & MBD/CPU specifications? > > Yiorgos Adamopoulos wrote: > > I think I found the answer to why the clock is slow in a PR, namely to > turn off apm support. But that still doesnt tell me how to get the thing > to reboot properly (which is also very important). > > OK, here is the full dmesg from that box: > > 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.2-STABLE #3: Wed Aug 4 09:13:58 PDT 1999 > nim@caerbanog.nimlabs.org:/usr/src/sys/compile/CAERBANOG > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 74704326 Hz > CPU: AMD K5 model 0 (74.70-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x500 Stepping=0 > Features=0x3bf > real memory = 33554432 (32768K bytes) > avail memory = 29786112 (29088K bytes) > Preloaded elf kernel "kernel" at 0xc02ed000. > Probing for devices on PCI bus 0: > chip0: rev 0x02 on pci0.0.0 > ide_pci0: rev 0x04 on pci0.1.0 > de0: rev 0x22 int a irq 11 on pci0.9.0 > de0: Asante 21140A [10-100Mb/s] pass 2.2 > de0: address 00:00:94:a1:a6:d7 > de0: enabling 10baseT port > Qlogic ISP Driver, FreeBSD CAM Version 0.991, Core Version 1.8 > isp0: rev 0x02 int a irq 10 on pci0.10.0 > isp0: using Memory space register mapping > isp0: set PCI line size to 16 > isp0: set PCI latency to 64 > isp0: Board Revision 1020A, loaded F/W Revision 7.63.0 > isp0: not supporting QFRZ option for target 0 > isp0: not supporting QFRZ option for target 1 > isp0: not supporting QFRZ option for target 2 > isp0: not supporting QFRZ option for target 3 > isp0: not supporting QFRZ option for target 4 > isp0: not supporting QFRZ option for target 5 > isp0: not supporting QFRZ option for target 6 > isp0: not supporting QFRZ option for target 7 > isp0: not supporting QFRZ option for target 8 > isp0: not supporting QFRZ option for target 9 > isp0: not supporting QFRZ option for target 10 > isp0: not supporting QFRZ option for target 11 > isp0: not supporting QFRZ option for target 12 > isp0: not supporting QFRZ option for target 13 > isp0: not supporting QFRZ option for target 14 > isp0: not supporting QFRZ option for target 15 > isp0: skipping settings for target 8 bus 0 > isp0: skipping settings for target 9 bus 0 > isp0: skipping settings for target 10 bus 0 > isp0: skipping settings for target 11 bus 0 > isp0: skipping settings for target 12 bus 0 > isp0: skipping settings for target 13 bus 0 > isp0: skipping settings for target 14 bus 0 > isp0: skipping settings for target 15 bus 0 > Probing for PnP devices: > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <16 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > psm0 not found > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 2060MB (4219425 sectors), 4465 cyls, 15 heads, 63 S/T, 512 B/S > wdc1 not found at 0x170 > ppc0 at 0x378 irq 7 flags 0x40 on isa > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > ppi0: on ppbus 0 > plip0: on ppbus 0 > ep0 not found at 0x300 > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > Waiting 5 seconds for SCSI devices to settle > isp0: driver initiated bus reset of bus 0 > isp0: target 0 lun 0 had an unexpected bus free > isp0: Auto Request Sense failed for target 0 lun 0 > chanda0 at isp0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 8) > da0: 516MB (1057616 512 byte sectors: 64H 32S/T 516C) > ging root device to wd0s1a > WARNING: / was not properly dismounted > de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) > de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) > de0: abnormal interrupt: transmit underflow (switching to store-and-forward mode) > > Hope that helps. > > -- > Nick Martin, nim@nimlabs.org, http://www.nimlabs.org > > If God didn't mean for us to juggle, tennis balls wouldn't come three > to a can. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- WBW Andy V. Oleynik (When U work in virtual office prime.net.ua's U have good chance to obtain system administrator virtual money ö%-) +380442448363 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 2:38:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20]) by hub.freebsd.org (Postfix) with ESMTP id E2FE7151A9 for ; Mon, 9 Aug 1999 02:38:20 -0700 (PDT) (envelope-from sinbin.demos.su!yormungandr.demos.su!mishania@kremvax.demos.su) Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.5.31] for with ESMTP id NAA06183; Mon, 9 Aug 1999 13:35:42 +0400 Received: from yormungandr.demos.su by sinbin.demos.su with ESMTP id NAA34522; (8.6.12/D) Mon, 9 Aug 1999 13:35:23 +0400 Received: (from mishania@localhost) by yormungandr.demos.su (8.9.3/8.9.2) id NAA51182 for stable@freebsd.org; Mon, 9 Aug 1999 13:34:54 +0400 (MSD) (envelope-from mishania) Date: Mon, 9 Aug 1999 13:34:53 +0400 From: "Mikhail A. Sokolov" To: stable@freebsd.org Subject: repeated panics of recent -stable. Message-ID: <19990809133453.A51116@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, this's what savecore thinks about crashes in FreeBSD x.demos.su 3.2-STABLE FreeBSD 3.2-STABLE #0: Thu Aug 5 00:14:22 MSD 1999 mishania@x.demos.su:/usr/src/sys/compile/x i386 /mnt/pub/crash# gdb -k *26 initial pcb at 227b10 panicstr: vm_fault: fault on nofault entry, addr: cda40000 panic messages: --- panic: vm_fault: fault on nofault entry, addr: cda40000 syncing disks... 90 10 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 (da1:ahc1:0:1:0): Invalid command operation code Erm, this. Shouldn't it have gone away like long ago? Yes, it's Infortrend's RAID0x2 mirrored. dumping to dev 20401, offset 1691306 dump 512 ... --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xc013cf39 in panic ( fmt=0xc02067ce "vm_fault: fault on nofault entry, addr: %lx") at ../../kern/kern_shutdown.c:446 #2 0xc01c8b6e in vm_fault (map=0xc023e7b8, vaddr=3450077184, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:232 #3 0xc01ebf40 in trap_pfault (frame=0xd2f03ce0, usermode=0, eva=3450078844) at ../../i386/i386/trap.c:824 #4 0xc01ebbf2 in trap (frame={tf_es = 16, tf_ds = -1012989936, tf_edi = 13944, tf_esi = -1012975360, tf_ebp = -756007520, tf_isp = -756007672, tf_ebx = -844888456, tf_edx = -847849456, tf_ecx = 8191, tf_eax = 145016, tf_trapno = 12, tf_err = 0, tf_eip = -1071900669, tf_cs = 8, tf_eflags = 66182, tf_esp = -756297472, tf_ss = -756007204}) at ../../i386/i386/trap.c:437 #5 0xc01c1803 in ufs_lookup (ap=0xd2f03ddc) at ../../ufs/ufs/ufs_lookup.c:238 #6 0xc01c6615 in ufs_vnoperate (ap=0xd2f03ddc) at ../../ufs/ufs/ufs_vnops.c:2299 #7 0xc015bb48 in vfs_cache_lookup (ap=0xd2f03e38) at vnode_if.h:55 #8 0xc01c6615 in ufs_vnoperate (ap=0xd2f03e38) at ../../ufs/ufs/ufs_vnops.c:2299 #9 0xc015e01d in lookup (ndp=0xd2f03eb8) at vnode_if.h:31 #10 0xc015daf0 in namei (ndp=0xd2f03eb8) at ../../kern/vfs_lookup.c:152 #11 0xc01631bc in stat (p=0xd2e79a20, uap=0xd2f03f94) at ../../kern/vfs_syscalls.c:1614 #12 0xc01ec523 in syscall (frame={tf_es = 39, tf_ds = -1078001625, tf_edi = -1077945600, tf_esi = -1077945616, tf_ebp = -1077945640, tf_isp = -756006940, tf_ebx = 266344, tf_edx = 266355, tf_ecx = 0, tf_eax = 188, tf_trapno = 12, tf_err = 7, tf_eip = 141013, tf_cs = 31, tf_eflags = 646, tf_esp = -1077945748, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #13 0x226d5 in ?? () #14 0x651a in ?? () #15 0x65ad in ?? () #16 0x30fe in ?? () #17 0x10d3 in ?? () -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 3:28:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.stack.nl (zelden.stack.nl [131.155.140.128]) by hub.freebsd.org (Postfix) with ESMTP id F011714C1D for ; Mon, 9 Aug 1999 03:28:50 -0700 (PDT) (envelope-from marcolz@stack.nl) Received: from toad.stack.nl (toad.stack.nl [131.155.140.135]) by mailhost.stack.nl (Postfix) with ESMTP id 83B822D05 for ; Mon, 9 Aug 1999 12:26:51 +0200 (MET DST) Received: by toad.stack.nl (Postfix, from userid 333) id E4B2E969E; Mon, 9 Aug 1999 12:26:52 +0200 (CEST) Date: Mon, 9 Aug 1999 12:26:52 +0200 From: Marc Olzheim To: stable@freebsd.org Subject: 3.2-stable crash Message-ID: <19990809122652.A20347@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i X-Operating-System: FreeBSD toad.stack.nl 2.2.8-STABLE FreeBSD 2.2.8-STABLE X-URL: http://www.stack.nl/~marcolz/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. While testing some code with socketbuffers it came up that it's possible for any user to crash a 3.2-STABLE machine by just creating a lot of socketpairs, allocating some buffer memory for them, putting them in NONBLOCK mode and filling the buffer. FreeBSD 3.2 then simply panics and reboots. Linux is capable of handling the problem... Source of an example program at http://www.stack.nl/~marcolz/testsockbuf.c Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 5:36: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id 1577D15218 for ; Mon, 9 Aug 1999 05:35:57 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id IAA27736; Mon, 9 Aug 1999 08:33:46 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xma027035; Mon, 9 Aug 99 08:32:50 -0400 Date: Mon, 09 Aug 1999 08:32:46 -0400 (EDT) From: Seth Subject: Re: continued crashes with 3.1-Stable In-reply-to: <199908081822.LAA25860@freeway.dcfinc.com> To: "Chad R. Larson" Cc: tcobb@staff.circle.net, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My intention, of course, was not to start a war over who could generate the most load. You win. :) Keep in mind that load can represent the lack of processing capability of your machine as jobs are queued up 'cause they can't find CPU time in which to complete.... Ah. You're running Solaris. That explains it. :) SB On Sun, 8 Aug 1999, Chad R. Larson wrote: > As I recall, Seth wrote: > > Have to disagree. 3.1-R had some problems. 3.2-S works flawlessly, even > > under heavy load (big disk I/O and >24 system load averages). This is a > > dual Xeon 450, scsi disks off an adaptec 7890, 384 megs RAM. > > Heavy load? Hah! I laugh at your heavy load. Witness: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > chad@freebie[/home/chad]:21> telnet 138.113.17.2 > Trying 138.113.17.2... > Connected to stormy.anasazi.com. > Escape character is '^]'. > UNIX(r) System V Release 4.0 (stormy) > login: chad > Password: > UNIX System V Release 4, 1.1-94d079 Pyramid NILE > stormy > Copyright (c) 1984 AT&T > All Rights Reserved > Last login: Fri Jul 30 10:39:42 from freebie.dcfinc.com > TERM set to cons25 > No mail > 11:16am up 72 days, 2:33, 3 users, load average: 126.16, 123.52, 122.47 > chad@stormy[/home/chad]:22> logout > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > :-) ;-) :-) > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.net > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 6:57:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from chumbly.math.missouri.edu (chumbly.math.missouri.edu [128.206.72.12]) by hub.freebsd.org (Postfix) with ESMTP id 2B54F15183 for ; Mon, 9 Aug 1999 06:57:18 -0700 (PDT) (envelope-from rich@chumbly.math.missouri.edu) Received: (from rich@localhost) by chumbly.math.missouri.edu (8.9.1a/8.9.1) id IAA10323; Mon, 9 Aug 1999 08:55:07 -0500 (CDT) From: Rich Winkel Message-Id: <199908091355.IAA10323@chumbly.math.missouri.edu> Subject: Re: make installworld 3.2R -> 3.2S fails over NFS To: rich@chumbly.math.missouri.edu (Rich Winkel) Date: Mon, 9 Aug 1999 08:55:07 -0500 (CDT) Cc: freebsd-stable@freebsd.org In-Reply-To: <199907251851.NAA25780@chumbly.math.missouri.edu> from "Rich Winkel" at Jul 25, 99 01:51:52 pm 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just cvsupped fresh sources this weekend with the same result. Does anyone else use nfs to "installworld"? Or am I the only one having this problem? According to Rich Winkel: > > This is from 3.2 sources cvsup'd today. > The buildworld on the nfs server goes fine, the make.conf files are > identical on the server and client, but make installworld on the client gives: > > [... lots of lines ...] > ===> gnu/usr.bin/perl/perl > install -c -s -o root -g wheel -m 555 perl /usr/bin > /usr/bin/perl5 -> /usr/bin/perl > /usr/bin/perl5.00503 -> /usr/bin/perl > cd /usr/obj/usr/src/gnu/usr.bin/perl/perl/ext/B ; make -B install INSTALLPRIVLI > B=/usr/libdata/perl/5.00503 INSTALLARCHLIB=/usr/libdata/perl/5.00503/mach > make: don't know how to make Makefile.PL. Stop > *** Error code 2 > > Stop. > *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 6:59:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by hub.freebsd.org (Postfix) with ESMTP id 4F08C1521A for ; Mon, 9 Aug 1999 06:59:39 -0700 (PDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id JAA00379 for ; Mon, 9 Aug 1999 09:56:43 -0400 (EDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Date: Mon, 9 Aug 1999 09:56:43 -0400 (EDT) From: Greg Lynn To: freebsd-stable@freebsd.org Subject: testsockbuf.c Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 2.2.6 and this program WREAKED havoc on it :) Rebooted and then when I tried delete the a.out I got a page fault. I wasn't able to read it though because the machine again rebooted :( Scary... I also got strange socket errors after the machine was rebooted those two times... -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 7: 6:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (Postfix) with ESMTP id 56829151EE for ; Mon, 9 Aug 1999 07:06:09 -0700 (PDT) (envelope-from owensc@enc.edu) Received: from enc.edu (r2s1.r.its.enc.edu [10.100.0.21]) by itsdsv1.enc.edu (8.7.5/8.7.3) with ESMTP id JAA19399; Mon, 9 Aug 1999 09:45:26 -0400 (EDT) Message-ID: <37AEDFCA.E6984EDE@enc.edu> Date: Mon, 09 Aug 1999 10:03:54 -0400 From: Charles Owens Organization: Eastern Nazarene College X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Rich Winkel Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make installworld 3.2R -> 3.2S fails over NFS References: <199908091355.IAA10323@chumbly.math.missouri.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rich Winkel wrote: > I just cvsupped fresh sources this weekend with the same result. > Does anyone else use nfs to "installworld"? > Or am I the only one having this problem? From 3.0R to at least 3.1-stable I've seen this problem. The (annoying) workaround has been to do RW mounts of /usr/src and /usr/obj. I've seen some discussion of this problem on the -hackers list of late, with some mention of fixes. I updated my sources to the latest 3.2-stable on August 4th and happily found that running installworld over read-only NFS mounts worked again! So... I hope what you're seen doesn't mean it's broken again.... > According to Rich Winkel: > ? > ? This is from 3.2 sources cvsup'd today. > ? The buildworld on the nfs server goes fine, the make.conf files are > ? identical on the server and client, but make installworld on the client gives: > ? > ? [... lots of lines ...] > ? ===? gnu/usr.bin/perl/perl > ? install -c -s -o root -g wheel -m 555 perl /usr/bin > ? /usr/bin/perl5 -? /usr/bin/perl > ? /usr/bin/perl5.00503 -? /usr/bin/perl > ? cd /usr/obj/usr/src/gnu/usr.bin/perl/perl/ext/B ; make -B install INSTALLPRIVLI > ? B=/usr/libdata/perl/5.00503 INSTALLARCHLIB=/usr/libdata/perl/5.00503/mach > ? make: don't know how to make Makefile.PL. Stop > ? *** Error code 2 > ? > ? Stop. > ? *** Error code 1 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network ? Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 8:48:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id C708214BF1 for ; Mon, 9 Aug 1999 08:48:25 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id IAA29007; Mon, 9 Aug 1999 08:44:00 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199908091544.IAA29007@freeway.dcfinc.com> Subject: Re: continued crashes with 3.1-Stable In-Reply-To: from Seth at "Aug 9, 99 08:32:46 am" To: seth@freebie.dp.ny.frb.org (Seth) Date: Mon, 9 Aug 1999 08:44:00 -0700 (MST) Cc: tcobb@staff.circle.net, lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Seth wrote: > My intention, of course, was not to start a war over who could > generate the most load. You win. :) > > Keep in mind that load can represent the lack of processing capability > of your machine as jobs are queued up 'cause they can't find CPU time > in which to complete.... Ah. You're running Solaris. That explains > it. :) Actually, that machine is a Pyramid, running SysVr4 (Pyramid calls it DC/OSx). It's the machine our developers (ab)use. But it does set a standard for grace/stability under load. Even Pyramid is impressed. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 9:52:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id D54101521F for ; Mon, 9 Aug 1999 09:52:05 -0700 (PDT) (envelope-from kwc@world.std.com) Received: from world.std.com by europe.std.com (STD1.2/BZS-8-1.0) id MAA26794; Mon, 9 Aug 1999 12:49:45 -0400 (EDT) Received: by world.std.com (TheWorld/Spike-2.0) id AA09804; Mon, 9 Aug 1999 12:48:18 -0400 Date: Mon, 9 Aug 1999 12:48:18 -0400 From: kwc@world.std.com (Kenneth W Cochran) Message-Id: <199908091648.AA09804@world.std.com> To: freebsd-stable@freebsd.org Subject: Kernel ppp (pppd) version 2.3.5 --> 2.3.8 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the "status" of pppd more recent than 2.3.5 (2.3.8, for example) making it into -STABLE (RELENG_3)? Not a show-stopper, but I'm getting a strange "received bad configure-nak/rej" (at LOG_ERR level while trying to negotiate CCP) every time I connect. I do not get this behavior under Linux (Slackware 4.0/kernel 2.2.10/pppd-2.3.7). I don't recall getting it under Linux with pppd 2.3.5, though, either... IIRC the Linux version "properly" rejects the CCP negotiation it doesn't like... :) According to the pppd-2.3.8 sources, they have updated it for FreeBSD 3.0. I suppose I could install it "manually" but I'm not (yet) keen on messing with the source tree (ie. I don't want to mess-up the cvsup procedure). Is this worth my filing a pr? Thanks, -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 12:28:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.stack.nl (zelden.stack.nl [131.155.140.128]) by hub.freebsd.org (Postfix) with ESMTP id DD0CC152B8 for ; Mon, 9 Aug 1999 12:27:51 -0700 (PDT) (envelope-from marcolz@stack.nl) Received: from toad.stack.nl (toad.stack.nl [131.155.140.135]) by mailhost.stack.nl (Postfix) with ESMTP id 356362D06; Mon, 9 Aug 1999 21:23:21 +0200 (MET DST) Received: by toad.stack.nl (Postfix, from userid 333) id 2B117969E; Mon, 9 Aug 1999 21:23:24 +0200 (CEST) Date: Mon, 9 Aug 1999 21:23:24 +0200 From: Marc Olzheim To: Greg Lynn Cc: freebsd-stable@freebsd.org Subject: Re: testsockbuf.c Message-ID: <19990809212324.A4984@stack.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Greg Lynn on Mon, Aug 09, 1999 at 09:56:43AM -0400 X-Operating-System: FreeBSD toad.stack.nl 2.2.8-STABLE FreeBSD 2.2.8-STABLE X-URL: http://www.stack.nl/~marcolz/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm running 2.2.6 and this program WREAKED havoc on it :) It seems to work on NetBSD 1.3.2 too.... Perhaps a BSD-ism ? Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 12:28:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by hub.freebsd.org (Postfix) with ESMTP id AFAB514F66 for ; Mon, 9 Aug 1999 12:28:51 -0700 (PDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id PAA01214; Mon, 9 Aug 1999 15:26:24 -0400 (EDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Date: Mon, 9 Aug 1999 15:26:24 -0400 (EDT) From: Greg Lynn To: Marc Olzheim Cc: freebsd-stable@freebsd.org Subject: Re: testsockbuf.c In-Reply-To: <19990809212324.A4984@stack.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Marc Olzheim wrote: > > > > I'm running 2.2.6 and this program WREAKED havoc on it :) > > It seems to work on NetBSD 1.3.2 too.... > Perhaps a BSD-ism ? > > Marc > Isn't this a huge problem for ordinary users on a system?? I mean there aren't any user restrictions on sockets right? I imagine there will be some sort of follow up on this exploit? -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 12:37: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from soms.stack.nl (soms.stack.nl [131.155.141.134]) by hub.freebsd.org (Postfix) with ESMTP id B43431519E for ; Mon, 9 Aug 1999 12:37:03 -0700 (PDT) (envelope-from marcolz@stack.nl) Received: from toad.stack.nl (toad.stack.nl [131.155.140.135]) by soms.stack.nl (Postfix) with ESMTP id 2B634EF57; Mon, 9 Aug 1999 21:34:49 +0200 (CEST) Received: by toad.stack.nl (Postfix, from userid 333) id 37C1D969E; Mon, 9 Aug 1999 21:34:49 +0200 (CEST) Date: Mon, 9 Aug 1999 21:34:49 +0200 From: Marc Olzheim To: Greg Lynn Cc: Marc Olzheim , freebsd-stable@freebsd.org Subject: Re: testsockbuf.c Message-ID: <19990809213449.A5585@stack.nl> References: <19990809212324.A4984@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Greg Lynn on Mon, Aug 09, 1999 at 03:26:24PM -0400 X-Operating-System: FreeBSD toad.stack.nl 2.2.8-STABLE FreeBSD 2.2.8-STABLE X-URL: http://www.stack.nl/~marcolz/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Isn't this a huge problem for ordinary users on a system?? I mean > there aren't any user restrictions on sockets right? I imagine > there will be some sort of follow up on this exploit? Well, there is a 256k limit per socket of the buffer (I & O), try sysctl kern.maxsockbuf and you can limit the number of sockets with the maximum number of filedescriptors per process (ulimit -a), but that's just not safe enough. It seems that the kernel doesn't check wether the space it wants to allocate still exists or not. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 13:22:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 818DB152AF for ; Mon, 9 Aug 1999 13:22:34 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id NAA05943; Mon, 9 Aug 1999 13:19:28 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 09 Aug 1999 13:19:28 -0700 Date: Mon, 9 Aug 1999 13:19:28 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: Marc Olzheim Cc: Greg Lynn , freebsd-stable@freebsd.org Subject: Re: testsockbuf.c In-Reply-To: <19990809213449.A5585@stack.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: marcolz@stack.nl,dglynn@vaview5.vavu.vt.edu,freebsd-stable@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would raising the number of NMBCLUSTERS help? Or would it just postpone the problem? Solaris/x86 also does not have any problems with the code. -Kip On Mon, 9 Aug 1999, Marc Olzheim wrote: > > Isn't this a huge problem for ordinary users on a system?? I mean > > there aren't any user restrictions on sockets right? I imagine > > there will be some sort of follow up on this exploit? > > Well, there is a 256k limit per socket of the buffer (I & O), try > sysctl kern.maxsockbuf and you can limit the number of sockets with > the maximum number of filedescriptors per process (ulimit -a), but that's > just not safe enough. > > It seems that the kernel doesn't check wether the space it wants to > allocate still exists or not. > > Marc > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 9 21:17:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from public.guangzhou.gd.cn (smtp.guangzhou.gd.cn [202.96.128.111]) by hub.freebsd.org (Postfix) with ESMTP id 838A315010 for ; Mon, 9 Aug 1999 21:16:43 -0700 (PDT) (envelope-from sniper@mail.777.net.cn) Received: from xzh (max3-208.guangzhou.gd.cn [202.96.185.208]) by public.guangzhou.gd.cn (8.9.3/8.9.1) with SMTP id MAA27902 for ; Tue, 10 Aug 1999 12:01:22 +0800 (CST) Message-ID: <003401bee2e6$fbc1f360$170a0a0a@xzh> From: "sniper" To: Subject: Date: Tue, 10 Aug 1999 12:14:22 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 2c4e7798 unsubscribe freebsd-stable sniper@mail.777.net.cn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 10 1:53:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ms1.tomail.com.tw (ms1.tomail.com.tw [139.175.250.174]) by hub.freebsd.org (Postfix) with SMTP id 3AADE1527C for ; Tue, 10 Aug 1999 01:53:01 -0700 (PDT) (envelope-from silver@tomail.com.tw) Received: (qmail 92262 invoked from network); 10 Aug 1999 08:11:19 -0000 Received: from eva.pchome.com.tw (HELO tomail.com.tw) (203.70.70.2) by ms1.tomail.com.tw with SMTP; 10 Aug 1999 08:11:19 -0000 Message-ID: <37AFDE9D.DEF0369D@tomail.com.tw> Date: Tue, 10 Aug 1999 16:11:09 +0800 From: Silver CHEN X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en,zh-TW MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: [Q] 'ELF interpreter /usr/libexec/ld-elf.so.1 not found' on an basy server??? Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir: I have an very busy server for email service. there are more than 100K virtual users on that machine. It is an PII-400 w/ 256MB RAM, OS is 3.2-stable. The general performance is good, but under some conditions, I got the following messages: ELF interpreter /usr/libexec/ld-elf.so.1 not found ELF interpreter /usr/libexec/ld-elf.so.1 not found ELF interpreter /usr/libexec/ld-elf.so.1 not found ELF interpreter /usr/libexec/ld-elf.so.1 not found ELF interpreter /usr/libexec/ld-elf.so.1 not found ..... It seems that the OS can't find that file wher it needs, but I do sure that it is just there. I have tunned my MAX_USER to 256, so it seems not a 'file-descriptor run out' problem. I can't find a possible reason for this, so I post this message. Thanks for any response. -- +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | Shan-Ta CHEN E-Mail : sansil@pchome.com.tw | | Silver CHEN Tel(O) : +886-2-2773-9858-288 | | ³¯µ½¹F Tel(H) : +886-2-2914-1402 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ _____________________________________________________________ Get Your Free E-Mail at http://www.ToMail.com.tw Right Now! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 10 9:42:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from chumbly.math.missouri.edu (chumbly.math.missouri.edu [128.206.72.12]) by hub.freebsd.org (Postfix) with ESMTP id B38C214BF3 for ; Tue, 10 Aug 1999 09:42:38 -0700 (PDT) (envelope-from rich@chumbly.math.missouri.edu) Received: (from rich@localhost) by chumbly.math.missouri.edu (8.9.1a/8.9.1) id LAA19011; Tue, 10 Aug 1999 11:42:29 -0500 (CDT) From: Rich Winkel Message-Id: <199908101642.LAA19011@chumbly.math.missouri.edu> Subject: Re: make installworld 3.2R -> 3.2S fails over NFS To: owensc@enc.edu (Charles Owens) Date: Tue, 10 Aug 1999 11:42:29 -0500 (CDT) Cc: rich@chumbly.math.missouri.edu, freebsd-stable@freebsd.org In-Reply-To: <37AEDFCA.E6984EDE@enc.edu> from "Charles Owens" at Aug 9, 99 10:03:54 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Charles Owens: > Rich Winkel wrote: > > I just cvsupped fresh sources this weekend with the same result. > > Does anyone else use nfs to "installworld"? > > Or am I the only one having this problem? > > From 3.0R to at least 3.1-stable I've seen this problem. The > (annoying) workaround has been to do RW mounts of /usr/src and > /usr/obj. I've seen some discussion of this problem on the -hackers > list of late, with some mention of fixes. I updated my sources to the > latest 3.2-stable on August 4th and happily found that running > installworld over read-only NFS mounts worked again! Actually this error arises with a r/w mount. I get a different error (while trying to make a symbolic link) when it's r/o. In other words, it's completely broken :-< Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 10 17:26:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 80790154C8 for ; Tue, 10 Aug 1999 17:26:38 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-2-69.dialup.rdu.ipass.net [209.170.133.69]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id UAA12554 for ; Tue, 10 Aug 1999 20:26:36 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id UAA00807 for stable@freebsd.org; Tue, 10 Aug 1999 20:27:52 -0400 (EDT) (envelope-from rhh) Date: Tue, 10 Aug 1999 20:27:52 -0400 From: Randall Hopper To: stable@freebsd.org Subject: (Bug?) Console toasted by XFree 3.9.15 Message-ID: <19990810202752.A709@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before I report to XFree86, I thought I'd post here to make sure it isn't likely to be a FreeBSD syscons issue. I just built XFree86 3.9.15 on 3.2-RELEASE. I haven't done much testing, but it does come up and display xterms, TV windows, etc. However, when I hit -- to kill X and dump to the console, the video card quit emitting a signal altogether (that is, my monitor's "lost-signal" menu came up). Anybody seen this one? Report it to XFree86? Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 10 17:42: 5 1999 Delivered-To: freebsd-stable@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 5014D154B9 for ; Tue, 10 Aug 1999 17:42:02 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:a4WJWFBBRbdcR3BnJWpzc7Hmp8FV1SB6@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA14470; Wed, 11 Aug 1999 09:40:35 +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 JAA01126; Wed, 11 Aug 1999 09:44:55 +0900 (JST) Message-Id: <199908110044.JAA01126@zodiac.mech.utsunomiya-u.ac.jp> To: Randall Hopper Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: (Bug?) Console toasted by XFree 3.9.15 In-reply-to: Your message of "Tue, 10 Aug 1999 20:27:52 -0400." <19990810202752.A709@ipass.net> References: <19990810202752.A709@ipass.net> Date: Wed, 11 Aug 1999 09:44:54 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I just built XFree86 3.9.15 on 3.2-RELEASE. I haven't done much testing, >but it does come up and display xterms, TV windows, etc. > >However, when I hit -- to kill X and dump to the console, >the video card quit emitting a signal altogether (that is, my monitor's >"lost-signal" menu came up). > >Anybody seen this one? Report it to XFree86? Which video card and X server are you using? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 10 18:12:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 421A815546 for ; Tue, 10 Aug 1999 18:12:33 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-2-69.dialup.rdu.ipass.net [209.170.133.69]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id UAA16426; Tue, 10 Aug 1999 20:47:19 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id UAA01839; Tue, 10 Aug 1999 20:48:39 -0400 (EDT) (envelope-from rhh) Date: Tue, 10 Aug 1999 20:48:39 -0400 From: Randall Hopper To: Kazutaka YOKOTA Cc: stable@freebsd.org Subject: Re: (Bug?) Console toasted by XFree 3.9.15 Message-ID: <19990810204839.A1711@ipass.net> References: <19990810202752.A709@ipass.net> <199908110044.JAA01126@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199908110044.JAA01126@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Wed, Aug 11, 1999 at 09:44:54AM +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA: | |>I just built XFree86 3.9.15 on 3.2-RELEASE. I haven't done much testing, |>but it does come up and display xterms, TV windows, etc. |> |>However, when I hit -- to kill X and dump to the console, |>the video card quit emitting a signal altogether (that is, my monitor's |>"lost-signal" menu came up). |> |>Anybody seen this one? Report it to XFree86? | |Which video card and X server are you using? CARD : STB Velocity 3D 4Meg (S3 Virge/VX) SERVER: s3virge X VID MODE: 1600x1200 virtual, 1344x1008x16bpp actual SYSCONS MODE: 132x43 I tried the vga driver first, thinking the old SVGA server might have been rolled into that, but it didn't know 16bpp. So I switched to s3virge. Randall ------------------------------------------------------------------------------- (**) |-->Screen "STB-Viewsonic" (0) (**) | |-->Monitor "Viewsonic PT813" (**) | |-->Device "STB Velocity 3D" ... (--) PCI: (0:9:0) 3Dfx Interactive Voodoo Graphics rev 2, Mem @ 0xe7000000/24 (--) PCI: (0:11:0) BrookTree 848 rev 17, Mem @ 0xe6800000/12 (--) PCI: (0:12:0) S3 ViRGE/VX rev 2, Mem @ 0xe0000000/26 ... VGA: card at 0:12:0 is claimed by a Device section ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 10 18:21:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 3CA0D14BD4 for ; Tue, 10 Aug 1999 18:21:37 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from elbas.partitur.se (elbas.partitur.se [193.219.246.222]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id DAA24228; Wed, 11 Aug 1999 03:20:54 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by elbas.partitur.se (8.9.3/8.9.3) with ESMTP id DAA70675; Wed, 11 Aug 1999 03:20:54 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <37B0CFF6.473C68DC@partitur.se> Date: Wed, 11 Aug 1999 01:20:54 +0000 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-isp@freebbsd.org Subject: fresh fbsd-stable and real audio server hangs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm experiencing something strange: I just updated one of our servers this week-end, and now the real audio server won't run. I have rmserver on a bunch of similar machines, and it works fine for them with practically the same setup. I updated the system from FreeBSD-3-STABLE as of March 31st to FreeBSD-3-STABLE as of Aug 8. I also added a second processor. It works very satisfactory, apart from this. There's no way to access any of the rmserver's services; there's no answer on the http admin port either.... When trying to connect with rvplayer, the connection hangs on "Contacting host" until I kill the server. I then get an error message 29, server disconnected. The log files are never touched. I'm of course sending this to the RealAudio support folks, but I get the feeling they might not be able to help, since this seems pretty OS related (I updated the OS, other machines run fine with the same realaudio installation but with older (July 7th) FreeBSD systems). I'm not to familiar at debugging this sort of thing, but I can see a few differencies: on the machines where rmserver works fine, lsof -i reveals: # lsof -i | grep rmserver rmserver 38163 root 6u inet 0xca8caa80 0t0 TCP pingpong-ing.hj.se:7070 (LISTEN) rmserver 38163 root 7u inet 0xca8ca720 0t0 TCP pingpong-ing.hj.se:rtsp (LISTEN) rmserver 38163 root 8u inet 0xca8c6720 0t0 TCP pingpong-ing.hj.se:8080 (LISTEN) rmserver 38163 root 9u inet 0xca8c72a0 0t0 TCP pingpong-ing.hj.se:2737 (LISTEN) rmserver 38163 root 10u inet 0xca8cd3c0 0t0 TCP localhost:7070 (LISTEN) rmserver 38163 root 11u inet 0xca8c82a0 0t0 TCP localhost:rtsp (LISTEN) rmserver 38163 root 12u inet 0xca8c7720 0t0 TCP localhost:8080 (LISTEN) rmserver 38163 root 13u inet 0xca8ceba0 0t0 TCP localhost:2737 (LISTEN) rmserver 38165 root 5u inet 0xca8cc3c0 0t0 TCP *:4040 (LISTEN) rmserver 38167 root 5u inet 0xca8c8720 0t0 TCP *:mmcc (LISTEN) rmserver 38170 root 5u inet 0xca8cb960 0t0 TCP *:9090 (LISTEN) rmserver 38172 root 7u inet 0xca853d80 0t0 UDP *:1131 rmserver 38172 root 8u inet 0xca853de0 0t0 UDP *:6770 while on the bad machine, the last "*:port#" rows are missing: rmserver 62759 root 6u inet 0xc9f01de0 0t0 TCP puka.partitur.se:7070 (LISTEN) rmserver 62759 root 7u inet 0xc9f12720 0t0 TCP puka.partitur.se:rtsp (LISTEN) rmserver 62759 root 8u inet 0xc9f0e3c0 0t0 TCP puka.partitur.se:8080 (LISTEN) rmserver 62759 root 9u inet 0xc9f124e0 0t0 TCP puka.partitur.se:3098 (LISTEN) rmserver 62759 root 10u inet 0xc9f11180 0t0 TCP localhost.partitur.se:7070 (LISTEN) rmserver 62759 root 11u inet 0xc9f09180 0t0 TCP localhost.partitur.se:rtsp (LISTEN) rmserver 62759 root 12u inet 0xc9f07960 0t0 TCP localhost.partitur.se:8080 (LISTEN) rmserver 62759 root 13u inet 0xc9f10de0 0t0 TCP localhost.partitur.se:3098 (LISTEN) ------------------- When running the server from the command line with no redirect to dev/null, I can see it stopping before reading all of the Plugins: # /usr/local/libexec/rmserver/Bin/rmserver /usr/local/libexec/rmserver/rmserver.cfg Creating Server Space... Starting RealServer 6.0 Core... Loading RealServer License Files... I: Loading Plugins... I: /usr/local/libexec/rmserver/Plugins/adminfs.so.6.0 RealNetworks Admin File System I: /usr/local/libexec/rmserver/Plugins/allow.so.6.0 RealNetworks Basic Allowance Plugin I: /usr/local/libexec/rmserver/Plugins/archplin.so.6.0 RealNetworks Live Archiver Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks AU Renderer Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks PCM Renderer Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks AU File Format Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks WAVE File Format Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks AIFF File Format Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks DVI4 Renderer Plugin I: /usr/local/libexec/rmserver/Plugins/authmgr.so.6.0 RealNetworks Authentication Manager I: /usr/local/libexec/rmserver/Plugins/bascauth.so.6.0 RealNetworks Basic Authenticator I: /usr/local/libexec/rmserver/Plugins/dbmgr.so.6.0 RealNetworks Database Manager I: /usr/local/libexec/rmserver/Plugins/dbwrap.so.6.0 RealNetworks 5.0 Database Wrapper I: /usr/local/libexec/rmserver/Plugins/encoplin.so.6.0 RealNetworks Encoder Broadcast Plugin I: /usr/local/libexec/rmserver/Plugins/farmplin.so.6.0 RealNetworks Farm Split Broadcast Plugin I: /usr/local/libexec/rmserver/Plugins/liv3plin.so.6.0 RealNetworks Live Broadcast Plugin I: /usr/local/libexec/rmserver/Plugins/logplin.so.6.0 RealNetworks Logging Plugin I: /usr/local/libexec/rmserver/Plugins/plusplin.so.6.0 RealNetworks PlusURL File Format Plugin I: /usr/local/libexec/rmserver/Plugins/pplyplin.so.6.0 RealNetworks Scalable Multicast Plugin I: /usr/local/libexec/rmserver/Plugins/ppvallow.so.6.0 RealNetworks Pay Per View Allowance Plug I: /usr/local/libexec/rmserver/Plugins/ppvbasic.so.6.0 RealNetworks FlatFile Database Plugin I: /usr/local/libexec/rmserver/Plugins/ppvmsql.so.6.0 RealNetworks Mini SQL PPV Database Plugi I: /usr/local/libexec/rmserver/Plugins/pxcbmp.so.6.0 RealNetworks RealPix BMP Codec Plugin I: /usr/local/libexec/rmserver/Plugins/pxcgif.so.6.0 RealNetworks RealPix GIF Codec Plugin I: /usr/local/libexec/rmserver/Plugins/pxcjpeg.so.6.0 RealNetworks RealPix JPEG Codec Plugin I: /usr/local/libexec/rmserver/Plugins/pxexfx.so.6.0 RealNetworks RealPix External Effect Sam I: /usr/local/libexec/rmserver/Plugins/pxff.so.6.0 RealNetworks RealPix Format Plugin I: /usr/local/libexec/rmserver/Plugins/pxgf.so.6.0 RealNetworks GIF File Format Plugin I: /usr/local/libexec/rmserver/Plugins/pxjf.so.6.0 RealNetworks JPEG File Format Plugin I: /usr/local/libexec/rmserver/Plugins/ramplin.so.6.0 RealNetworks Ramgen File System I: /usr/local/libexec/rmserver/Plugins/rmffplin.so.6.0 RealNetworks RealMedia File Format Plugi I: /usr/local/libexec/rmserver/Plugins/rn5auth.so.6.0 RealNetworks RN5 Authenticator I: /usr/local/libexec/rmserver/Plugins/rtffplin.so.6.0 RealNetworks RealText File Format Plugin I: /usr/local/libexec/rmserver/Plugins/sdpplin.so.6.0 RealNetworks SDP Stream Description Plug I: /usr/local/libexec/rmserver/Plugins/smlffpln.so.6.0 RealNetworks SMIL File Format Plugin I: /usr/local/libexec/rmserver/Plugins/smonplin.so.6.0 RealNetworks System Monitor I: /usr/local/libexec/rmserver/Plugins/spltplin.so.6.0 RealNetworks Splitter Broadcast Plugin I: /usr/local/libexec/rmserver/Plugins/smplfsys.so.6.0 RealNetworks Local File System I: /usr/local/libexec/rmserver/Plugins/swff.so.6.0 Shockwave Flash Format Plugin But the a working copy goes somewhat further: # /usr/local/libexec/rmserver/Bin/rmserver /opt/etc/rmserver.cfg Creating Server Space... Starting RealServer 6.0 Core... Loading RealServer License Files... I: Loading Plugins... I: /usr/local/libexec/rmserver/Plugins/adminfs.so.6.0 RealNetworks Admin File System I: /usr/local/libexec/rmserver/Plugins/allow.so.6.0 RealNetworks Basic Allowance Plugin I: /usr/local/libexec/rmserver/Plugins/archplin.so.6.0 RealNetworks Live Archiver Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks AU Renderer Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks PCM Renderer Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks AU File Format Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks WAVE File Format Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks AIFF File Format Plugin I: /usr/local/libexec/rmserver/Plugins/audplin.so.6.0 RealNetworks DVI4 Renderer Plugin I: /usr/local/libexec/rmserver/Plugins/authmgr.so.6.0 RealNetworks Authentication Manager I: /usr/local/libexec/rmserver/Plugins/bascauth.so.6.0 RealNetworks Basic Authenticator I: /usr/local/libexec/rmserver/Plugins/dbmgr.so.6.0 RealNetworks Database Manager I: /usr/local/libexec/rmserver/Plugins/dbwrap.so.6.0 RealNetworks 5.0 Database Wrapper I: /usr/local/libexec/rmserver/Plugins/encoplin.so.6.0 RealNetworks Encoder Broadcast Plugin I: /usr/local/libexec/rmserver/Plugins/farmplin.so.6.0 RealNetworks Farm Split Broadcast Plugin I: /usr/local/libexec/rmserver/Plugins/liv3plin.so.6.0 RealNetworks Live Broadcast Plugin I: /usr/local/libexec/rmserver/Plugins/logplin.so.6.0 RealNetworks Logging Plugin I: /usr/local/libexec/rmserver/Plugins/plusplin.so.6.0 RealNetworks PlusURL File Format Plugin I: /usr/local/libexec/rmserver/Plugins/pplyplin.so.6.0 RealNetworks Scalable Multicast Plugin I: /usr/local/libexec/rmserver/Plugins/ppvallow.so.6.0 RealNetworks Pay Per View Allowance Plug I: /usr/local/libexec/rmserver/Plugins/ppvbasic.so.6.0 RealNetworks FlatFile Database Plugin I: /usr/local/libexec/rmserver/Plugins/ppvmsql.so.6.0 RealNetworks Mini SQL PPV Database Plugi I: /usr/local/libexec/rmserver/Plugins/pxcbmp.so.6.0 RealNetworks RealPix BMP Codec Plugin I: /usr/local/libexec/rmserver/Plugins/pxcgif.so.6.0 RealNetworks RealPix GIF Codec Plugin I: /usr/local/libexec/rmserver/Plugins/pxcjpeg.so.6.0 RealNetworks RealPix JPEG Codec Plugin I: /usr/local/libexec/rmserver/Plugins/pxexfx.so.6.0 RealNetworks RealPix External Effect Sam I: /usr/local/libexec/rmserver/Plugins/pxff.so.6.0 RealNetworks RealPix Format Plugin I: /usr/local/libexec/rmserver/Plugins/pxgf.so.6.0 RealNetworks GIF File Format Plugin I: /usr/local/libexec/rmserver/Plugins/pxjf.so.6.0 RealNetworks JPEG File Format Plugin I: /usr/local/libexec/rmserver/Plugins/ramplin.so.6.0 RealNetworks Ramgen File System I: /usr/local/libexec/rmserver/Plugins/rmffplin.so.6.0 RealNetworks RealMedia File Format Plugi I: /usr/local/libexec/rmserver/Plugins/rn5auth.so.6.0 RealNetworks RN5 Authenticator I: /usr/local/libexec/rmserver/Plugins/rtffplin.so.6.0 RealNetworks RealText File Format Plugin I: /usr/local/libexec/rmserver/Plugins/sdpplin.so.6.0 RealNetworks SDP Stream Description Plug I: /usr/local/libexec/rmserver/Plugins/smlffpln.so.6.0 RealNetworks SMIL File Format Plugin I: /usr/local/libexec/rmserver/Plugins/smonplin.so.6.0 RealNetworks System Monitor I: /usr/local/libexec/rmserver/Plugins/spltplin.so.6.0 RealNetworks Splitter Broadcast Plugin I: /usr/local/libexec/rmserver/Plugins/smplfsys.so.6.0 RealNetworks Local File System I: /usr/local/libexec/rmserver/Plugins/swff.so.6.0 Shockwave Flash Format Plugin I: /usr/local/libexec/rmserver/Plugins/vidplin.so.6.0 RealNetworks RGB Renderer Plugin I: /usr/local/libexec/rmserver/Plugins/vidplin.so.6.0 RealNetworks AVI File Format Plugin I: /usr/local/libexec/rmserver/Plugins/vidplin.so.6.0 RealNetworks QuickTime File Format Plugi I: /usr/local/libexec/rmserver/Plugins/vidplin.so.6.0 RealNetworks Active Stream Format Versio I: /usr/local/libexec/rmserver/Plugins/vivff.so.6.0 VivoActive File Format Plugin The last five lines are missing from the bad server startup. $ rmserver -v Creating Server Space... Starting RealServer 6.0 Core... RealServer (c) 1995-1998 RealNetworks, Inc. All rights reserved. Version: 6.0.3.353 Platform: freebsd3 Here's a tcpdump from trying to connect: 03:10:46.610541 elbas.partitur.se.4251 > puka.partitur.se.7070: S 3043916040:3043916040(0) win 16384 (DF) 03:10:46.610692 puka.partitur.se.7070 > elbas.partitur.se.4251: S 1357161008:1357161008(0) ack 3043916041 win 17520 (DF) 03:10:46.610729 elbas.partitur.se.4251 > puka.partitur.se.7070: . ack 1 win 17520 (DF) 03:10:46.611024 elbas.partitur.se.4251 > puka.partitur.se.7070: P 1:399(398) ack 1 win 17520 (DF) 03:10:46.715954 puka.partitur.se.7070 > elbas.partitur.se.4251: . ack 399 win 17122 (DF) 03:10:46.715992 elbas.partitur.se.4251 > puka.partitur.se.7070: P 399:400(1) ack 1 win 17520 (DF) 03:10:46.915932 puka.partitur.se.7070 > elbas.partitur.se.4251: . ack 400 win 17121 (DF) And when I click stop: 03:10:50.829169 elbas.partitur.se.4251 > puka.partitur.se.7070: F 400:400(0) ack 1 win 17520 (DF) 03:10:50.829279 puka.partitur.se.7070 > elbas.partitur.se.4251: . ack 401 win 17121 (DF) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 10 21:50: 7 1999 Delivered-To: freebsd-stable@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 18D8114F10 for ; Tue, 10 Aug 1999 21:49:58 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:xdmMfFle5AyYW7Bkd3UxKET1PxeFhB4I@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id NAA13545; Wed, 11 Aug 1999 13:49:53 +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 NAA04504; Wed, 11 Aug 1999 13:54:12 +0900 (JST) Message-Id: <199908110454.NAA04504@zodiac.mech.utsunomiya-u.ac.jp> To: Randall Hopper Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: (Bug?) Console toasted by XFree 3.9.15 In-reply-to: Your message of "Tue, 10 Aug 1999 20:48:39 -0400." <19990810204839.A1711@ipass.net> References: <19990810202752.A709@ipass.net> <199908110044.JAA01126@zodiac.mech.utsunomiya-u.ac.jp> <19990810204839.A1711@ipass.net> Date: Wed, 11 Aug 1999 13:54:11 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > |>However, when I hit -- to kill X and dump to the console, > |>the video card quit emitting a signal altogether (that is, my monitor's > |>"lost-signal" menu came up). > |> > |>Anybody seen this one? Report it to XFree86? > | > |Which video card and X server are you using? > > CARD : STB Velocity 3D 4Meg (S3 Virge/VX) > SERVER: s3virge > X VID MODE: 1600x1200 virtual, 1344x1008x16bpp actual >SYSCONS MODE: 132x43 > >I tried the vga driver first, thinking the old SVGA server might have been >rolled into that, but it didn't know 16bpp. So I switched to s3virge. Are you able to switch between the X session and text vtys by hitting Ctl-Alt-Fn while the X server is running? You set syscons into the VESA 132x43 mode. How did you do that? Did you run vidcontrol by hand? Or, you run it in /etc/rc*? Are all vtys set in this 132x43 mode? Or, just a single vty is set to this mode? Have you ever start the X server when all vtys are in the standard 80x25 mode? Have you had the same or similar problem before with the previous versions of XFree86? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 1:59:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from buffy.tpgi.com.au (buffy.tpgi.com.au [203.12.160.34]) by hub.freebsd.org (Postfix) with ESMTP id 8C2B315098 for ; Wed, 11 Aug 1999 01:59:02 -0700 (PDT) (envelope-from eirvine@tpgi.com.au) Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.8.7/8.8.7) id SAA13552 for ; Wed, 11 Aug 1999 18:58:14 +1000 Received: from kmidc71-67.ecopost.com.au(203.28.71.67), claiming to be "tpgi.com.au" via SMTP by buffy.tpgi.com.au, id smtpda13456; Wed Aug 11 18:57:59 1999 Message-ID: <37B13B0C.564196AA@tpgi.com.au> Date: Wed, 11 Aug 1999 18:57:48 +1000 From: eirvine X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Compiled a kernel with egcs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all. Running a recent cvsup of 3.2 on my new PC at home. I found I could compile a kernel with egcs. Is this expected behaviour? I thought I could only do this on current. Eddie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 7:47:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 6092514D28 for ; Wed, 11 Aug 1999 07:47:35 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 10:42:24 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B4057@FREYA> From: tcobb@staff.circle.net To: freebsd-stable@freebsd.org Subject: On freezes in 3.2-Stable Date: Wed, 11 Aug 1999 10:42:22 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a follow-up to series of postings a few days ago about freezes in 3.2-S on a heavily loaded large memory SMP machine. The symptoms were that almost daily we'd either get a complete system freeze, with no response to network or keyboard (and no panic), or we'd get one of the processors "stuck" with a single process in the RUN state that could not be killed. There were several thoughts as to why this happened, including a discovery of an Intel Pentium III Erratum which describes the freeze symptoms exactly. After replacing the BIOS in the machine with an update to work around the problem, a freeze still occurred. The machine is: Supermicro P6DBU Dual PIII-550 w/ 512K cache 1GB ECC RAM DPT RAID controller 3COM 3C905B NIC HOWEVER, I've been able to avoid a freeze for the past 36 hours now by doing one simple thing -- removing the last 256MB ECC RAM stick out of the box, leaving it with only 768MB. The removed RAM has tested out just fine, so that leaves one of two possibilities: 1. Supermicro can't handle a full 1GB, despite their specs OR 2. FreeBSD can't handle that much memory in a stable manner There have been talks of some large memory patches floating around, but a search of the mailing lists turned up nothing. Anyone know if patching FreeBSD is required in order to support 1GB RAM? Anyone successfully running their box w/ 1GB RAM and 3.2-S? Thanks! -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 7:55: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 7313815519 for ; Wed, 11 Aug 1999 07:55:01 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id KAA16696; Wed, 11 Aug 1999 10:54:48 -0400 (EDT) Message-Id: <3.0.5.32.19990811105322.01092140@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 11 Aug 1999 10:53:22 -0400 To: tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: On freezes in 3.2-Stable In-Reply-To: <307D63ED6749CF11AAE9005004461A5B4057@FREYA> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The removed RAM has tested out just fine, so that leaves >one of two possibilities: > >1. Supermicro can't handle a full 1GB, despite their specs >OR >2. FreeBSD can't handle that much memory in a stable manner > >There have been talks of some large memory patches floating >around, but a search of the mailing lists turned up nothing. > >Anyone know if patching FreeBSD is required in order to support >1GB RAM? Anyone successfully running their box w/ 1GB RAM >and 3.2-S? Is not CDROM.COM running 3.x STABLE ? 230-This machine is a Xeon/500 with 4GB of memory & 1/2 terabyte of RAID 5. 230-The operating system is FreeBSD. Should you wish to get your own copy of 230-FreeBSD, see the pub/FreeBSD directory or visit http://www.freebsd.org 230-for more information. FreeBSD on CDROM can be ordered using the WEB at 230-http://www.cdrom.com/titles/freebsd/freebsd.phtml or by sending email to 230-orders@cdrom.com. 230- Dont know if its SMP though. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 8: 3:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 121CA15006 for ; Wed, 11 Aug 1999 08:03:17 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 10:58:44 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B4059@FREYA> From: tcobb@staff.circle.net To: mike@sentex.net, freebsd-stable@FreeBSD.ORG Subject: RE: On freezes in 3.2-Stable Date: Wed, 11 Aug 1999 10:58:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is not CDROM.COM running 3.x STABLE ? Yes, but DG used some special hacks to get the system to be stable and working. - Troy > 230-This machine is a Xeon/500 with 4GB of memory & 1/2 > terabyte of RAID 5. > 230-The operating system is FreeBSD. Should you wish to get > your own copy of > 230-FreeBSD, see the pub/FreeBSD directory or visit http://www.freebsd.org 230-for more information. FreeBSD on CDROM can be ordered using the WEB at 230-http://www.cdrom.com/titles/freebsd/freebsd.phtml or by sending email to 230-orders@cdrom.com. 230- Dont know if its SMP though. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 8: 3:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from correo.tamnet.com.mx (correo.tamnet.com.mx [200.34.205.20]) by hub.freebsd.org (Postfix) with ESMTP id E4CB615548 for ; Wed, 11 Aug 1999 08:03:35 -0700 (PDT) (envelope-from adepoo@tamnet.com.mx) Received: from correo.tamnet.com.mx (correo.tamnet.com.mx [200.34.205.20]) by correo.tamnet.com.mx (8.9.1a/8.9.1a) with SMTP id KAA18049 for ; Wed, 11 Aug 1999 10:03:41 -0500 (CDT) Date: Wed, 11 Aug 1999 10:03:41 -0500 (CDT) From: To: freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable In-Reply-To: <3.0.5.32.19990811105322.01092140@staff.sentex.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Mike Tancsa wrote: > >The removed RAM has tested out just fine, so that leaves > >one of two possibilities: > > > >1. Supermicro can't handle a full 1GB, despite their specs > >OR > >2. FreeBSD can't handle that much memory in a stable manner > > > >There have been talks of some large memory patches floating > >around, but a search of the mailing lists turned up nothing. > > > >Anyone know if patching FreeBSD is required in order to support > >1GB RAM? Anyone successfully running their box w/ 1GB RAM > >and 3.2-S? > > > Is not CDROM.COM running 3.x STABLE ? > > 230-This machine is a Xeon/500 with 4GB of memory & 1/2 terabyte of RAID 5. > 230-The operating system is FreeBSD. Should you wish to get your own copy of > 230-FreeBSD, see the pub/FreeBSD directory or visit http://www.freebsd.org > 230-for more information. FreeBSD on CDROM can be ordered using the WEB at > 230-http://www.cdrom.com/titles/freebsd/freebsd.phtml or by sending email to > 230-orders@cdrom.com. > 230- > > > Dont know if its SMP though. > > ---Mike Can it be the memory itself? We have a test box with 3.2, when we added some memory the machine start to act weird, just as the original post, freeze, no keyboard input, even sometimes the machine reboots. We take out the added memory, and then everything is going well. The machine is not SMP but it acted exactly as you said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 8: 9:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 0875315006 for ; Wed, 11 Aug 1999 08:09:37 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 11:05:05 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B405A@FREYA> From: tcobb@staff.circle.net To: adepoo@tamnet.com.mx, freebsd-stable@FreeBSD.ORG Subject: RE: On freezes in 3.2-Stable Date: Wed, 11 Aug 1999 11:04:59 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Can it be the memory itself? > >We have a test box with 3.2, when we added some memory the machine start >to act weird, just as the original post, freeze, no keyboard input, even >sometimes the machine reboots. > >We take out the added memory, and then everything is going well. I thought that might be the situation. So I removed the memory and put it into another box which worked fine w/ just that one DIMM. I'm guessing now that the memory was fine, but support for 1GB was the problem. I'd loved to find myself wrong in this, by the way. :) -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 8:17:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id C43B415519 for ; Wed, 11 Aug 1999 08:17:56 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 11:12:36 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B405C@FREYA> From: tcobb@staff.circle.net To: freebsd-stable@FreeBSD.ORG Subject: RE: On freezes in 3.2-Stable Date: Wed, 11 Aug 1999 11:12:28 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, but DG used some special hacks to get the system to be > stable and working. s/hacks/kernel modifications/g :) - T To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 8:28: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from darius.concentric.net (darius.concentric.net [207.155.198.79]) by hub.freebsd.org (Postfix) with ESMTP id 4585215534 for ; Wed, 11 Aug 1999 08:27:55 -0700 (PDT) (envelope-from dan@tsolab.org) Received: from mcfeely.concentric.net (mcfeely [207.155.198.83]) by darius.concentric.net (8.9.1a/(98/12/15 5.12)) id LAA03152; Wed, 11 Aug 1999 11:26:06 -0400 (EDT) [1-800-745-2747 The Concentric Network] Received: from tsolab.org (ts029d10.hil-ny.concentric.net [206.173.24.166]) by mcfeely.concentric.net (8.9.1a) id LAA02158; Wed, 11 Aug 1999 11:25:59 -0400 (EDT) Message-ID: <37B197FA.B0D98D65@tsolab.org> Date: Wed, 11 Aug 1999 11:34:18 -0400 From: Daniel Tso X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable References: <307D63ED6749CF11AAE9005004461A5B405A@FREYA> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >We take out the added memory, and then everything is going well. > > I thought that might be the situation. So I removed the memory > and put it into another box which worked fine w/ just that one > DIMM. I'm guessing now that the memory was fine, but support > for 1GB was the problem. >> Supermicro can't handle a full 1GB, despite their specs Just in case this tidbit isn't completely obvious... There are situations with motherboards and particular memory SIMM/DIMMs in which, from a digital/logical/programming standpoint, you can fill up to the max amount of support memory -- no problem. However from an *electrical* standpoint, it becomes unreliable or simply not workable. These situations often have to do with the maximum amount of capacitance the memory driving circuits can handle. Modern dynamic RAM is nothing but a whole bunch of capacitors. Plus there is appreciable capacitance in any IC or circuit. This is why sometimes it matters whether a SIMM has 3 chips or 9 chips, or 12 chips or 36 chips, etc, even though the digital/logical circuit is the same and the amount of memory is the same, the *electrical* interface that that SIMM presents to the memory bus can be quite different. So you may, if you can, wish to play with different DIMM/chip configurations. Or pose this sort of question to Supermicro... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 8:28:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 864BC15531 for ; Wed, 11 Aug 1999 08:28:14 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id QAA06530; Wed, 11 Aug 1999 16:26:43 +0100 (BST) (envelope-from rb) Message-Id: <3.0.6.32.19990811162641.007b8cb0@192.168.255.1> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 16:26:41 +0100 To: tcobb@staff.circle.net From: Bob Bishop Subject: Re: On freezes in 3.2-Stable Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <307D63ED6749CF11AAE9005004461A5B4057@FREYA> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 10:42 11/08/99 -0400, tcobb@staff.circle.net wrote: >[tail of woe truncated] >HOWEVER, I've been able to avoid a freeze for the past >36 hours now by doing one simple thing -- removing the last >256MB ECC RAM stick out of the box, leaving it with only >768MB. > >The removed RAM has tested out just fine, so that leaves >one of two possibilities: > >1. Supermicro can't handle a full 1GB, despite their specs >OR >2. FreeBSD can't handle that much memory in a stable manner OR 3. Something is marginal on the motherboard, and it won't drive 4 RAM modules (assuming that was 4 x 256 you were running). -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 8:28:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from loki.ideaglobal.com (loki.ideaglobal.com [194.36.20.54]) by hub.freebsd.org (Postfix) with ESMTP id C138115557 for ; Wed, 11 Aug 1999 08:28:26 -0700 (PDT) (envelope-from kiril@loki.ideaglobal.com) Received: (from kiril@localhost) by loki.ideaglobal.com (8.9.3/8.9.2) id PAA06643; Wed, 11 Aug 1999 15:35:08 GMT (envelope-from kiril) From: Kiril Mitev Message-Id: <199908111535.PAA06643@loki.ideaglobal.com> Subject: Re: On freezes in 3.2-Stable In-Reply-To: <3.0.5.32.19990811105322.01092140@staff.sentex.ca> from Mike Tancsa at "Aug 11, 1999 10:53:22 am" To: mike@sentex.net (Mike Tancsa) Date: Wed, 11 Aug 1999 15:35:08 +0000 (GMT) Cc: tcobb@staff.circle.net, freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >The removed RAM has tested out just fine, so that leaves > >one of two possibilities: > > > >1. Supermicro can't handle a full 1GB, despite their specs > >OR > >2. FreeBSD can't handle that much memory in a stable manner > > > >There have been talks of some large memory patches floating > >around, but a search of the mailing lists turned up nothing. > > > >Anyone know if patching FreeBSD is required in order to support > >1GB RAM? Anyone successfully running their box w/ 1GB RAM > >and 3.2-S? > > > Is not CDROM.COM running 3.x STABLE ? > > 230-This machine is a Xeon/500 with 4GB of memory & 1/2 terabyte of RAID 5. > 230-The operating system is FreeBSD. Should you wish to get your own copy of > 230-FreeBSD, see the pub/FreeBSD directory or visit http://www.freebsd.org > 230-for more information. FreeBSD on CDROM can be ordered using the WEB at > 230-http://www.cdrom.com/titles/freebsd/freebsd.phtml or by sending email to > 230-orders@cdrom.com. > 230- IIRC, cdrom.com runs a 'custom' kernel, and that's putting it mildly > > > Dont know if its SMP though. > > ---Mike > ------------------------------------------------------------------------ > Mike Tancsa, tel 01.519.651.3400 > Network Administrator, mike@sentex.net > Sentex Communications www.sentex.net > Cambridge, Ontario Canada > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > > -- Kiril Mitev, IT Operations Mgr, London IDEAglobal.com Standard Corporate Disclaimer applies, see http://www.ideaglobal.com/email-disclaimer.html for details. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 8:55: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from c004.sfo.cp.net (c004-h018.c004.sfo.cp.net [209.228.14.105]) by hub.freebsd.org (Postfix) with SMTP id 7B4FA14D1D for ; Wed, 11 Aug 1999 08:54:57 -0700 (PDT) (envelope-from jason@intercom.com) Received: (cpmta 22643 invoked from network); 11 Aug 1999 08:52:26 -0700 Received: from shagalicious.com (HELO intercom.com) (206.98.165.250) by smtp.intercom.com with SMTP; 11 Aug 1999 08:52:26 -0700 X-Sent: 11 Aug 1999 15:52:26 GMT Message-ID: <37B19C3B.9143E26A@intercom.com> Date: Wed, 11 Aug 1999 11:52:27 -0400 From: "Jason J. Horton" Organization: Intercom Online Inc. X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kiril Mitev Cc: Mike Tancsa , tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable References: <199908111535.PAA06643@loki.ideaglobal.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kiril Mitev wrote: > IIRC, cdrom.com runs a 'custom' kernel, and that's putting it mildly Now I am curious as to why these special mods are not available in -CURRENT or -STABLE.... -- -Jason J. Horton Moving Target Intercom Online Inc. 212.376.7440 ext 21 | http://www.intercom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 9:16:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 2CAD714EE4 for ; Wed, 11 Aug 1999 09:16:16 -0700 (PDT) (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 JAA25608; Wed, 11 Aug 1999 09:10:31 -0700 (PDT) Message-Id: <199908111610.JAA25608@implode.root.com> To: "Jason J. Horton" Cc: Kiril Mitev , Mike Tancsa , tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Wed, 11 Aug 1999 11:52:27 EDT." <37B19C3B.9143E26A@intercom.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Aug 1999 09:10:31 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Kiril Mitev wrote: >> IIRC, cdrom.com runs a 'custom' kernel, and that's putting it mildly > >Now I am curious as to why these special mods are not available >in -CURRENT or -STABLE.... They are. Wcarchive's kernel is very close to stock except for a few parameter tweaks which aren't appropriate for general use. This hasn't always been true, however. I often develop performance enhancements for wcarchive and slowly merge them into -current as appropriate. I just haven't had any reason to do this recently since we ran out of bandwidth and the machine is plenty fast enough to keep up with current demands. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 9:16:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 95A1E155D6 for ; Wed, 11 Aug 1999 09:16:46 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA23136; Wed, 11 Aug 1999 09:15:58 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 11 Aug 1999 09:15:58 -0700 Date: Wed, 11 Aug 1999 09:15:58 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: eirvine Cc: stable@freebsd.org Subject: Re: Compiled a kernel with egcs In-Reply-To: <37B13B0C.564196AA@tpgi.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: eirvine@tpgi.com.au,stable@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I assume so, I have done the same. Although when I used late snapshots of gcc-2.95(about a month pre-release)to recompile libc_r, all of sudden my threaded programs were totally broken. -Kip On Wed, 11 Aug 1999, eirvine wrote: > Hi all. > > Running a recent cvsup of 3.2 on my new PC at home. I found I could > compile a kernel with egcs. > > Is this expected behaviour? I thought I could only do this on current. > > Eddie. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 9:21:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail-atm.maine.rr.com (ns.maine.rr.com [204.210.64.1]) by hub.freebsd.org (Postfix) with ESMTP id 987A014EF9 for ; Wed, 11 Aug 1999 09:21:47 -0700 (PDT) (envelope-from brunner@maine.rr.com) Received: from computername (dt0b4n1b.maine.rr.com [24.95.12.27]) by mail-atm.maine.rr.com (8.8.7/8.8.8) with SMTP id MAA13428 for ; Wed, 11 Aug 1999 12:20:54 -0400 (EDT) Message-Id: <3.0.6.32.19990811122710.0192c970@maine.rr.com> X-Sender: brunner@maine.rr.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 12:27:10 -0400 To: freebsd-stable@FreeBSD.ORG From: Eric Brunner Subject: Problem reporting build failure (rebuilding bootstrap, crtbegin.c:33) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying to "report" a problem since about August 2nd. a) has anyone actually seen my prior traffic with the problem statement, and b) does anyone actually manage to rebuild the bootstrap libraries (buildworld), in particular crtbegin.c The offending error message is: /usr/src/lib/csu/i386-elf/crtbegin.c:33: section attributes are not supported for this target Thanks in advance, Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 9:22:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 1DD1415113 for ; Wed, 11 Aug 1999 09:22:07 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 12:16:50 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B4063@FREYA> From: tcobb@staff.circle.net To: dg@root.com, jason@intercom.com Cc: kiril@ideaglobal.com, mike@sentex.net, tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG Subject: RE: On freezes in 3.2-Stable Date: Wed, 11 Aug 1999 12:16:45 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David, Is it close to stock FreeBSD-stable, or stock FreeBSD-current? -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: David Greenman [mailto:dg@root.com] > Sent: Wednesday, August 11, 1999 12:11 PM > To: Jason J. Horton > Cc: Kiril Mitev; Mike Tancsa; tcobb@staff.circle.net; > freebsd-stable@FreeBSD.ORG > Subject: Re: On freezes in 3.2-Stable > > > >Kiril Mitev wrote: > >> IIRC, cdrom.com runs a 'custom' kernel, and that's > putting it mildly > > > >Now I am curious as to why these special mods are not available > >in -CURRENT or -STABLE.... > > They are. Wcarchive's kernel is very close to stock > except for a few > parameter tweaks which aren't appropriate for general use. > This hasn't always > been true, however. I often develop performance > enhancements for wcarchive > and slowly merge them into -current as appropriate. I just > haven't had any > reason to do this recently since we ran out of bandwidth > and the machine is > plenty fast enough to keep up with current demands. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 9:33:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from trooper.velocet.ca (trooper.velocet.net [209.167.225.226]) by hub.freebsd.org (Postfix) with ESMTP id DC41514C59 for ; Wed, 11 Aug 1999 09:33:09 -0700 (PDT) (envelope-from dgilbert@trooper.velocet.ca) Received: (from dgilbert@localhost) by trooper.velocet.ca (8.9.3/8.9.3) id MAA62875; Wed, 11 Aug 1999 12:32:24 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14257.42391.714176.159128@trooper.velocet.ca> Date: Wed, 11 Aug 1999 12:32:23 -0400 (EDT) To: Kiril Mitev Cc: mike@sentex.net (Mike Tancsa), tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable In-Reply-To: <199908111535.PAA06643@loki.ideaglobal.com> References: <3.0.5.32.19990811105322.01092140@staff.sentex.ca> <199908111535.PAA06643@loki.ideaglobal.com> X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Kiril" == Kiril Mitev writes: Kiril> IIRC, cdrom.com runs a 'custom' kernel, and that's putting it Kiril> mildly Someone should publish that patch set.... Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 9:42:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id CD1AF15579 for ; Wed, 11 Aug 1999 09:42:37 -0700 (PDT) (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 JAA25841; Wed, 11 Aug 1999 09:38:12 -0700 (PDT) Message-Id: <199908111638.JAA25841@implode.root.com> To: tcobb@staff.circle.net Cc: jason@intercom.com, kiril@ideaglobal.com, mike@sentex.net, freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Wed, 11 Aug 1999 12:16:45 EDT." <307D63ED6749CF11AAE9005004461A5B4063@FREYA> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Aug 1999 09:38:11 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is it close to stock FreeBSD-stable, or stock FreeBSD-current? -stable of course. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 9:54:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cits-darla.robins.af.mil (cits-darla.robins.af.mil [137.244.215.8]) by hub.freebsd.org (Postfix) with ESMTP id 4F53D155BA for ; Wed, 11 Aug 1999 09:54:44 -0700 (PDT) (envelope-from Andrew.Lofthouse@robins.af.mil) Received: from cits-darla.robins.af.mil (root@localhost) by cits-darla.robins.af.mil with ESMTP id MAA04340; Wed, 11 Aug 1999 12:54:44 -0400 (EDT) Received: from fsuhhz30.robins.af.mil (fsuhhz30.robins.af.mil [137.244.190.201]) by cits-darla.robins.af.mil with ESMTP id MAA04335; Wed, 11 Aug 1999 12:54:44 -0400 (EDT) Received: by fsuhhz30.robins.af.mil with Internet Mail Service (5.5.2232.9) id ; Wed, 11 Aug 1999 16:54:15 -0000 Message-ID: <3F69A3D5863ED211B31F0000F809353502C4889B@FSUHHZ33> From: Lofthouse Andrew 2Lt WRALC/TIECT To: Eric Brunner , freebsd-stable@FreeBSD.ORG Subject: RE: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) Date: Wed, 11 Aug 1999 16:54:23 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Eric Brunner [SMTP:brunner@maine.rr.com] Sent: Wednesday, August 11, 1999 12:27 PM To: freebsd-stable@FreeBSD.ORG Subject: Problem reporting build failure (rebuilding bootstrap, crtbegin.c:33) I've been trying to "report" a problem since about August 2nd. a) has anyone actually seen my prior traffic with the problem statement, and b) does anyone actually manage to rebuild the bootstrap libraries (buildworld), in particular crtbegin.c The offending error message is: /usr/src/lib/csu/i386-elf/crtbegin.c:33: section attributes are not supported for this target I had the same problem; I posted the message about it yesterday: Yesterday I tried "make world" with the -STABLE sources on my machine running 2.2.8-RELEASE. Below is the final output of the make process... -------------------------------------------------------------- >>> Rebuilding bootstrap libraries -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/sr c/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/lo cal/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/libexec /usr/obj/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/usr/src/tmp -f Makefile.inc1 bootstrap-libraries cd /usr/src/lib/csu/i386-elf; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj rm -f .depend /usr/obj/usr/src/lib/csu/i386-elf/GPATH /usr/obj/usr/src/lib/csu/i386-elf/GRTAGS /usr/obj/usr/src/lib/csu/i386-elf/GSYMS /usr/obj/usr/src/lib/csu/i386-elf/GTAGS cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/csu/i386-elf/crt1.c -o crt1.o cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/csu/i386-elf/crtbegin.c -o crtbegin.o /usr/src/lib/csu/i386-elf/crtbegin.c:32: section attributes are not supported for this target /usr/src/lib/csu/i386-elf/crtbegin.c:33: section attributes are not supported for this target {standard input}: Assembler messages: {standard input}:68: Error: Unknown pseudo-op: `.section' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Andrew J. Lofthouse, 2LT, USAF Technology Applications Engineer COM (912) 926-6617 DSN 468-6617 FAX (912) 926-7638 Andrew.Lofthouse@robins.af.mil WR-ALC/TIECT 420 Second St. Suite 100 Robins AFB, GA 31098-1640 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 10:10:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 896DE14C31 for ; Wed, 11 Aug 1999 10:10:11 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA21104; Wed, 11 Aug 1999 10:09:46 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: tcobb@staff.circle.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Wed, 11 Aug 1999 10:42:22 EDT." <307D63ED6749CF11AAE9005004461A5B4057@FREYA> Date: Wed, 11 Aug 1999 10:09:46 -0700 Message-ID: <21100.934391386@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm virtually certain thta this is a bogus motherboard. I know of a number of systems running 1GB of memory that are perfectly stable (including the quad processor Xeon at WC we use for testing) just as I know of several situations in the past were a motherboard completely fell over after having all of its SIMM sockets populated. As someone else noted, there are often electrical limitations which present themselves only when you stuff the board full of RAM. It would be an easy test to simply swap this motherboard and move the memory back in. Also, how did you test the memory? With a hardware tester, I hope, since all software memory tests are inherently bogus. Don't trust them to tell you anything more than the fact that there's power to the memory. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 10:18:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id 6115614BCE for ; Wed, 11 Aug 1999 10:18:48 -0700 (PDT) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id NAA23496 for ; Wed, 11 Aug 1999 13:18:20 -0400 (EDT) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id NAA23207 for freebsd-stable@FreeBSD.ORG; Wed, 11 Aug 1999 13:18:20 -0400 (EDT) Message-ID: <19990811131819.E22386@stat.Duke.EDU> Date: Wed, 11 Aug 1999 13:18:19 -0400 From: "Sean O'Connell" To: FreeBSD stable Subject: NFS weirdness Reply-To: "Sean O'Connell" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All- I am in the process of updating all of the departements FreeBSD boxes to 3.2-STABLE. I have set up one of my test machines, and I have noticed something weird wrt email (we are currently still using nfs-mounted /var/spool/mail directory, for now ...). This version of the OS was cvsup'd on 1999 Jul 30 after most of the big NFS changes were MFC'd---I believe. I am running tkpostage---a cute mail counter utility that uses tcl's file(n) call to keep track mod time changes and then an open(n) call to then regex(n) to get the count and the subject portion. When I manipulate my spool file (using mutt) on one of our client Digital Unix boxes (spool file located on Digital Unix server), the FreeBSD machine sees the changes in my spool file: the size and mod times adjust properly _but_ the content of the file is not updated. It seems just truncate the previous version to the new size. If I happen to get a new email message, the file content is then updated properly. Since we are hopelessly dependent on NFS (people's home directories, email (for now), etc), this looks like a disaster waiting to happen---especially with running and commercial software: Matlab, Splus, Mathematica, Netscape (doesn't seem to enforce disk cache quotas over nfs), etc. Is this a FreeBSD mmap/nfs type bug? - It is quite reproducible. Is this a FreeBSD mmap/nfs interaction with tcl/tk? - It seems to update properly when this is not running. - Could it be bad tcl coding? Or am I using the wrong the nfs mount options? - I am not doing anything other nfs mounting the /var/spool/mail off the Digital Unix box. Or should I just bite the bullet and run current? :) Details: relevant fstab entry: server:/var/spool/mail /var/mail nfs rw,bg,intr,nodev 0 0 output from sysctl vfs.nfs: vfs.nfs.nfs_privport: 0 vfs.nfs.async: 0 vfs.nfs.gatherdelay: 10000 vfs.nfs.gatherdelay_v3: 0 vfs.nfs.defect: 0 vfs.nfs.diskless_valid: 0 vfs.nfs.diskless_rootpath: vfs.nfs.diskless_swappath: vfs.nfs.access_cache_timeout: 2 vfs.nfs.access_cache_hits: 16321 vfs.nfs.access_cache_fills: 13715 Looking at a quick tcpdump, it is doing nfs over udp... not sure which version, but I would guess version 3. Thanks, S -- ----------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 10:21:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 55A1A14CBE for ; Wed, 11 Aug 1999 10:21:28 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id KAA67556; Wed, 11 Aug 1999 10:20:21 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37B1B0D7.29AE7D58@gorean.org> Date: Wed, 11 Aug 1999 10:20:23 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jason J. Horton" Cc: Kiril Mitev , Mike Tancsa , tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable References: <199908111535.PAA06643@loki.ideaglobal.com> <37B19C3B.9143E26A@intercom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jason J. Horton" wrote: > > Kiril Mitev wrote: > > IIRC, cdrom.com runs a 'custom' kernel, and that's putting it mildly > > Now I am curious as to why these special mods are not available > in -CURRENT or -STABLE.... The last post I saw from DG on this topic he said that 90% (more?) of the stuff he has done for wcarchive is in 3.2-Stable now. The rest is of extremely limited interest, would be harder to document than it was to write, and would result in hordes of questions from foolish people who shot themselves in the foot with it even after being told not to use it if they don't understand it. The above is my paraphrase of my current understanding of the situation, so don't hold DG accountable for it. :) This next is purely my commentary on the question itself. The guy makes his living (or part of it anyway) designing high performance systems for people. I don't blame him one little bit if he wants to "hold back" some of what gives him an edge in *highly* competetive field. He's certainly done a WHOLE LOT for the project, much of which the average user never sees, and even more than I am aware of I'm sure. In short, give the guy a break. :) Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 10:25:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from c004.sfo.cp.net (c004-h006.c004.sfo.cp.net [209.228.14.77]) by hub.freebsd.org (Postfix) with SMTP id 1D9271558A for ; Wed, 11 Aug 1999 10:25:29 -0700 (PDT) (envelope-from jason@intercom.com) Received: (cpmta 29697 invoked from network); 11 Aug 1999 10:25:02 -0700 Received: from shagalicious.com (HELO intercom.com) (206.98.165.250) by smtp.intercom.com with SMTP; 11 Aug 1999 10:25:02 -0700 X-Sent: 11 Aug 1999 17:25:02 GMT Message-ID: <37B1B20A.D5398285@intercom.com> Date: Wed, 11 Aug 1999 13:25:30 -0400 From: "Jason J. Horton" Organization: Intercom Online Inc. X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug Cc: freebsd-stable@freebsd.org Subject: Re: On freezes in 3.2-Stable References: <199908111535.PAA06643@loki.ideaglobal.com> <37B19C3B.9143E26A@intercom.com> <37B1B0D7.29AE7D58@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Now I am curious as to why these special mods are not available > > in -CURRENT or -STABLE.... > The above is my paraphrase of my current understanding of the situation, > so don't hold DG accountable for it. :) This next is purely my commentary > on the question itself. The guy makes his living (or part of it anyway) > designing high performance systems for people. I don't blame him one little > bit if he wants to "hold back" some of what gives him an edge in *highly* > competetive field. He's certainly done a WHOLE LOT for the project, much of > which the average user never sees, and even more than I am aware of I'm > sure. In short, give the guy a break. :) Definately was not busting his nuts or anything, was just curious. You occasionally hear word of these super secret modifications, any human is gonna get curious and want a peek :) -- -Jason J. Horton Moving Target Intercom Online Inc. 212.376.7440 ext 21 | http://www.intercom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 12:19: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id EB45E155FB for ; Wed, 11 Aug 1999 12:19:05 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 15:13:57 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B4069@FREYA> From: tcobb@staff.circle.net To: jkh@zippy.cdrom.com Cc: freebsd-stable@FreeBSD.ORG Subject: RE: On freezes in 3.2-Stable Date: Wed, 11 Aug 1999 15:13:50 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It happened with TWO Supermicro motherboards, one a P6SBU the other a P6DBU (one dual, one single). Both of these boards had four sticks of RAM in them before, but just 128's. Could be the electrical issue with more chips on the 256's. So, the consensus is that no adjustments are necessary for FreeBSD to support 1GB or greater? -Troy Cobb Circle Net, Inc. http://www.circle.net > I'm virtually certain thta this is a bogus motherboard. I know of a > number of systems running 1GB of memory that are perfectly stable > (including the quad processor Xeon at WC we use for > testing) just as I > know of several situations in the past were a motherboard completely > fell over after having all of its SIMM sockets populated. > As someone > else noted, there are often electrical limitations which present > themselves only when you stuff the board full of RAM. It > would be an > easy test to simply swap this motherboard and move the > memory back in. > > Also, how did you test the memory? With a hardware tester, I hope, > since all software memory tests are inherently bogus. Don't trust > them to tell you anything more than the fact that there's > power to the > memory. :) > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 12:56:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 4B88914BD8 for ; Wed, 11 Aug 1999 12:56:04 -0700 (PDT) (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 MAA27616; Wed, 11 Aug 1999 12:51:49 -0700 (PDT) Message-Id: <199908111951.MAA27616@implode.root.com> To: tcobb@staff.circle.net Cc: jkh@zippy.cdrom.com, freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Wed, 11 Aug 1999 15:13:50 EDT." <307D63ED6749CF11AAE9005004461A5B4069@FREYA> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Aug 1999 12:51:49 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It happened with TWO Supermicro motherboards, one a P6SBU >the other a P6DBU (one dual, one single). Both of these >boards had four sticks of RAM in them before, but just >128's. Could be the electrical issue with more chips on >the 256's. You need registered CL2 SDRAM DIMMs in order to use 4x256MB. I'll bet that you have CL3 DIMMs, which won't work with 4 of them (but should work with 3). >So, the consensus is that no adjustments are necessary for >FreeBSD to support 1GB or greater? On 3.2-stable, yes. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 13: 5:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.forumone.com (orion.forumone.com [207.197.141.10]) by hub.freebsd.org (Postfix) with ESMTP id 3C83914D69 for ; Wed, 11 Aug 1999 13:05:01 -0700 (PDT) (envelope-from adhir@forumone.com) Received: from adhir (unknown [216.181.56.84]) by mail.forumone.com (Postfix) with SMTP id 97774A8C5 for ; Wed, 11 Aug 1999 16:04:29 -0400 (EDT) Reply-To: To: Subject: uthread patches in -stable Date: Wed, 11 Aug 1999 16:05:42 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal From: adhir@forumone.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently running a libc_r built with patched uthread code in order to run MySQL using kernel threads in a stable fashion. Things are working fine so far. I'd like to go back to using the 'stock' -stable libc_r if the uthread stuff in there has been fixed. Can anyone verify? Thanks Al Dhir Forum One Communications, Inc. adhir@forumone.com +1.703.548.1855 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 13:14:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A7CDA14CD3; Wed, 11 Aug 1999 13:14:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 92ED51CD66D; Wed, 11 Aug 1999 13:14:43 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Wed, 11 Aug 1999 13:14:43 -0700 (PDT) From: Kris Kennaway To: Lofthouse Andrew 2Lt WRALC/TIECT Cc: Eric Brunner , freebsd-stable@FreeBSD.ORG Subject: RE: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) In-Reply-To: <3F69A3D5863ED211B31F0000F809353502C4889B@FSUHHZ33> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Aug 1999, Lofthouse Andrew 2Lt WRALC/TIECT wrote: > I had the same problem; I posted the message about it yesterday: > > Yesterday I tried "make world" with the -STABLE sources on my machine > running 2.2.8-RELEASE. Below is the final output of the make process... make world is not for updating between major revisions (2.x to 3.x). There's a different target for this (make upgrade or something, check the header of the /usr/src/Makefile). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 13:21:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from exit-gw.power.net (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id B784114BFE; Wed, 11 Aug 1999 13:21:42 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by exit-gw.power.net (8.8.8/8.8.8) with ESMTP id NAA14098; Wed, 11 Aug 1999 13:20:57 -0700 (PDT) (envelope-from frank@tinker.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.1) id NAA10212; Wed, 11 Aug 1999 13:21:22 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <199908112021.NAA10212@realtime.exit.com> Subject: Re: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) In-Reply-To: from Kris Kennaway at "Aug 11, 1999 1:14:43 pm" To: kris@hub.freebsd.org (Kris Kennaway) Date: Wed, 11 Aug 1999 13:21:22 -0700 (PDT) Cc: Andrew.Lofthouse@robins.af.mil, brunner@maine.rr.com, freebsd-stable@FreeBSD.ORG Reply-To: frank@exit.com 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > On Wed, 11 Aug 1999, Lofthouse Andrew 2Lt WRALC/TIECT wrote: > > > I had the same problem; I posted the message about it yesterday: > > > > Yesterday I tried "make world" with the -STABLE sources on my machine > > running 2.2.8-RELEASE. Below is the final output of the make process... > > make world is not for updating between major revisions (2.x to 3.x). > There's a different target for this (make upgrade or something, check the > header of the /usr/src/Makefile). "Make upgrade." Which, of course, doesn't work. It breaks in the elf build of libmytinfo. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 14:54:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 59E7B15630 for ; Wed, 11 Aug 1999 14:54:36 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA07021; Wed, 11 Aug 1999 17:53:15 -0400 (EDT) Date: Wed, 11 Aug 1999 17:53:15 -0400 (EDT) From: Daniel Eischen Message-Id: <199908112153.RAA07021@pcnet1.pcnet.com> To: adhir@forumone.com, stable@FreeBSD.ORG Subject: Re: uthread patches in -stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm currently running a libc_r built with patched uthread code in order to run > MySQL using kernel threads in a stable fashion. Things are working fine so far. > > I'd like to go back to using the 'stock' -stable libc_r if the uthread stuff in > there has been fixed. Those changes were merged into -stable a few weeks ago. ---------------------------- revision 1.16.2.2 date: 1999/07/23 13:00:24; author: deischen; state: Exp; lines: +172 -90 MFC: Bring in both bug fixes, performance improvements, and enhancements (addition of wrapped poll). This should fix MySQL problems. ---------------------------- Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 15:11: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id DE7EE155E8 for ; Wed, 11 Aug 1999 15:10:46 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id XAA26473 for ; Wed, 11 Aug 1999 23:05:04 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id NAA13657 for stable@freebsd.org; Wed, 11 Aug 1999 13:08:21 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Wed, 11 Aug 1999 13:08:21 +0100 From: Nik Clayton To: stable@freebsd.org Subject: HEADS UP: doc/ tree breakage on Sunday 15th August Message-ID: <19990811130821.A13506@kilt.nothing-going-on.org> Reply-To: nik@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, A couple of people have pointed out that this is appropriate for people tracking/building -stable as well. Please take note. N ----- Forwarded message from Nik Clayton ----- Delivered-To: freebsd-current@freebsd.org Date: Tue, 10 Aug 1999 15:53:01 +0100 From: Nik Clayton To: doc@freebsd.org, current@freebsd.org, committers@freebsd.org Subject: HEADS UP: doc/ tree breakage on Sunday 15th August Organization: FreeBSD Project Heads up, [ cc: to -doc, -current, -committers, reply-to: nik ] On Sunday 15th August the doc/ tree will break. John Polstra will be performing surgery on the CVS repository[1], and when he's completed that I will be going in to fix up the build system infrastructure (all the Makefiles, primarily). If things go smoothly, the doc/ tree should be back and working by late Sunday evening (BST). If things go badly then it will be back and working by the end of Monday evening (BST). Prior to making these changes, John will announce a freeze on the doc/ repository. While this is going on, the doc/ tree will fail to build. This will impact on: * The web site, which uses the doc/ tree to build the FAQ, Handbook, and tutorials. On Thursday or Friday I will be altering the "webbuild" script so that it uses archived copies of the doc/ tree when rebuilding the web site. The site will therefore not be affected, however, any commits made to the FAQ, Handbook, or tutorials after I make the change will not show up on the site. The rest of the web site is unaffected. This will also affect our web site mirrors. I have been e-mailing the contacts for the mirrors to advise them, but a lot of the messages have been bouncing. Be prepared for some of the web site mirrors to either be out of date or broken for 24 hours or so. * "make release". Make sure you build with "NODOC=YES", otherwise the release build will fail. Jordan might want to make this the default -- although for what will hopefully amount to less than 24 hours of breakage it's probably not worthwhile. * Obviously, any -doc committers should get any commits they want in before the work by Saturday afternoon at the latest. So you know, there's a lot of work lined up in the queue ready to happen when this surgery is complete (I've been putting it off, because I didn't want to load the repository up with new files and then be moving them all over the place) including: * French translations of the FAQ and Handbook * The FAQ in DocBook * The beginnings of an infrastructure for http://docs.freebsd.org/ N [1] The nature of this surgery has been discussed extensively on the -doc mailing list, so I won't repeat that here. -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. - Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message ----- End forwarded message ----- -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 15:47:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.ripco.com (relay.ripco.com [209.100.227.3]) by hub.freebsd.org (Postfix) with SMTP id 478CA14BF2 for ; Wed, 11 Aug 1999 15:47:26 -0700 (PDT) (envelope-from aphor@ripco.NOSPAM.com) Received: (qmail 7540 invoked from network); 11 Aug 1999 22:46:44 -0000 Received: from 228-121.ppp.ripco.net (HELO ripco.NOSPAM.com) (@209.100.228.121) by relay.ripco.com with SMTP; 11 Aug 1999 22:46:44 -0000 Message-ID: <37B1FD73.C8DDB723@ripco.NOSPAM.com> Date: Wed, 11 Aug 1999 17:47:15 -0500 From: Jeremy McMillan Reply-To: aphor@ripco.com Organization: Loose.. X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable References: <21100.934391386@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In 5 years of tweaking PC hardware, I've found you get what you pay for. The thing with memory and buses is all timing. More expensive motherboards will either come burned-in with RAM, support only certain (premium priced) DIMMS, or they will sacrifice a nominal amount of performance to put extra buffer chips between memory modules to isolate the electrical interfaces of the RAM from the actual memory bus. The sad part of this is QC is usually "sampling" parts off the production line. That means they have a margin for error on the parts that get shipped. Usually, the better the replacement policy is, the less sampling they do, and the bigger the number of bad parts end up in customers' hands. On top of that, you may belong to the 5% of the population that has worse operating conditions than their QC test bench, thus even if you get a burned-in part you could still be out of luck. The more of a power-user you are, the further out on the statistical curve you get. Please remember, we are dealing with manufacturers and vendors who make their money on *commodity* hardware, which is usually never tested to (though it may have been designed for) each checkbox on the spec sheet. Wise men have no time for bad PC hardware. "Jordan K. Hubbard" wrote: > > I'm virtually certain thta this is a bogus motherboard. I know of a > number of systems running 1GB of memory that are perfectly stable > (including the quad processor Xeon at WC we use for testing) just as I > know of several situations in the past were a motherboard completely > fell over after having all of its SIMM sockets populated. As someone > else noted, there are often electrical limitations which present > themselves only when you stuff the board full of RAM. It would be an > easy test to simply swap this motherboard and move the memory back in. > > Also, how did you test the memory? With a hardware tester, I hope, > since all software memory tests are inherently bogus. Don't trust > them to tell you anything more than the fact that there's power to the > memory. :) > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- PLEASE NOTICE: THERE MAY BE NOSPAM IN THE HEADERS WHEN YOU HIT "REPLY"!!! Jeremy McMillan | Ask for PGP-2.6.2 or 5.0i Chicago FreeBSD Users Group http://pages.ripco.com/~aphor/ChiFUG.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 17:43:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22]) by hub.freebsd.org (Postfix) with ESMTP id 3CFE4156A0 for ; Wed, 11 Aug 1999 17:43:29 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-100-227.asm.bellsouth.net [216.78.100.227]) by mail2.atl.bellsouth.net (8.9.3/8.9.3) with ESMTP id UAA14779; Wed, 11 Aug 1999 20:43:33 -0400 (EDT) Received: from wghicks.bellsouth.net (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id UAA11267; Wed, 11 Aug 1999 20:46:44 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199908120046.UAA11267@bellsouth.net> To: tcobb@staff.circle.net Cc: freebsd-stable@freebsd.org, wghicks@wghicks.bellsouth.net Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Wed, 11 Aug 1999 10:42:22 EDT." <307D63ED6749CF11AAE9005004461A5B4057@FREYA> Date: Wed, 11 Aug 1999 20:46:43 -0400 From: W Gerald Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. Supermicro can't handle a full 1GB, despite their specs $100 says that's it. Better Luck, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 19:58:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id AC885156E0 for ; Wed, 11 Aug 1999 19:58:26 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id TAA09487; Wed, 11 Aug 1999 19:56:50 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199908120256.TAA09487@gndrsh.aac.dev.com> Subject: Re: On freezes in 3.2-Stable In-Reply-To: <199908120046.UAA11267@bellsouth.net> from W Gerald Hicks at "Aug 11, 1999 08:46:43 pm" To: wghicks@bellsouth.net (W Gerald Hicks) Date: Wed, 11 Aug 1999 19:56:49 -0700 (PDT) Cc: tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG, wghicks@wghicks.bellsouth.net X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 1. Supermicro can't handle a full 1GB, despite their specs > > $100 says that's it. $200 says that you using low density 256MB DIMMS that are overloading the BUS specification of the chipset on the motherboard. Current price ratio (well, okay 7/30/1999) on 18 chip vs 36 chip 32Mx72b ECC PC100 8nS is still 1:2, or about $300.00 vs $600.00. Alls I can say to those folks trying to do more than 512MB in a box with any current chip set is ``You have to spend the money for 18 chip parts if you want to have any type of reliable operation, no current chipset was designed to drive 144 chips'' Between David Greenman and my self we probably went through $25,000 of parts from various manufactures who claimed that they would work before we finally decided they are all wrong, and that we would just have to wait for the next generation of chips that would allow 18 chip 256MB DIMMS. If your memory vendor doesn't know what 18 chip 256MB DIMMS are drop me an email, they are in ready supply from either manufacture we deal with. All parts are lifetime warrantied. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 20: 8:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 5283914CC0 for ; Wed, 11 Aug 1999 20:08:16 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt4-208-166-127-26.dialup.HiWAAY.net [208.166.127.26]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id WAA09593; Wed, 11 Aug 1999 22:07:43 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id TAA54114; Wed, 11 Aug 1999 19:35:58 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908120035.TAA54114@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Bob Bishop Cc: tcobb@staff.circle.net, freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: On freezes in 3.2-Stable In-reply-to: Message from Bob Bishop of "Wed, 11 Aug 1999 16:26:41 BST." <3.0.6.32.19990811162641.007b8cb0@192.168.255.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Aug 1999 19:35:58 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Bishop writes: > >1. Supermicro can't handle a full 1GB, despite their specs > >OR > >2. FreeBSD can't handle that much memory in a stable manner > > OR > 3. Something is marginal on the motherboard, and it won't drive 4 RAM > modules (assuming that was 4 x 256 you were running). At Gateway or Dell customize-your-system sites I've seen notes stating one can't fill the 3rd or 4th memory slot if one has more than 2 or 3 internal HD's. I wonder if its a power supply issue? -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 20:12:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id C73C714CC0 for ; Wed, 11 Aug 1999 20:12:42 -0700 (PDT) (envelope-from freebsd.list@bug.tasam.com) Received: from bug (216-164-241-26.s26.tnt10.lnh.md.dialup.rcn.com [216.164.241.26]) by tasam.com (8.9.3/8.9.1) with SMTP id XAA04398; Wed, 11 Aug 1999 23:12:39 -0400 (EDT) Message-ID: <006e01bee470$7e964540$0286860a@tasam.com> From: "Joe Gleason" To: "Bob Bishop" , "David Kelly" Cc: , References: <199908120035.TAA54114@nospam.hiwaay.net> Subject: Re: On freezes in 3.2-Stable Date: Wed, 11 Aug 1999 23:11:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bob Bishop writes: > > >1. Supermicro can't handle a full 1GB, despite their specs > > >OR > > >2. FreeBSD can't handle that much memory in a stable manner > > > > OR > > 3. Something is marginal on the motherboard, and it won't drive 4 RAM > > modules (assuming that was 4 x 256 you were running). > > At Gateway or Dell customize-your-system sites I've seen notes stating > one can't fill the 3rd or 4th memory slot if one has more than 2 or 3 > internal HD's. I wonder if its a power supply issue? > More likely an internal space issue. On many systems I have seen, the 3.5 hard drive rack hits the ram or processor. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 11 21:16:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22]) by hub.freebsd.org (Postfix) with ESMTP id 453FB14D87 for ; Wed, 11 Aug 1999 21:16:32 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-45-75.ath.bellsouth.net [216.78.45.75]) by mail2.atl.bellsouth.net (8.9.3/8.9.3) with ESMTP id AAA15198; Thu, 12 Aug 1999 00:16:03 -0400 (EDT) Received: from wghicks.bellsouth.net (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id AAA11935; Thu, 12 Aug 1999 00:19:14 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199908120419.AAA11935@bellsouth.net> To: David Kelly Cc: Bob Bishop , tcobb@staff.circle.net, freebsd-stable@freebsd.org, wghicks@wghicks.bellsouth.net Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Wed, 11 Aug 1999 19:35:58 CDT." <199908120035.TAA54114@nospam.hiwaay.net> Date: Thu, 12 Aug 1999 00:19:14 -0400 From: W Gerald Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At Gateway or Dell customize-your-system sites I've seen notes stating > one can't fill the 3rd or 4th memory slot if one has more than 2 or 3 > internal HD's. I wonder if its a power supply issue? Naw, it's a capacitive loading issue :) Rod hit the nail on the head. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 1:42:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailg.telia.com (mailg.telia.com [194.22.194.26]) by hub.freebsd.org (Postfix) with ESMTP id 9A64E156E0 for ; Thu, 12 Aug 1999 01:41:50 -0700 (PDT) (envelope-from khaled@mailbox.telia.net) Received: from mailbox.telia.net (khaled@mailbox.telia.net [194.237.170.234]) by mailg.telia.com (8.8.5/8.8.8) with ESMTP id KAA03328 for ; Thu, 12 Aug 1999 10:40:51 +0200 (CEST) Received: from localhost (khaled@localhost) by mailbox.telia.net (8.9.1/8.8.5) with SMTP id KAA15836 for ; Thu, 12 Aug 1999 10:40:58 +0200 (CEST) Date: Thu, 12 Aug 1999 10:40:58 +0200 (CEST) From: Khaled Daham To: freebsd-stable@freebsd.org Subject: DE-500BA problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I have 3 machines with digital DE-500 ethernet cards One machine has DE-500AA and is working perfectly .. The two other machines have DE-500BA cards and in 100BaseTX/full-duplex netstat reports errors and collisions input (Total) output packets errs bytes packets errs bytes colls 84 0 17128 192 0 82128 0 392 0 408687 106 3 85912 3 239 0 216316 221 2 69636 4 112 0 86087 0 0 58206 0 78 0 16203 106 1 66902 0 Ive replaced cables,switched cards ( these machines have 2 nic's each , but im only using one at the moment ) and switched ports on the catalyst 5000 .. newsb.telia.net# uname -a FreeBSD newsb.telia.net 3.1-19990219-STABLE FreeBSD 3.1-19990219-STABLE #0: Mon Feb 22 16:31:18 GMT 1999 root@newsb.telia.net:/usr/src/sys/compile/NEWS i386 (Yes its due to an upgrade) newsc.telia.net# uname -a FreeBSD newsc.telia.net 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Wed Aug 11 12:53:00 CEST 1999 root@newsb.telia.net:/usr/src/sys/compile/NEWS_KERNEL i386 the cards are recognized as this on both machines ( the DE500-AA has a 21140 chip ) de0: irq 11 at device 10.0 on pci0 de0: DEC DE500-BA 21143 [10-100Mb/s] pass 3.0 de0: address 00:00:f8:10:38:73 de1: irq 12 at device 11.0 on pci0 de1: DEC DE500-BA 21143 [10-100Mb/s] pass 3.0 de1: address 00:00:f8:10:42:4d Any hints on what could be causing the errors & collisions ? if the driver is at fault here I can test patches as one machine is not used in production at all .. I know that bsd/os had problems with the DE500-BA cards aswell , but that problem resulted in a freezing machine on heavy netload .. /Khaled, Telia Network Services Mail: khaled@telia.net Cell: 070-6785492 Work: 08-4567281 :hacker: /n./ [originally, someone who makes furniture with an axe] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 2:37:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9CF8514E9F for ; Thu, 12 Aug 1999 02:37:38 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA17230; Thu, 12 Aug 1999 11:37:15 +0200 (CEST) (envelope-from des) To: tcobb@staff.circle.net Cc: mike@sentex.net, freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable References: <307D63ED6749CF11AAE9005004461A5B4059@FREYA> From: Dag-Erling Smorgrav Date: 12 Aug 1999 11:37:14 +0200 In-Reply-To: tcobb@staff.circle.net's message of "Wed, 11 Aug 1999 10:58:36 -0400" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcobb@staff.circle.net writes: > > Is not CDROM.COM running 3.x STABLE ? > Yes, but DG used some special hacks to get the system to be > stable and working. "Objection, your honor! That's hearsay!" -- "Sustained." DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 3: 2:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from volodya.prime.net.ua (volodya.prime.net.ua [195.64.229.17]) by hub.freebsd.org (Postfix) with ESMTP id 9BEF414D46 for ; Thu, 12 Aug 1999 03:02:25 -0700 (PDT) (envelope-from andyo@prime.net.ua) Received: from prime.net.ua (localhost [127.0.0.1]) by volodya.prime.net.ua (8.9.3/8.8.8) with ESMTP id NAA01419 for ; Thu, 12 Aug 1999 13:02:44 +0300 (EEST) (envelope-from andyo@prime.net.ua) Message-ID: <37B29BC2.8899E739@prime.net.ua> Date: Thu, 12 Aug 1999 13:02:43 +0300 From: "Andy V. Oleynik" Organization: M-Info X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en, ru, uk MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable References: <307D63ED6749CF11AAE9005004461A5B4059@FREYA> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why this is a top secret? Dag-Erling Smorgrav wrote: > tcobb@staff.circle.net writes: > > > Is not CDROM.COM running 3.x STABLE ? > > Yes, but DG used some special hacks to get the system to be > > stable and working. > > "Objection, your honor! That's hearsay!" -- "Sustained." > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- WBW Andy V. Oleynik (When U work in virtual office prime.net.ua's U have good chance to obtain system administrator virtual money ö%-) +380442448363 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 4: 0:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 2430015705 for ; Thu, 12 Aug 1999 04:00:10 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id DAA10520 for freebsd-stable@FreeBSD.ORG; Thu, 12 Aug 1999 03:59:08 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199908121059.DAA10520@gndrsh.aac.dev.com> Subject: Re: On freezes in 3.2-Stable (fwd) To: freebsd-stable@FreeBSD.ORG Date: Thu, 12 Aug 1999 03:59:08 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I didn't realize this person asked this off list, so I am forwarding my reply onto the list, it has information in it that someone should use to write a FAQ/FSA, this issue has come up some many times over the years that I am getting sick of reading it every time memory generations change. Basic rule, Don't ever expect to be able to drive more than 72 DRAM chips with anything in the PC world, period. You have to do bus buffering using balanced drivers and real clean layout work on the PC Board, and there ain't a PC maker out there who is going to bother with this unless they are supporting 8 sockets or more in high dollar server machines. ----- Forwarded message (env-from rgrimes) ----- From rgrimes Thu Aug 12 03:51:20 1999 Subject: Re: On freezes in 3.2-Stable In-Reply-To: <000e01bee4a7$d5d94550$0286860a@tasam.com> from Joe Gleason at "Aug 12, 1999 05:48:21 am" To: clash@tasam.com (Joe Gleason) Date: Thu, 12 Aug 1999 03:51:20 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] [Charset iso-8859-1 unsupported, filtering to ASCII...] > Other than price, is the a good way to tell the diffrence between 16 and 36 > chip modules when shopping? > > What manufacture/dealer do you deal with? I won't disclose that as they wouldn't due business with you at these quantities anyway so it would do you little good to know. I can say that the chips are always from major manufactures, Micron, Seimens, Hitachi, Fujistu, NEC, Samsung etc. > I am currently looking to upgrade my server that has 2x 256mb modules (the > 36 chip kind). > > Also, I am not on location so I can't check myself, but am I correct in > assuming that 36 chips would be for parity/ECC and 32 for non-parity? And > the same with 18/16? Yes, that would be the correct assumption. Note that in lower capacity parts you get into 8 and 9 chip or the oddball 3 and 12 chip versions of these things (on DIMMS that would only occur on newer parts that are 4 or 16MB if I did the math in my head right). > Do you have any idea what the "safe" threshold is for number of chips? The typical memory bus designer uses the standard current best practicies when determining the bus load that he is anticipating for the design. This leads to the conclusion that 16/18 chips per module as the limit. There is a reason that 36 chip modules will work if you stick 2 of them in a board that has 4 dimm slots, you only putting a total of 36 chips on a bus that was designed for 36 chips: (4*18==2*36, magic ain't it :-)). > Can you mix 36 chip and 18 chip modules in the same server? Generally not, the big thing to remeber is to keep the total chip count under the design load of the memory drivers, and today that is typically calculated as number_of_dimm_slots * standard_dimm_chipcount, nominal numbers are 4 * 18 == 72 chips total. If you have in EE background you'll note that this is getting upwards of a 100pF load, something pretty hard to drive at a 100MHZ without huge driver transitors and a lot of current! > Sorry for all the questions, but you seem to know what your talking about. > ;-) Having been in memory system design back in the days of the 16K to 256K DRAM chip doing 2+MB boards that where 12x18" gives me a pretty good clue as to what goes on with memory designs... and I keep up on all the latest in technology. Just wait till RAMbus hits in volume, boy are we going to have some ``flakey'' boxes caused by some of the poor design work done by the off shore groups. > > > > > 1. Supermicro can't handle a full 1GB, despite their specs > > > > > > $100 says that's it. > > > > $200 says that you using low density 256MB DIMMS that are overloading > > the BUS specification of the chipset on the motherboard. > > > > Current price ratio (well, okay 7/30/1999) on 18 chip vs 36 chip > > 32Mx72b ECC PC100 8nS is still 1:2, or about $300.00 vs $600.00. > > > > Alls I can say to those folks trying to do more than 512MB in a box > > with any current chip set is ``You have to spend the money for 18 chip > > parts if you want to have any type of reliable operation, no current > > chipset was designed to drive 144 chips'' > > > > Between David Greenman and my self we probably went through $25,000 > > of parts from various manufactures who claimed that they would work > > before we finally decided they are all wrong, and that we would just > > have to wait for the next generation of chips that would allow 18 chip > > 256MB DIMMS. > > > > If your memory vendor doesn't know what 18 chip 256MB DIMMS are drop > > me an email, they are in ready supply from either manufacture we deal > > with. All parts are lifetime warrantied. > > > > -- > > Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net ----- End of forwarded message (env-from rgrimes) ----- -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 5:19:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cits-darla.robins.af.mil (cits-darla.robins.af.mil [137.244.215.8]) by hub.freebsd.org (Postfix) with ESMTP id 06F7E14E91; Thu, 12 Aug 1999 05:19:46 -0700 (PDT) (envelope-from Andrew.Lofthouse@robins.af.mil) Received: from cits-darla.robins.af.mil (root@localhost) by cits-darla.robins.af.mil with ESMTP id IAA13712; Thu, 12 Aug 1999 08:16:51 -0400 (EDT) Received: from fsuhhz30.robins.af.mil (fsuhhz30.robins.af.mil [137.244.190.201]) by cits-darla.robins.af.mil with ESMTP id IAA13708; Thu, 12 Aug 1999 08:16:50 -0400 (EDT) Received: by fsuhhz30.robins.af.mil with Internet Mail Service (5.5.2232.9) id ; Thu, 12 Aug 1999 12:16:23 -0000 Message-ID: <3F69A3D5863ED211B31F0000F809353502D1D653@FSUHHZ33> From: Lofthouse Andrew 2Lt WRALC/TIECT To: frank@TINKER.exit.com, kris@hub.freebsd.org Cc: freebsd-stable@FreeBSD.ORG Subject: RE: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) Date: Thu, 12 Aug 1999 12:16:26 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I had the same problem; I posted the message about it yesterday: > > > > Yesterday I tried "make world" with the -STABLE sources on my machine > > running 2.2.8-RELEASE. Below is the final output of the make process... > > make world is not for updating between major revisions (2.x to 3.x). > There's a different target for this (make upgrade or something, check the > header of the /usr/src/Makefile). "Make upgrade." Which, of course, doesn't work. It breaks in the elf build of libmytinfo. what I'm hearing is that there is no way to upgrade from 2.2.8 to 3.2 (-RELEASE or -STABLE) by using "make world." So, exactly how can I upgrade to (or even install) 3.2 when I have the continuing problem described earlier (see below)? I've just tried installing 3.2-RELEASE on my computer using boot floppies and installing from a DOS partition. When booting the kernel on the boot floppy, the hardware probe doesn't find my primary controller (wdc0), and, as a consequence, doesn't find my hard drives, either. I've looked at the IRQ and the port addresses; they shouldn't be a problem (I've had 2.2.8-RELEASE running on the same machine without problems; the default IRQ and port for wdc0 are the same for both versions). I've got no device conflicts either. Could it be a problem with the new bootstrap procedure? or maybe the parallel port bus? Originally, I had my hard drives' geometry set by the user in the BIOS. I then changed it to autodetect the geometry. I tried booting the BSD boot floppy again, and it found wdc0 on the probe. I set up BSD as I normally do, then when I rebooted, the probe didn't find wdc0! (and, hence, the kernel panicked because it couldn't find my root partition). I tried using the install boot floppy again and ran into the same problem (couldn't find wdc0). Here's how my machine is set up: Intel 430 TX chipset w/ Pentium 200 MMX CPU; two hard drives (both on primary controller); one CD-ROM drive as master on secondary controller. I have multiple operating systems installed (NT, Win95, Linux, BSD, DOS); I had no problems running 2.2.8 with this configuration. I tried upgrading from 2.2.8 with 3.2 binaries, but ran into the same problems (couldn't mount root because of controller problems.) Any ideas please? Andrew J. Lofthouse, 2LT, USAF Technology Applications Engineer COM (912) 926-6617 DSN 468-6617 FAX (912) 926-7638 Andrew.Lofthouse@robins.af.mil WR-ALC/TIECT 420 Second St. Suite 100 Robins AFB, GA 31098-1640 > -----Original Message----- > From: Frank Mayhar [SMTP:frank@TINKER.exit.com] > Sent: Wednesday, August 11, 1999 4:21 PM > To: kris@hub.freebsd.org > Cc: Andrew.Lofthouse@robins.af.mil; brunner@maine.rr.com; > freebsd-stable@FreeBSD.ORG > Subject: Re: Problem reporting build failure (rebuilding bootstrap, > crtbeg in.c:33) > > Kris Kennaway wrote: > > On Wed, 11 Aug 1999, Lofthouse Andrew 2Lt WRALC/TIECT wrote: > > > > > I had the same problem; I posted the message about it yesterday: > > > > > > Yesterday I tried "make world" with the -STABLE sources on my machine > > > running 2.2.8-RELEASE. Below is the final output of the make > process... > > > > make world is not for updating between major revisions (2.x to 3.x). > > There's a different target for this (make upgrade or something, check > the > > header of the /usr/src/Makefile). > > "Make upgrade." Which, of course, doesn't work. It breaks in the elf > build > of libmytinfo. > -- > Frank Mayhar frank@exit.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 6:36:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.cioe.com (ns1.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id 6FDA015014 for ; Thu, 12 Aug 1999 06:36:47 -0700 (PDT) (envelope-from steve@ns1.cioe.com) Received: (from steve@localhost) by ns1.cioe.com (8.9.3/8.9.3) id IAA31060 for freebsd-stable@freebsd.org; Thu, 12 Aug 1999 08:35:54 -0500 (EST) (envelope-from steve) Date: Thu, 12 Aug 1999 08:35:54 -0500 (EST) From: Steve Ames Message-Id: <199908121335.IAA31060@ns1.cioe.com> To: freebsd-stable@freebsd.org Subject: Async mounted NFS exports? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any speed advantage to mounting NFS exported partitions in async mode? -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 9:51:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 48D8614D00 for ; Thu, 12 Aug 1999 09:51:28 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA24445; Thu, 12 Aug 1999 09:50:06 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Andy V. Oleynik" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Thu, 12 Aug 1999 13:02:43 +0300." <37B29BC2.8899E739@prime.net.ua> Date: Thu, 12 Aug 1999 09:50:06 -0700 Message-ID: <24441.934476606@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are no secrets here - people are simply making more of some simple configuration tweaks than is warranted. ftp.cdrom.com is not running a special version of FreeBSD, nor was it constructed with information gleaned from the aliens who crash-landed in Area 51, nor has Elvis been involved in the administration of the system. Get a life, you guys! - Jordan > Why this is a top secret? > Dag-Erling Smorgrav wrote: > > > tcobb@staff.circle.net writes: > > > > Is not CDROM.COM running 3.x STABLE ? > > > Yes, but DG used some special hacks to get the system to be > > > stable and working. > > > > "Objection, your honor! That's hearsay!" -- "Sustained." > > > > DES > > -- > > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > WBW Andy V. Oleynik (When U work in virtual office > prime.net.ua's U have good chance to obtain > system administrator virtual money ö%-) > +380442448363 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 12:29:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 34A0514D54; Thu, 12 Aug 1999 12:29:14 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id MAA81435; Thu, 12 Aug 1999 12:29:01 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Thu, 12 Aug 1999 12:29:01 -0700 (PDT) From: Doug X-Sender: doug@dt011n65.san.rr.com To: Lofthouse Andrew 2Lt WRALC/TIECT Cc: frank@TINKER.exit.com, kris@hub.freebsd.org, freebsd-stable@FreeBSD.ORG Subject: RE: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) In-Reply-To: <3F69A3D5863ED211B31F0000F809353502D1D653@FSUHHZ33> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Lofthouse Andrew 2Lt WRALC/TIECT wrote: > what I'm hearing is that there is no way to upgrade from 2.2.8 to 3.2 > (-RELEASE or -STABLE) by using "make world." That is partially correct. You can do the upgrade using 'make upgrade' which does 2+ world builds for you. See http://home.san.rr.com/freebsd/make-upgrade.html. However if I understand your situation accurately you might be better off just wiping your disk and starting fresh. Alternatively, if you can get your system to a stable/-stable version of 2.2.8 you should be able to do the make upgrade using the procedure on that page. Good luck, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 12:33:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 08CC614F80 for ; Thu, 12 Aug 1999 12:33:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA24458 for ; Thu, 12 Aug 1999 13:33:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA05527 for ; Thu, 12 Aug 1999 13:33:42 -0600 (MDT) Message-Id: <199908121933.NAA05527@harmony.village.org> To: stable@freebsd.org Subject: Kludge-o-round for 1 3.2 STABLE NFS problem Date: Thu, 12 Aug 1999 13:33:41 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We were having all kinds of problems using NFS on locally mounted file systems (that is, the client and server were on the same machine). It turns out that this can cause deadlock when large amounts of data are processed (a simple cat /tmp/11M-file /local-nfa/tmp would cause it). After working with Matt Dillon for a while, I came up with the following kludge-o-round. It messes with the very performance sensitive getnewbuffer() routine in vfs_bio.c, and generally works hard to prevent the deadlock from happening. It isn't a suitable fix for -stable, so I'm posting it here for people to use in the interrum. It only impacts locally mounted nfs file systems and note remotely mounted ones. The only reason that we hit this was due to our heavy use of the automounter... It also is relevant only for -stable. Matt's changes in -current (which can't easily be merged into -stable) make this deadlock impossible. I'm working with Matt to come up with a committable fix, but until then I thought I'd post this for people experiencing hangs on their -current systems with locally mounted file systems. It is provided as-is with no warrantee or support what so ever. Warner Index: kern/vfs_bio.c =================================================================== RCS file: /base/FreeBSD-CVS/src/sys/kern/vfs_bio.c,v retrieving revision 1.193.2.6 diff -u -r1.193.2.6 vfs_bio.c --- vfs_bio.c 1999/08/09 00:48:50 1.193.2.6 +++ vfs_bio.c 1999/08/11 18:52:02 @@ -51,6 +51,8 @@ #include #include #include +/* XXX this is bogus, but needed */ +#include static MALLOC_DEFINE(M_BIOBUF, "BIO buffer", "BIO buffer"); @@ -760,8 +762,8 @@ --numdirtybuffers; bp->b_flags &= ~B_DELWRI; } - vfs_bio_need_satisfy(); } + vfs_bio_need_satisfy(); /* unlock */ bp->b_flags &= ~(B_ORDERED | B_WANTED | B_BUSY | @@ -979,20 +981,65 @@ * We keep the file I/O from hogging metadata I/O * This is desirable because file data is cached in the * VM/Buffer cache even if a buffer is freed. + * + * If the NFS server is causing this potential flush out, then don't + * flush NFS buffers. This avoids a deadlock situation where the + * nfs server needs a buffer and indirectly causes the nfs client + * to try to flush a buffer out, which never completes because the + * nfs server is locking the receive queue. */ +queue_age: if ((bp = TAILQ_FIRST(&bufqueues[QUEUE_AGE]))) { #if !defined(MAX_PERF) if (bp->b_qindex != QUEUE_AGE) panic("getnewbuf: inconsistent AGE queue, qindex=%d", bp->b_qindex); #endif - } else if ((bp = TAILQ_FIRST(&bufqueues[QUEUE_LRU]))) { + if ((curproc->p_flag & P_NFSSERV) && + bp->b_vp->v_tag == VT_NFS && (bp->b_flags & B_DELWRI)) { + if (bp->b_usecount == 0) { + bp = NULL; + goto queue_lru; + } + bp->b_usecount--; + TAILQ_REMOVE(&bufqueues[QUEUE_AGE], bp, b_freelist); + if (TAILQ_FIRST(&bufqueues[QUEUE_AGE]) != NULL) { + TAILQ_INSERT_TAIL(&bufqueues[QUEUE_AGE], bp, + b_freelist); + goto queue_age; + } + TAILQ_INSERT_TAIL(&bufqueues[QUEUE_AGE], bp, + b_freelist); + bp = NULL; + } + } +queue_lru: + if (!bp && (bp = TAILQ_FIRST(&bufqueues[QUEUE_LRU]))) { #if !defined(MAX_PERF) if (bp->b_qindex != QUEUE_LRU) panic("getnewbuf: inconsistent LRU queue, qindex=%d", bp->b_qindex); #endif + if ((curproc->p_flag & P_NFSSERV) && + bp->b_vp->v_tag == VT_NFS && (bp->b_flags & B_DELWRI)) { + if (bp->b_usecount == 0) { + bp = NULL; + goto waitbuf; + } + bp->b_usecount--; + TAILQ_REMOVE(&bufqueues[QUEUE_LRU], bp, b_freelist); + if (TAILQ_FIRST(&bufqueues[QUEUE_LRU]) != NULL) { + TAILQ_INSERT_TAIL(&bufqueues[QUEUE_LRU], bp, + b_freelist); + bp = NULL; + goto queue_lru; + } + TAILQ_INSERT_TAIL(&bufqueues[QUEUE_LRU], bp, + b_freelist); + bp = NULL; + } } +waitbuf: if (!bp) { /* wait for a free buffer of any kind */ needsbuffer |= VFS_BIO_NEED_ANY; @@ -1022,7 +1069,6 @@ TAILQ_INSERT_TAIL(&bufqueues[QUEUE_LRU], bp, b_freelist); } } - /* if we are a delayed write, convert to an async write */ if ((bp->b_flags & (B_DELWRI | B_INVAL)) == B_DELWRI) { Index: nfs/nfs_syscalls.c =================================================================== RCS file: /base/FreeBSD-CVS/src/sys/nfs/nfs_syscalls.c,v retrieving revision 1.44.2.1 diff -u -r1.44.2.1 nfs_syscalls.c --- nfs_syscalls.c 1999/06/30 22:05:18 1.44.2.1 +++ nfs_syscalls.c 1999/08/11 16:21:58 @@ -483,6 +483,7 @@ bzero((caddr_t)nfsd, sizeof (struct nfsd)); s = splnet(); nfsd->nfsd_procp = p; + p->p_flag |= P_NFSSERV; TAILQ_INSERT_TAIL(&nfsd_head, nfsd, nfsd_chain); nfs_numnfsd++; } else Index: sys/proc.h =================================================================== RCS file: /base/FreeBSD-CVS/src/sys/sys/proc.h,v retrieving revision 1.66.2.4 diff -u -r1.66.2.4 proc.h --- proc.h 1999/05/14 06:32:41 1.66.2.4 +++ proc.h 1999/08/11 16:21:41 @@ -268,6 +268,7 @@ #define P_NOCLDWAIT 0x400000 /* No zombies if child dies */ +#define P_NFSSERV 0x2000000 /* Stamp NFS servers */ /* * MOVE TO ucred.h? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 12:46:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id C3A2F1585F for ; Thu, 12 Aug 1999 12:46:44 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id MAA98218; Thu, 12 Aug 1999 12:46:47 -0700 (PDT) Date: Thu, 12 Aug 1999 12:46:47 -0700 (PDT) From: David Wolfskill Message-Id: <199908121946.MAA98218@pau-amma.whistle.com> To: imp@village.org, stable@FreeBSD.ORG Subject: Re: Kludge-o-round for 1 3.2 STABLE NFS problem In-Reply-To: <199908121933.NAA05527@harmony.village.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Thu, 12 Aug 1999 13:33:41 -0600 >From: Warner Losh >We were having all kinds of problems using NFS on locally mounted file >systems (that is, the client and server were on the same machine)..... I encountered similar symptoms back when I started here, at around 2.2.6-R. My circumvention was to hack the amd maps in such a way that amd would recognize when the client & server had the same name: * If not, do the usual NFS stuff; * If so, instead of providing the illusion of an NFS mount, provide the illusion of a symlink. This is what allowed me to get anything at all done for the past several months.... I *thought* I had sent a note to one of the freebsd lists about it, including some of the stuff in the amd maps. If it appears to be of use, I'm certainly willing to share. (The note to the effect that "a weird imagination is most useful to gain full advantage of some of all the [amd] features" is well-advised.) And of course, I freely admit that the approach merely masks the problem. Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 14:43:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 317C414D17 for ; Thu, 12 Aug 1999 14:43:13 -0700 (PDT) (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 QAA04979; Thu, 12 Aug 1999 16:42:45 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.3/8.7.3) id QAA26893; Thu, 12 Aug 1999 16:42:45 -0500 (CDT) Date: Thu, 12 Aug 1999 16:42:45 -0500 From: Alan Cox To: eirvine Cc: stable@freebsd.org Subject: Re: Compiled a kernel with egcs Message-ID: <19990812164245.A26812@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Running a recent cvsup of 3.2 on my new PC at home. I found I could > compile a kernel with egcs. > > Is this expected behaviour? I thought I could only do this on current. I don't recommend running it. There is a least one bug caused by gcc -> egcs migration that we fixed in -Current a couple weeks ago. See the changelog for i386/include/atomic.h. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 15:27:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C4BCC14C89 for ; Thu, 12 Aug 1999 15:27:04 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA24941; Thu, 12 Aug 1999 16:27:09 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA06512; Thu, 12 Aug 1999 16:27:03 -0600 (MDT) Message-Id: <199908122227.QAA06512@harmony.village.org> To: Alan Cox Subject: Re: Compiled a kernel with egcs Cc: eirvine , stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 12 Aug 1999 16:42:45 CDT." <19990812164245.A26812@nonpc.cs.rice.edu> References: <19990812164245.A26812@nonpc.cs.rice.edu> Date: Thu, 12 Aug 1999 16:27:03 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990812164245.A26812@nonpc.cs.rice.edu> Alan Cox writes: : > Running a recent cvsup of 3.2 on my new PC at home. I found I could : > compile a kernel with egcs. : > : > Is this expected behaviour? I thought I could only do this on current. : : I don't recommend running it. There is a least one bug caused : by gcc -> egcs migration that we fixed in -Current a couple weeks : ago. See the changelog for i386/include/atomic.h. So you wouldn't be interested in a patch that works on UP machines to allow it to compile under the old 3.x compiler? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 16: 5:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id ED98914C83 for ; Thu, 12 Aug 1999 16:05:38 -0700 (PDT) (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 SAA06683; Thu, 12 Aug 1999 18:05:48 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.3/8.7.3) id SAA27373; Thu, 12 Aug 1999 18:05:48 -0500 (CDT) Date: Thu, 12 Aug 1999 18:05:48 -0500 From: Alan Cox To: Warner Losh Cc: stable@freebsd.org Subject: Re: Compiled a kernel with egcs Message-ID: <19990812180548.A27359@nonpc.cs.rice.edu> References: <19990812164245.A26812@nonpc.cs.rice.edu> <199908122227.QAA06512@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199908122227.QAA06512@harmony.village.org>; from Warner Losh on Thu, Aug 12, 1999 at 04:27:03PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 12, 1999 at 04:27:03PM -0600, Warner Losh wrote: > > So you wouldn't be interested in a patch that works on UP machines to > allow it to compile under the old 3.x compiler? > Yes, I would be interested. As far as we know, the combination of -STABLE's atomic.h and gcc-2.7.2.x generates safe code, but there's no point in relying on chance (i.e., the specifics of an old gcc's code generator) if we can avoid it. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 16:23:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A42DE14E2F for ; Thu, 12 Aug 1999 16:23:06 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA25116; Thu, 12 Aug 1999 17:23:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA06773; Thu, 12 Aug 1999 17:23:12 -0600 (MDT) Message-Id: <199908122323.RAA06773@harmony.village.org> To: Alan Cox Subject: Re: Compiled a kernel with egcs Cc: stable@freebsd.org In-reply-to: Your message of "Thu, 12 Aug 1999 18:05:48 CDT." <19990812180548.A27359@nonpc.cs.rice.edu> References: <19990812180548.A27359@nonpc.cs.rice.edu> <19990812164245.A26812@nonpc.cs.rice.edu> <199908122227.QAA06512@harmony.village.org> Date: Thu, 12 Aug 1999 17:23:11 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990812180548.A27359@nonpc.cs.rice.edu> Alan Cox writes: : Yes, I would be interested. As far as we know, the combination : of -STABLE's atomic.h and gcc-2.7.2.x generates safe code, but there's no : point in relying on chance (i.e., the specifics of an old gcc's : code generator) if we can avoid it. Agreed. Since we've vetted the old gcc code generators, the patches I have use the old way for them and the new way for 2.8 and newer. Mostly because I have never understood the constraints in asm statements... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 17:26:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 5028514A2D for ; Thu, 12 Aug 1999 17:26:51 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-108.dialup.HiWAAY.net [216.180.14.108]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id TAA22785; Thu, 12 Aug 1999 19:26:47 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id SAA05415; Thu, 12 Aug 1999 18:56:16 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908122356.SAA05415@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: W Gerald Hicks Cc: Bob Bishop , tcobb@staff.circle.net, freebsd-stable@freebsd.org, wghicks@wghicks.bellsouth.net From: David Kelly Subject: Re: On freezes in 3.2-Stable In-reply-to: Message from W Gerald Hicks of "Thu, 12 Aug 1999 00:19:14 EDT." <199908120419.AAA11935@bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Aug 1999 18:56:16 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG W Gerald Hicks writes: > > > At Gateway or Dell customize-your-system sites I've seen notes stating > > one can't fill the 3rd or 4th memory slot if one has more than 2 or 3 > > internal HD's. I wonder if its a power supply issue? > > Naw, it's a capacitive loading issue :) > > Rod hit the nail on the head. I too believe Rod is right. But the number of internal HD's doesn't have anything to do with the memory bus loading. Have never given much thought to how much power memory consumes. Not having one of the systems I was "configuring" online, I don't know if they have a problem where the 2nd or 3rd HD consumes the space where the 3rd or 4th memory SIMM would go or now. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 21:34:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id C97D014C3B for ; Thu, 12 Aug 1999 21:34:21 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-36-202.ath.bellsouth.net [216.78.36.202]) by mail1.atl.bellsouth.net (3.3.0/8.9.3) with ESMTP id AAA00231; Fri, 13 Aug 1999 00:31:11 -0400 (EDT) Received: from wghicks.bellsouth.net (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id AAA00518; Fri, 13 Aug 1999 00:37:40 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199908130437.AAA00518@bellsouth.net> To: David Kelly Cc: freebsd-stable@freebsd.org Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Thu, 12 Aug 1999 18:56:16 CDT." <199908122356.SAA05415@nospam.hiwaay.net> Date: Fri, 13 Aug 1999 00:37:40 -0400 From: W Gerald Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The scary part (at least to me) about drive power consumption really occurs during the initial power-on inrush. When I kept up with the numbers for these things in a former life working for a disk manufacturer, I was always astounded at how much current the drives pulled during their power-on sequence. After startup, current begins to taper off rapidly. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 12 21:46: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id B670814C3B for ; Thu, 12 Aug 1999 21:46:03 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 22643 invoked by uid 100); 13 Aug 1999 04:45:55 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Aug 1999 04:45:55 -0000 Date: Thu, 12 Aug 1999 21:45:55 -0700 (PDT) From: Mike Meyer To: freebsd-stable@freebsd.org Subject: Re: On freezes in 3.2-Stable In-Reply-To: <199908130437.AAA00518@bellsouth.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Aug 1999, W Gerald Hicks wrote: :->When I kept up with the numbers for these things in a former :->life working for a disk manufacturer, I was always astounded :->at how much current the drives pulled during their power-on :->sequence. After startup, current begins to taper off rapidly. This stopped being relevant a long time ago, but... DEC MIPS-based workstations worked around this problem by having tweaked PROMs on their SCSI drives, with a SPIN-UP-ON-POWERON bit that defaulted to off. Ultrix would send the drives the SCSI command to spin them up - *after* everything else in the system was powered on. This meant they could use a cheaper power supply, as no supported configuration required it to deal with more than one drive spinning up at a time. Dealing with this was the *least* of the problems in trying to use DEC SCSI drives on other platforms. But they could be made to work. X-Sender: nadav@csd To: Mike Meyer Cc: freebsd-chat@freebsd.org Subject: Re: On freezes in 3.2-Stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Aug 1999, Mike Meyer wrote: > On Fri, 13 Aug 1999, W Gerald Hicks wrote: > :->When I kept up with the numbers for these things in a former > :->life working for a disk manufacturer, I was always astounded > :->at how much current the drives pulled during their power-on > :->sequence. After startup, current begins to taper off rapidly. > > This stopped being relevant a long time ago, but... Moved to -chat then. > > DEC MIPS-based workstations worked around this problem by having > tweaked PROMs on their SCSI drives, with a SPIN-UP-ON-POWERON bit that > defaulted to off. Ultrix would send the drives the SCSI command to > spin them up - *after* everything else in the system was powered > on. This meant they could use a cheaper power supply, as no supported > configuration required it to deal with more than one drive spinning up > at a time. DEC used this scheme on _all_ their machines. This makes a lot of sense, at least to me, when you have many disks. I think most Alpha's do it to this day. VAXen used to do that too, and at least under VMS (never admin'ed anything else on a VAX), the console would spin up the boot device, and the mount commands would spin up the rest of the disks. I think many extenral RAID cases also power up disks sequentially to prevent overloading the power supply (DEC's StorageWorks do). > > Dealing with this was the *least* of the problems in trying to use DEC > SCSI drives on other platforms. But they could be made to work. They had a jumper - no big deal. BTW, many other disks (at least my IBM DDRS's at home) have such a jumper, only it defaults to on. > > > > > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 6:20:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cits-darla.robins.af.mil (cits-darla.robins.af.mil [137.244.215.8]) by hub.freebsd.org (Postfix) with ESMTP id B1A8914C25 for ; Fri, 13 Aug 1999 06:20:33 -0700 (PDT) (envelope-from Andrew.Lofthouse@robins.af.mil) Received: from cits-darla.robins.af.mil (root@localhost) by cits-darla.robins.af.mil with ESMTP id JAA20273 for ; Fri, 13 Aug 1999 09:20:33 -0400 (EDT) Received: from fsuhhz31.robins.af.mil (fsuhhz31.robins.af.mil [137.244.190.209]) by cits-darla.robins.af.mil with ESMTP id JAA20267 for ; Fri, 13 Aug 1999 09:20:33 -0400 (EDT) Received: by fsuhhz31.robins.af.mil with Internet Mail Service (5.5.2232.9) id ; Fri, 13 Aug 1999 13:20:18 -0000 Message-ID: <3F69A3D5863ED211B31F0000F809353502D1DC84@FSUHHZ33> From: Lofthouse Andrew 2Lt WRALC/TIECT To: freebsd-stable@FreeBSD.ORG Subject: RE: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) Date: Fri, 13 Aug 1999 13:20:19 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > what I'm hearing is that there is no way to upgrade from 2.2.8 to 3.2 > (-RELEASE or -STABLE) by using "make world." That is partially correct. You can do the upgrade using 'make upgrade' which does 2+ world builds for you. See http://home.san.rr.com/freebsd/make-upgrade.html. However if I understand your situation accurately you might be better off just wiping your disk and starting fresh. Alternatively, if you can get your system to a stable/-stable version of 2.2.8 you should be able to do the make upgrade using the procedure on that page. I wish it were that simple. I just tried doing make upgrade last night with -STABLE, but the build crashed (an error with ioctl.c; there was an undefined function in ioctl.c and another problem with one of the include files; I didn't bring my script output with me today so I can't remember exactly what the problems were.) Perhaps that's because I didn't have 2.2.8-STABLE (just -RELEASE). Thanks for the tip on the cited website; I'll check it out. I've tried starting fresh, but the new 3.2-RELEASE kernel hardware probe hasn't been detecting my primary IDE controller (?); which is a mystery to me. Andrew J. Lofthouse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 8:57:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 024AD15062 for ; Fri, 13 Aug 1999 08:57:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id IAA19864; Fri, 13 Aug 1999 08:56:30 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA32830; Fri, 13 Aug 1999 08:56:27 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 13 Aug 1999 08:56:27 -0700 (PDT) Message-Id: <199908131556.IAA32830@vashon.polstra.com> To: Andrew.Lofthouse@robins.af.mil Subject: Re: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) In-Reply-To: <3F69A3D5863ED211B31F0000F809353502D1DC84@FSUHHZ33> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3F69A3D5863ED211B31F0000F809353502D1DC84@FSUHHZ33>, Lofthouse Andrew 2Lt WRALC/TIECT wrote: > > I wish it were that simple. I just tried doing make upgrade last night with > -STABLE, but the build crashed (an error with ioctl.c; there was an > undefined function in ioctl.c and another problem with one of the include > files; I didn't bring my script output with me today so I can't remember > exactly what the problems were.) Perhaps that's because I didn't have > 2.2.8-STABLE (just -RELEASE). Thanks for the tip on the cited website; I'll > check it out. Use "make upgrade" to get from 2.2.8-stable to 3.0-release. Then use "make world" to get from 3.0-release to 3.x-stable. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 10: 1:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7965C14F22 for ; Fri, 13 Aug 1999 10:01:20 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA61444; Fri, 13 Aug 1999 11:00:55 -0600 (MDT) (envelope-from ken) Message-Id: <199908131700.LAA61444@panzer.kdm.org> Subject: Re: On freezes in 3.2-Stable In-Reply-To: from Mike Meyer at "Aug 12, 1999 09:45:55 pm" To: mwm@phone.net (Mike Meyer) Date: Fri, 13 Aug 1999 11:00:55 -0600 (MDT) Cc: freebsd-stable@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote... > On Fri, 13 Aug 1999, W Gerald Hicks wrote: > :->When I kept up with the numbers for these things in a former > :->life working for a disk manufacturer, I was always astounded > :->at how much current the drives pulled during their power-on > :->sequence. After startup, current begins to taper off rapidly. > > This stopped being relevant a long time ago, but... > > DEC MIPS-based workstations worked around this problem by having > tweaked PROMs on their SCSI drives, with a SPIN-UP-ON-POWERON bit that > defaulted to off. Ultrix would send the drives the SCSI command to > spin them up - *after* everything else in the system was powered > on. This meant they could use a cheaper power supply, as no supported > configuration required it to deal with more than one drive spinning up > at a time. > > Dealing with this was the *least* of the problems in trying to use DEC > SCSI drives on other platforms. But they could be made to work. Most disks have a jumper that disables power-on spinup. Believe it or not, we've got something similar to the Ultrix spin-up stuff. FreeBSD/CAM will spin up drives on boot that are not already spinning. Generally, this happens in the probe stage, at the serial number inquiry stage. Most disks will not return a serial number without being spun up. Some disks, most notably high end IBM disks, will return their serial number without being spun up. So the boot process goes on in that case, and the drives are spun up when the da driver sends its read capacity command. By default, CAM will only attempt to spin up 4 drives at a time, to avoid overloading a power supply. You can adjust the maximum number of concurrent start unit commands allowed with the CAM_MAX_HIGHPOWER kernel config option. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 12: 2:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8B35214BEA for ; Fri, 13 Aug 1999 12:02:09 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA27376; Fri, 13 Aug 1999 20:52:11 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id SAA01361; Fri, 13 Aug 1999 18:39:51 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908131639.SAA01361@yedi.iaf.nl> Subject: Re: On freezes in 3.2-Stable In-Reply-To: from Mike Meyer at "Aug 12, 1999 9:45:55 pm" To: mwm@phone.net (Mike Meyer) Date: Fri, 13 Aug 1999 18:39:51 +0200 (CEST) Cc: freebsd-stable@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Mike Meyer wrote ... > On Fri, 13 Aug 1999, W Gerald Hicks wrote: > :->When I kept up with the numbers for these things in a former > :->life working for a disk manufacturer, I was always astounded > :->at how much current the drives pulled during their power-on > :->sequence. After startup, current begins to taper off rapidly. > > This stopped being relevant a long time ago, but... > > DEC MIPS-based workstations worked around this problem by having > tweaked PROMs on their SCSI drives, with a SPIN-UP-ON-POWERON bit that > defaulted to off. Ultrix would send the drives the SCSI command to > spin them up - *after* everything else in the system was powered > on. This meant they could use a cheaper power supply, as no supported > configuration required it to deal with more than one drive spinning up > at a time. This applies to older DEC RZxx drives. The newer ones are set for staggered spinup which boils down to a delayed spinup after powerup with the delay being determined by the SCSI ID the drive is set to. So, something like: delay=3 seconds * SCSI ID This works just fine and helps a lot if you want to be easy on your PSUs. And for the record: it is no limited to MIPS Ultrix boxes, all DEC RZ drives had the wait for spinup command enabled. In some cases you can alter this behaviour by jumpering the drive, in other cases it is flipping a mode page bit. And it is not Ultrix sending the spinup command but the console code. Would be a bit difficult to boot a kernel from a disc waiting for a spinup command originating from the same kernel.. > Dealing with this was the *least* of the problems in trying to use DEC > SCSI drives on other platforms. But they could be made to work. What is so problematic about DEC scsi drives? You make me curious... Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 13:23: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from exit-gw.power.net (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 7F1FC14C2D for ; Fri, 13 Aug 1999 13:22:57 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by exit-gw.power.net (8.8.8/8.8.8) with ESMTP id NAA05673; Fri, 13 Aug 1999 13:21:33 -0700 (PDT) (envelope-from frank@tinker.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.1) id NAA17423; Fri, 13 Aug 1999 13:21:32 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <199908132021.NAA17423@realtime.exit.com> Subject: Re: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) In-Reply-To: <199908131556.IAA32830@vashon.polstra.com> from John Polstra at "Aug 13, 1999 8:56:27 am" To: jdp@polstra.com (John Polstra) Date: Fri, 13 Aug 1999 13:21:32 -0700 (PDT) Cc: Andrew.Lofthouse@robins.af.mil, stable@FreeBSD.ORG Reply-To: frank@exit.com 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article <3F69A3D5863ED211B31F0000F809353502D1DC84@FSUHHZ33>, > Lofthouse Andrew 2Lt WRALC/TIECT wrote: > > > > I wish it were that simple. I just tried doing make upgrade last night with > > -STABLE, but the build crashed (an error with ioctl.c; there was an > > undefined function in ioctl.c and another problem with one of the include > > files; I didn't bring my script output with me today so I can't remember > > exactly what the problems were.) Perhaps that's because I didn't have > > 2.2.8-STABLE (just -RELEASE). Thanks for the tip on the cited website; I'll > > check it out. > > Use "make upgrade" to get from 2.2.8-stable to 3.0-release. Then > use "make world" to get from 3.0-release to 3.x-stable. "Make upgrade" doesn't exist in 3.0-release. There's just world, aout-to-elf, aout-to-elf-build, aout-to-elf-install and move-aout-libs. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 13:40:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A77C814DA1 for ; Fri, 13 Aug 1999 13:40:17 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id NAA20975; Fri, 13 Aug 1999 13:38:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA34229; Fri, 13 Aug 1999 13:38:53 -0700 (PDT) (envelope-from jdp@polstra.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: <199908132021.NAA17423@realtime.exit.com> Date: Fri, 13 Aug 1999 13:38:52 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Frank Mayhar Subject: Re: Problem reporting build failure (rebuilding bootstrap, crtbe Cc: stable@FreeBSD.ORG, Andrew.Lofthouse@robins.af.mil Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Mayhar wrote: > John Polstra wrote: >> >> Use "make upgrade" to get from 2.2.8-stable to 3.0-release. Then >> use "make world" to get from 3.0-release to 3.x-stable. > > "Make upgrade" doesn't exist in 3.0-release. There's just > world, aout-to-elf, aout-to-elf-build, aout-to-elf-install and > move-aout-libs. Sorry. Use "make aout-to-elf" then. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 15:13:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 7D7A215042 for ; Fri, 13 Aug 1999 15:13:19 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id PAA93300; Fri, 13 Aug 1999 15:11:46 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 13 Aug 1999 15:11:46 -0700 (PDT) From: Doug X-Sender: doug@dt011n65.san.rr.com To: Frank Mayhar Cc: John Polstra , Andrew.Lofthouse@robins.af.mil, stable@FreeBSD.ORG Subject: Re: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) In-Reply-To: <199908132021.NAA17423@realtime.exit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Aug 1999, Frank Mayhar wrote: > "Make upgrade" doesn't exist in 3.0-release. There's just world, aout-to-elf, > aout-to-elf-build, aout-to-elf-install and move-aout-libs. I think I sent you this already, but if I didn't take a look at http://home.san.rr.com/freebsd/make-upgrade.html. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 15:24:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by hub.freebsd.org (Postfix) with ESMTP id 43C7814FE3; Fri, 13 Aug 1999 15:24:16 -0700 (PDT) (envelope-from rjs@fdy2.demon.co.uk) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.8/8.8.8) id XAA00384; Thu, 12 Aug 1999 23:15:17 +0100 (BST) (envelope-from rjs) Date: Thu, 12 Aug 1999 23:15:17 +0100 (BST) Message-Id: <199908122215.XAA00384@fdy2.demon.co.uk> From: Robert Swindells To: Doug@gorean.org Cc: Andrew.Lofthouse@robins.af.mil, frank@TINKER.exit.com, kris@hub.freebsd.org, freebsd-stable@freebsd.org In-reply-to: (message from Doug on Thu, 12 Aug 1999 12:29:01 -0700 (PDT)) Subject: Re: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> what I'm hearing is that there is no way to upgrade from 2.2.8 to 3.2 >> (-RELEASE or -STABLE) by using "make world." >That is partially correct. You can do the upgrade using 'make >upgrade' which does 2+ world builds for you. See >http://home.san.rr.com/freebsd/make-upgrade.html. However if I understand >your situation accurately you might be better off just wiping your disk >and starting fresh. Alternatively, if you can get your system to a >stable/-stable version of 2.2.8 you should be able to do the make upgrade >using the procedure on that page. I can confirm that it does still work. I upgraded one of my systems two days ago from 2.2.8-STABLE to 3.2-STABLE. Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 15:41:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 7998514F9C for ; Fri, 13 Aug 1999 15:41:19 -0700 (PDT) (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 PAA01501; Fri, 13 Aug 1999 15:34:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908132234.PAA01501@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: tcobb@staff.circle.net Cc: freebsd-stable@freebsd.org Subject: Re: On freezes in 3.2-Stable In-reply-to: Your message of "Wed, 11 Aug 1999 10:42:22 EDT." <307D63ED6749CF11AAE9005004461A5B4057@FREYA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 15:34:08 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Anyone know if patching FreeBSD is required in order to support > 1GB RAM? Anyone successfully running their box w/ 1GB RAM > and 3.2-S? We have built several releases (including 3.2, if I remember correctly) on a box with 1GB of memory, using no special patches or configuration options. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 16:19:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 45B1414F69 for ; Fri, 13 Aug 1999 16:19:43 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-33.dialup.rdu.ipass.net [209.170.132.33]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id TAA28790; Fri, 13 Aug 1999 19:19:31 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id TAA00913; Fri, 13 Aug 1999 19:20:48 -0400 (EDT) (envelope-from rhh) Date: Fri, 13 Aug 1999 19:20:48 -0400 From: Randall Hopper To: Kazutaka YOKOTA Cc: stable@freebsd.org Subject: Re: (Bug?) Console toasted by XFree 3.9.15 Message-ID: <19990813192047.A744@ipass.net> References: <19990810202752.A709@ipass.net> <199908110044.JAA01126@zodiac.mech.utsunomiya-u.ac.jp> <19990810204839.A1711@ipass.net> <199908110454.NAA04504@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199908110454.NAA04504@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Wed, Aug 11, 1999 at 01:54:11PM +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA: | |> |>However, when I hit -- to kill X and dump to the console, |> |>the video card quit emitting a signal altogether (that is, my monitor's |> |>"lost-signal" menu came up). |> |> |> |>Anybody seen this one? Report it to XFree86? |> | |> |Which video card and X server are you using? |> |> CARD : STB Velocity 3D 4Meg (S3 Virge/VX) |> SERVER: s3virge |> X VID MODE: 1600x1200 virtual, 1344x1008x16bpp actual |>SYSCONS MODE: 132x43 |> |>I tried the vga driver first, thinking the old SVGA server might have been |>rolled into that, but it didn't know 16bpp. So I switched to s3virge. | |Are you able to switch between the X session and text vtys by |hitting Ctl-Alt-Fn while the X server is running? No. When I try to switch to a console tty, my video card loses its signal. (If I recall the monitor viewmeter correctly, the video card is thrown down into a 2KHz horizontal, 0 Hz vertical setting -- or something along those lines). |You set syscons into the VESA 132x43 mode. How did you do that? |Did you run vidcontrol by hand? Or, you run it in /etc/rc*? /etc/rc.local: vidcontrol < /dev/ttyv0 -f 8x8 cp866-8x8 vidcontrol < /dev/ttyv0 132x43 vidcontrol < /dev/ttyv1 132x43 vidcontrol < /dev/ttyv2 132x43 |Are all vtys set in this 132x43 mode? Or, just a single vty is set |to this mode? All vtys. |Have you ever start the X server when all vtys are in the standard |80x25 mode? I just tried that. Quiting/suspending XFree86 3.9.15 toasted the video clocks just the same as before with 132x43. |Have you had the same or similar problem before with the previous versions |of XFree86? No. XFree86 3.3.3.1 works just fine quiting/suspending X to 80x25 or 132x43. Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 16:48:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 434B21504A for ; Fri, 13 Aug 1999 16:48:34 -0700 (PDT) (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 QAA01905; Fri, 13 Aug 1999 16:42:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908132342.QAA01905@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Rodney W. Grimes" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: On freezes in 3.2-Stable (fwd) In-reply-to: Your message of "Thu, 12 Aug 1999 03:59:08 PDT." <199908121059.DAA10520@gndrsh.aac.dev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 16:42:04 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I didn't realize this person asked this off list, so I am forwarding > my reply onto the list, it has information in it that someone should > use to write a FAQ/FSA, this issue has come up some many times over > the years that I am getting sick of reading it every time memory > generations change. > > Basic rule, Don't ever expect to be able to drive more than 72 DRAM > chips with anything in the PC world, period. You have to do bus > buffering using balanced drivers and real clean layout work on the PC Board, > and there ain't a PC maker out there who is going to bother with > this unless they are supporting 8 sockets or more in high dollar > server machines. Er. The Intel AD450NX has 32 DIMM sockets. Unless someone starts making 2-chip DIMMs, I don't see how you would run 8GB in this box (and I have seen it being done under other operating systems). You might want to qualify the issue a little further; specifically with regard to "typical memory controllers", logic families and fanout. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 16:51:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from chumbly.math.missouri.edu (chumbly.math.missouri.edu [128.206.72.12]) by hub.freebsd.org (Postfix) with ESMTP id 6C2F91505C for ; Fri, 13 Aug 1999 16:51:29 -0700 (PDT) (envelope-from rich@chumbly.math.missouri.edu) Received: (from rich@localhost) by chumbly.math.missouri.edu (8.9.1a/8.9.1) id SAA24994; Fri, 13 Aug 1999 18:49:41 -0500 (CDT) From: Rich Winkel Message-Id: <199908132349.SAA24994@chumbly.math.missouri.edu> Subject: Re: make installworld 3.2R -> 3.2S fails over NFS To: rich@chumbly.math.missouri.edu (Rich Winkel) Date: Fri, 13 Aug 1999 18:49:40 -0500 (CDT) Cc: owensc@enc.edu, rich@chumbly.math.missouri.edu, freebsd-stable@freebsd.org In-Reply-To: <199908101642.LAA19011@chumbly.math.missouri.edu> from "Rich Winkel" at Aug 10, 99 11:42:29 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Rich Winkel: > According to Charles Owens: > > Rich Winkel wrote: > > > I just cvsupped fresh sources this weekend with the same result. > > > Does anyone else use nfs to "installworld"? > > > Or am I the only one having this problem? > > From 3.0R to at least 3.1-stable I've seen this problem. The > > (annoying) workaround has been to do RW mounts of /usr/src and > > /usr/obj. I've seen some discussion of this problem on the -hackers > > list of late, with some mention of fixes. I updated my sources to the > > latest 3.2-stable on August 4th and happily found that running > > installworld over read-only NFS mounts worked again! > Actually this error arises with a r/w mount. I get a different > error (while trying to make a symbolic link) when it's r/o. I just cvsupped RELENG_3 again today (8/13/99) and I'm still having the same problem. If anyone out there has this working properly over a r/o OR r/w nfs mount I'd like to know about it. Or should I just set NOPERL=true in /etc/make.conf and forget about it? ===> gnu/usr.bin/ld install -c -s -o root -g wheel -m 555 ld /usr/libexec/aout install -c -o root -g wheel -m 444 ld.1aout.gz /usr/share/man/man1aout ===> gnu/usr.bin/perl ===> gnu/usr.bin/perl/libperl ln -sf /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/config_h.SH config_h.sh ln: config_h.sh: Read-only file system Incurably optimistically, Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 17:46: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 1A38814EA1 for ; Fri, 13 Aug 1999 17:45:57 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id RAA02542; Fri, 13 Aug 1999 17:46:02 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199908140046.RAA02542@gndrsh.aac.dev.com> Subject: Re: On freezes in 3.2-Stable (fwd) In-Reply-To: <199908132342.QAA01905@dingo.cdrom.com> from Mike Smith at "Aug 13, 1999 04:42:04 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 13 Aug 1999 17:46:01 -0700 (PDT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I didn't realize this person asked this off list, so I am forwarding > > my reply onto the list, it has information in it that someone should > > use to write a FAQ/FSA, this issue has come up some many times over > > the years that I am getting sick of reading it every time memory > > generations change. > > > > Basic rule, Don't ever expect to be able to drive more than 72 DRAM > > chips with anything in the PC world, period. You have to do bus > > buffering using balanced drivers and real clean layout work on the PC Board, > > and there ain't a PC maker out there who is going to bother with > > this unless they are supporting 8 sockets or more in high dollar ^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^ > > server machines. ^^^^^^^^^^^^^^^^ > > Er. The Intel AD450NX has 32 DIMM sockets. Unless someone starts > making 2-chip DIMMs, I don't see how you would run 8GB in this box (and > I have seen it being done under other operating systems). The Intel AD450NX in in the class ``supporting 8 sockets or more''. The Intel AD450NX is in the class ``high dollar server machines''. > > You might want to qualify the issue a little further; specifically with > regard to "typical memory controllers", logic families and fanout. I think I qualified it plenty enough... As far as logic families and fanout, well they really don't matter much with regards to this issue, memory drivers are special, not made with the same configuration that the logic family is, and thus it's fanout is quite different. The constant has been 72 for a very long time, since I started duing mos memory system designs with 54xx/74xx TTL in the 80's until today with the latest in CMOS and BiCMOS. Yea.. I could design a supper honking driver that can drive 288 chips in the memory controller, but then all the RAM chips would have to have larger data drivers to handle that side of the bus. It ain't changed in 20 years, and it ain't likely to change, infact if anything it is going to decrease as f goes up. RAMBUS is already starting to push some very tough real world physical limits. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 19:56:41 1999 Delivered-To: freebsd-stable@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 7AE5415082 for ; Fri, 13 Aug 1999 19:56:35 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:LpkZ4qsm6PQukgO/c8dn7XIMeVNoz7o2@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id LAA23721; Sat, 14 Aug 1999 11:56:06 +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 MAA10586; Sat, 14 Aug 1999 12:00:25 +0900 (JST) Message-Id: <199908140300.MAA10586@zodiac.mech.utsunomiya-u.ac.jp> To: Randall Hopper Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: (Bug?) Console toasted by XFree 3.9.15 In-reply-to: Your message of "Fri, 13 Aug 1999 19:20:48 -0400." <19990813192047.A744@ipass.net> References: <19990810202752.A709@ipass.net> <199908110044.JAA01126@zodiac.mech.utsunomiya-u.ac.jp> <19990810204839.A1711@ipass.net> <199908110454.NAA04504@zodiac.mech.utsunomiya-u.ac.jp> <19990813192047.A744@ipass.net> Date: Sat, 14 Aug 1999 12:00:24 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > |Have you ever start the X server when all vtys are in the standard > |80x25 mode? > >I just tried that. Quiting/suspending XFree86 3.9.15 toasted the video >clocks just the same as before with 132x43. So, the VESA module is not the cause... > |Have you had the same or similar problem before with the previous versions > |of XFree86? > >No. XFree86 3.3.3.1 works just fine quiting/suspending X to 80x25 or 132x43. Ok, we can now say this problem lies in the XFree86 S3 Virge server. You had better report this to the XFree86 project. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 20:26: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 1B86A150F2 for ; Fri, 13 Aug 1999 20:24:56 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-4-236.dialup.rdu.ipass.net [209.170.134.236]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id XAA05679; Fri, 13 Aug 1999 23:22:32 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id XAA01193; Fri, 13 Aug 1999 23:23:50 -0400 (EDT) (envelope-from rhh) Date: Fri, 13 Aug 1999 23:23:50 -0400 From: Randall Hopper To: Kazutaka YOKOTA Cc: stable@freebsd.org Subject: Re: (Bug?) Console toasted by XFree 3.9.15 Message-ID: <19990813232350.B804@ipass.net> References: <19990810202752.A709@ipass.net> <199908110044.JAA01126@zodiac.mech.utsunomiya-u.ac.jp> <19990810204839.A1711@ipass.net> <199908110454.NAA04504@zodiac.mech.utsunomiya-u.ac.jp> <19990813192047.A744@ipass.net> <199908140300.MAA10586@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199908140300.MAA10586@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Sat, Aug 14, 1999 at 12:00:24PM +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA: |> |>No. XFree86 3.3.3.1 works just fine quiting/suspending X to 80x25 or |>132x43. | |Ok, we can now say this problem lies in the XFree86 S3 Virge server. |You had better report this to the XFree86 project. That's what I figured. I'll send in the bug report shortly. Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 13 22:30:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 3EBA21509A for ; Fri, 13 Aug 1999 22:30:17 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 78478 invoked by uid 100); 14 Aug 1999 05:28:56 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Aug 1999 05:28:56 -0000 Date: Fri, 13 Aug 1999 22:28:56 -0700 (PDT) From: Mike Meyer To: stable@freebsd.org Subject: Random disk read problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been shuffling some data around in preperation for archiving it. Being a bit paranoid, I tend to md5 sum the stuff at both ends, and then verify the checksums. I'm getting random differences. I.e. - the diff of the md5 sums will turn up a file or two that are different. Running diff or cmp on them by hand - and they're the same. Likewise, running md5 on them by hand turns up correct sums. This worries me. I'm running an older version of 3.2-stable on a SuperMicro motherboard with 256Meg of ram and a Seagate ST39173W SCSI drive. Is this something that udpating the OS might fix, or am I seeing evidence of hardware problems (but I'm not seeing anything in syslog!), or possibly bugs in both diff and md5? Help appreciated - and wanted, ; Sat, 14 Aug 1999 02:31:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id LAA23169; Sat, 14 Aug 1999 11:25:53 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id LAA53789; Sat, 14 Aug 1999 11:07:00 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908140907.LAA53789@yedi.iaf.nl> Subject: Re: On freezes in 3.2-Stable (fwd) In-Reply-To: <199908140046.RAA02542@gndrsh.aac.dev.com> from "Rodney W. Grimes" at "Aug 13, 1999 5:46: 1 pm" To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Sat, 14 Aug 1999 11:07:00 +0200 (CEST) Cc: mike@smith.net.au, freebsd-stable@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Rodney W. Grimes wrote ... > > Er. The Intel AD450NX has 32 DIMM sockets. Unless someone starts > > making 2-chip DIMMs, I don't see how you would run 8GB in this box (and > > I have seen it being done under other operating systems). > > The Intel AD450NX in in the class ``supporting 8 sockets or more''. > The Intel AD450NX is in the class ``high dollar server machines''. > > > > > You might want to qualify the issue a little further; specifically with > > regard to "typical memory controllers", logic families and fanout. > > I think I qualified it plenty enough... > > As far as logic families and fanout, well they really don't matter much > with regards to this issue, memory drivers are special, not made with the > same configuration that the logic family is, and thus it's fanout is > quite different. The constant has been 72 for a very long time, since I > started duing mos memory system designs with 54xx/74xx TTL in the 80's > until today with the latest in CMOS and BiCMOS. Yea.. I could design a > supper honking driver that can drive 288 chips in the memory controller, > but then all the RAM chips would have to have larger data drivers to > handle that side of the bus. You could use buffered DIMMs I guess. Not really PC standard stuff though. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 10: 8:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 18FE11520B for ; Sat, 14 Aug 1999 10:08:21 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id KAA05443; Sat, 14 Aug 1999 10:07:45 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199908141707.KAA05443@gndrsh.aac.dev.com> Subject: Re: On freezes in 3.2-Stable (fwd) In-Reply-To: <199908140907.LAA53789@yedi.iaf.nl> from Wilko Bulte at "Aug 14, 1999 11:07:00 am" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sat, 14 Aug 1999 10:07:45 -0700 (PDT) Cc: mike@smith.net.au, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As Rodney W. Grimes wrote ... > > > > Er. The Intel AD450NX has 32 DIMM sockets. Unless someone starts > > > making 2-chip DIMMs, I don't see how you would run 8GB in this box (and > > > I have seen it being done under other operating systems). > > > > The Intel AD450NX in in the class ``supporting 8 sockets or more''. > > The Intel AD450NX is in the class ``high dollar server machines''. > > > > > > > > You might want to qualify the issue a little further; specifically with > > > regard to "typical memory controllers", logic families and fanout. > > > > I think I qualified it plenty enough... > > > > As far as logic families and fanout, well they really don't matter much > > with regards to this issue, memory drivers are special, not made with the > > same configuration that the logic family is, and thus it's fanout is > > quite different. The constant has been 72 for a very long time, since I > > started duing mos memory system designs with 54xx/74xx TTL in the 80's > > until today with the latest in CMOS and BiCMOS. Yea.. I could design a > > supper honking driver that can drive 288 chips in the memory controller, > > but then all the RAM chips would have to have larger data drivers to > > handle that side of the bus. > > You could use buffered DIMMs I guess. Not really PC standard stuff though. If the memory controller was designed to deal with them, or you use faster DRAM's themselves to compensate for the additional delay that buffered DIMMS add. 6nS DRAM'S price difference would probably be more than going from a clone MB to one like the AD450NX that is designed for large memory modules. Also buffered DIMMS usually take care of the address line loading issue, you may still have a problem with the databus drivers in the DRAM chips being able to drive data back to the CPU. Buffering both the data and address lines would push you close to needing 5nS chips. (The address lines see one package pin of loading for each chip in the whole memory array, datalines see one, two or four package pin of loading for each DIMM in the array, dependent on single or double row, normal or low density dimms.) -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 12: 2: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alice.gba.oz.au (gba-254.tmx.com.au [203.9.155.254]) by hub.freebsd.org (Postfix) with SMTP id 095F414BEC for ; Sat, 14 Aug 1999 12:01:54 -0700 (PDT) (envelope-from gjb-freebsd@gba.oz.au) Received: (qmail 21043 invoked by uid 1001); 14 Aug 1999 20:39:11 +1000 Message-ID: <19990814103911.21042.qmail@alice.gba.oz.au> X-Posted-By: GBA-Post 1.03 20-Sep-1998 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Date: Sat, 14 Aug 1999 20:39:10 +1000 From: Greg Black To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Random disk read problems References: In-reply-to: of Fri, 13 Aug 1999 22:28:56 MST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer writes: > I've been shuffling some data around in preperation for archiving > it. Being a bit paranoid, I tend to md5 sum the stuff at both ends, > and then verify the checksums. > > I'm getting random differences. I.e. - the diff of the md5 sums will > turn up a file or two that are different. Running diff or cmp on them > by hand - and they're the same. Likewise, running md5 on them by hand > turns up correct sums. > > This worries me. I'm running an older version of 3.2-stable on a > SuperMicro motherboard with 256Meg of ram and a Seagate ST39173W SCSI > drive. Is this something that udpating the OS might fix, or am I > seeing evidence of hardware problems (but I'm not seeing anything in > syslog!), or possibly bugs in both diff and md5? It's a near certainty that you have bad memory. -- Greg Black -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 12:10: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A1DD614EDC; Sat, 14 Aug 1999 12:10:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 86D2A1CD891; Sat, 14 Aug 1999 12:10:03 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Sat, 14 Aug 1999 12:10:03 -0700 (PDT) From: Kris Kennaway To: Mike Meyer Cc: stable@freebsd.org Subject: Re: Random disk read problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Aug 1999, Mike Meyer wrote: > I'm getting random differences. I.e. - the diff of the md5 sums will > turn up a file or two that are different. Running diff or cmp on them > by hand - and they're the same. Likewise, running md5 on them by hand > turns up correct sums. Are any of the filesystems NFS, or some other weird (non-UFS) or weirdly-mounted filesystem? It could be a bug, or it may in fact be that you have someone on board trying to hide their tracks. Were there any obvious patterns in the binaries which were showing up (e.g. all system binaries, etc)? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 15: 5:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 3B7D914BCC for ; Sat, 14 Aug 1999 15:05:01 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id PAA20793; Sat, 14 Aug 1999 15:07:18 -0700 Received: from da007.inetex.com(139.142.118.22), claiming to be "cwsys.cwsent.com" via SMTP by point.osg.gov.bc.ca, id smtpda20791; Sat Aug 14 15:07:11 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id OAA75747; Sat, 14 Aug 1999 14:04:46 -0700 (PDT) Message-Id: <199908142104.OAA75747@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdO75743; Sat Aug 14 14:04:04 1999 X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 2.2.8-RELEASE X-Sender: cy To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Random disk read problems In-reply-to: Your message of "Fri, 13 Aug 1999 22:28:56 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Aug 1999 14:04:04 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Mike Meye r writes: > I've been shuffling some data around in preperation for archiving > it. Being a bit paranoid, I tend to md5 sum the stuff at both ends, > and then verify the checksums. > > I'm getting random differences. I.e. - the diff of the md5 sums will > turn up a file or two that are different. Running diff or cmp on them > by hand - and they're the same. Likewise, running md5 on them by hand > turns up correct sums. > > This worries me. I'm running an older version of 3.2-stable on a > SuperMicro motherboard with 256Meg of ram and a Seagate ST39173W SCSI > drive. Is this something that udpating the OS might fix, or am I > seeing evidence of hardware problems (but I'm not seeing anything in > syslog!), or possibly bugs in both diff and md5? I had a similar problem with a SCSI Zip drive attached to a 1542CF, primarily when the Zip drive was being used simultaneously while other SCSI devices were using the SCSI bus. In my case, corrupted data was being written to the Zip drive. Replacing the 1542CF with a 2940UW solved the problem. In the mean time I've reinstalled the 1542CF and only attached the Zip drive to it, leaving 2 SCSI disks, a CDROM drive and a 4mm DAT attached to the 2940UW. This configuration has worked for a number of months without problems. I've been told that 1542's do not work well with multi-user/multi-taskin g O/S's. I'm not sure what SCSI controller you're using. Could it be that your controller is corrupting data when it is "very" busy? Other than that, additional information will be needed to diagnose the problem, including a uname -a, dmesg output, and a copy of your kernel config file posted to this list. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 15:14: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id A89BA14DF3 for ; Sat, 14 Aug 1999 15:13:54 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 11Fm46-0006Hv-00 for stable@FreeBSD.ORG; Sat, 14 Aug 1999 18:14:14 -0400 Date: Sat, 14 Aug 1999 18:14:13 -0400 From: Peter Radcliffe To: stable@FreeBSD.ORG Subject: Re: Random disk read problems Message-ID: <19990814181413.A19563@pir.net> Mail-Followup-To: stable@FreeBSD.ORG References: <199908142104.OAA75747@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908142104.OAA75747@cwsys.cwsent.com>; from Cy Schubert - ITSD Open Systems Group on Sat, Aug 14, 1999 at 02:04:04PM -0700 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert probably said: > I've been told that 1542's do not work well with multi-user/multi-taskin > g O/S's. I'm not sure what SCSI controller you're using. Could it be > that your controller is corrupting data when it is "very" busy? I had a couple of small routers/dialup machines built around 486s with a 1542CF (no need for the multi-io card, it drives the floppy to) and FreeBSD (this was around 2.1.* era) and had zero problems with corruption even when they were busy - I hate a tape drive one of them since it doubled as a backup server. This also doesn't explain why the diffs are identical. > Other than that, additional information will be needed to diagnose the > problem, including a uname -a, dmesg output, and a copy of your kernel > config file posted to this list. P. -- pir pir@pir.net pir@shore.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 21:37:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from unix01.voicenet.com (unix01.voicenet.com [209.71.48.250]) by hub.freebsd.org (Postfix) with SMTP id 3EBDA14DA6 for ; Sat, 14 Aug 1999 21:37:34 -0700 (PDT) (envelope-from jpapalia@voicenet.com) Received: (qmail 8140 invoked by uid 4485); 15 Aug 1999 04:35:39 -0000 Date: Sun, 15 Aug 1999 00:35:39 -0400 (EDT) From: John X-Sender: jpapalia@unix01 To: freebsd-stable@freebsd.org Subject: IP's, NIC's, and masquerading in 3.2-Stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I know the first that will happen will be a request for more information, but I'm not sure which information I need, which is why I'm here =) I have two PC's running - a winblowz box, and a FreeBSD box. My FreeBSD box is configured as my gateway, and I have configured masquerading. When using dial-up modem access to my ISP, all goes well. Thing is, I'm now living on campus, and have access to ethernet in my apartment. So, I installed a second ethernet card in my FBSD box. When i set up fxp0 *and* fxp1 in my kernel, and then set up in rc.conf to show both ethernet cards configured, I end up with *neither* card working right - the gateway fails between the two boxes. Questions - how does one correctly configure having two ethernet cards within the same box? how do i define one to allow masquerading between the boxes, while having the other as being either static or dynamic IP addy offa the ethernet hookup? I'm a newbie at ethernetting to the outside world, so any guidance/tutorials that you can point me to would be great. Please just ask if i Need to provide more info. Thanks!!! --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 21:37:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0DFDC14DA6 for ; Sat, 14 Aug 1999 21:37:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA34549; Sat, 14 Aug 1999 22:36:02 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA22431; Sat, 14 Aug 1999 22:36:22 -0600 (MDT) Message-Id: <199908150436.WAA22431@harmony.village.org> To: Cy Schubert - ITSD Open Systems Group Subject: Re: Random disk read problems Cc: Mike Meyer , stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 14 Aug 1999 14:04:04 PDT." <199908142104.OAA75747@cwsys.cwsent.com> References: <199908142104.OAA75747@cwsys.cwsent.com> Date: Sat, 14 Aug 1999 22:36:22 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908142104.OAA75747@cwsys.cwsent.com> Cy Schubert - ITSD Open Systems Group writes: : I've been told that 1542's do not work well with multi-user/multi-taskin : g O/S's. I'm not sure what SCSI controller you're using. Could it be : that your controller is corrupting data when it is "very" busy? That's crap. Pure crap. The 1522's maybe, but not the 1542. They have a good DMA architecture. There may be a bug in the 1542 driver for FreeBSD, but it isn't the fault of the cards. And if there is a bug, I'd like to know how to recreate it so I can fix it... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 22: 3:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 87E8F150ED for ; Sat, 14 Aug 1999 22:03:32 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 509 invoked by uid 100); 15 Aug 1999 05:02:28 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Aug 1999 05:02:28 -0000 Date: Sat, 14 Aug 1999 22:02:28 -0700 (PDT) From: Mike Meyer To: Kris Kennaway Cc: stable@freebsd.org Subject: Re: Random disk read problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Aug 1999, Kris Kennaway wrote: :->> I'm getting random differences. I.e. - the diff of the md5 sums will :->> turn up a file or two that are different. Running diff or cmp on them :->> by hand - and they're the same. Likewise, running md5 on them by hand :->> turns up correct sums. :->Are any of the filesystems NFS, or some other weird (non-UFS) or :->weirdly-mounted filesystem? Most of them were UFS; one was a cd imaged on UFS mounted via vn. :->It could be a bug, or it may in fact be that you have someone on board :->trying to hide their tracks. Were there any obvious patterns in the :->binaries which were showing up (e.g. all system binaries, etc)? If it were those, I'd bevieve it. ; Sat, 14 Aug 1999 22:03:57 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 527 invoked by uid 100); 15 Aug 1999 05:04:17 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Aug 1999 05:04:17 -0000 Date: Sat, 14 Aug 1999 22:04:17 -0700 (PDT) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Random disk read problems In-Reply-To: <19990814103911.21042.qmail@alice.gba.oz.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Aug 1999, Greg Black wrote: :->> I've been shuffling some data around in preperation for archiving :->> it. Being a bit paranoid, I tend to md5 sum the stuff at both ends, :->> and then verify the checksums. :->It's a near certainty that you have bad memory. Nuts. This system has been reliable - anb up most of the time - for the last year, and I haven't seen these problems. Could a power outage have caused the chips to fail? Thanx, ; Sat, 14 Aug 1999 23:21:18 -0700 (PDT) (envelope-from brooks@one-eyed-alien.net) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id XAA11800; Sat, 14 Aug 1999 23:19:07 -0700 (PDT) From: brooks@one-eyed-alien.net X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Sat, 14 Aug 1999 23:19:07 -0700 (PDT) X-Sender: brdavis@orion.ac.hmc.edu To: John Cc: freebsd-stable@FreeBSD.ORG Subject: Re: IP's, NIC's, and masquerading in 3.2-Stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Aug 1999, John wrote: > Questions - > > how does one correctly configure having two ethernet cards > within the same box? With pci cards like the ones with the fxp driver, don't do anything. You don't need to add a second driver (that might even by your problem) because most pci drivers grow automagicaly. > how do i define one to allow masquerading between the boxes, while having > the other as being either static or dynamic IP addy offa the ethernet > hookup? Unfortunatly, I can't help much here. You'll probably want to use natd to do address translation (masquerading). Other then that, it shoudl basicaly work just like before. If you want dynamic addresses for your windows box (or mabey for visitor's laptops) then just install the net/isc-dhcp2 port. The examples in the dhcpd manpage should get you started. -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 23:30:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ares.maths.adelaide.edu.au (Ares.maths.adelaide.edu.au [129.127.44.147]) by hub.freebsd.org (Postfix) with ESMTP id EC82F1519E; Sat, 14 Aug 1999 23:30:24 -0700 (PDT) (envelope-from glewis@ares.maths.adelaide.edu.au) Received: (from glewis@localhost) by ares.maths.adelaide.edu.au (8.9.3/8.9.3) id QAA09941; Sun, 15 Aug 1999 16:03:25 +0930 (CST) (envelope-from glewis) From: Greg Lewis Message-Id: <199908150633.QAA09941@ares.maths.adelaide.edu.au> Subject: Re: SMP and WINE In-Reply-To: <3.0.3.32.19990814230557.00f46c20@pop.interaccess.com> from Ford Prefect at "Aug 14, 1999 11:05:57 pm" To: Ford Prefect Date: Sun, 15 Aug 1999 16:03:25 +0930 (CST) Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A few weeks ago there was a post about WINE not being able to run on an SMP > system, if I recall -current would allow it at that time, but not -stable. > something about sharing data segments between forked proccess I think. I'm > putting together a SMP system and would like to use WINE. I'm wondering if > there have been any changes to -stable in this area, or if there are any > other tricks to get wine running under an SMP kernel. I think that was probably my post :). I've been following the committers list (cvs-all) and haven't seen any of the necessary changes backported to -stable. I believe that Luoqi Chen's vmspace sharing code is necessary for Wine to work under SMP. This was committed to -current April 27th. There have been a couple of related patches since that (as far as I can tell from the commit logs anyway). Does anyone know if there is an intention to backport these changes to -stable or has the code diverged too far for that to be viable? The alternative is to hunt down all the related patches and backport them oneself. I'd love to see Wine working on our SMP server machine, but I'm not about to run -current on it :). -- Greg Lewis glewis@trc.adelaide.edu.au Computing Officer +61 8 8303 5083 Teletraffic Research Centre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 14 23:34:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id B2F4C1519E for ; Sat, 14 Aug 1999 23:34:45 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 1158 invoked by uid 100); 15 Aug 1999 06:32:01 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Aug 1999 06:32:01 -0000 Date: Sat, 14 Aug 1999 23:32:01 -0700 (PDT) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Random disk read problems In-Reply-To: <199908150436.WAA22431@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Aug 1999, Warner Losh wrote: :-> I've been told that 1542's do not work well with multi-user/multi-taskin :-> g O/S's. I'm not sure what SCSI controller you're using. Could it be :-> that your controller is corrupting data when it is "very" busy? I've got two: An Adaptac 7890 Ultra II LVD built into the motherboard that the Seagate disk is on, and an Adaptac 2940UW that the slower devices (CD-ROM, CDR, Jazz) are on. The latter isn't involved in these things - yet, anyway. Bad memory seems like the best bet. The BIOS on the motherboard (a SuperMicro S2DGU) has settings for memory checking that are disabled (it came from the vendor that way, with FreeBSD 2.2.8 installed). Is there any point in turning this on? Anything I can do besides buying another DIMM to plug in to test it? Thanx,