From owner-freebsd-current Sun Jun 20 2:44:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 900ED14C9B for ; Sun, 20 Jun 1999 02:44:07 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id FAA17550; Sun, 20 Jun 1999 05:44:57 -0400 (EDT) Date: Sun, 20 Jun 1999 04:44:53 -0500 (EST) From: Alfred Perlstein To: Chuck Robey Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: laying down tags In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Jun 1999, Chuck Robey wrote: > On Sat, 19 Jun 1999, Jordan K. Hubbard wrote: > > > > I notice that in the last 6 months a change has occurred in how we use > > > our cvs tools, in that there's a great increase in the usage of tags. > > > > And that's a good thing. Even though it adds some file bloat, > > insufficient use of tags has made some painful events in the past more > > painful than they had to be and it restricted other people from doing > > certain types of experimental work. We have been traditionally quite > > tag-shy for the reasons you mention and it limits the full benefits of > > CVS considerably to be so. > > > > > I also notice that while I often want to see the last version of a > > > particular port, I can not remember, ever, needing to see more than > > > that. The ports tree's profusion of 2-4 versions of the same piece of > > > > That's why ports are rarely tagged. > > I should not have brought up the thing about ports in that post, > because while ports' bloat annoys me, it hasn't anything to do with > tags, and probably just served to confuse. > > > In short, I disagree completely with you on the question of tags. > > Would you mind giving one example where not having tags hurt us? > I just want to fix in my head the type of thing, because it seems to me > that the same effect could have been gotten another (cheaper) way, and > one example will probably set me straight. Consider it preventative measures, several major overhauls of the VM, NFS and FS have occurred, had one of these mega commits been proven to be flawed in a major way it would have probably been extremely annoying to deal with, no? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 3:51:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id A6E4914CB4 for ; Sun, 20 Jun 1999 03:51:04 -0700 (PDT) (envelope-from attila@hun.org) Received: from localhost (attila@localhost) by hun.org (8.9.3/8.9.2) with ESMTP id KAA08388; Sun, 20 Jun 1999 10:51:02 GMT (envelope-from attila@hun.org) Date: Sun, 20 Jun 1999 10:51:02 +0000 (GMT) From: attila Reply-To: attila@hun.org To: freebsd-current@freebsd.org Subject: ROOTDEVNAME error in conf/LINT Message-ID: Owner: attila@hun.org Organization: home for unpenitent hackers and anarcho-cryptophreaks Encrypted: NO MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG in /usr/src/sys/i386/conf/LINT options ROOTDEVNAME=\"da0s2e\" must be specified as: options ROOTDEVNAME="da0s2e" else 'make depend' loses the string. w/o quotes it's just an undefined. parser change to eliminate quote requirements for config file defines obviated need for hard quotes in ROOTDEVNAME>. "config" does not grok the errors. am one of those who suffers from lack of politically correct attitude -- I dont do M$lop (refuse to), so why should I worry about slices? never need slices before M$lop.... however, that may change as SCSI disk sizes keep climbing and too large partitions take performance hits. alternative is to change MAXPARTITIONS? to 16? although options ROOTDEVNAME="da0a" does not alleviate necessity of specifying set rootdev=disk1a set currdev=$rootdev in /boot/loader.rc, it's just one more chink; it appears that the only way to beat the final mile is to patch the loader each time I update... attila out... ___ ___ ___ _ __ ___ | _ ) __| \ freeBSD: The Power to Serve! _ __ ___ ____ | _ \__ \ |) | Release 4.0 - The Fast Lane! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 6:33:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id E377514F55 for ; Sun, 20 Jun 1999 06:33:01 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id PAA13042 for freebsd-current@freebsd.org; Sun, 20 Jun 1999 15:33:00 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m10vhXN-000WyUC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Sun, 20 Jun 1999 15:21:29 +0200 (CEST) Message-ID: <19990620152129.Z180@mips.rhein-neckar.de> Date: Sun, 20 Jun 1999 15:21:29 +0200 From: Christian Weisgerber To: freebsd-current@freebsd.org Subject: audio-Device gone mute Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My audio-Device just seems to have gone mute. (I was fiddling around with "tosha -o - | pcmplay -" at the time.) Various attempts to produce sounds with pcmplay, mpg123, and cat >/dev/audio now remain silent. According to aumix, the mixer state is okay. Conf: 4.0-CURRENT (May 29), ES1370 (Soundblaster PCI 64) with pcm(4). mpg123 always reports "[0:00]", so apparently writes block somewhere. Any idea what has happened, and, more importantly, how can I reset the sound driver other than rebooting? -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de 100+ SF Book Reviews: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 7:36:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 830A314BEC for ; Sun, 20 Jun 1999 07:36:49 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id KAA79169; Sun, 20 Jun 1999 10:36:00 -0400 (EDT) Date: Sun, 20 Jun 1999 10:36:00 -0400 (EDT) From: Chuck Robey To: Alfred Perlstein Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: laying down tags In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Jun 1999, Alfred Perlstein wrote: > > > In short, I disagree completely with you on the question of tags. > > > > Would you mind giving one example where not having tags hurt us? > > I just want to fix in my head the type of thing, because it seems to me > > that the same effect could have been gotten another (cheaper) way, and > > one example will probably set me straight. > > Consider it preventative measures, several major overhauls of the > VM, NFS and FS have occurred, had one of these mega commits been > proven to be flawed in a major way it would have probably been > extremely annoying to deal with, no? Maybe I'm wrong, it seemed to me I could merely note the time of that mega-commit (the one I woulc be bothered by) and ask cvs to roll back the clock to that time. Zero cost in space to do this. > > -Alfred > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 7:57:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 687A314FA0 for ; Sun, 20 Jun 1999 07:57:24 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id QAA29227 for freebsd-current@FreeBSD.ORG; Sun, 20 Jun 1999 16:57:23 +0200 (CEST) (envelope-from olli) Date: Sun, 20 Jun 1999 16:57:23 +0200 (CEST) From: Oliver Fromme Message-Id: <199906201457.QAA29227@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: audio-Device gone mute Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote in list.freebsd-current: > My audio-Device just seems to have gone mute. (I was fiddling around > with "tosha -o - | pcmplay -" at the time.) Various attempts to produce > sounds with pcmplay, mpg123, and cat >/dev/audio now remain silent. > According to aumix, the mixer state is okay. > > Conf: 4.0-CURRENT (May 29), ES1370 (Soundblaster PCI 64) with pcm(4). > > mpg123 always reports "[0:00]", so apparently writes block somewhere. > Any idea what has happened, and, more importantly, how can I reset the > sound driver other than rebooting? Did you check (with fstat or lsof) if there's still another process which has the audio device open? (Maybe some pcmplay process gone wild... Although in that case it shouldn't block, but rather print "device busy" or something like that.) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 10:41:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id E2BEF14F05 for ; Sun, 20 Jun 1999 10:41:46 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id TAA28690 for freebsd-current@freebsd.org; Sun, 20 Jun 1999 19:41:45 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m10vlFF-000WyXC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Sun, 20 Jun 1999 19:19:01 +0200 (CEST) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: audio-Device gone mute Date: 20 Jun 1999 19:18:58 +0200 Message-ID: <7kj7q2$qoo$1@mips.rhein-neckar.de> References: <199906201457.QAA29227@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > Did you check (with fstat or lsof) if there's still > another process which has the audio device open? Yes I did, and no there isn't. > (Maybe some pcmplay process gone wild... Although > in that case it shouldn't block, but rather print > "device busy" or something like that.) Well, the blocking thing is peculiar. "buffer -S1024 /dev/audio" writes 120kB into /dev/audio, then it blocks. (buffer was the first thing that came to mind that can output how much data it has copied.) When I call it again, it blocks immediately. Now, if I start mpg123 and subsequently call buffer again, I can again write 120kB to /dev/audio before it blocks. So mpg123 seems to perform some kind of partial reset. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de >H Deutsche Transhumanismus-Mailingliste echo 'subscribe trans-de' | mail majordomo@lists.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 11:33:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles514.castles.com [208.214.165.78]) by hub.freebsd.org (Postfix) with ESMTP id 751F114C17 for ; Sun, 20 Jun 1999 11:33:27 -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 LAA06064; Sun, 20 Jun 1999 11:30:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906201830.LAA06064@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: attila@hun.org Cc: freebsd-current@freebsd.org Subject: Re: ROOTDEVNAME error in conf/LINT In-reply-to: Your message of "Sun, 20 Jun 1999 10:51:02 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Jun 1999 11:30:23 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > am one of those who suffers from lack of politically correct > attitude -- I dont do M$lop (refuse to), so why should I > worry about slices? never need slices before M$lop.... however, > that may change as SCSI disk sizes keep climbing and too large > partitions take performance hits. Has nothing to do with Microsoft. Has everything to do with correct disk layout. Must use slice entries for system disks likely to be shared with other operating systems. Should use "truly dedicated" disk layout for non-shared disks. Defect in libdisk prevents this. Fix libdisk. Become hero. -- \\ 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-current" in the body of the message From owner-freebsd-current Sun Jun 20 12:36:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix7.ix.netcom.com (dfw-ix7.ix.netcom.com [206.214.98.7]) by hub.freebsd.org (Postfix) with ESMTP id A08E214BEA for ; Sun, 20 Jun 1999 12:36:32 -0700 (PDT) (envelope-from spork@narcissus.net) Received: (from smap@localhost) by dfw-ix7.ix.netcom.com (8.8.4/8.8.4) id OAA21501 for ; Sun, 20 Jun 1999 14:36:30 -0500 (CDT) Received: from nyc-ny63-18.ix.netcom.com(209.109.224.82) by dfw-ix7.ix.netcom.com via smap (V1.3) id rma021494; Sun Jun 20 14:36:20 1999 Date: Sun, 20 Jun 1999 15:34:57 -0400 (EDT) From: Spike X-Sender: spork@nyc-ny63-18.ix.netcom.com1011 Reply-To: sporkl@ix.netcom.com To: freebsd-current@freebsd.org Subject: Patches to LPD Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-128825567-929906504=:2600" Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-128825567-929906504=:2600 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Included for review are two patches against -current's lpd. The first adds a new flag to lpd ("-s") which will cause lpd not to bind to the TCP printer port. The second patch updates the man page to reflect the changes. These are the first patches I've submitted, so if I've messed them up please tell me how to fix them. Thanks. --Spike Gronim sporkl@ix.netcom.com --0-128825567-929906504=:2600 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=lpd-patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=lpd-patch KioqIC4vbHBkLmMJU3VuIEp1biAyMCAxNToxNDo0MyAxOTk5DQotLS0gLi9s cGQtbmV3LmMJU3VuIEp1biAyMCAxNToxNjoxMiAxOTk5DQoqKioqKioqKioq KioqKioNCioqKiAxMDQsMTA5ICoqKioNCi0tLSAxMDQsMTEwIC0tLS0NCiAg I2luY2x1ZGUgImV4dGVybi5oIg0KICANCiAgaW50CWxmbGFnOwkJCQkvKiBs b2cgcmVxdWVzdHMgZmxhZyAqLw0KKyBpbnQgICAgIHNmbGFnOyAgICAgICAg ICAgICAgICAgICAgICAgICAgLyogZG8gbm90IGJpbmQgdG8gdGNwIGZsYWcu ICovDQogIGludAlmcm9tX3JlbW90ZTsJCQkvKiBmcm9tIHJlbW90ZSBzb2Nr ZXQgKi8NCiAgDQogIGludAkJICBtYWluIF9fUCgoaW50LCBjaGFyICoqKSk7 DQoqKioqKioqKioqKioqKioNCioqKiAxNDQsMTUwICoqKioNCiAgCQllcnJ4 KEVYX05PUEVSTSwibXVzdCBydW4gYXMgcm9vdCIpOw0KICANCiAgCWVycnMg PSAwOw0KISAJd2hpbGUgKChpID0gZ2V0b3B0KGFyZ2MsIGFyZ3YsICJkbCIp KSAhPSAtMSkNCiAgCQlzd2l0Y2ggKGkpIHsNCiAgCQljYXNlICdkJzoNCiAg CQkJb3B0aW9ucyB8PSBTT19ERUJVRzsNCi0tLSAxNDUsMTUxIC0tLS0NCiAg CQllcnJ4KEVYX05PUEVSTSwibXVzdCBydW4gYXMgcm9vdCIpOw0KICANCiAg CWVycnMgPSAwOw0KISAJd2hpbGUgKChpID0gZ2V0b3B0KGFyZ2MsIGFyZ3Ys ICJkbHMiKSkgIT0gLTEpDQogIAkJc3dpdGNoIChpKSB7DQogIAkJY2FzZSAn ZCc6DQogIAkJCW9wdGlvbnMgfD0gU09fREVCVUc7DQoqKioqKioqKioqKioq KioNCioqKiAxNTIsMTU3ICoqKioNCi0tLSAxNTMsMTYxIC0tLS0NCiAgCQlj YXNlICdsJzoNCiAgCQkJbGZsYWcrKzsNCiAgCQkJYnJlYWs7DQorIAkJY2Fz ZSAncyc6DQorIAkJICAgICAgICBzZmxhZysrOw0KKyAJCQlicmVhazsNCiAg CQlkZWZhdWx0Og0KICAJCQllcnJzKys7DQogIAkJfQ0KKioqKioqKioqKioq KioqDQoqKiogMjc3LDI5OSAqKioqDQogIAlzaWdwcm9jbWFzayhTSUdfU0VU TUFTSywgJm9tYXNrLCAoc2lnc2V0X3QgKikwKTsNCiAgCUZEX1pFUk8oJmRl ZnJlYWRmZHMpOw0KICAJRkRfU0VUKGZ1bml4LCAmZGVmcmVhZGZkcyk7DQoh IAlsaXN0ZW4oZnVuaXgsIDUpOw0KISAJZmluZXQgPSBzb2NrZXQoQUZfSU5F VCwgU09DS19TVFJFQU0sIDApOw0KISAJaWYgKGZpbmV0ID49IDApIHsNCiEg CQlpZiAob3B0aW9ucyAmIFNPX0RFQlVHKQ0KISAJCQlpZiAoc2V0c29ja29w dChmaW5ldCwgU09MX1NPQ0tFVCwgU09fREVCVUcsIDAsIDApIDwgMCkgew0K ISAJCQkJc3lzbG9nKExPR19FUlIsICJzZXRzb2Nrb3B0IChTT19ERUJVRyk6 ICVtIik7DQohIAkJCQltY2xlYW51cCgwKTsNCiEgCQkJfQ0KISAJCW1lbXNl dCgmc2luLCAwLCBzaXplb2Yoc2luKSk7DQohIAkJc2luLnNpbl9mYW1pbHkg PSBBRl9JTkVUOw0KISAJCXNpbi5zaW5fcG9ydCA9IHNwLT5zX3BvcnQ7DQoh IAkJaWYgKGJpbmQoZmluZXQsIChzdHJ1Y3Qgc29ja2FkZHIgKikmc2luLCBz aXplb2Yoc2luKSkgPCAwKSB7DQohIAkJCXN5c2xvZyhMT0dfRVJSLCAiYmlu ZDogJW0iKTsNCiEgCQkJbWNsZWFudXAoMCk7DQohIAkJfQ0KISAJCUZEX1NF VChmaW5ldCwgJmRlZnJlYWRmZHMpOw0KISAJCWxpc3RlbihmaW5ldCwgNSk7 DQogIAl9DQogIAkvKg0KICAJICogTWFpbiBsb29wOiBhY2NlcHQsIGRvIGEg cmVxdWVzdCwgY29udGludWUuDQotLS0gMjgxLDMwNSAtLS0tDQogIAlzaWdw cm9jbWFzayhTSUdfU0VUTUFTSywgJm9tYXNrLCAoc2lnc2V0X3QgKikwKTsN CiAgCUZEX1pFUk8oJmRlZnJlYWRmZHMpOw0KICAJRkRfU0VUKGZ1bml4LCAm ZGVmcmVhZGZkcyk7DQohIAlsaXN0ZW4oZnVuaXgsIDUpOwkNCiEgCWlmIChz ZmxhZyA9PSAwKSB7DQohIAkgICAgZmluZXQgPSBzb2NrZXQoQUZfSU5FVCwg U09DS19TVFJFQU0sIDApOw0KISAJICAgIGlmIChmaW5ldCA+PSAwKSB7DQoh IAkgICAgICAgCSAgICBpZiAob3B0aW9ucyAmIFNPX0RFQlVHKQ0KISAJCSAg ICAgICAgICAgIGlmIChzZXRzb2Nrb3B0KGZpbmV0LCBTT0xfU09DS0VULCBT T19ERUJVRywgMCwgMCkgPCAwKSB7DQohIAkJCSAgICAgICAgICAgIHN5c2xv ZyhMT0dfRVJSLCAic2V0c29ja29wdCAoU09fREVCVUcpOiAlbSIpOw0KISAJ CQkJICAgIG1jbGVhbnVwKDApOw0KISAJCQkgICAgfQ0KISAJCSAgICBtZW1z ZXQoJnNpbiwgMCwgc2l6ZW9mKHNpbikpOw0KISAJCSAgICBzaW4uc2luX2Zh bWlseSA9IEFGX0lORVQ7DQohIAkJICAgIHNpbi5zaW5fcG9ydCA9IHNwLT5z X3BvcnQ7DQohIAkJICAgIGlmIChiaW5kKGZpbmV0LCAoc3RydWN0IHNvY2th ZGRyICopJnNpbiwgc2l6ZW9mKHNpbikpIDwgMCkgew0KISAJCSAgICAgICAg ICAgIHN5c2xvZyhMT0dfRVJSLCAiYmluZDogJW0iKTsNCiEgCQkgICAgICAg ICAgICBtY2xlYW51cCgwKTsNCiEgCQkgICAgfQ0KISAJCSAgICBGRF9TRVQo ZmluZXQsICZkZWZyZWFkZmRzKTsNCiEgCQkgICAgbGlzdGVuKGZpbmV0LCA1 KTsNCiEgCSAgICB9DQogIAl9DQogIAkvKg0KICAJICogTWFpbiBsb29wOiBh Y2NlcHQsIGRvIGEgcmVxdWVzdCwgY29udGludWUuDQoqKioqKioqKioqKioq KioNCioqKiAzMTgsMzI0ICoqKioNCiAgCQkJZG9tYWluID0gQUZfVU5JWCwg ZnJvbWxlbiA9IHNpemVvZihmcm9tdW5peCk7DQogIAkJCXMgPSBhY2NlcHQo ZnVuaXgsDQogIAkJCSAgICAoc3RydWN0IHNvY2thZGRyICopJmZyb211bml4 LCAmZnJvbWxlbik7DQohIAkJfSBlbHNlIC8qIGlmIChGRF9JU1NFVChmaW5l dCwgJnJlYWRmZHMpKSAqLyAgew0KICAJCQlkb21haW4gPSBBRl9JTkVULCBm cm9tbGVuID0gc2l6ZW9mKGZyb21pbmV0KTsNCiAgCQkJcyA9IGFjY2VwdChm aW5ldCwNCiAgCQkJICAgIChzdHJ1Y3Qgc29ja2FkZHIgKikmZnJvbWluZXQs ICZmcm9tbGVuKTsNCi0tLSAzMjQsMzMwIC0tLS0NCiAgCQkJZG9tYWluID0g QUZfVU5JWCwgZnJvbWxlbiA9IHNpemVvZihmcm9tdW5peCk7DQogIAkJCXMg PSBhY2NlcHQoZnVuaXgsDQogIAkJCSAgICAoc3RydWN0IHNvY2thZGRyICop JmZyb211bml4LCAmZnJvbWxlbik7DQohIAkJfSBlbHNlIGlmIChzZmxhZyA9 PSAwKSB7DQogIAkJCWRvbWFpbiA9IEFGX0lORVQsIGZyb21sZW4gPSBzaXpl b2YoZnJvbWluZXQpOw0KICAJCQlzID0gYWNjZXB0KGZpbmV0LA0KICAJCQkg ICAgKHN0cnVjdCBzb2NrYWRkciAqKSZmcm9taW5ldCwgJmZyb21sZW4pOw0K KioqKioqKioqKioqKioqDQoqKiogMzMzLDM0NSAqKioqDQogIAkJCWNvbnRp bnVlOw0KICAJCX0NCiAgCQlpZiAoZm9yaygpID09IDApIHsNCiEgCQkJc2ln bmFsKFNJR0NITEQsIFNJR19JR04pOw0KICAJCQlzaWduYWwoU0lHSFVQLCBT SUdfSUdOKTsNCiAgCQkJc2lnbmFsKFNJR0lOVCwgU0lHX0lHTik7DQogIAkJ CXNpZ25hbChTSUdRVUlULCBTSUdfSUdOKTsNCiAgCQkJc2lnbmFsKFNJR1RF Uk0sIFNJR19JR04pOw0KICAJCQkodm9pZCkgY2xvc2UoZnVuaXgpOw0KISAJ CQkodm9pZCkgY2xvc2UoZmluZXQpOw0KICAJCQlkdXAyKHMsIDEpOw0KICAJ CQkodm9pZCkgY2xvc2Uocyk7DQogIAkJCWlmIChkb21haW4gPT0gQUZfSU5F VCkgew0KLS0tIDMzOSwzNTIgLS0tLQ0KICAJCQljb250aW51ZTsNCiAgCQl9 DQogIAkJaWYgKGZvcmsoKSA9PSAwKSB7DQohIAkJICAgICAgIAlzaWduYWwo U0lHQ0hMRCwgU0lHX0lHTik7DQogIAkJCXNpZ25hbChTSUdIVVAsIFNJR19J R04pOw0KICAJCQlzaWduYWwoU0lHSU5ULCBTSUdfSUdOKTsNCiAgCQkJc2ln bmFsKFNJR1FVSVQsIFNJR19JR04pOw0KICAJCQlzaWduYWwoU0lHVEVSTSwg U0lHX0lHTik7DQogIAkJCSh2b2lkKSBjbG9zZShmdW5peCk7DQohIAkJCWlm IChzZmxhZyA9PSAwKQ0KISAJCQkgICAgICAgICh2b2lkKSBjbG9zZShmaW5l dCk7DQogIAkJCWR1cDIocywgMSk7DQogIAkJCSh2b2lkKSBjbG9zZShzKTsN CiAgCQkJaWYgKGRvbWFpbiA9PSBBRl9JTkVUKSB7DQoqKioqKioqKioqKioq KioNCioqKiA2MjksNjM0ICoqKioNCiAgc3RhdGljIHZvaWQNCiAgdXNhZ2Uo KQ0KICB7DQohIAlmcHJpbnRmKHN0ZGVyciwgInVzYWdlOiBscGQgWy1kbF0g W3BvcnQjXVxuIik7DQogIAlleGl0KEVYX1VTQUdFKTsNCiAgfQ0KLS0tIDYz Niw2NDEgLS0tLQ0KICBzdGF0aWMgdm9pZA0KICB1c2FnZSgpDQogIHsNCiEg CWZwcmludGYoc3RkZXJyLCAidXNhZ2U6IGxwZCBbLWRsc10gW3BvcnQjXVxu Iik7DQogIAlleGl0KEVYX1VTQUdFKTsNCiAgfQ0K --0-128825567-929906504=:2600 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=lpd-man-patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=lpd-man-patch KioqIC4vbHBkLjgub3JpZwlTdW4gSnVuIDIwIDExOjAwOjQwIDE5OTkNCi0t LSAuL2xwZC44CVN1biBKdW4gMjAgMTA6NTk6MzQgMTk5OQ0KKioqKioqKioq KioqKioqDQoqKiogMzksNDUgKioqKg0KICAuTmQgbGluZSBwcmludGVyIHNw b29sZXIgZGFlbW9uDQogIC5TaCBTWU5PUFNJUw0KICAuTm0gbHBkDQohIC5P cCBGbCBkbA0KICAuT3AgQXIgcG9ydCMNCiAgLlNoIERFU0NSSVBUSU9ODQog IC5ObSBMcGQNCi0tLSAzOSw0NSAtLS0tDQogIC5OZCBsaW5lIHByaW50ZXIg c3Bvb2xlciBkYWVtb24NCiAgLlNoIFNZTk9QU0lTDQogIC5ObSBscGQNCiEg Lk9wIEZsIGRscw0KICAuT3AgQXIgcG9ydCMNCiAgLlNoIERFU0NSSVBUSU9O DQogIC5ObSBMcGQNCioqKioqKioqKioqKioqKg0KKioqIDcyLDc3ICoqKioN Ci0tLSA3Miw4MyAtLS0tDQogIC5ObQ0KICB0byBsb2cgdmFsaWQgcmVxdWVz dHMgcmVjZWl2ZWQgZnJvbSB0aGUgbmV0d29yay4gVGhpcyBjYW4gYmUgdXNl ZnVsDQogIGZvciBkZWJ1Z2dpbmcgcHVycG9zZXMuDQorIC5JdCBGbCBzDQor IFRoZQ0KKyAuRmwgcw0KKyBmbGFnIGNhdXNlcw0KKyAuTm0NCisgbm90IHRv IGJpbmQgdG8gYSBUQ1Agc29ja2V0LiBUaGlzIGlzIHNpbWlsYXIgdG8gdGhl ICItcyIgZmxhZyB0byBzeXNsb2dkLg0KICAuSXQgQXIgInBvcnQjIg0KICBU aGUgSW50ZXJuZXQgcG9ydCBudW1iZXIgdXNlZCB0byByZW5kZXp2b3VzDQog IHdpdGggb3RoZXIgcHJvY2Vzc2VzIGlzIG5vcm1hbGx5IG9idGFpbmVkIHdp dGgNCg== --0-128825567-929906504=:2600-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 13:45:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id A085A14C23 for ; Sun, 20 Jun 1999 13:45:23 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id WAA07067 for freebsd-current@FreeBSD.ORG; Sun, 20 Jun 1999 22:45:22 +0200 (CEST) (envelope-from olli) Date: Sun, 20 Jun 1999 22:45:22 +0200 (CEST) From: Oliver Fromme Message-Id: <199906202045.WAA07067@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: audio-Device gone mute Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote in list.freebsd-current: > Well, the blocking thing is peculiar. > > "buffer -S1024 /dev/audio" writes 120kB into /dev/audio, > then it blocks. (buffer was the first thing that came to mind that can > output how much data it has copied.) (dd can do it, too.) > When I call it again, it blocks > immediately. Now, if I start mpg123 and subsequently call buffer again, > I can again write 120kB to /dev/audio before it blocks. So mpg123 seems > to perform some kind of partial reset. This sounds like a bug in the device driver. If I'm not mistaken, it uses a pair of 64 Kb DMA buffers which are used alternating ("double buffering" -- data is written to one buffer while the other one performs audio playback). So, in your case the playback isn't initiated for some reason, so it is just filling those two buffers and then blocks because the first buffer isn't available again. Sorry, but I'm not that familiar with the sound driver code, so someone else will have to look into this... Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 16:15:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id E6E8F14D1C for ; Sun, 20 Jun 1999 16:15:39 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA03124; Mon, 21 Jun 1999 09:15:25 +1000 Date: Mon, 21 Jun 1999 09:15:25 +1000 From: Bruce Evans Message-Id: <199906202315.JAA03124@godzilla.zeta.org.au> To: attila@hun.org, freebsd-current@FreeBSD.ORG Subject: Re: ROOTDEVNAME error in conf/LINT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > in /usr/src/sys/i386/conf/LINT > >options ROOTDEVNAME=\"da0s2e\" > > must be specified as: > >options ROOTDEVNAME="da0s2e" > > else 'make depend' loses the string. w/o quotes it's just an > undefined. parser change to eliminate quote requirements > for config file defines obviated need for hard quotes in > ROOTDEVNAME>. "config" does not grok the errors. No. At least in -current, the former works, but latter gives no quotes in opt_rootdevname.h and thus a syntax error in autoconf.c. > am one of those who suffers from lack of politically correct > attitude -- I dont do M$lop (refuse to), so why should I > worry about slices? never need slices before M$lop.... however, > that may change as SCSI disk sizes keep climbing and too large > partitions take performance hits. > > alternative is to change MAXPARTITIONS? to 16? One reason is that the slice data format is better. It doesn't have arbitrary limits like 8 or 16 (it's essentially a linked list). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 16:47:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 8B59414D8D; Sun, 20 Jun 1999 16:47:33 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA06571; Mon, 21 Jun 1999 09:17:35 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA45273; Mon, 21 Jun 1999 09:17:42 +0930 (CST) Date: Mon, 21 Jun 1999 09:17:42 +0930 From: Greg Lehey To: Wes Peters Cc: FreeBSD current users , FreeBSD Hackers Subject: Re: Remote serial gdb--status? Message-ID: <19990621091742.U6820@freebie.lemis.com> References: <19990618114450.Q9893@freebie.lemis.com> <376AA1E6.F529ED99@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <376AA1E6.F529ED99@softweyr.com>; from Wes Peters on Fri, Jun 18, 1999 at 01:45:42PM -0600 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 18 June 1999 at 13:45:42 -0600, Wes Peters wrote: > Greg Lehey wrote: >> >> I've been away from work for several weeks, and I now find that I can >> no longer start remote serial gdb. I am using sio0 on the debugged >> machine side, and sio1 on the debugging machine side. Here are the >> relevant dmesg outputs: >> >> panic (debugged machine): >> >> sio0: system console >> sio0: gdb debugging port >> ... >> sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 >> sio0: type 16550A >> >> freebie (debugging machine): >> >> sio1 at port 0x2f8-0x2ff irq 3 on isa0 >> sio1: type 16550A >> sio1: interrupting at irq 3 >> >> I can communicate fine using cu, and a breakout box shows all modem >> signals asserte (DCD, DTR, DSR, RTS, CTS). When I go into remote >> debug on panic, RxD flashes, and when freebie tries to attach to >> panic, TxD flashes, so I'm obviously addressing the correct ports. >> I've checked the bit rate and configuration of the ports before going >> into debug, and they look right (9600 bps, cs8, -istrip, -parenb). I >> don't know what else to look for. Any ideas? > > I think you need flags 0x50 (instead of 0x90) on panic. From sio(4): > > Meaning of flags: > ... > 0x00010 device is potential system console > 0x00020 device is forced to become system console > 0x00040 device is reserved for low-level IO (e. g. for remote > kernel debugging) > ... In fact, it was all OK. The serial port seems to be flaky. It works OK at 9600 bps, but drops characters at 38400. I'm still investigating whether this is hardware or software: it seems to work fine in normal mode, but when it's in serial debug mode it can often drop two characters at a time, and there's no overrun indication. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 17: 1:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 532ED14F09 for ; Sun, 20 Jun 1999 17:01:53 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id JAA22133; Mon, 21 Jun 1999 09:31:23 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990621093123:337=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Mon, 21 Jun 1999 09:31:23 +0930 (CST) From: "Daniel O'Connor" To: Chuck Robey Subject: Re: laying down tags Cc: freebsd-current@FreeBSD.ORG, "Jordan K. Hubbard" , Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990621093123:337=_ Content-Type: text/plain; charset=us-ascii On 20-Jun-99 Chuck Robey wrote: > > Consider it preventative measures, several major overhauls of the > > VM, NFS and FS have occurred, had one of these mega commits been > > proven to be flawed in a major way it would have probably been > > extremely annoying to deal with, no? > Maybe I'm wrong, it seemed to me I could merely note the time of that > mega-commit (the one I woulc be bothered by) and ask cvs to roll back > the clock to that time. Zero cost in space to do this. Yes, but if I'm trying to track down a bug and I want to roll back my tree to before a certain commit a tag is much easier to deal with than a date.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990621093123:337=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN22A01bYW/HEoF9pAQHrPQP/f73Q8S1JM6EyH+0hpJZyoj2C8jXPxsPo rAv6t198DFxYLBeGgBUp204f8/VpdihBQfp9J0dNOwJaiKkCZn7x3TWiWltfwHq3 sfwHDUnGwJQCayl7VUIk6fn5HVpY/cFUwK3cqyFDcR8C7gQxl5LHkSXR7/SZIr3y hJQx4ld6La0= =/vAn -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990621093123:337=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 17:24:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id DBEB214F09 for ; Sun, 20 Jun 1999 17:24:02 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id SAA00602; Sun, 20 Jun 1999 18:13:19 -0600 (MDT) Date: Sun, 20 Jun 1999 18:13:19 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199906210013.SAA00602@narnia.plutotech.com> To: Greg Lehey Cc: current@FreeBSD.org Subject: Re: Remote serial gdb--status? X-Newsgroups: pluto.freebsd.current In-Reply-To: <19990618114450.Q9893@freebie.lemis.com> <376AA1E6.F529ED99@softweyr.com> <19990621091742.U6820@freebie.lemis.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990621091742.U6820@freebie.lemis.com> you wrote: > > In fact, it was all OK. The serial port seems to be flaky. It works > OK at 9600 bps, but drops characters at 38400. I'm still > investigating whether this is hardware or software: it seems to work > fine in normal mode, but when it's in serial debug mode it can often > drop two characters at a time, and there's no overrun indication. It looks like isa/sio.c still won't allow you to set a port as both a low-level console and the gdb port. I could not get remote gdb to work correctly after the sio probe without designating the port for low-level console I/O. Now that I've done that, I can't debug at 115200 any more. 38400 seems to work for me, but that is with only minimal testing. Who broke remote debugging in sio? This is a critical tool we can't afford to have broken... 8-( -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 17:47:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 6DAF91525A for ; Sun, 20 Jun 1999 17:47:29 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA06750; Mon, 21 Jun 1999 10:17:30 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA45473; Mon, 21 Jun 1999 10:17:36 +0930 (CST) Date: Mon, 21 Jun 1999 10:17:36 +0930 From: Greg Lehey To: "Justin T. Gibbs" Cc: current@FreeBSD.org Subject: Re: Remote serial gdb--status? Message-ID: <19990621101736.Y6820@freebie.lemis.com> References: <19990618114450.Q9893@freebie.lemis.com> <199906210013.SAA00602@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906210013.SAA00602@narnia.plutotech.com>; from Justin T. Gibbs on Sun, Jun 20, 1999 at 06:13:19PM -0600 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 20 June 1999 at 18:13:19 -0600, Justin T. Gibbs wrote: > In article <19990621091742.U6820@freebie.lemis.com> you wrote: >> >> In fact, it was all OK. The serial port seems to be flaky. It works >> OK at 9600 bps, but drops characters at 38400. I'm still >> investigating whether this is hardware or software: it seems to work >> fine in normal mode, but when it's in serial debug mode it can often >> drop two characters at a time, and there's no overrun indication. > > It looks like isa/sio.c still won't allow you to set a port as both > a low-level console and the gdb port. I could not get remote gdb > to work correctly after the sio probe without designating the port > for low-level console I/O. Now that I've done that, I can't debug > at 115200 any more. Interesting. I think there must be something wrong with the interface Are some interrupts getting through, for example? The debugging interface uses programmed I/O, but when characters get lost, there should be an overrun indication, and I test for that and find none. Here's an example of what I'm logging: Correct (9600 bps): +$Hc-1#09 +$qOffsets#4b +$?#3f +$Hg0#df +$g#67 +$mc027e0e4,4#f7 +$mc026b458,8#cf +$mc026b460,8#c8 +$mc026b468,8#d0 +$mc026b470,8#c9 +$mc027e0e4,4#f7 +$mc026b458,8#cf +$mc026b460,8#c8 +$mc026b468,8#d0 +$mc026b470,8#c9 +$mc0215df8,1#f7 +$mc0215df8,1#f7 +$mc0215df9,1#f8 +$mc0215dfa,1#20 +$mc0215dfb,1#21 +$mc0215dfc,1#22 +$mc0215dfb,1#21 +$mc0215dfb,1#21 +$mc0215dfb,1#21 +$mc027e0dc,4#25 +$mc027e0e0,4#f3 +$mc027e0e0,4#f3 +$mc027e108,4#c7 +$mc027e10c,4#f2 +$mc027e100,4#bf +$mc027e104,4#c3 +$mc027e104,4#c3 +$mc027e128,4#c9 +$mc027e12c,4#f4 +$mc027e130,4#c2 +$mc027e120,4#c1 +$mc027e124,4#c5 +$mc027e124,4#c5 +$mc027e144,4#c7 +$mc027e148,4#cb +$mc027e13c,4#f5 +$mc027e140,4#c3 +$mc027e140,4#c3 +$mc027e154,50#f9 +$mc027e14c,4#f6 +$Hc0#db +$c#63 Incorrect (38400 bps): +$Hc-1#09 +$qOffsets#4b +$?#3f +$Hg0#df +$g#67 +$mc027e0e4,4#f7 +$mc026b458,8#cf +$mc0b460,8#c8$mc026b460,8#c8 See this? It corresponds to +$mc026b460,8#c8 in the correct example. It dropped 2 characters in the address, then retried. What doesn't show is that I check for overrun in the status register, and it never shows. You'll see a *lot* of errors of this kind in the stuff below. These two examples were generated from the same input to gdb. +$mc026b468,8#d0 +$mc026b470,8#c9 +$mc027e0e4,4#f7 +$mc026b8,8#cf$mc026b458,8#cf +$mc026b460,8#c8 +$mc026b468,8#d0 +$mc026b470,8#c9 +$mc0215df8#f7$mc0215df8,1#f7 +$mc0215df8,1#f7 +$mc0215df9,1#f8 +$mc0215dfa,1#20 +$mc0215dfb,1#1$mc0215dfb,1#21$mc0215dfb,1#21 +$mc0215dfc,1#22 +$mc0215dfb,1#21 +$mc0215dfb,1#21 +c0215dfb,1#21$mc0215dfb,1#21 +$mc027e0dc,4#25 +$mc027e0e0,4#f3 +$mc027e0e0,4#f3 +$mc7e108,4#c7$mc027e108,4#c7 +$mc027e10c,4#f2 +$mc027e100,4#bf +$mc027e104,4#c3 +$mc02704,4#c3$mc027e104,4#c3 +$mc027e128,4#c9 +$mc027e12c,4#f4 +$mc027e130,4#c2 +$mc027e124#c1$mc027e120,4#c1 +$mc027e124,4#c5 +$mc027e124,4#c5 +$mc027e144,4#c7 +$mc027e148,4b$mc027e148,4#cb$mc027e148,4#cb +$mc027e13c,4#f5 +$mc027e140,4#c3 +$mc027e140,4#c3 +$mc027e154,4#c8 +$mc027e14c,4#f6 +$Hc0#db +$c#63 > 38400 seems to work for me, but that is with only minimal testing. > Who broke remote debugging in sio? This is a critical tool we can't > afford to have broken... 8-( I have had this kind of problem since day one, just sometimes it's better, sometimes it's worse. I think that there may have been some problems with the new version of gdb (4.18), which at least initially had much larger timeouts. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 18:36: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 60C9415170 for ; Sun, 20 Jun 1999 18:36:01 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA92793; Sun, 20 Jun 1999 21:34:57 -0400 (EDT) Date: Sun, 20 Jun 1999 21:34:57 -0400 (EDT) From: Chuck Robey To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG, "Jordan K. Hubbard" , Alfred Perlstein Subject: Re: laying down tags In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Jun 1999, Daniel O'Connor wrote: > > On 20-Jun-99 Chuck Robey wrote: > > > Consider it preventative measures, several major overhauls of the > > > VM, NFS and FS have occurred, had one of these mega commits been > > > proven to be flawed in a major way it would have probably been > > > extremely annoying to deal with, no? > > Maybe I'm wrong, it seemed to me I could merely note the time of that > > mega-commit (the one I woulc be bothered by) and ask cvs to roll back > > the clock to that time. Zero cost in space to do this. > > Yes, but if I'm trying to track down a bug and I want to roll back > my tree to before a certain commit a tag is much easier to deal with > than a date.. I think I know Jordan well enough, he wouldn't have made his statement without there being more behind it. No one would consider that a fair trade, all that huge bloat of the archive, if the effect gained was only an easy way to remember a rollback timestamp. I never saw the use of it in FreeBSD, which probably means we've been lucky. The only really great use of tags I saw, was tagging releases, so that establishes a real solid pointer to each release timestamp. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 18:52:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id E865E14C88 for ; Sun, 20 Jun 1999 18:52:46 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA22100; Mon, 21 Jun 1999 11:52:39 +1000 Date: Mon, 21 Jun 1999 11:52:39 +1000 From: Bruce Evans Message-Id: <199906210152.LAA22100@godzilla.zeta.org.au> To: gibbs@narnia.plutotech.com, grog@lemis.com Subject: Re: Remote serial gdb--status? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It looks like isa/sio.c still won't allow you to set a port as both >a low-level console and the gdb port. I could not get remote gdb >to work correctly after the sio probe without designating the port >for low-level console I/O. Now that I've done that, I can't debug >at 115200 any more. 38400 seems to work for me, but that is with >only minimal testing. Who broke remote debugging in sio? This >is a critical tool we can't afford to have broken... 8-( Designating a port for low-level "console" i/o (flags 0x40) currently makes it unavailable for ordinary console i/o (flags 0x10) and debugging (flags 0x80). I think this is a bug. Go back a couple of versions if you want to use flags (0x40 | 0x80). I think the problem with "high" speeds is caused by the low-level console driver doesn't initialise the UART's (receiver) fifo. The siocn i/o routines are unbuffered, but gdb apparently requires some buffering, and a 16-character fifo apparently provides enough buffering. It's surprising that the unbuffered routines work at all. The output routine busy-waits until everything is sent, so sending large packets would break receiving large packets. To use gdb on a normal port (except while booting), stty the port to the same settings as gdb is using. This annulls the context switching in the siocn i/o routines (they switch the context on every character so that debugging using ddb works evern if the port is being probed, but this doesn't work for gdb since its i/o isn't one character at a time). The sio probe and attach routines should handle the gdb port like they handle the console port. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 19: 3: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id 1D31215283 for ; Sun, 20 Jun 1999 19:02:58 -0700 (PDT) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.2/8.9.1) with SMTP id CAA65750; Mon, 21 Jun 1999 02:03:40 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19990620185538.009714e0@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 20 Jun 1999 18:55:38 -0700 To: Chuck Robey From: "Kurt D. Zeilenga" Subject: Re: laying down tags Cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG, "Jordan K. Hubbard" , Alfred Perlstein In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tags can span time, span branches, and subsets of the repository. A tag may not represent a bulk commit. Tags are associated with specific revisions of files, not some arbitary date. Assuming that the tag represents a bulk commit over a subtree of a single branch of the repository, it may be possible to use a date specifier instead. However, you need to know the exact date required for the operation. On a busy repository, you may have to resort to logs to determine what date to use. Use of date specifiers, especially those gleamed off of local clocks, are error prone. You should take advantage of the power of CVS, use tags! As far as disk space, disk space is cheap. Time isn't. I, for one, would love to see more CVS branches and tag use in FreeBSD. I would love to see committer using private branches. It's much easier for me to test developments if I can just cvs checkout the work in progress. I look forward to the day that I can 'rm /usr/bin/patch'. (note: patch is a lovely, useful tool; but updating source via patches when you have CVS is arcane). Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 19:54: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 8F82814D2D for ; Sun, 20 Jun 1999 19:53:39 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id WAA93143; Sun, 20 Jun 1999 22:52:15 -0400 (EDT) Date: Sun, 20 Jun 1999 22:52:15 -0400 (EDT) From: Chuck Robey To: "Kurt D. Zeilenga" Cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG, "Jordan K. Hubbard" , Alfred Perlstein Subject: Re: laying down tags In-Reply-To: <3.0.5.32.19990620185538.009714e0@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Jun 1999, Kurt D. Zeilenga wrote: > Tags can span time, span branches, and subsets of the repository. > A tag may not represent a bulk commit. Tags are associated with > specific revisions of files, not some arbitary date. > > Assuming that the tag represents a bulk commit over a subtree > of a single branch of the repository, it may be possible to > use a date specifier instead. However, you need to know the > exact date required for the operation. On a busy repository, > you may have to resort to logs to determine what date to > use. Use of date specifiers, especially those gleamed off > of local clocks, are error prone. > > You should take advantage of the power of CVS, use tags! > As far as disk space, disk space is cheap. Time isn't. > > I, for one, would love to see more CVS branches and tag use > in FreeBSD. I would love to see committer using private > branches. It's much easier for me to test developments > if I can just cvs checkout the work in progress. I look > forward to the day that I can 'rm /usr/bin/patch'. > > (note: patch is a lovely, useful tool; but updating > source via patches when you have CVS is arcane). Well, reading over this, it appears (though it's not clear) that you agree that dates can do the job of tags. Since we keep full logs, and the clock is the one on freefall, so dependencies on local clocks are not important, it falls to your argument about disk space. Do you know how many hundreds of kilobytes the last tag cost, or the present size of your archive? I don't know the actual size myself, I just know it takes quite a long time to download it all, so a megabyte wouldn't surprise me, every tag. I won't take it any longer tho, I don't seem to get any support on this. > > Kurt > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 20: 5:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 8768014D2D for ; Sun, 20 Jun 1999 20:05:28 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA24132; Mon, 21 Jun 1999 12:34:31 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990621123431:337=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Mon, 21 Jun 1999 12:34:31 +0930 (CST) From: "Daniel O'Connor" To: Chuck Robey Subject: Re: laying down tags Cc: Alfred Perlstein Cc: Alfred Perlstein , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG, "Kurt D. Zeilenga" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990621123431:337=_ Content-Type: text/plain; charset=us-ascii On 21-Jun-99 Chuck Robey wrote: > how many hundreds of kilobytes the last tag cost, or the present size of > your archive? I don't know the actual size myself, I just know it takes > quite a long time to download it all, so a megabyte wouldn't surprise > me, every tag. Well FYI the current source repository is 500 meg and a checked out copy of 3.0-STABLE is 207 meg. Personally I think 500 meg of space isn't very much anymore so it doesn't bother me. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990621123431:337=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN22rv1bYW/HEoF9pAQEIoAP/WkSBPalwb2tawPBiSM8Ch1JYM5Km9DuW YwksEQAHXDPNmj4HQE4OQ9KqaTMI70QYVjZCQkM4xrqSw7OuWlr/+QkPAbjyjkj1 hMAk9lefrfNJ1/KahbKoZckojs616hP3GKToyi4BOrNXfmbGEgkuxbAtkXWnml96 RNRVKydC+1Y= =RHko -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990621123431:337=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 22:19:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 9826614D7A; Sun, 20 Jun 1999 22:19:06 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA03695; Sun, 20 Jun 1999 23:18:52 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <376DCB36.27D3177A@softweyr.com> Date: Sun, 20 Jun 1999 23:18:46 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: FreeBSD current users , FreeBSD Hackers Subject: Re: Remote serial gdb--status? References: <19990618114450.Q9893@freebie.lemis.com> <376AA1E6.F529ED99@softweyr.com> <19990621091742.U6820@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Friday, 18 June 1999 at 13:45:42 -0600, Wes Peters wrote: > > Greg Lehey wrote: > >> > >> I've been away from work for several weeks, and I now find that I can > >> no longer start remote serial gdb. I am using sio0 on the debugged > >> machine side, and sio1 on the debugging machine side. Here are the > >> relevant dmesg outputs: > >> > >> [...] > > > > I think you need flags 0x50 (instead of 0x90) on panic. From sio(4): > > > > [...] > > In fact, it was all OK. The serial port seems to be flaky. It works > OK at 9600 bps, but drops characters at 38400. I'm still > investigating whether this is hardware or software: it seems to work > fine in normal mode, but when it's in serial debug mode it can often > drop two characters at a time, and there's no overrun indication. Ick. Is this a port on the motherboard? I'd try a known good card if you have one about. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 23:17:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id C39BE14C13 for ; Sun, 20 Jun 1999 23:17:09 -0700 (PDT) (envelope-from attila@hun.org) Received: (from attila@localhost) by hun.org (8.9.3/8.9.2) id GAA10996; Mon, 21 Jun 1999 06:16:47 GMT (envelope-from attila) Date: Mon, 21 Jun 1999 06:16:47 GMT Message-Id: <199906210616.GAA10996@hun.org> From: attila! Reply-To: attila@hun.org To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: ROOTDEVNAME error in conf/LINT Owner: attila@hun.org Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks Mailer: XEmacs V20.4 (see alt.religion.emacs) Encrypted: NO Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From mike@smith.net.au Mon Jun 21 05:41:50 1999 * Subject: Re: ROOTDEVNAME error in conf/LINT * * attila said: * > * > am one of those who suffers from lack of politically correct * > attitude -- I dont do M$lop (refuse to), so why should I * > worry about slices? never need slices before M$lop.... however, * > that may change as SCSI disk sizes keep climbing and too large * > partitions take performance hits. * * Has nothing to do with Microsoft. Has everything to do with correct * disk layout. Must use slice entries for system disks likely to be * shared with other operating systems. Should use "truly dedicated" disk * layout for non-shared disks. Defect in libdisk prevents this. Fix * libdisk. Become hero. * well, maybe it is not exclusively M$lop, but I do not run other operating systems... I'm a real BSD bigot. so I run "dangerously dedicated". start with your definition of virgin -out of the box drives and install the old way. never had to live with the boot sector virus from Redmond... manually create fstab and partitions for a pair of IBM 4.5G UW2 SCSIs: # Device Mountpoint FStype Options Dump Pass# /dev/da0b none swap sw 0 0 /dev/da1b none swap sw 0 0 /dev/da0a / ufs rw 1 1 /dev/da0e /user ufs rw 2 2 /dev/da0f /var ufs rw 2 2 /dev/da0g /usr ufs rw 2 2 /dev/da1e /tmp ufs rw 2 2 /dev/da1f /x1 ufs rw 2 2 /dev/da1g /x2 ufs rw 2 2 /dev/da1h /x3 ufs rw 2 2 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 manually (with a script) create the device entries and wipe out any of the slice entries, wd entries and other non-functionals. the boot/loader in 4.0 wants to start you off with disk1s1; first I modified it manually at load, then added /boot/loader.rc load /kernel set rootdev=disk1a set currdev=$rootdev autoboot and off we go --no problems. so, what is the problem in "libdisk" and how do I "become a hero"? --I'm no hero to my 5 kids anymore... might be nice to be known other than as 'pops', 'gramps', or 'the old fart' for a change. ___ ___ ___ _ __ ___ | _ ) __| \ freeBSD: The Power to Serve! _ __ ___ ____ | _ \__ \ |) | Release 4.0 - The Fast Lane! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 23:24:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id 774B714C13 for ; Sun, 20 Jun 1999 23:24:42 -0700 (PDT) (envelope-from attila@hun.org) Received: (from attila@localhost) by hun.org (8.9.3/8.9.2) id GAA11007; Mon, 21 Jun 1999 06:17:09 GMT (envelope-from attila) Date: Mon, 21 Jun 1999 06:17:09 GMT Message-Id: <199906210617.GAA11007@hun.org> From: attila! Reply-To: attila@hun.org To: Bruce Evans Cc: freebsd-current@freeBSD.org Subject: Re: ROOTDEVNAME error in conf/LINT Owner: attila@hun.org Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks Mailer: XEmacs V20.4 (see alt.religion.emacs) Encrypted: NO Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Jun 1999, Bruce Evans wrote: *Date: Mon, 21 Jun 1999 09:15:25 +1000 *From: Bruce Evans *To: attila@hun.org, freebsd-current@FreeBSD.ORG *Subject: Re: ROOTDEVNAME error in conf/LINT * *> in /usr/src/sys/i386/conf/LINT *> *>options ROOTDEVNAME=\"da0s2e\" *> *> must be specified as: *> *>options ROOTDEVNAME="da0s2e" *> *> else 'make depend' loses the string. w/o quotes it's just an *> undefined. parser change to eliminate quote requirements *> for config file defines obviated need for hard quotes in *> ROOTDEVNAME>. "config" does not grok the errors. * *No. At least in -current, the former works, but latter gives no quotes *in opt_rootdevname.h and thus a syntax error in autoconf.c. * not so... former does does not work in -current as of current build from cvs files through Thu 17 Jun 99 0616 GMT. the back-slashes hose config. the quotes w/o the literal are parsed correctly in last 48 hours.... *> am one of those who suffers from lack of politically correct *> attitude -- I dont do M$lop (refuse to), so why should I *> worry about slices? never need slices before M$lop.... however, *> that may change as SCSI disk sizes keep climbing and too large *> partitions take performance hits. *> *> alternative is to change MAXPARTITIONS? to 16? * *One reason is that the slice data format is better. It doesn't have *arbitrary limits like 8 or 16 (it's essentially a linked list). * are you suggesting a layout for a disk pair such as: --------------- disk 0 da0s1a 100M root da0s1b 250M swap da0s2c 1G /usr da0s3c 1G /usr/src da0s4c 2G /user da0s5c 1G /usr/local/etc/www/data --------------- disk 1 da1s1e 100 M /tmp da1s1b 250 swap da1s2c 1G /usr/X11R6 da1s3c 4G /usr/prod da1s4c 1G /var you say there is no arbitrary limit on slices? but... : #define MAX_SLICES 32 is the data format better? if so, why? using a slice as a partition does not change the organization of the real estate under FFS if the slice then contains a single "partition" --is it easier to translate slice-partition than it is to translate cylinder-sector information for multiple partitions on a non-sliced disk? OTOH, if you muck with the partition limit, in you run into a wall: #ifdef MAXPARTITIONS /* XXX don't depend on disklabel.h */ #if MAXPARTITIONS != 8 /* but check consistency if possible */ #error "inconsistent MAXPARTITIONS" #endif #else #define MAXPARTITIONS 8 #endif and it will need to be patched as it flat overrides changing MAXPARTITIONS in this raises a flag... why the bomb? or was there a major change in FFS with the advent of the slice? [I'll admit to not _seriously_ looking at the FFS partition code since the early 80s... ] the only reason that merits discussion is the "obscene" sizes of the current generation disks -- 25 Gbyte... 30 Gbyte, etc. if you start defining partitions at 8 Gbyte, you have a large number of cylinders-sectors in the current mapping, which also means a larger number of spare tables to be maintained --all of which probably translates into more accessing latency if you are not doing softupdates which is an idea I am not comfortable with. the problem is that the disks will get larger and larger and the disk version of Parkinson's Law will obviously follow. I can remember going into ecstasy when I took shipment of two 680 Mbyte Fujitsu 10" platter Eagles --one for each VAX... cost me about $12,500 each plus $2,000 for the controller. of course, the VAX750 core box was $38,000 OEM at that time... the point is, we lived with no storage; today, I can not live with 9 Gbyte on the desktop... and a 9Gbyte SCSI drive is <$500. and, to really show my antiquity --IBM 30 gal "pony" magnetic drums... or "walking" the washing machine RP4s... one obvious maneuver might be to increase the absolute sector size from the industry standard of 512 --this requires cooperation from the hardware vendors. yeah, sure...! we can fake it, and do, but with less success. attila out... ___ ___ ___ _ __ ___ | _ ) __| \ freeBSD: The Power to Serve! _ __ ___ ____ | _ \__ \ |) | Release 4.0 - The Fast Lane! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 20 23:53:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id 1AAE414C13 for ; Sun, 20 Jun 1999 23:53:26 -0700 (PDT) (envelope-from Kurt@OpenLDAP.Org) Received: from OpenLDAP.Org (localhost [127.0.0.1]) by cantor.boolean.net (8.9.2/8.9.1) with ESMTP id GAA67750; Mon, 21 Jun 1999 06:54:34 GMT (envelope-from Kurt@OpenLDAP.Org) Message-ID: <376DDFC3.2ADEF3F0@OpenLDAP.Org> Date: Sun, 20 Jun 1999 23:46:27 -0700 From: "Kurt D. Zeilenga" Organization: OpenLDAP X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en-GB,en-US,en,de-DE,de MIME-Version: 1.0 To: Chuck Robey Cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG, "Jordan K. Hubbard" , Alfred Perlstein Subject: Re: laying down tags References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > On Sun, 20 Jun 1999, Kurt D. Zeilenga wrote: > > > Tags can span time, span branches, and subsets of the repository. > > A tag may not represent a bulk commit. Tags are associated with > > specific revisions of files, not some arbitary date. > > Well, reading over this, it appears (though it's not clear) that you > agree that dates can do the job of tags. No, I said that under very limited circumstances, data specifiers can do the job of tags. The circumstances are quite limiting and require significant attention to details [ie: scouring of logs for the right date (and tag if commit was on a branch) to use]. If you want to cut down on space used by a tag, only tag subtrees. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 0:29:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 98A9E14ECC for ; Mon, 21 Jun 1999 00:29:43 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA08733; Mon, 21 Jun 1999 17:29:28 +1000 Date: Mon, 21 Jun 1999 17:29:28 +1000 From: Bruce Evans Message-Id: <199906210729.RAA08733@godzilla.zeta.org.au> To: attila@hun.org, bde@zeta.org.au Subject: Re: ROOTDEVNAME error in conf/LINT Cc: freebsd-current@freeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >*No. At least in -current, the former works, but latter gives no quotes >*in opt_rootdevname.h and thus a syntax error in autoconf.c. >* > > not so... > > former does does not work in -current as of current build > from cvs files through Thu 17 Jun 99 0616 GMT. the back-slashes > hose config. the quotes w/o the literal are parsed correctly in > last 48 hours.... That's not what I see here. LINT uses the backslashes, and the part of it that uses ROODEVNAME has been building properly for several months. >*One reason is that the slice data format is better. It doesn't have >*arbitrary limits like 8 or 16 (it's essentially a linked list). >* > > are you suggesting a layout for a disk pair such as: > > --------------- disk 0 > > da0s1a 100M root > da0s1b 250M swap > > da0s2c 1G /usr > da0s3c 1G /usr/src > da0s4c 2G /user > da0s5c 1G /usr/local/etc/www/data Nothing so complicated. Use slices for everything so you don't have any evil nested partitions :->. > you say there is no arbitrary limit on slices? but... > > : #define MAX_SLICES 32 That's not as fundamental as the MAXPARTITIONS limit. Labels really want to live in a single sector. > is the data format better? if so, why? using a slice as a partition > does not change the organization of the real estate under FFS if > the slice then contains a single "partition" --is it easier to > translate slice-partition than it is to translate cylinder-sector > information for multiple partitions on a non-sliced disk? The slice/label data is outside of FFS. Slice (M$ partition) data is distributed as a linked list but label data is packed into an array. Each of these layouts has advantages and disadvantages. Linked lists are easier to expand and harder to translate. > OTOH, if you muck with the partition limit, in > you run into a wall: > > #ifdef MAXPARTITIONS /* XXX don't depend on disklabel.h */ > #if MAXPARTITIONS != 8 /* but check consistency if possible */ > #error "inconsistent MAXPARTITIONS" > #endif > #else > #define MAXPARTITIONS 8 > #endif > > and it will need to be patched as it flat overrides changing > MAXPARTITIONS in this raises a flag... why > the bomb? The openmask bitmaps use type u_char, so MAXPARTITIONS must be <= 8 (== 8 is a bit strong). Larger openmask bitmaps would waste space and not remove the need for the bomb - you would still have to check that MAXPARTITIONS <= NUMBER_OF_BITS_IN_OPENMASK_BITMAP_T. > or was there a major change in FFS with the advent of the slice? > [I'll admit to not _seriously_ looking at the FFS partition code > since the early 80s... ] No. Slice and partition data is mostly outside of FFS. I implemented slices in a layered fashion mainly so that disklabel and newfs, etc. don't need to know about their internals. > the only reason that merits discussion is the "obscene" sizes > of the current generation disks -- 25 Gbyte... 30 Gbyte, etc. > if you start defining partitions at 8 Gbyte, you have a large > number of cylinders-sectors in the current mapping, which also > means a larger number of spare tables to be maintained --all of > which probably translates into more accessing latency if you > are not doing softupdates which is an idea I am not comfortable > with. I think lots of small partitions would cause even more latency unless most of them aren't used most of the time. newfs already uses the weired default geometry of 1 track with 4096 sectors partly to handle yesterday's "obscenely" large disks (4GB...). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 7:46: 5 1999 Delivered-To: freebsd-current@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 3293214F55 for ; Mon, 21 Jun 1999 07:45:58 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:X95tTDpo9+awMWf9XL5MI04HoBv02axq@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id XAA26907; Mon, 21 Jun 1999 23:45:48 +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 XAA25349; Mon, 21 Jun 1999 23:49:58 +0900 (JST) Message-Id: <199906211449.XAA25349@zodiac.mech.utsunomiya-u.ac.jp> To: Bruce Evans Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: siocnprobe() (was: Re: Remote serial gdb--status?) In-reply-to: Your message of "Mon, 21 Jun 1999 11:52:39 +1000." <199906210152.LAA22100@godzilla.zeta.org.au> References: <199906210152.LAA22100@godzilla.zeta.org.au> Date: Mon, 21 Jun 1999 23:49:57 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Different, but related issue. Even when the sio? port is disabled, siocnprobe() will check if it should be initialized for the console or for gdb. The disabled port should not be touched. Attached patch will check the resource value "disabled", and if it is set for the port, siocnprobe() will skip this port. Kazu Index: sio.c =================================================================== RCS file: /src/CVS/src/sys/isa/sio.c,v retrieving revision 1.249 diff -u -r1.249 sio.c --- sio.c 1999/06/20 13:10:09 1.249 +++ sio.c 1999/06/21 14:44:36 @@ -2814,6 +2814,11 @@ for (unit = 0; unit < 16; unit++) { /* XXX need to know how many */ int flags; + int disabled; + if (resource_int_value("sio", unit, "disabled", &disabled) == 0) { + if (disabled) + continue; + } if (resource_int_value("sio", unit, "flags", &flags)) continue; if (COM_CONSOLE(flags) || COM_DEBUGGER(flags)) { >>It looks like isa/sio.c still won't allow you to set a port as both >>a low-level console and the gdb port. I could not get remote gdb >>to work correctly after the sio probe without designating the port >>for low-level console I/O. Now that I've done that, I can't debug >>at 115200 any more. 38400 seems to work for me, but that is with >>only minimal testing. Who broke remote debugging in sio? This >>is a critical tool we can't afford to have broken... 8-( > >Designating a port for low-level "console" i/o (flags 0x40) currently >makes it unavailable for ordinary console i/o (flags 0x10) and >debugging (flags 0x80). I think this is a bug. Go back a couple >of versions if you want to use flags (0x40 | 0x80). > >I think the problem with "high" speeds is caused by the low-level console >driver doesn't initialise the UART's (receiver) fifo. The siocn i/o >routines are unbuffered, but gdb apparently requires some buffering, and a >16-character fifo apparently provides enough buffering. It's surprising >that the unbuffered routines work at all. The output routine busy-waits >until everything is sent, so sending large packets would break receiving >large packets. > >To use gdb on a normal port (except while booting), stty the port to the >same settings as gdb is using. This annulls the context switching in >the siocn i/o routines (they switch the context on every character so >that debugging using ddb works evern if the port is being probed, but >this doesn't work for gdb since its i/o isn't one character at a time). > >The sio probe and attach routines should handle the gdb port like they >handle the console port. > >Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 8:36:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id AEECA15017 for ; Mon, 21 Jun 1999 08:36:38 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id RAA53934; Mon, 21 Jun 1999 17:35:49 +0200 (CEST) (envelope-from des) To: Chuck Robey Cc: "Kurt D. Zeilenga" , "Daniel O'Connor" , freebsd-current@FreeBSD.ORG, "Jordan K. Hubbard" , Alfred Perlstein Subject: Re: laying down tags References: From: Dag-Erling Smorgrav Date: 21 Jun 1999 17:35:48 +0200 In-Reply-To: Chuck Robey's message of "Sun, 20 Jun 1999 22:52:15 -0400 (EDT)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey writes: > Well, reading over this, it appears (though it's not clear) that you > agree that dates can do the job of tags. You can't slide date specs. Now buy yourself some more disk and stop being a big wuss :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 9:47:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mclean3-mail.usae.bah.com (mclean3-mail.usae.bah.com [156.80.5.65]) by hub.freebsd.org (Postfix) with ESMTP id 4457914FB5 for ; Mon, 21 Jun 1999 09:47:12 -0700 (PDT) (envelope-from suo_zhong-gui@bah.com) Received: from bah.com ([156.80.45.213]) by mclean3-mail.usae.bah.com (Netscape Messaging Server 3.61) with ESMTP id AAA21B for ; Mon, 21 Jun 1999 12:45:33 -0400 Message-ID: <376E6C9C.F6FB898C@bah.com> Date: Mon, 21 Jun 1999 12:47:24 -0400 From: "Suo Zhong-Gui" X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 9:58:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 755DC15091 for ; Mon, 21 Jun 1999 09:58:16 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id JAA39200; Mon, 21 Jun 1999 09:58:09 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 21 Jun 1999 09:58:09 -0700 (PDT) From: Doug White To: attila Cc: freebsd-current@FreeBSD.ORG Subject: Re: ROOTDEVNAME error in conf/LINT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Jun 1999, attila wrote: > am one of those who suffers from lack of politically correct > attitude -- I dont do M$lop (refuse to), so why should I > worry about slices? never need slices before M$lop.... however, > that may change as SCSI disk sizes keep climbing and too large > partitions take performance hits. From the support department: Some PC BIOSes won't boot a disk without a MS partition table. Try booting a dangerously dedicated disk on a Phoenix machine and you'll see what I mean. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 10:16:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (unknown [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id A72F3150B9 for ; Mon, 21 Jun 1999 10:16:12 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA05545; Mon, 21 Jun 1999 11:15:54 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA04383; Mon, 21 Jun 1999 11:15:53 -0600 Date: Mon, 21 Jun 1999 11:15:53 -0600 Message-Id: <199906211715.LAA04383@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: laying down tags In-Reply-To: References: <69071.929844133@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I notice that in the last 6 months a change has occurred in how we use > > > our cvs tools, in that there's a great increase in the usage of tags. > > Would you mind giving one example where not having tags hurt us? Sure. When multiple developers are trying to work together as well as track -current, everything has to be done by hand. Case in point is the work that the VM guys want to do. It would be alot easier for both the developers *AND* the testers to share code this way. This also makes it much easier for the developer to 'merge' in changes made to the main branch, rather than having to hand-merge it in everytime, build diffs, and re-distribute them. The other developers then need to back-out the original diffs, re-apply the new diffs, which is alot more work. With CVS, this is done *ONCE* for each change (by CVS), hence the amount of work to help out is much less. What 'cheaper' way could this kind of easy integration be done, short of using the 'magic' branch tags in the FreeBSD CVS version that I don't if anyone has ever used because I don't think anyone knows exactly if it works, and how to make it work. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 10:23: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 09CA21508A for ; Mon, 21 Jun 1999 10:22:47 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id NAA95678; Mon, 21 Jun 1999 13:21:35 -0400 (EDT) Date: Mon, 21 Jun 1999 13:21:35 -0400 (EDT) From: Chuck Robey To: Nate Williams Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: laying down tags In-Reply-To: <199906211715.LAA04383@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Jun 1999, Nate Williams wrote: > > > > I notice that in the last 6 months a change has occurred in how we use > > > > our cvs tools, in that there's a great increase in the usage of tags. > > > > Would you mind giving one example where not having tags hurt us? > > > Sure. When multiple developers are trying to work together as well as > track -current, everything has to be done by hand. Case in point is the > work that the VM guys want to do. It would be alot easier for both the > developers *AND* the testers to share code this way. This also makes it > much easier for the developer to 'merge' in changes made to the main > branch, rather than having to hand-merge it in everytime, build diffs, > and re-distribute them. > > The other developers then need to back-out the original diffs, re-apply > the new diffs, which is alot more work. With CVS, this is done *ONCE* > for each change (by CVS), hence the amount of work to help out is much > less. > > What 'cheaper' way could this kind of easy integration be done, short of > using the 'magic' branch tags in the FreeBSD CVS version that I don't if > anyone has ever used because I don't think anyone knows exactly if it > works, and how to make it work. OK, now I see the light. I've had a lot of people responding, but all the other responses could be covered by the use of date checkouts. This makes sense. I get very stubborn when I'm given (what appears to me to be) a bogus argument, even if the ultimate conclusion is right. The reason given for the conclusion has to hold water. > > > > Nate > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 10:29:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 16E34150C7 for ; Mon, 21 Jun 1999 10:29:33 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id NAA09550 for current@freebsd.org; Mon, 21 Jun 1999 13:29:31 -0400 (EDT) (envelope-from mi) Message-Id: <199906211729.NAA09550@misha.cisco.com> Subject: Re: ROOTDEVNAME error in conf/LINT In-Reply-To: <199906202315.JAA03124@godzilla.zeta.org.au> from Bruce Evans at "Jun 21, 1999 09:15:25 am" To: current@freebsd.org Date: Mon, 21 Jun 1999 13:29:31 -0400 (EDT) Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans once wrote: > > that may change as SCSI disk sizes keep climbing and too large > > partitions take performance hits. > > > > alternative is to change MAXPARTITIONS? to 16? > > One reason is that the slice data format is better. It doesn't have > arbitrary limits like 8 or 16 (it's essentially a linked list). For a total of 3-5 slices/partitions/chunks like / /usr swap /home /var /tmp I'd much rather have an array then a link list... And shorter device names too... Is it worth it to keep the two tactics in place with the kernel build option? I don't know... Sincerely, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 10:54:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 146C015131 for ; Mon, 21 Jun 1999 10:54:17 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id KAA37783; Mon, 21 Jun 1999 10:54:00 -0700 (PDT) Date: Mon, 21 Jun 1999 10:53:59 -0700 (PDT) From: Julian Elischer To: "Justin T. Gibbs" Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: Remote serial gdb--status? In-Reply-To: <199906210013.SAA00602@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Jun 1999, Justin T. Gibbs wrote: > It looks like isa/sio.c still won't allow you to set a port as both > a low-level console and the gdb port. I could not get remote gdb > to work correctly after the sio probe without designating the port > for low-level console I/O. Now that I've done that, I can't debug > at 115200 any more. 38400 seems to work for me, but that is with > only minimal testing. Who broke remote debugging in sio? This > is a critical tool we can't afford to have broken... 8-( Kirk.. I had a differnt set of patches to do the sam ething, but he took a different approach. I'm sure th breakage is unintentional.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 16:26:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B5410151BE for ; Mon, 21 Jun 1999 16:26:12 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id QAA61027 for ; Mon, 21 Jun 1999 16:26:11 -0700 (PDT) Message-ID: <376ECA12.FF6D5DF@whistle.com> Date: Mon, 21 Jun 1999 16:26:10 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: NFS Test patch.. Anyone tested it? References: <199906150421.VAA14439@apollo.backplane.com> <199906160330.UAA25113@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > Here's the location: > > http://www.backplane.com/FreeBSD4/ > > It's in the 'NFS bugs first found by David E. Cross' section. > I've looked it over a bit and can't see any major problems.. and it definitly does fix some problems.. Has anyone tried it in a heavy server environment? if so, any problems? It's running ok here but it's only very lightly tested in our environment. I'd like to get it checked in if it really is an improvement.... julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 17:35:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id CE47414BDB for ; Mon, 21 Jun 1999 17:35:09 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA02053; Mon, 21 Jun 1999 20:35:00 -0400 (EDT) Message-Id: <199906220035.UAA02053@cs.rpi.edu> To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: NFS Test patch.. Anyone tested it? In-Reply-To: Message from Julian Elischer of "Mon, 21 Jun 1999 16:26:10 PDT." <376ECA12.FF6D5DF@whistle.com> Date: Mon, 21 Jun 1999 20:34:59 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have not tested, but I also gave it a very good look, and it looks solid. I would certainly like to see it in -current for some real life testing and then MFC-ed at the earliest convience :). Currently we are running off of some patches that I have written... that scares me, alot :) I would love to put those to death.. On the other hand we are rapidly approaching 5 days of uptime (the average before was 1.54 days, usually the server woiuld hit arround 2.5 and then we would get a couple of reboots on the same day) -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 19:37:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B176114BCC for ; Mon, 21 Jun 1999 19:37:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA14135; Mon, 21 Jun 1999 19:37:07 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Chuck Robey Cc: Nate Williams , freebsd-current@FreeBSD.ORG Subject: Re: laying down tags In-reply-to: Your message of "Mon, 21 Jun 1999 13:21:35 EDT." Date: Mon, 21 Jun 1999 19:37:07 -0700 Message-ID: <14131.930019027@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I get very stubborn when I'm given (what appears to me to be) a bogus > argument, even if the ultimate conclusion is right. The reason given > for the conclusion has to hold water. I figured somebody else would jump on this one, which is why I never bothered to respond myself. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 20:29:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 07C9A14C27 for ; Mon, 21 Jun 1999 20:29:47 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA03744 for ; Mon, 21 Jun 1999 23:29:45 -0400 (EDT) Message-Id: <199906220329.XAA03744@cs.rpi.edu> To: current@freebsd.org Subject: what's different with AHC between -stable and -current? Date: Mon, 21 Jun 1999 23:29:45 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have 3 AHC devices that work great under -STABLE, but -CURRENT doesn't even acknowledge they exist. GENERIC kernels on both. Here is the boot information from the working -STABLE system: Probing for devices on PCI bus 1: ahc0: rev 0x00 int a irq 21 on pci1.4.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 22 on pci1.6.0 ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc2: rev 0x03 int a irq 20 on pci1.8.0 ahc2: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs -CURRENT sees nothing. What additional information will I need to provide? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 21 21: 4:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 82D0614ED4 for ; Mon, 21 Jun 1999 21:04:32 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id WAA32213; Mon, 21 Jun 1999 22:04:28 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199906220404.WAA32213@panzer.plutotech.com> Subject: Re: what's different with AHC between -stable and -current? In-Reply-To: <199906220329.XAA03744@cs.rpi.edu> from "David E. Cross" at "Jun 21, 1999 11:29:45 pm" To: crossd@cs.rpi.edu (David E. Cross) Date: Mon, 21 Jun 1999 22:04:28 -0600 (MDT) Cc: current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David E. Cross wrote... > I have 3 AHC devices that work great under -STABLE, but -CURRENT doesn't > even acknowledge they exist. GENERIC kernels on both. Here is the boot > information from the working -STABLE system: > > Probing for devices on PCI bus 1: > ahc0: rev 0x00 int a irq 21 on pci1.4.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc1: rev 0x00 int a irq 22 on pci1.6.0 > ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc2: rev 0x03 int a irq 20 on pci1.8.0 > ahc2: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs > > -CURRENT sees nothing. > > What additional information will I need to provide? I suspect this has something to do with devices on your second PCI bus not getting probed under -current. Perhaps your bridge chip isn't getting probed properly. Verbose dmesg output and the output of 'pciconf -l' mailed to the list might help folks figure out what's going on. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 3:41:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 5AE5114FE6 for ; Tue, 22 Jun 1999 03:41:28 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id MAA23862 for freebsd-current@freebsd.org; Tue, 22 Jun 1999 12:41:23 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m10w5Ub-000WyXC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Mon, 21 Jun 1999 16:56:13 +0200 (CEST) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: audio-Device gone mute Date: 21 Jun 1999 16:56:09 +0200 Message-ID: <7kljq9$105$1@mips.rhein-neckar.de> References: <199906202045.WAA07067@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > This sounds like a bug in the device driver. If it is, then the driver succeeds into getting the card into a state it can't recover from. I rebooted and the problem persisted. It actually took a powercycle to make the card operational again. I'll see whether this repeats itself. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de carpe librum: books 'n' reviews To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 6: 6:36 1999 Delivered-To: freebsd-current@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 9BD3914F7C for ; Tue, 22 Jun 1999 06:06:29 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:DDWzqpTptolxuvV30ss3jb7ihlJ42cxz@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id WAA30511 for ; Tue, 22 Jun 1999 22:06:28 +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 WAA26731; Tue, 22 Jun 1999 22:10:38 +0900 (JST) Message-Id: <199906221310.WAA26731@zodiac.mech.utsunomiya-u.ac.jp> To: current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: HEADS UP!: syscons update comming up Date: Tue, 22 Jun 1999 22:10:37 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the next few hours I will commit a bunch of changes to syscons console driver. This is the second phase of syscons reorganization. Here are some warnings :) 1) Because a few new files will be added to the source tree, you will need to run config(8) on your kernel configuration file before compiling a new kernel. Most of you don't need to update the kernel configuration file itself. However, some of you may have to add the following options. options SC_PIXEL_MODE Syscons has supported the raster console mode (VESA 800x600) by default. This is now an optional feature, and must be explicitly enabled by SC_PIXEL_MODE. If you have been using this mode, add the above option. options SC_DFLT_FONT makeoptions "SC_DFLT_FONT=_font_name_" This new option replaces the existing STD8X16FONT option which loads the specified 16-line font. The new option will load not only 16-line font, but also 14- and 8- line font. 2) Recompile all screen savers and splash screen modules, because some header files will be changed. 3) Optionally update kbdcontrol and vidcontrol. If you regularly do "make world", you will be Ok. This is not mandatory because old binaries will still work with the new kernel. That's all. If you find any difficulties or problems, please report in the -current mailing list. Kazu yokota@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 6:33:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E6E7315403 for ; Tue, 22 Jun 1999 06:33:17 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA17486; Tue, 22 Jun 1999 09:33:17 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA13691; Tue, 22 Jun 1999 09:32:33 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 22 Jun 1999 09:32:32 -0400 (EDT) To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS Test patch.. Anyone tested it? In-Reply-To: <376ECA12.FF6D5DF@whistle.com> References: <199906150421.VAA14439@apollo.backplane.com> <199906160330.UAA25113@apollo.backplane.com> <376ECA12.FF6D5DF@whistle.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14191.36569.359260.192182@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > Matthew Dillon wrote: > > > > Here's the location: > > > > http://www.backplane.com/FreeBSD4/ > > > > It's in the 'NFS bugs first found by David E. Cross' section. > > > > > I've looked it over a bit and can't see any major problems.. > and it definitly does fix some problems.. > > Has anyone tried it in a heavy server environment? > if so, any problems? It's running ok here but it's only > very lightly tested in our environment. > > I'd like to get it checked in if it really is an improvement.... > > julian I'm in the process of deploying a box with these patches. It will be used to serve a large "scratch" filesystem to a large number of heterogenous clients. I anticipate that it should get beaten on fairly hard. In a few days, I'll let you (and Matt) know how its going. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 11:12:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from dead-end.net (dead-end.net [216.15.131.2]) by hub.freebsd.org (Postfix) with ESMTP id 05A9115222 for ; Tue, 22 Jun 1999 11:12:16 -0700 (PDT) (envelope-from rock@dead-end.net) Received: from dead-end.net (pC19F74DE.dip.t-online.de [193.159.116.222]) by dead-end.net (8.9.3/DEAD-END/1999022000) with ESMTP id UAA86046 for ; Tue, 22 Jun 1999 20:12:13 +0200 (CEST) (envelope-from rock@dead-end.net) Message-ID: <376FD21F.D5625A64@dead-end.net> Date: Tue, 22 Jun 1999 20:12:47 +0200 From: "D. Rock" Organization: ... X-Mailer: Mozilla 4.6 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: ROOTDEVNAME error in conf/LINT References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White schrieb: > > Some PC BIOSes won't boot a disk without a MS partition table. Try > booting a dangerously dedicated disk on a Phoenix machine and you'll see > what I mean. Hmm, I remember having exact this problem with a machine (Phoenix BIOS). After some hacks to the secondary boot I was able to boot from the dangerous dedicated disk, though. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 12:45:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AAC815674 for ; Tue, 22 Jun 1999 12:45:36 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id PAA24439; Tue, 22 Jun 1999 15:45:31 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA23833; Tue, 22 Jun 1999 15:44:46 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 22 Jun 1999 15:44:46 -0400 (EDT) To: Julian Elischer , dillon@backplane.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS Test patch.. Anyone tested it? In-Reply-To: <376ECA12.FF6D5DF@whistle.com> References: <199906150421.VAA14439@apollo.backplane.com> <199906160330.UAA25113@apollo.backplane.com> <376ECA12.FF6D5DF@whistle.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14191.44898.659493.845175@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > Matthew Dillon wrote: > > > > Here's the location: > > > > http://www.backplane.com/FreeBSD4/ > > > > It's in the 'NFS bugs first found by David E. Cross' section. > > > > > I've looked it over a bit and can't see any major problems.. > and it definitly does fix some problems.. > > Has anyone tried it in a heavy server environment? > if so, any problems? It's running ok here but it's only > very lightly tested in our environment. > > I'd like to get it checked in if it really is an improvement.... > OK. First minor problem & fix: Solaris 2.7 (5.7 Generic_106541-04 sun4u sparc) hosts cannot do a V3 mount of an nfs server with these patches applied. V2 mounts still seem to work. It turns out that this is because when a solaris 2.7 host does an NFSv3 mount, it calls the null procedure & Matt's diffs expose a bug in nfssvc_nfsd. The following patch, applied in addtion to the diffs above, corrects the problem: Index: nfs_syscalls.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_syscalls.c,v retrieving revision 1.49 diff -u -b -B -r1.49 nfs_syscalls.c --- nfs_syscalls.c 1999/04/27 11:17:52 1.49 +++ nfs_syscalls.c 1999/06/22 19:32:26 @@ -651,7 +651,7 @@ slp, nfsd->nfsd_procp, &mreq); if (mreq == NULL) break; - if (error) { + if (error != 0 && error != NFSERR_RETVOID) { if (nd->nd_procnum != NQNFSPROC_VACATED) nfsstats.srv_errs++; nfsrv_updatecache(nd, FALSE, mreq); Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 13:10:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id AB58D14BCC for ; Tue, 22 Jun 1999 13:10:13 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA08831; Tue, 22 Jun 1999 13:10:10 -0700 (PDT) Date: Tue, 22 Jun 1999 13:10:08 -0700 (PDT) From: Julian Elischer To: Andrew Gallatin Cc: dillon@backplane.com, freebsd-current@FreeBSD.ORG Subject: Re: NFS Test patch.. Anyone tested it? In-Reply-To: <14191.44898.659493.845175@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok I 've incorporated that into the patch set I have ready to commit.. I've also been playing in 3.x The patches apply almost cleanly there, except for 3 small problems that I'm fixing by hand.. I'll then make a 3.x version of the patches available. Hopefully people can start testing that.. julian On Tue, 22 Jun 1999, Andrew Gallatin wrote: > > Julian Elischer writes: > > Matthew Dillon wrote: > > > > > > Here's the location: > > > > > > http://www.backplane.com/FreeBSD4/ > > > > > > It's in the 'NFS bugs first found by David E. Cross' section. > > > > > > > > > I've looked it over a bit and can't see any major problems.. > > and it definitly does fix some problems.. > > > > Has anyone tried it in a heavy server environment? > > if so, any problems? It's running ok here but it's only > > very lightly tested in our environment. > > > > I'd like to get it checked in if it really is an improvement.... > > > > OK. First minor problem & fix: > > Solaris 2.7 (5.7 Generic_106541-04 sun4u sparc) hosts cannot do a V3 > mount of an nfs server with these patches applied. V2 mounts still > seem to work. > > It turns out that this is because when a solaris 2.7 host does an > NFSv3 mount, it calls the null procedure & Matt's diffs expose a bug > in nfssvc_nfsd. The following patch, applied in addtion to the diffs > above, corrects the problem: > > Index: nfs_syscalls.c > =================================================================== > RCS file: /home/ncvs/src/sys/nfs/nfs_syscalls.c,v > retrieving revision 1.49 > diff -u -b -B -r1.49 nfs_syscalls.c > --- nfs_syscalls.c 1999/04/27 11:17:52 1.49 > +++ nfs_syscalls.c 1999/06/22 19:32:26 > @@ -651,7 +651,7 @@ > slp, nfsd->nfsd_procp, &mreq); > if (mreq == NULL) > break; > - if (error) { > + if (error != 0 && error != NFSERR_RETVOID) { > if (nd->nd_procnum != NQNFSPROC_VACATED) > nfsstats.srv_errs++; > nfsrv_updatecache(nd, FALSE, mreq); > > > > Cheers, > > Drew > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 13:58: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id DF74715344 for ; Tue, 22 Jun 1999 13:57:52 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id NAA03639; Tue, 22 Jun 1999 13:57:28 -0700 (PDT) Date: Tue, 22 Jun 1999 13:57:29 -0700 (PDT) From: Tom Bartol To: Julian Elischer Cc: Andrew Gallatin , dillon@backplane.com, freebsd-current@FreeBSD.ORG Subject: Re: NFS Test patch.. Anyone tested it? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll be happy to test a 3.2-STABLE version of the patches as soon as they become available. Tom On Tue, 22 Jun 1999, Julian Elischer wrote: > Ok I 've incorporated that into the patch set I have ready to commit.. > I've also been playing in 3.x > > The patches apply almost cleanly there, except for 3 small problems that > I'm fixing by hand.. > > I'll then make a 3.x version of the patches available. > Hopefully people can start testing that.. > > julian > > > On Tue, 22 Jun 1999, Andrew Gallatin wrote: > > > > > Julian Elischer writes: > > > Matthew Dillon wrote: > > > > > > > > Here's the location: > > > > > > > > http://www.backplane.com/FreeBSD4/ > > > > > > > > It's in the 'NFS bugs first found by David E. Cross' section. > > > > > > > > > > > > > I've looked it over a bit and can't see any major problems.. > > > and it definitly does fix some problems.. > > > > > > Has anyone tried it in a heavy server environment? > > > if so, any problems? It's running ok here but it's only > > > very lightly tested in our environment. > > > > > > I'd like to get it checked in if it really is an improvement.... > > > > > > > OK. First minor problem & fix: > > > > Solaris 2.7 (5.7 Generic_106541-04 sun4u sparc) hosts cannot do a V3 > > mount of an nfs server with these patches applied. V2 mounts still > > seem to work. > > > > It turns out that this is because when a solaris 2.7 host does an > > NFSv3 mount, it calls the null procedure & Matt's diffs expose a bug > > in nfssvc_nfsd. The following patch, applied in addtion to the diffs > > above, corrects the problem: > > > > Index: nfs_syscalls.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/nfs/nfs_syscalls.c,v > > retrieving revision 1.49 > > diff -u -b -B -r1.49 nfs_syscalls.c > > --- nfs_syscalls.c 1999/04/27 11:17:52 1.49 > > +++ nfs_syscalls.c 1999/06/22 19:32:26 > > @@ -651,7 +651,7 @@ > > slp, nfsd->nfsd_procp, &mreq); > > if (mreq == NULL) > > break; > > - if (error) { > > + if (error != 0 && error != NFSERR_RETVOID) { > > if (nd->nd_procnum != NQNFSPROC_VACATED) > > nfsstats.srv_errs++; > > nfsrv_updatecache(nd, FALSE, mreq); > > > > > > > > Cheers, > > > > Drew > > ------------------------------------------------------------------------------ > > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > > Duke University Email: gallatin@cs.duke.edu > > Department of Computer Science Phone: (919) 660-6590 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 14: 1:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 30FF5152FA for ; Tue, 22 Jun 1999 14:01:00 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id OAA11989; Tue, 22 Jun 1999 14:00:42 -0700 (PDT) Date: Tue, 22 Jun 1999 14:00:41 -0700 (PDT) From: Julian Elischer To: Tom Bartol Cc: Andrew Gallatin , dillon@backplane.com, freebsd-current@FreeBSD.ORG Subject: Re: NFS Test patch.. Anyone tested it? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I said on -hackers.. > > There is a backported version of MAtt's NFS fixes at: > > ftp://ftp.whistle.com/pub/julian/nfs-3.diffs > > These include Andrew's fix to the fix > > results apreciated. > If you've been having NFS server side problems on 3.x check these out.. > > julian > > On Tue, 22 Jun 1999, Tom Bartol wrote: > > I'll be happy to test a 3.2-STABLE version of the patches as soon as they > become available. > > Tom > > > On Tue, 22 Jun 1999, Julian Elischer wrote: > > > Ok I 've incorporated that into the patch set I have ready to commit.. > > I've also been playing in 3.x > > > > The patches apply almost cleanly there, except for 3 small problems that > > I'm fixing by hand.. > > > > I'll then make a 3.x version of the patches available. > > Hopefully people can start testing that.. > > > > julian > > > > > > On Tue, 22 Jun 1999, Andrew Gallatin wrote: > > > > > > > > Julian Elischer writes: > > > > Matthew Dillon wrote: > > > > > > > > > > Here's the location: > > > > > > > > > > http://www.backplane.com/FreeBSD4/ > > > > > > > > > > It's in the 'NFS bugs first found by David E. Cross' section. > > > > > > > > > > > > > > > > > I've looked it over a bit and can't see any major problems.. > > > > and it definitly does fix some problems.. > > > > > > > > Has anyone tried it in a heavy server environment? > > > > if so, any problems? It's running ok here but it's only > > > > very lightly tested in our environment. > > > > > > > > I'd like to get it checked in if it really is an improvement.... > > > > > > > > > > OK. First minor problem & fix: > > > > > > Solaris 2.7 (5.7 Generic_106541-04 sun4u sparc) hosts cannot do a V3 > > > mount of an nfs server with these patches applied. V2 mounts still > > > seem to work. > > > > > > It turns out that this is because when a solaris 2.7 host does an > > > NFSv3 mount, it calls the null procedure & Matt's diffs expose a bug > > > in nfssvc_nfsd. The following patch, applied in addtion to the diffs > > > above, corrects the problem: > > > > > > Index: nfs_syscalls.c > > > =================================================================== > > > RCS file: /home/ncvs/src/sys/nfs/nfs_syscalls.c,v > > > retrieving revision 1.49 > > > diff -u -b -B -r1.49 nfs_syscalls.c > > > --- nfs_syscalls.c 1999/04/27 11:17:52 1.49 > > > +++ nfs_syscalls.c 1999/06/22 19:32:26 > > > @@ -651,7 +651,7 @@ > > > slp, nfsd->nfsd_procp, &mreq); > > > if (mreq == NULL) > > > break; > > > - if (error) { > > > + if (error != 0 && error != NFSERR_RETVOID) { > > > if (nd->nd_procnum != NQNFSPROC_VACATED) > > > nfsstats.srv_errs++; > > > nfsrv_updatecache(nd, FALSE, mreq); > > > > > > > > > > > > Cheers, > > > > > > Drew > > > ------------------------------------------------------------------------------ > > > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > > > Duke University Email: gallatin@cs.duke.edu > > > Department of Computer Science Phone: (919) 660-6590 > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 14:14:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9B844152E2 for ; Tue, 22 Jun 1999 14:14:32 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA20135 for ; Tue, 22 Jun 1999 17:14:29 -0400 (EDT) Message-Id: <199906222114.RAA20135@cs.rpi.edu> To: freebsd-current@freebsd.org Subject: vinum in -current Date: Tue, 22 Jun 1999 17:14:29 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The recent patches include a reference to "strerr()" in kernel mode... there is no such beast. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 17:29:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id EAF9115550 for ; Tue, 22 Jun 1999 17:29:35 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA17967; Wed, 23 Jun 1999 09:59:39 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA43416; Wed, 23 Jun 1999 09:59:51 +0930 (CST) Date: Wed, 23 Jun 1999 09:59:50 +0930 From: Greg Lehey To: "David E. Cross" Cc: freebsd-current@FreeBSD.ORG Subject: Re: vinum in -current Message-ID: <19990623095950.A76907@freebie.lemis.com> References: <199906222114.RAA20135@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906222114.RAA20135@cs.rpi.edu>; from David E. Cross on Tue, Jun 22, 1999 at 05:14:29PM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 22 June 1999 at 17:14:29 -0400, David E. Cross wrote: > The recent patches include a reference to "strerr()" in kernel mode... there > is no such beast. Ugh. Fixed. That's what you get for compiling before I've enabled it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 19:15:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id AA76914F94 for ; Tue, 22 Jun 1999 19:15:08 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA26278; Tue, 22 Jun 1999 22:14:55 -0400 (EDT) Message-Id: <199906230214.WAA26278@cs.rpi.edu> To: Greg Lehey Cc: "David E. Cross" , freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: vinum in -current In-Reply-To: Message from Greg Lehey of "Wed, 23 Jun 1999 09:59:50 +0930." <19990623095950.A76907@freebie.lemis.com> Date: Tue, 22 Jun 1999 22:14:55 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, now that you have fixed the strerr() bug, I have another -current vinum dilema... I have 3 disks... da0, da1, and da2. da0 has a 100M /, 200M /var, 2048M /usr, 512M swap. each of da1 and da2 have 512M swap. I have a vinum config similiar to: disk drive1 /dev/da0s1h disk drive2 /dev/da1s1h disk drive3 /dev/da2s1h volume data plex org striped 4m sd len 5000m drive drive1 sd len 5000m drive drive2 sd len 5000m drive drive3 plex org striped 4m sd len 2000m drive drive2 sd len 2000m drive drive3 When I "vinum create" this the last plex (doesn't matter if I reverse the order of the plexes in the file, it is the last defined plex that this refers to) is always in "status: initializing", and never leaves, the sd-s of that plex are listed "empty". Also, it lists the size of the volume as 15G... *NOT* 19G. This is true even if the 15G is listed second and is in the "initializing" status. This is -CURRENT as of today. Any ideas? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 19:37:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 6EBC914ECE for ; Tue, 22 Jun 1999 19:37:14 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA18467; Wed, 23 Jun 1999 12:07:18 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA45966; Wed, 23 Jun 1999 12:07:30 +0930 (CST) Date: Wed, 23 Jun 1999 12:07:30 +0930 From: Greg Lehey To: "David E. Cross" Cc: freebsd-current@FreeBSD.ORG Subject: Re: vinum in -current Message-ID: <19990623120730.H76907@freebie.lemis.com> References: <199906230214.WAA26278@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906230214.WAA26278@cs.rpi.edu>; from David E. Cross on Tue, Jun 22, 1999 at 10:14:55PM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 22 June 1999 at 22:14:55 -0400, David E. Cross wrote: > Ok, now that you have fixed the strerr() bug, I have another -current > vinum dilema... > > I have 3 disks... da0, da1, and da2. da0 has a 100M /, 200M /var, > 2048M /usr, 512M swap. each of da1 and da2 have 512M swap. > I have a vinum config similiar to: > > disk drive1 /dev/da0s1h > disk drive2 /dev/da1s1h > disk drive3 /dev/da2s1h > > volume data > plex org striped 4m > sd len 5000m drive drive1 > sd len 5000m drive drive2 > sd len 5000m drive drive3 > plex org striped 4m > sd len 2000m drive drive2 > sd len 2000m drive drive3 > > When I "vinum create" this the last plex (doesn't matter if I reverse the > order of the plexes in the file, it is the last defined plex that this > refers to) is always in "status: initializing", and never leaves, the sd-s > of that plex are listed "empty". This is a feature, not a bug, and it's described in vinum(8): setupstate When creating a multi-plex volume, assume that the contents of all the plexes are consistent. This is normally not the case, and correctly you should use the init command to first bring them to a consistent state. In the case of striped and concatenated plexes, however, it does not normally cause problems to leave them inconsistent: when using a volume for a file system or a swap partition, the previous contents of the disks are not of interest, so they may be ignored. If you want to take this risk, use this keyword. It will only apply to the plexes defined immediately after the volume in the configuration file. If you add plexes to a volume at a later time, you must integrate them. > Also, it lists the size of the volume as 15G... *NOT* 19G. That's correct. > This is true even if the 15G is listed second and is in the > "initializing" status. This is -CURRENT as of today. Any ideas? I think you misunderstand what this config does. Each plex replicates the entire address space of the volume, so this gives you a 16 GB volume with the first 4 GB mirrored. I suspect that you're trying to get a non-mirrored, striped volume with a total of 19 GB. Unfortunately, you currently can't do that in a sensible manner with drives of unequal sizes. One possibility would be: disk drive1 /dev/da0h disk drive2 /dev/da1h disk drive3 /dev/da2h volume data plex org striped 512k sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive2 sd len 1000m drive drive3 You'll note that I've changed the stripe size from 4m to 512k; there are some indications that a larger stripe size is not beneficial, though I currently can't say why. I've also changed the names of the drives. With the old ones, you won't be able to start the volume after a reboot. To quote vinum(8): drive name option Define a drive. The option must be: device devicename Specify the device on which the drive resides. devicename must be the name of a disk compati- bility partition, for example /dev/da1e or /dev/wd3h, and it should be of type vinum. Do not use the c partition, which is reserved for the complete disk, and should be of type unused. It is currently possible to create drives on other disk devices, for example /dev/da0s1 or /dev/da0s1e, but it will not be possible to start these drives after a reboot. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 22:33:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (Postfix) with SMTP id 506F614D04 for ; Tue, 22 Jun 1999 22:33:39 -0700 (PDT) (envelope-from herbelot@cybercable.fr) Received: (qmail 11669 invoked from network); 23 Jun 1999 05:33:38 -0000 Received: from d106.paris-26.cybercable.fr (HELO cybercable.fr) ([212.198.26.106]) (envelope-sender ) by bouvreuil.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 23 Jun 1999 05:33:38 -0000 Message-ID: <377071AF.4541C060@cybercable.fr> Date: Wed, 23 Jun 1999 07:33:35 +0200 From: Thierry Herbelot Organization: Les barbus =?iso-8859-1?Q?associ=E9s?=, Paris, France X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: "David E. Cross" , freebsd-current@FreeBSD.ORG Subject: Re: vinum in -current References: <199906230214.WAA26278@cs.rpi.edu> <19990623120730.H76907@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Greg, If I may intrude in this discussion, I was wondering what is the correct syntax for naming vinum drives in rc.conf. I've got two drives merged and striped with vinum, but I'm not sure what to put in rc.conf vinum_conf : drive drive1 device /dev/wd1s1h drive drive2 device /dev/wd2s1h volume initial plex org striped 512b sd length 19806208b drive drive1 sd length 19806208b drive drive2 in rc.conf : Is the following correct : vinum_drives="/dev/wd1s1h /dev/wd2s1h" or should it be vinum_drives="/dev/wd1h /dev/wd2h" Big kudos for vinum TfH Greg Lehey wrote: > [SNIP] > I've also changed the names of the drives. With the old ones, you > won't be able to start the volume after a reboot. To quote vinum(8): > > drive name option > > Define a drive. The option must be: > > device devicename Specify the device on which the drive resides. > devicename must be the name of a disk compati- > bility partition, for example /dev/da1e or > /dev/wd3h, and it should be of type vinum. Do > not use the c partition, which is reserved for > the complete disk, and should be of type > unused. It is currently possible to create > drives on other disk devices, for example > /dev/da0s1 or /dev/da0s1e, but it will not be > possible to start these drives after a reboot. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 22:49:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E72AC154DD for ; Tue, 22 Jun 1999 22:49:34 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA18976; Wed, 23 Jun 1999 15:19:38 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA00640; Wed, 23 Jun 1999 15:19:51 +0930 (CST) Date: Wed, 23 Jun 1999 15:19:50 +0930 From: Greg Lehey To: Thierry Herbelot Cc: "David E. Cross" , freebsd-current@FreeBSD.ORG Subject: Re: vinum in -current Message-ID: <19990623151950.A581@freebie.lemis.com> References: <199906230214.WAA26278@cs.rpi.edu> <19990623120730.H76907@freebie.lemis.com> <377071AF.4541C060@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <377071AF.4541C060@cybercable.fr>; from Thierry Herbelot on Wed, Jun 23, 1999 at 07:33:35AM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 23 June 1999 at 7:33:35 +0200, Thierry Herbelot wrote: > Greg Lehey wrote: >> > > [SNIP] > >> I've also changed the names of the drives. With the old ones, you >> won't be able to start the volume after a reboot. To quote vinum(8): >> >> drive name option >> >> Define a drive. The option must be: >> >> device devicename Specify the device on which the drive resides. >> devicename must be the name of a disk compati- >> bility partition, for example /dev/da1e or >> /dev/wd3h, and it should be of type vinum. Do >> not use the c partition, which is reserved for >> the complete disk, and should be of type >> unused. It is currently possible to create >> drives on other disk devices, for example >> /dev/da0s1 or /dev/da0s1e, but it will not be >> possible to start these drives after a reboot. > > Hello Greg, > > If I may intrude in this discussion, I was wondering what is the correct > syntax for naming vinum drives in rc.conf. > I've got two drives merged and striped with vinum, but I'm not sure what > to put in rc.conf > vinum_conf : > drive drive1 device /dev/wd1s1h > drive drive2 device /dev/wd2s1h As the man page excerpt that you quoted above shows, this is wrong. It should be /dev/wd1h and /dev/wd2h. > volume initial > plex org striped 512b > sd length 19806208b drive drive1 > sd length 19806208b drive drive2 > > in rc.conf : > Is the following correct : > vinum_drives="/dev/wd1s1h /dev/wd2s1h" > or should it be > vinum_drives="/dev/wd1h /dev/wd2h" In fact, it should be vinum_drives="" start_vinum=YES That way, vinum will start all drives. > Big kudos for vinum Thanks. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 22:50:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id D3BEA154DD for ; Tue, 22 Jun 1999 22:50:34 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id BAA29664; Wed, 23 Jun 1999 01:50:19 -0400 (EDT) Message-Id: <199906230550.BAA29664@cs.rpi.edu> To: Thierry Herbelot Cc: Greg Lehey , "David E. Cross" , freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: vinum in -current In-Reply-To: Message from Thierry Herbelot of "Wed, 23 Jun 1999 07:33:35 +0200." <377071AF.4541C060@cybercable.fr> Date: Wed, 23 Jun 1999 01:50:19 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neither is correct, you want to leave the parition identifier ("h") off of it. When vinum starts it scans all the partitions by attempting to add one of [abdefgh] to the end of whatever you give it. If you give it "wd0s1h" it will look for "wd0s1ha ... wd0s1hh" and never find it. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 22 22:55:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 6BD9315509 for ; Tue, 22 Jun 1999 22:55:14 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA19014; Wed, 23 Jun 1999 15:25:18 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA00690; Wed, 23 Jun 1999 15:25:33 +0930 (CST) Date: Wed, 23 Jun 1999 15:25:33 +0930 From: Greg Lehey To: "David E. Cross" Cc: Thierry Herbelot , freebsd-current@FreeBSD.ORG Subject: Re: vinum in -current Message-ID: <19990623152532.B581@freebie.lemis.com> References: <199906230550.BAA29664@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906230550.BAA29664@cs.rpi.edu>; from David E. Cross on Wed, Jun 23, 1999 at 01:50:19AM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 23 June 1999 at 1:50:19 -0400, David E. Cross wrote: > Neither is correct, you want to leave the parition identifier ("h") off of > it. When vinum starts it scans all the partitions by attempting to add > one of [abdefgh] to the end of whatever you give it. If you give it > "wd0s1h" it will look for "wd0s1ha ... wd0s1hh" and never find it. I assume this is a reply to Thierry's question: > Is the following correct : > vinum_drives="/dev/wd1s1h /dev/wd2s1h" > or should it be > vinum_drives="/dev/wd1h /dev/wd2h" I stated that the correct answer was to set the start_vinum variable, but there are reasons to use vinum_drives (otherwise it wouldn't be there). You use vinum_drives to specify that you want to start only certain drives, not all of them. In this case, yes, it should be /dev/wd1 and /dev/wd2 (or /dev/wd1s1 and /dev/wd2s1 if you insist). There should be no partition letter at the end. Note also that vinum will not use partition c. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 11:45:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id E00AF14E81 for ; Wed, 23 Jun 1999 11:45:13 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA05740 for ; Wed, 23 Jun 1999 11:45:12 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 23 Jun 1999 11:45:12 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: freebsd-current@freebsd.org Subject: ktrace causes kernel panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Using a recent (few days) -current I had a process lock up on me last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a while. When I issued a 'ktrace -C' in another screen, everything froze and the kernel panic'ed. I dropped to the debugger on the console and it was definintely ktrace that caused the panic. There are at least two possibilities I can think of for this problem, one being that ktrace.out filled up the root partition (although I'm 99% sure that I was in the expansive /usr fs at the time) or it's also very possible that the process I was tracing exited while I was trace'ing it. However to my mind this shoudln't have caused the kernel to panic either way. If this is a known problem I won't mess with it any more, since the circumstance that caused the problem would be near impossible to reproduce. However if it's something that needs to be tracked down I'll do what I can to help. Thanks, Doug PS, it's a multi-processor system with an SMP kernel if that makes any difference. -- 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-current" in the body of the message From owner-freebsd-current Wed Jun 23 12:23:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 1336314FC4 for ; Wed, 23 Jun 1999 12:23:50 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA05962 for ; Wed, 23 Jun 1999 12:23:50 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 23 Jun 1999 12:23:49 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: freebsd-current@freebsd.org Subject: New ATA stuff, questions and comment Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First a question, namely what is the current state of the ATA drivers in -current? Are they reliable (where "reliable" goes by -current terms obviously)? I finally am in a position to test them with a new workstation that has IDE disks, so I thought I'd give it a go. Also, I was trying to set up the CD player on this workstation and had a difficult time with the "atapicd" vs. "acd" stuff, so I finally just went back to the old w* stuff. Basically, LINT mentions atapicd0, but both devices.i386 and majors.i386, as well as /dev/MAKEDEV mention acd. Any comments or insights are welcome. Thanks, 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-current" in the body of the message From owner-freebsd-current Wed Jun 23 12:41:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8220B15113 for ; Wed, 23 Jun 1999 12:41:04 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id PAA86948; Wed, 23 Jun 1999 15:41:05 -0400 (EDT) Date: Wed, 23 Jun 1999 15:41:05 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Doug Cc: freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Jun 1999, Doug wrote: > First a question, namely what is the current state of the ATA > drivers in -current? Are they reliable (where "reliable" goes by -current > terms obviously)? I finally am in a position to test them with a new > workstation that has IDE disks, so I thought I'd give it a go. For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, I'm happy with the atapi-fd driver :) See: ata-pci0: irq 0 at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ta0: master: setting up UDMA2 mode on Aladdin chip OK ad0: ATA-4 disk at ata0 as master ad0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: master: setting up WDMA2 mode on Aladdin chip OK ad1: ATA-? disk at ata1 as master ad1: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=-1 ad1: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata0 as slave acd0: drive speed 2067KB/sec, 128KB cache acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked afd0: rewriteable drive at ata1 as slave afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S afd0: Medium: Unknown media (0x0) > > Also, I was trying to set up the CD player on this workstation and > had a difficult time with the "atapicd" vs. "acd" stuff, so I finally just > went back to the old w* stuff. Basically, LINT mentions atapicd0, but both > devices.i386 and majors.i386, as well as /dev/MAKEDEV mention acd. A device name isn't necessarily the same as a device node, you know. > > Any comments or insights are welcome. > > Thanks, > > 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-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 14:16:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 47F4414E9C for ; Wed, 23 Jun 1999 14:16:41 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA07484; Wed, 23 Jun 1999 14:16:23 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 23 Jun 1999 14:16:23 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: "Brian F. Feldman" Cc: Doug , freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Jun 1999, Brian F. Feldman wrote: > On Wed, 23 Jun 1999, Doug wrote: > > > First a question, namely what is the current state of the ATA > > drivers in -current? Are they reliable (where "reliable" goes by -current > > terms obviously)? I finally am in a position to test them with a new > > workstation that has IDE disks, so I thought I'd give it a go. > > For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, > I'm happy with the atapi-fd driver :) See: Great news, thanks. > A device name isn't necessarily the same as a device node, you know. Actually I do know that, but I've never come across a situation in freebsd where I would call something one thing in my kernel config file and something else in /dev. If you are saying that I ought to include atapicd in my kernel config and use the acdN device node, that's all I need to know, but it does bring up the question of why the two things are different. It seems like unecessary obfuscation to me. Thanks for your response, 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-current" in the body of the message From owner-freebsd-current Wed Jun 23 15:45:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 1406C14E29 for ; Wed, 23 Jun 1999 15:45:34 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id SAA90006; Wed, 23 Jun 1999 18:45:36 -0400 (EDT) Date: Wed, 23 Jun 1999 18:45:36 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Doug Cc: freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Jun 1999, Doug wrote: > On Wed, 23 Jun 1999, Brian F. Feldman wrote: > > > On Wed, 23 Jun 1999, Doug wrote: > > > > > First a question, namely what is the current state of the ATA > > > drivers in -current? Are they reliable (where "reliable" goes by -current > > > terms obviously)? I finally am in a position to test them with a new > > > workstation that has IDE disks, so I thought I'd give it a go. > > > > For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, > > I'm happy with the atapi-fd driver :) See: > > Great news, thanks. > > > A device name isn't necessarily the same as a device node, you know. > > Actually I do know that, but I've never come across a situation in > freebsd where I would call something one thing in my kernel config file > and something else in /dev. If you are saying that I ought to include > atapicd in my kernel config and use the acdN device node, that's all I > need to know, but it does bring up the question of why the two things are > different. It seems like unecessary obfuscation to me. atapi-cd, atapi-fd, atapi-disk are more descriptive (self-explanatory) for the config file. acd, afd, and ad are shorter, in the concise "/dev/node" way. Complain to Soren if you don't like it ;) > > Thanks for your response, > > 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 > > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 15:54:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 1971414D0F for ; Wed, 23 Jun 1999 15:54:13 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id PAA08594 for ; Wed, 23 Jun 1999 15:54:12 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 23 Jun 1999 15:54:11 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: freebsd-current@freebsd.org Subject: Re: ktrace causes kernel panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Jun 1999, Doug wrote: > Using a recent (few days) -current I had a process lock up on me > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > while. When I issued a 'ktrace -C' in another screen, everything froze and > the kernel panic'ed. I dropped to the debugger on the console and it was > definintely ktrace that caused the panic. To add excitement to this, I worked on it for a while (in part because I still need to ktrace this process, and in part because I wanted to see if I could reproduce the crash) and ktrace is not performing the way I remember it. The last time I used ktrace (which was about a year ago) all I had to do was 'ktrace -p pid#' and it would attach to that process, and not let go till I killed it, or the process died. In my current attempt at it, each time I do the ktrace command it dumps about 1.8M worth of ktrace.out, then ktrace exits, even though the process is still alive and kicking. I don't see anything that I might be missing from the man page, so any insight would be appreciated. Otherwise I will call this a bug and send a PR. Thanks, 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-current" in the body of the message From owner-freebsd-current Wed Jun 23 16:15:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 6DE3414D2E for ; Wed, 23 Jun 1999 16:15:41 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA32024; Thu, 24 Jun 1999 09:15:32 +1000 Date: Thu, 24 Jun 1999 09:15:32 +1000 From: Bruce Evans Message-Id: <199906232315.JAA32024@godzilla.zeta.org.au> To: Doug@gorean.org, green@unixhelp.org Subject: Re: New ATA stuff, questions and comment Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, >I'm happy with the atapi-fd driver :) See: UDMA mode 2 is normal 33 MB/sec UDMA mode and has been supported by the old driver for about 2 years now (although not for all chipsets). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 17:30: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 922DD14CB0 for ; Wed, 23 Jun 1999 17:29:59 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id UAA91812; Wed, 23 Jun 1999 20:29:56 -0400 (EDT) Date: Wed, 23 Jun 1999 20:29:56 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Bruce Evans Cc: Doug@gorean.org, freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: <199906232315.JAA32024@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Jun 1999, Bruce Evans wrote: > >For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, > >I'm happy with the atapi-fd driver :) See: > > UDMA mode 2 is normal 33 MB/sec UDMA mode and has been supported by the > old driver for about 2 years now (although not for all chipsets). I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being very nice :) The old driver never did any form of DMA for me, much less UDMA, so I'm very glad to have the ATA drivers. > > Bruce > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 17:38:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 1AE1914FBE for ; Wed, 23 Jun 1999 17:38:28 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA23410; Thu, 24 Jun 1999 10:08:27 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA31227; Thu, 24 Jun 1999 10:08:26 +0930 (CST) Date: Thu, 24 Jun 1999 10:08:25 +0930 From: Greg Lehey To: Doug Cc: freebsd-current@FreeBSD.ORG Subject: Re: ktrace causes kernel panic Message-ID: <19990624100825.G417@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Doug on Wed, Jun 23, 1999 at 11:45:12AM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote: > Using a recent (few days) -current I had a process lock up on me > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > while. When I issued a 'ktrace -C' in another screen, everything froze and > the kernel panic'ed. I dropped to the debugger on the console and it was > definintely ktrace that caused the panic. So where's the dump? A stack trace would be informative. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 18:11:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 4A6DF15144 for ; Wed, 23 Jun 1999 18:11:30 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id SAA09476; Wed, 23 Jun 1999 18:11:21 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 23 Jun 1999 18:11:21 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Greg Lehey Cc: Doug , freebsd-current@FreeBSD.ORG Subject: Re: ktrace causes kernel panic In-Reply-To: <19990624100825.G417@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Jun 1999, Greg Lehey wrote: > On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote: > > Using a recent (few days) -current I had a process lock up on me > > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > > while. When I issued a 'ktrace -C' in another screen, everything froze and > > the kernel panic'ed. I dropped to the debugger on the console and it was > > definintely ktrace that caused the panic. > > So where's the dump? A stack trace would be informative. Sorry, forgot to mention that I didn't have time to write down the trace because the boss was breathing down my neck to get the thing back on line. I remember distinctly that the second to last function was ktrace() if that's any help. 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-current" in the body of the message From owner-freebsd-current Wed Jun 23 18:15: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 72AC515185 for ; Wed, 23 Jun 1999 18:15:04 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA23605; Thu, 24 Jun 1999 10:45:03 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA36058; Thu, 24 Jun 1999 10:45:03 +0930 (CST) Date: Thu, 24 Jun 1999 10:45:02 +0930 From: Greg Lehey To: Doug Cc: freebsd-current@FreeBSD.ORG Subject: Re: ktrace causes kernel panic Message-ID: <19990624104502.N417@freebie.lemis.com> References: <19990624100825.G417@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Doug on Wed, Jun 23, 1999 at 06:11:21PM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 23 June 1999 at 18:11:21 -0700, Doug wrote: > On Thu, 24 Jun 1999, Greg Lehey wrote: > >> On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote: >>> Using a recent (few days) -current I had a process lock up on me >>> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a >>> while. When I issued a 'ktrace -C' in another screen, everything froze and >>> the kernel panic'ed. I dropped to the debugger on the console and it was >>> definintely ktrace that caused the panic. >> >> So where's the dump? A stack trace would be informative. > > Sorry, forgot to mention that I didn't have time to write down the > trace because the boss was breathing down my neck to get the thing back on > line. I remember distinctly that the second to last function was ktrace() > if that's any help. Not much. You'll need to get a dump. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 19: 2:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id E7F5314EDA; Wed, 23 Jun 1999 19:02:27 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id KAA13091; Thu, 24 Jun 1999 10:01:19 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id KAA10129; Thu, 24 Jun 1999 10:02:25 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA15200; Thu, 24 Jun 1999 10:02:24 +0800 Message-Id: <199906240202.KAA15200@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org, multimedia@freebsd.org Subject: PCM sound problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Jun 1999 10:02:24 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a problem with the way my soundcard behaves. It stutters when using mpg123, where a small segment of music is played a number of time before moving onto the next segment. Looking at the code, I see that the DMA is set up in auto mode. I can only surmise that interrupts are not being serviced - perhaps we're sleeping at too high a priority? My machine's bios is set up believing that it has a PnP aware OS, resource allocation is automatic and all IRQs are available for Pnp/PCI. My dmesg output is below, as is my machine config file Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Jun 24 00:29:17 WST 1999 toor@bloop.craftncomp.com:/usr/src/sys/compile/bloop Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 399666517 Hz CPU: AMD-K6(tm) 3D processor (399.67-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping=12 Features=0x8021bf real memory = 67043328 (65472K bytes) FreeBSD Kernel Configuration Utility - Version 1.2 Type "help" for help. config> pnp 1 0 os enable port0 0x534 port2 0x220 irq0 9 drq1 3 config> quit sio0: system console avail memory = 62095360 (60640K bytes) Preloaded elf kernel "kernel" at 0xc02fe000. Probing for PnP devices: CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] mss_attach 1 at 0x530 irq 9 dma 0:3 flags 0x13 pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 9 drq 0 flags 0x13 on isa npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: irq 11 at device 7.2 on pci0 usb0: on uhci0 uhub0 at usb0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: at device 7.3 on pci0 rl0: irq 5 at device 9.0 on pci0 rl0: Ethernet address: 00:00:e8:53:a2:3e rl0: autoneg complete, link status good (half-duplex, 10Mbps) 3DFX Voodoo 1 has mem at phys 0xe4000000, vir 0xc3d9b000 type 0x1, vendor 0x121a voodoo0: <3DFX Voodoo 1> at device 10.0 on pci0 vga-pci0: irq 12 at device 11.0 on pci0 ncr0: irq 10 at device 12.0 on pci0 isa0: on motherboard atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Winbond chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 ata1: unwanted interrupt 1 status = ff ds0 XXX: driver didn't set ifq_maxlen ata0: master: setting up generic WDMA2 mode OK ad0: ATA-4 disk at ata0 as master ad0: 6179MB (12656448 sectors), 12556 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: unwanted interrupt 2 status = 50 acd0: CDROM drive at ata1 as slave acd0: drive speed 687 - 6875KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 6 seconds for SCSI devices to settle sa0 at ncr0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers changing root device to wd0s4a tsleep returns 4 machine "i386" ident bloop maxusers 10 options MAXDSIZ="(256*1024*1024)" options DFLDSIZ="(256*1024*1024)" options PQ_LARGECACHE # color for 512k/16k cache #options PQ_HUGECACHE # color for 1024k/16k cache options INCLUDE_CONFIG_FILE # Include this file in kernel #config kernel root on ad0 dumps on ad0 cpu "I486_CPU" cpu "I586_CPU" # aka Pentium(tm) cpu "I686_CPU" # aka Pentium Pro(tm) options "CPU_WT_ALLOC" options "NO_F00F_HACK" options "COMPAT_43" options USER_LDT #allow user-level control of i386 ldt options SYSVSHM options SYSVSEM options SYSVMSG options DDB options KTRACE #kernel tracing options INVARIANTS options INVARIANT_SUPPORT options PERFMON options UCONSOLE options USERCONFIG #boot -c editor options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver (ppp(8), nos-tun(8)) options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options MROUTING # Multicast routing options FFS #Fast filesystem options MFS #Memory File System options NFS #Network File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options SOFTUPDATES options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options _KPOSIX_VERSION="199309L" controller scbus0 #base SCSI code device ch0 #SCSI media changers device da0 #SCSI direct access devices (aka disks) device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs #device od0 #SCSI optical disk #device pass0 #CAM passthrough driver options SCSI_DELAY=6000 # Be pessimistic about Joe SCSI device options SA_SPACE_TIMEOUT="(60)" options SA_REWIND_TIMEOUT="(2*60)" options SA_ERASE_TIMEOUT="(4*60)" pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's options MSGBUF_SIZE="40960" controller isa0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? port ? conflicts options VESA # needs VM86 defined too!! options XSERVER # support for running an X server. device sc0 at isa? device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives controller fdc0 at isa? port "IO_FD1" irq 6 drq 2 disk fd0 at fdc0 drive 0 device sio0 at isa? port "IO_COM1" flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" irq 3 controller pnp0 #device pcm0 device pcm0 at isa? port ? irq 9 drq 0 flags 0x13 #device pca0 at isa? port "IO_TIMER1" controller pci0 controller ncr0 device de0 device rl0 device voodoo0 # I hope this works.... controller ppbus0 device lpt0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? device ppc0 at isa? port? irq 7 options PMAP_SHPGPERPROC="201" options SHMALL=1025 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=33 options SHMSEG=9 controller uhci0 controller ohci0 controller usb0 device ums0 device ukbd0 device ulpt0 device uhid0 device ugen0 -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 19:18:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id E2D8F151AA; Wed, 23 Jun 1999 19:18:22 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id KAA13124; Thu, 24 Jun 1999 10:17:14 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id KAA27475; Thu, 24 Jun 1999 10:18:18 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA15228; Thu, 24 Jun 1999 10:18:17 +0800 Message-Id: <199906240218.KAA15228@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org, multimedia@freebsd.org Subject: Re: PCM sound problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Jun 1999 10:18:17 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, forgot my pnpinfo output.... Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CSC4236 (0x3642630e), Serial Number 0xffffffff PnP Version 1.0, Vendor Version 5 Device Description: Crystal Codec Logical Device ID: CSC0000 0x0000630e #0 Device Description: WSS/SB TAG Start DF Good Configuration DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Type A DMA: channel(s) 0 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 - only one type (true/edge) I/O Range 0x534 .. 0x534, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x220, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Acceptable Configuration DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Type A DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 7 9 11 12 15 - only one type (true/edge) I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x260, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 7 9 11 12 15 - only one type (true/edge) I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x3f8, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x300, alignment 0x20, len 0x10 [16-bit addr] TAG End DF Logical Device ID: CSC0001 0x0100630e #1 Device Description: GAME TAG Start DF Good Configuration I/O Range 0x200 .. 0x200, alignment 0x8, len 0x8 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x208 .. 0x208, alignment 0x8, len 0x8 [16-bit addr] TAG End DF Logical Device ID: CSC0010 0x1000630e #2 Device Description: CTRL I/O Range 0x120 .. 0xff8, alignment 0x8, len 0x8 [16-bit addr] Logical Device ID: CSC0003 0x0300630e #3 Device Description: MPU TAG Start DF Good Configuration IRQ: 9 - only one type (true/edge) I/O Range 0x330 .. 0x330, alignment 0x8, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 9 11 12 15 - only one type (true/edge) I/O Range 0x330 .. 0x360, alignment 0x8, len 0x2 [16-bit addr] TAG Start DF Sub-optimal Configuration I/O Range 0x330 .. 0x3e0, alignment 0x8, len 0x2 [16-bit addr] TAG End DF End Tag Successfully got 46 resources, 4 logical fdevs -- card select # 0x0001 CSN CSC4236 (0x3642630e), Serial Number 0xffffffff Logical device #0 IO: 0x0534 0x0000 0x0220 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 9 0 DMA 0 3 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 Logical device #2 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 Logical device #3 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 # -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 20:50:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 695ED14DC2 for ; Wed, 23 Jun 1999 20:50:27 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm4094.cableco-op.com [208.138.40.94]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id UAA73761 for ; Wed, 23 Jun 1999 20:50:24 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <3771AB00.63F63721@MexComUSA.net> Date: Wed, 23 Jun 1999 20:50:24 -0700 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.6 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Current@FreeBSD.ORG Subject: Make world doesn't get past dhclient Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe I didn't get all the changes. I'm going to cvsup again and check. Thanks, ed cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o hash.o icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o socket.o tables.o tree.o upf.o packet.o: In function `assemble_hw_header': packet.o(.text+0x8c): undefined reference to `assemble_ethernet_header' packet.o: In function `decode_hw_header': packet.o(.text+0x1b4): undefined reference to `decode_ethernet_header' *** Error code 1 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 23 23: 4: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id EED9D14CA8 for ; Wed, 23 Jun 1999 23:03:57 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id XAA51963 for freebsd-current@freebsd.org; Wed, 23 Jun 1999 23:07:17 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199906240607.XAA51963@troutmask.apl.washington.edu> Subject: recent pkg_install commit To: freebsd-current@freebsd.org Date: Wed, 23 Jun 1999 23:07:17 -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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can some one back out the recent commits in usr.sbin/pkg_install that adds ? to getopt(3) optarg string? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 0: 5:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 076CF14A13 for ; Thu, 24 Jun 1999 00:05:09 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id CAA17951 for freebsd-current@freebsd.org; Thu, 24 Jun 1999 02:05:09 -0500 (CDT) Date: Thu, 24 Jun 1999 02:05:09 -0500 From: Tim Tsai To: freebsd-current@freebsd.org Subject: sc0 and serial console broken? Message-ID: <19990624015057.A17246@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried every variation of the kernel I can think of, including GENERIC, and same thing. I finally changed to vt0 and it booted up fine. I am using the standard sio0 config with the 0x10 flag and a /boot.config file with "-h". Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 FreeBSD/i386 bootstrap loader, Revision 0.7 640/64512kB (root@haha.com, Wed Jun 23 22:54:06 CDT 1999) Loading /boot/defaults/loader.conf /kernel text=0x10bf98 data=0x1c27c+0x1a26c syms=[0x4+0x1c4f0+0x4+0x1efb9] - Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Thu Jun 24 01:19:25 CDT 1999 root@haha.com:/usr/src/sys/compile/TIM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 179629198 Hz CPU: Pentium Pro (179.63-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff real memory = 67108864 (65536K bytes) config> di zp0 No such device: zp0 Invalid command or syntax. Type `?' for help. config> di ze0 No such device: ze0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ex0 No such device: ex0 Invalid command or syntax. Type `?' for help. config> di ep0 No such device: ep0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di wt0 No such device: wt0 Invalid command or syntax. Type `?' for help. config> di scd0 No such device: scd0 Invalid command or syntax. Type `?' for help. config> di mcd0 No such device: mcd0 Invalid command or syntax. Type `?' for help. config> di matcdc0 No such device: matcdc0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> en ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> po ed0 0x300 No such device: ed0 Invalid command or syntax. Type `?' for help. config> ir ed0 5 No such device: ed0 Invalid command or syntax. Type `?' for help. config> iom ed0 0xd8000 No such device: ed0 Invalid command or syntax. Type `?' for help. config> f ed0 0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> q avail memory = 62644224 (61176K bytes) Preloaded elf kernel "kernel" at 0xc0280000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028009c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 Correcting Natoma config for non-SMP Correcting Natoma config for non-SMP chip0: at device 0.0 on pci0 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 fxp0: irq 10 at device 18.0 on pci0 fxp0: Ethernet address 00:a0:c9:a0:32:ee fxp1: irq 12 at device 19.0 on pci0 fxp1: Ethernet address 00:90:27:75:59:f1 vga-pci0: irq 5 at device 20.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 1204MB (2467584 sectors), 2448 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 0:10:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id C0E6514BE2 for ; Thu, 24 Jun 1999 00:10:51 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id CAA18087 for freebsd-current@FreeBSD.ORG; Thu, 24 Jun 1999 02:10:51 -0500 (CDT) Date: Thu, 24 Jun 1999 02:10:51 -0500 From: Tim Tsai To: freebsd-current@FreeBSD.ORG Subject: Re: sc0 and serial console broken? Message-ID: <19990624021050.A18027@futuresouth.com> References: <19990624015057.A17246@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990624015057.A17246@futuresouth.com>; from Tim Tsai on Thu, Jun 24, 1999 at 02:05:09AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Grrr, forgot the trap information: From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried every variation of the kernel I can think of, including GENERIC, and same thing. I finally changed to vt0 and it booted up fine. I am using the standard sio0 config with the 0x10 flag and a /boot.config file with "-h". Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 FreeBSD/i386 bootstrap loader, Revision 0.7 640/64512kB (root@haha.com, Wed Jun 23 22:54:06 CDT 1999) Loading /boot/defaults/loader.conf /kernel text=0x10bf98 data=0x1c27c+0x1a26c syms=[0x4+0x1c4f0+0x4+0x1efb9] - Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Thu Jun 24 01:19:25 CDT 1999 root@haha.com:/usr/src/sys/compile/TIM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 179629198 Hz CPU: Pentium Pro (179.63-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff real memory = 67108864 (65536K bytes) config> di zp0 No such device: zp0 Invalid command or syntax. Type `?' for help. config> di ze0 No such device: ze0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ex0 No such device: ex0 Invalid command or syntax. Type `?' for help. config> di ep0 No such device: ep0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di wt0 No such device: wt0 Invalid command or syntax. Type `?' for help. config> di scd0 No such device: scd0 Invalid command or syntax. Type `?' for help. config> di mcd0 No such device: mcd0 Invalid command or syntax. Type `?' for help. config> di matcdc0 No such device: matcdc0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> en ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> po ed0 0x300 No such device: ed0 Invalid command or syntax. Type `?' for help. config> ir ed0 5 No such device: ed0 Invalid command or syntax. Type `?' for help. config> iom ed0 0xd8000 No such device: ed0 Invalid command or syntax. Type `?' for help. config> f ed0 0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> q avail memory = 62644224 (61176K bytes) Preloaded elf kernel "kernel" at 0xc0280000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028009c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 Correcting Natoma config for non-SMP Correcting Natoma config for non-SMP chip0: at device 0.0 on pci0 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 fxp0: irq 10 at device 18.0 on pci0 fxp0: Ethernet address 00:a0:c9:a0:32:ee fxp1: irq 12 at device 19.0 on pci0 fxp1: Ethernet address 00:90:27:75:59:f1 vga-pci0: irq 5 at device 20.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 1204MB (2467584 sectors), 2448 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xa fault code = supervisor read, page not present instruction pointer = 0x8:0xc01df028 stack pointer = 0x10:0xc0294eec frame pointer = 0x10:0xc0294ef8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam kernel: type 12 trap, code=0 Stopped at sc_get_softc+0x34: testb $0x1,0xa(%eax) db> trace sc_get_softc(0,0,0,0,0) at sc_get_softc+0x34 scinit(0,0,c0979f40,0,c0964800) at scinit+0x74 sc_attach_unit(0,0,9,0,c0294f60) at sc_attach_unit+0x2b scattach(c0979f40,c0979f40,c0294f78,c01481bb,c0979f40) at scattach+0x35 DEVICE_ATTACH(c0979f40,c0979f40,c02289f0,299000,c0294f88) at DEVICE_ATTACH+0x33 device_probe_and_attach(c0979f40) at device_probe_and_attach+0x4b bus_generic_attach(c0964800) at bus_generic_attach+0x16 configure(0) at configure+0x55 mi_startup(c0294fb4,ffe,299000,c014c061,c0403000) at mi_startup+0x92 begin() at begin+0x4b db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 0 c02415a0 c0293000 0 0 0 000204 2 swapper db> call boot(0) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 0:41:22 1999 Delivered-To: freebsd-current@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 A2CC114E5D for ; Thu, 24 Jun 1999 00:41:18 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:4Yuk8FpK/ThA8fldlw4E1pABfuubeSqN@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id QAA05143; Thu, 24 Jun 1999 16:40:40 +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 QAA13876; Thu, 24 Jun 1999 16:44:50 +0900 (JST) Message-Id: <199906240744.QAA13876@zodiac.mech.utsunomiya-u.ac.jp> To: Tim Tsai Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: sc0 and serial console broken? In-reply-to: Your message of "Thu, 24 Jun 1999 02:05:09 EST." <19990624015057.A17246@futuresouth.com> References: <19990624015057.A17246@futuresouth.com> Date: Thu, 24 Jun 1999 16:44:50 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried >every variation of the kernel I can think of, including GENERIC, and same >thing. I finally changed to vt0 and it booted up fine. A bug was found earlier today in syscons_isa.c. Apply the following patch to /sys/isa/syscons_isa.c and see if it works. Kazu Index: syscons_isa.c =================================================================== RCS file: /src/CVS/src/sys/isa/syscons_isa.c,v retrieving revision 1.5 diff -u -r1.5 syscons_isa.c --- syscons_isa.c 1999/06/22 14:13:41 1.5 +++ syscons_isa.c 1999/06/24 01:24:22 @@ -79,7 +79,7 @@ static driver_t sc_driver = { SC_DRIVER_NAME, sc_methods, - 1, /* XXX */ + sizeof(sc_softc_t), }; static sc_softc_t main_softc = { 0, 0, 0, -1, NULL, -1, NULL, }; @@ -125,7 +125,7 @@ main_softc.unit = unit; return &main_softc; } else { - sc = (sc_softc_t *)devclass_get_softc(sc_devclass, unit); + sc = (sc_softc_t *)device_get_softc(devclass_get_device(sc_devclass, unit)); if (!(sc->flags & SC_INIT_DONE)) { sc->unit = unit; sc->keyboard = -1; @@ -148,7 +148,7 @@ return sc; units = devclass_get_maxunit(sc_devclass); for (i = 0; i < units; ++i) { - sc = (sc_softc_t *)devclass_get_softc(sc_devclass, i); + sc = (sc_softc_t *)device_get_softc(devclass_get_device(sc_devclass, i)); if (sc == NULL) continue; if (((adp == NULL) || (adp == sc->adp)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 1: 1:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 7E0731504E for ; Thu, 24 Jun 1999 01:01:17 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id DAA19668; Thu, 24 Jun 1999 03:01:09 -0500 (CDT) Date: Thu, 24 Jun 1999 03:01:09 -0500 From: Tim Tsai To: Kazutaka YOKOTA Cc: freebsd-current@FreeBSD.ORG Subject: Re: sc0 and serial console broken? Message-ID: <19990624030109.A19637@futuresouth.com> References: <19990624015057.A17246@futuresouth.com> <199906240744.QAA13876@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199906240744.QAA13876@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Thu, Jun 24, 1999 at 04:44:50PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That fixed it. Thanks! Tim On Thu, Jun 24, 1999 at 04:44:50PM +0900, Kazutaka YOKOTA wrote: > >>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried > >every variation of the kernel I can think of, including GENERIC, and same > >thing. I finally changed to vt0 and it booted up fine. > > A bug was found earlier today in syscons_isa.c. Apply the following > patch to /sys/isa/syscons_isa.c and see if it works. > > Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 2:36:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id C91C114F16 for ; Thu, 24 Jun 1999 02:36:17 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10x5v3-000D45-00; Thu, 24 Jun 1999 11:35:41 +0200 From: Sheldon Hearn To: Doug Cc: "Brian F. Feldman" , freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-reply-to: Your message of "Wed, 23 Jun 1999 14:16:23 MST." Date: Thu, 24 Jun 1999 11:35:41 +0200 Message-ID: <50224.930216941@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Jun 1999 14:16:23 MST, Doug wrote: > If you are saying that I ought to include atapicd in my kernel config > and use the acdN device node, that's all I need to know, but it does > bring up the question of why the two things are different. It seems > like unecessary obfuscation to me. It's necessary because the new ATA stuff is intended to replace the old wd/acd stuff, eventually. We don't want to use a new name for atapi-cd and you can't use both drivers, so why confuse the issue? :-) Having said that, it _is_ a confusing state of affairs if you haven't followed the history of IDE and ATAPI support in FreeBSD. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 6:27:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B033814F00 for ; Thu, 24 Jun 1999 06:27:42 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id PAA51412; Thu, 24 Jun 1999 15:27:06 +0200 (CEST) (envelope-from des) To: Doug Cc: "Brian F. Feldman" , freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment References: From: Dag-Erling Smorgrav Date: 24 Jun 1999 15:27:05 +0200 In-Reply-To: Doug's message of "Wed, 23 Jun 1999 14:16:23 -0700 (PDT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug writes: > On Wed, 23 Jun 1999, Brian F. Feldman wrote: > > A device name isn't necessarily the same as a device node, you know. > Actually I do know that, but I've never come across a situation in > freebsd where I would call something one thing in my kernel config file > and something else in /dev. man bpf DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 6:31:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 964CD14F00 for ; Thu, 24 Jun 1999 06:31:32 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id PAA51510; Thu, 24 Jun 1999 15:31:26 +0200 (CEST) (envelope-from des) To: "Brian F. Feldman" Cc: Bruce Evans , Doug@gorean.org, freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment References: From: Dag-Erling Smorgrav Date: 24 Jun 1999 15:31:26 +0200 In-Reply-To: "Brian F. Feldman"'s message of "Wed, 23 Jun 1999 20:29:56 -0400 (EDT)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" writes: > I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being > very nice :) The old driver never did any form of DMA for me, much less UDMA, so > I'm very glad to have the ATA drivers. controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff Will enable DMA mode with the old driver. It doesn't support UDMA on all chipsets (e.g. ALI), and in some cases may give very poor performance when using UDMA disks, but normal DMA mode should work. If you have UDMA disks but can't get UDMA to work, just disable UDMA in the BIOS setup utility and it will use normal DMA instead. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 7:43:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from Tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (Postfix) with ESMTP id E24FF15173 for ; Thu, 24 Jun 1999 07:43:17 -0700 (PDT) (envelope-from bruceb@panther.austx.tandem.com) Received: from fedex.austx.tandem.com (fedex.austx.tandem.com [131.124.250.27]) by Tandem.com (8.9.3/2.0.1) with ESMTP id HAA01352 for ; Thu, 24 Jun 1999 07:43:14 -0700 (PDT) Received: from panther.austx.tandem.com (panther.austx.tandem.com [131.124.4.106]) by fedex.austx.tandem.com (8.9.0/8.9.0) with ESMTP id JAA12140 for ; Thu, 24 Jun 1999 09:43:13 -0500 (CDT) Received: (from bruceb@localhost) by panther.austx.tandem.com (8.8.5/8.7.1) id JAA15122 for freebsd-current@freebsd.org; Thu, 24 Jun 1999 09:42:38 -0500 (CDT) From: Bruce Burden Message-Id: <199906241442.JAA15122@panther.austx.tandem.com> Subject: Re: Make world doesn't get past dhclient To: freebsd-current@freebsd.org Date: Thu, 24 Jun 1999 09:42:37 -0500 (CDT) Reply-To: bruceb@austx.tandem.com In-Reply-To: <3771AB00.63F63721@MexComUSA.net> from "Edwin Culp" at Jun 23, 99 08:50:24 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Ed, > > cc -nostdinc -O -pipe > -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes > -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp > -I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o > dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o hash.o > icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o > print.o raw.o socket.o tables.o tree.o upf.o > packet.o: In function `assemble_hw_header': > packet.o(.text+0x8c): undefined reference to `assemble_ethernet_header' > packet.o: In function `decode_hw_header': > packet.o(.text+0x1b4): undefined reference to `decode_ethernet_header' > *** Error code 1 > > Stop. > *** Error code 1 > I just had this problem. I got around it by adding "ethernet.c" to the sources line in the file: /usr/src/sbin/dhclient/Makefile All of the code is there, Make just doesn't know to make it... Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 7:49:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from Tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (Postfix) with ESMTP id D2F6714CE4 for ; Thu, 24 Jun 1999 07:49:26 -0700 (PDT) (envelope-from bruceb@panther.austx.tandem.com) Received: from fedex.austx.tandem.com (fedex.austx.tandem.com [131.124.250.27]) by Tandem.com (8.9.3/2.0.1) with ESMTP id HAA02718 for ; Thu, 24 Jun 1999 07:49:25 -0700 (PDT) Received: from panther.austx.tandem.com (panther.austx.tandem.com [131.124.4.106]) by fedex.austx.tandem.com (8.9.0/8.9.0) with ESMTP id JAA12257 for ; Thu, 24 Jun 1999 09:49:24 -0500 (CDT) Received: (from bruceb@localhost) by panther.austx.tandem.com (8.8.5/8.7.1) id JAA15173 for freebsd-current@freebsd.org; Thu, 24 Jun 1999 09:48:49 -0500 (CDT) From: Bruce Burden Message-Id: <199906241448.JAA15173@panther.austx.tandem.com> Subject: Make world doesn't get past ifconfig To: freebsd-current@freebsd.org Date: Thu, 24 Jun 1999 09:48:49 -0500 (CDT) Reply-To: bruceb@austx.tandem.com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Has this problem been fixed? ===> sbin/ifconfig cc -O -pipe -DUSE_IF_MEDIA -DUSE_VLANS -DNS -Wall -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I.. -c /omni/usr/src/sbin/ifconfig/ifconfig.c /omni/usr/src/sbin/ifconfig/ifconfig.c: In function `status': /omni/usr/src/sbin/ifconfig/ifconfig.c:723: storage size of `ifs' isn't known /omni/usr/src/sbin/ifconfig/ifconfig.c:806: `SIOCGIFSTATUS' undeclared (first use this function) /omni/usr/src/sbin/ifconfig/ifconfig.c:806: (Each undeclared identifier is reported only once /omni/usr/src/sbin/ifconfig/ifconfig.c:806: for each function it appears in.) /omni/usr/src/sbin/ifconfig/ifconfig.c:723: warning: unused variable `ifs' *** Error code 1 This is from a buildworld after an early morning (shortly after midnight CDT) cvsup on 24 June 1999. I can't find a definition for SIOCGIFSTATUS of "ifstat", of which 'ifs' is declared to be a type of. Thank you, Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 8:15:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id B3F5514CB9 for ; Thu, 24 Jun 1999 08:15:37 -0700 (PDT) (envelope-from DougGuy@dal.net) Received: from dal.net (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id IAA15125; Thu, 24 Jun 1999 08:15:04 -0700 (PDT) (envelope-from DougGuy@dal.net) Message-ID: <37724B77.781378DB@dal.net> Date: Thu, 24 Jun 1999 08:15:03 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Doug , "Brian F. Feldman" , freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Doug writes: > > On Wed, 23 Jun 1999, Brian F. Feldman wrote: > > > A device name isn't necessarily the same as a device node, you know. > > Actually I do know that, but I've never come across a situation in > > freebsd where I would call something one thing in my kernel config file > > and something else in /dev. > > man bpf Yes the confusion that the two different names causes (and the consequent volume of -questions mail on the topic) is an excellent example of why it's a bad idea. Thanks for the support. :) Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 8:24:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4492314EFD for ; Thu, 24 Jun 1999 08:24:16 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id RAA00909; Thu, 24 Jun 1999 17:24:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: bruceb@austx.tandem.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Make world doesn't get past ifconfig In-reply-to: Your message of "Thu, 24 Jun 1999 09:48:49 CDT." <199906241448.JAA15173@panther.austx.tandem.com> Date: Thu, 24 Jun 1999 17:24:12 +0200 Message-ID: <907.930237852@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make sure you install the include files. In message <199906241448.JAA15173@panther.austx.tandem.com>, Bruce Burden write s: > > Hi all, > > Has this problem been fixed? > >===> sbin/ifconfig >cc -O -pipe -DUSE_IF_MEDIA -DUSE_VLANS -DNS -Wall -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I.. -c /omni/usr/src/sbin/ifconfig/ifconfig.c >/omni/usr/src/sbin/ifconfig/ifconfig.c: In function `status': >/omni/usr/src/sbin/ifconfig/ifconfig.c:723: storage size of `ifs' isn't known >/omni/usr/src/sbin/ifconfig/ifconfig.c:806: `SIOCGIFSTATUS' undeclared (first use this function) >/omni/usr/src/sbin/ifconfig/ifconfig.c:806: (Each undeclared identifier is reported only once >/omni/usr/src/sbin/ifconfig/ifconfig.c:806: for each function it appears in.) >/omni/usr/src/sbin/ifconfig/ifconfig.c:723: warning: unused variable `ifs' >*** Error code 1 > > This is from a buildworld after an early morning (shortly after > midnight CDT) cvsup on 24 June 1999. I can't find a definition for > SIOCGIFSTATUS of "ifstat", of which 'ifs' is declared to be a type of. > > Thank you, > Bruce >-- >------------------------------------------------------------------------------- > Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. > 512-432-8944 Network Verification 14231 Tandem Blvd. > Auto answer(4 rings) Austin, TX 78726 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 9:37:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewey.excite.com (ewey-rwcmta.excite.com [198.3.99.191]) by hub.freebsd.org (Postfix) with ESMTP id 171D814D44 for ; Thu, 24 Jun 1999 09:37:51 -0700 (PDT) (envelope-from john_wilson100@excite.com) Received: from bessie.excite.com ([199.172.152.102]) by ewey.excite.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19990624163751.QKVX1890.ewey@bessie.excite.com> for ; Thu, 24 Jun 1999 09:37:51 -0700 From: john_wilson100@excite.com To: freebsd-current@freebsd.org Subject: FreeBSD on Merced Message-Id: <930242270.19444.219@excite.com> Date: Thu, 24 Jun 1999 09:37:50 PDT X-Mailer: Excite Mail X-Sender-Ip: 129.12.41.34 MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there any plans to port FreeBSD to the IA-64 architecture when it comes out? The docs have recently been released http://developer.intel.com/design/ia64/architecture.htm so I was wondering if anyone had a chance to look at the stuff. It'll be a shame to see FreeBSD for Intel go with the last x86 processor. John _______________________________________________________ Get your free, private email at http://mail.excite.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 10:47:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 9D44714EA9 for ; Thu, 24 Jun 1999 10:47:23 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id TAA11494 for ; Thu, 24 Jun 1999 19:47:21 +0200 (MET DST) Date: Thu, 24 Jun 1999 19:47:19 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD current mailing list Subject: place of logfile for cron (PR 7682) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log. The FreeBSD style is to put those things in /var/log (/var/log/cron). Anyone any opinions on this? Which scripts depend on that location? Nick http://www.freebsd.org/cgi/query-pr.cgi?pr=7682 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 10:53:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6FBFE14C2F for ; Thu, 24 Jun 1999 10:53:10 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA09296; Thu, 24 Jun 1999 13:52:48 -0400 (EDT) Date: Thu, 24 Jun 1999 13:52:48 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: Bruce Evans , Doug@gorean.org, freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Jun 1999, Dag-Erling Smorgrav wrote: > "Brian F. Feldman" writes: > > I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being > > very nice :) The old driver never did any form of DMA for me, much less UDMA, so > > I'm very glad to have the ATA drivers. > > controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > > Will enable DMA mode with the old driver. It doesn't support UDMA on > all chipsets (e.g. ALI), and in some cases may give very poor > performance when using UDMA disks, but normal DMA mode should work. If > you have UDMA disks but can't get UDMA to work, just disable UDMA in > the BIOS setup utility and it will use normal DMA instead. Actually, I couldn't disable UDMA in the BIOS, and UDMA didn't work. So, the old driver did _not_ do DMA for me. Of course, I knew about the wdc flags. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 11:11:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CD83114BEE for ; Thu, 24 Jun 1999 11:11:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA54008; Thu, 24 Jun 1999 11:11:13 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: john_wilson100@excite.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD on Merced In-reply-to: Your message of "Thu, 24 Jun 1999 09:37:50 PDT." <930242270.19444.219@excite.com> Date: Thu, 24 Jun 1999 11:11:13 -0700 Message-ID: <54004.930247873@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are there any plans to port FreeBSD to the IA-64 architecture when it comes > out? The docs have recently been released There have been plans to do this for as long as Intel has had plans to make the processor. :) The question will simply come down to hardware availability and documentation. Once enough of us have access to both, something will no doubt happen. > It'll be a shame to see FreeBSD for Intel go with the last x86 processor. Unless a meteor strikes the earth and ends all life here first, I seriously doubt that this will happen. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 11:43:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1BCEC152A5 for ; Thu, 24 Jun 1999 11:43:00 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA27690; Thu, 24 Jun 1999 20:42:40 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906241842.UAA27690@freebsd.dk> Subject: Re: FreeBSD on Merced In-Reply-To: <54004.930247873@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jun 24, 1999 11:11:13 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Thu, 24 Jun 1999 20:42:40 +0200 (CEST) Cc: john_wilson100@excite.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Jordan K. Hubbard wrote: > > Are there any plans to port FreeBSD to the IA-64 architecture when it comes > > out? The docs have recently been released > > There have been plans to do this for as long as Intel has had plans to > make the processor. :) > > The question will simply come down to hardware availability and > documentation. Once enough of us have access to both, something will > no doubt happen. > > > It'll be a shame to see FreeBSD for Intel go with the last x86 processor. > > Unless a meteor strikes the earth and ends all life here first, I > seriously doubt that this will happen. :) Just get one of those Merced boxen on my table, and I'll do what I can to make it happen... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 12: 0:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id C87B914E5E for ; Thu, 24 Jun 1999 11:59:58 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA19555; Fri, 25 Jun 1999 04:59:39 +1000 Date: Fri, 25 Jun 1999 04:59:39 +1000 From: Bruce Evans Message-Id: <199906241859.EAA19555@godzilla.zeta.org.au> To: des@flood.ping.uio.no, green@unixhelp.org Subject: Re: New ATA stuff, questions and comment Cc: bde@zeta.org.au, Doug@gorean.org, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > >Will enable DMA mode with the old driver. It doesn't support UDMA on >all chipsets (e.g. ALI), and in some cases may give very poor Not e.g. ALI (Aladdin IV/V) (unless the ALI support is broken). >performance when using UDMA disks, but normal DMA mode should work. If Which cases? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 12: 5: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 089DA15152 for ; Thu, 24 Jun 1999 12:04:48 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id PAA10632; Thu, 24 Jun 1999 15:04:34 -0400 (EDT) Date: Thu, 24 Jun 1999 15:04:34 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Bruce Evans Cc: des@flood.ping.uio.no, Doug@gorean.org, freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: <199906241859.EAA19555@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Jun 1999, Bruce Evans wrote: > >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > > > >Will enable DMA mode with the old driver. It doesn't support UDMA on > >all chipsets (e.g. ALI), and in some cases may give very poor > > Not e.g. ALI (Aladdin IV/V) (unless the ALI support is broken). > Guess so. > >performance when using UDMA disks, but normal DMA mode should work. If > > Which cases? ALi Aladdin-V chipset. I already pasted the dmesg's relevant parts. > > Bruce > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 14: 0:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6F33B14C10 for ; Thu, 24 Jun 1999 14:00:44 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id XAA61996; Thu, 24 Jun 1999 23:00:31 +0200 (CEST) (envelope-from des) To: Bruce Evans Cc: green@unixhelp.org, Doug@gorean.org, freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment References: <199906241859.EAA19555@godzilla.zeta.org.au> From: Dag-Erling Smorgrav Date: 24 Jun 1999 23:00:30 +0200 In-Reply-To: Bruce Evans's message of "Fri, 25 Jun 1999 04:59:39 +1000" Message-ID: Lines: 35 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > > > >Will enable DMA mode with the old driver. It doesn't support UDMA on > >all chipsets (e.g. ALI), and in some cases may give very poor > > Not e.g. ALI (Aladdin IV/V) (unless the ALI support is broken). Excerpts from dmesg on an ASUSTek Super Socket 7 motherboard with a 350 MHz AMD K6-2, running yesterday's -CURRENT: pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 chip1: at device 3.0 on pci0 ide_pci0: irq 0 at device 15.0 on pci0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 9641MB (19746720 sectors), 19590 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S The IBM disk is an UDMA model. UDMA is disabled in the BIOS setup utility because of symptoms previously described on -current. It works fine in UDMA mode with sos' new atapi driver, btw. The Seagate drive is an old DMA-only (no UDMA) model. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 14:17:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C3199152A6 for ; Thu, 24 Jun 1999 14:17:31 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id RAA13063; Thu, 24 Jun 1999 17:17:25 -0400 (EDT) Date: Thu, 24 Jun 1999 17:17:25 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: Bruce Evans , Doug@gorean.org, freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You misunderstand. I _cannot_ disable UDMA in my BIOS. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 14:32:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C986214EAD for ; Thu, 24 Jun 1999 14:32:43 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id XAA62813; Thu, 24 Jun 1999 23:32:40 +0200 (CEST) (envelope-from des) To: "Brian F. Feldman" Cc: Dag-Erling Smorgrav , Bruce Evans , Doug@gorean.org, freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment References: From: Dag-Erling Smorgrav Date: 24 Jun 1999 23:32:40 +0200 In-Reply-To: "Brian F. Feldman"'s message of "Thu, 24 Jun 1999 17:17:25 -0400 (EDT)" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" writes: > You misunderstand. I _cannot_ disable UDMA in my BIOS. I know. The mail you answered wasn't addressed to you. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 14:45:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from kushnir.kiev.ua (n179.cdialup.kar.net [195.178.130.179]) by hub.freebsd.org (Postfix) with ESMTP id 3204B14EAD for ; Thu, 24 Jun 1999 14:44:09 -0700 (PDT) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by kushnir.kiev.ua (8.9.3/8.9.3) with ESMTP id AAA01577 for ; Fri, 25 Jun 1999 00:43:01 +0300 (EEST) (envelope-from kushn@mail.kar.net) X-Authentication-Warning: kushnir.kiev.ua: volodya owned process doing -bs Date: Fri, 25 Jun 1999 00:42:10 +0300 (EEST) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: freebsd-current@FreeBSD.ORG Subject: CTM's still down :-( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Sorry for being annoying but is there still anything wrong with CTM generation? The last src-cur delta was from 8th of June. Regards, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 15: 6: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from fasterix.frmug.org (d066.paris-81.cybercable.fr [212.198.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 9616A14DCF for ; Thu, 24 Jun 1999 15:05:46 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.3/8.9.3/pb-19990315) id AAA00900 for freebsd-current@FreeBSD.org; Fri, 25 Jun 1999 00:05:41 +0200 (CEST) Message-ID: <19990625000537.A657@fasterix.frmug.fr.net> Date: Fri, 25 Jun 1999 00:05:37 +0200 From: Pierre Beyssac To: freebsd-current@FreeBSD.org Subject: please review: patch for PR kern/12265 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm working on a fix to PR kern/12265 (panic when trying to RTM_GET the default route while there is none). The problem is that in route_output(), in that case, rn_lookup() returns the root node of the radix table (he got it from rn_match()), while the code expects NULL or a node with an AF_INET address family. Later, rtfree() gets very confused and panics because the route node to be freed doesn't have the right address family. From TCP/IP Illustrated vol. 2, it seems that rtalloc1() is written to expect that from rn_match(): it explicitly checks if the returned node is the root node. So there are two solutions: - fix rn_match() to return NULL when it currently returns the root node; - fix RTM_GET and friends, and scan for the same kind of error elsewhere, to trap for this same condition. I'm testing the first approach with the following patch on my machine and there seems to be no ill-effect. Unless someone thinks the second solution or another approach is better, I'll commit this patch. --- radix.c.orig Thu Jun 24 23:26:04 1999 +++ radix.c Thu Jun 24 23:26:26 1999 @@ -261,7 +261,7 @@ * This extra grot is in case we are explicitly asked * to look up the default. Ugh! */ - if ((t->rn_flags & RNF_ROOT) && t->rn_dupedkey) + if (t->rn_flags & RNF_ROOT) t = t->rn_dupedkey; return t; on1: -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 15:20:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B4B8115076 for ; Thu, 24 Jun 1999 15:20:43 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id RAA13722; Thu, 24 Jun 1999 17:55:28 -0400 (EDT) Date: Thu, 24 Jun 1999 17:55:28 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: Bruce Evans , Doug@gorean.org, freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Jun 1999, Dag-Erling Smorgrav wrote: > "Brian F. Feldman" writes: > > You misunderstand. I _cannot_ disable UDMA in my BIOS. > > I know. The mail you answered wasn't addressed to you. *apologies*. However, many Award BIOSes (all?) do not allow you to turn off UDMA. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 15:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 59C731520B for ; Thu, 24 Jun 1999 15:34:56 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA02953; Fri, 25 Jun 1999 08:34:38 +1000 Date: Fri, 25 Jun 1999 08:34:38 +1000 From: Bruce Evans Message-Id: <199906242234.IAA02953@godzilla.zeta.org.au> To: des@flood.ping.uio.no, green@unixhelp.org Subject: Re: New ATA stuff, questions and comment Cc: bde@zeta.org.au, Doug@gorean.org, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >*apologies*. However, many Award BIOSes (all?) do not allow you to turn >off UDMA. All Award BIOSes that I have (for 5 working systems) support it if the hardware supports it (2 systems). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 16:49:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 1FE3614D50 for ; Thu, 24 Jun 1999 16:49:22 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA43578; Thu, 24 Jun 1999 19:48:11 -0400 (EDT) Date: Thu, 24 Jun 1999 19:48:11 -0400 (EDT) From: Chuck Robey To: Vladimir Kushnir Cc: freebsd-current@FreeBSD.ORG Subject: Re: CTM's still down :-( In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Jun 1999, Vladimir Kushnir wrote: > Hello, > Sorry for being annoying but is there still anything wrong with CTM > generation? The last src-cur delta was from 8th of June. I know, we're waiting until Ulf gets the new disk up and spinning. It's taking some time, but I think he's having some problems with it. > > Regards, > Vladimir > > ===========================|======================= > Vladimir Kushnir | > kushn@mail.kar.net, | Powered by FreeBSD > kushnir@ap3.bitp.kiev.ua | > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 17: 6:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 29470150EE for ; Thu, 24 Jun 1999 17:06:23 -0700 (PDT) (envelope-from ggm@azure.dstc.edu.au) Received: from azure.dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id KAA27871 for ; Fri, 25 Jun 1999 10:06:22 +1000 (EST) Received: (from ggm@localhost) by azure.dstc.edu.au (8.8.5/8.8.4) id KAA16826 for freebsd-current@FreeBSD.ORG; Fri, 25 Jun 1999 10:06:22 +1000 (EST) Date: Fri, 25 Jun 1999 10:06:22 +1000 (EST) From: George Michaelson Message-Id: <199906250006.KAA16826@azure.dstc.edu.au> To: freebsd-current@FreeBSD.ORG Subject: a few comments on make release Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1) a cross-reference to http://www.freebsd.org/FAQ/FAQ243.html#246 in the docs in /usr/src/release is useful! how about adding one to the Makefile 2) you can't always do a make release without 1:1 agreement between your runtime state and the CVS and /usr/src repositaries being used to do make release as an example, the re-integration of vinum exposed a Make failure copying nonexistant vinum.ko into the release build. re-cvsupping, and then make buildworld/installworld before make release should fix it. 3) now that CDburners are 10 a penny, pointers to how to cut the outcomes of make release to CD (even if pitifully simple) would be useful. cheers -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 19: 4:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id 1CA9E14E25 for ; Thu, 24 Jun 1999 19:04:49 -0700 (PDT) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.9.3/8.9.3) id WAA09632; Thu, 24 Jun 1999 22:04:15 -0400 (EDT) (envelope-from sjr) Message-Id: <199906250204.WAA09632@istari.home.net> Date: Thu, 24 Jun 1999 22:04:15 -0400 (EDT) From: "Stephen J. Roznowski" Subject: Re: place of logfile for cron (PR 7682) To: nick.hibma@jrc.it Cc: freebsd-current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Jun, Nick Hibma wrote: > > The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log. > The FreeBSD style is to put those things in /var/log (/var/log/cron). > > Anyone any opinions on this? Which scripts depend on that location? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=7682 I agree with you. I submitted a similiar PR in January: http://www.freebsd.org/cgi/query-pr.cgi?pr=9292 Whatever the decision, if your PR is closed, this one should be also. -- Stephen J. Roznowski (sjr@home.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 19:28:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 46DC014E25 for ; Thu, 24 Jun 1999 19:28:48 -0700 (PDT) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id TAA40481 for current@FreeBSD.org; Thu, 24 Jun 1999 19:29:11 -0700 (PDT) (envelope-from ulf) Message-ID: <19990624192911.B21287@TelcoSucks.org> Date: Thu, 24 Jun 1999 19:29:11 -0700 From: Ulf Zimmermann To: current@FreeBSD.org Subject: CTM machine (chi.Alameda.net) Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The machine itself is back up. Services are being restored currently. The machine has now a 12GB vinum filesystem for /ctm and should not run out of space so fast again. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 19:43:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from jason.freegaypix.com (www.freegaypix.com [216.65.3.226]) by hub.freebsd.org (Postfix) with ESMTP id CDBB215536 for ; Thu, 24 Jun 1999 19:43:43 -0700 (PDT) (envelope-from webmaster@jmsinternet.com) Received: from jason-s-pc (we-24-30-100-131.we.mediaone.net [24.30.100.131]) by jason.freegaypix.com (8.9.2/8.9.2) with SMTP id TAA04885 for ; Thu, 24 Jun 1999 19:45:43 -0700 (PDT) (envelope-from webmaster@jmsinternet.com) Message-Id: <4.1.19990624194249.00a674a0@mail.sirius.com> X-Sender: jms@mail.jmsinternet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 24 Jun 1999 19:42:59 -0700 To: freebsd-current@FreeBSD.ORG From: JMS Internet Subject: Intel Pro 100+ Server Adapter Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently purchased a Intel Pro 100+ Server Adapter for my FreeBSD machine (3.1), but I can't find any information if it is supported, or not... I'm also not sure which driver I would use for it.. Intel's site, and the FreeBSD site have no information regarding this adaptor's compatibility with FreeBSD... Anyone's help would be greatly appreciated... I need to install this adapter or get another one by Monday... I currently use a Intel Etherexpress 10/100... If these would be the same, I should have no problems... Thanks guys... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 24 20:16:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id 67EDC1555C for ; Thu, 24 Jun 1999 20:16:35 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id LAA16480 for ; Fri, 25 Jun 1999 11:15:26 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id LAA08319 for ; Fri, 25 Jun 1999 11:16:31 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id LAA17664; Fri, 25 Jun 1999 11:16:31 +0800 Message-Id: <199906250316.LAA17664@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: KLD cdev example doesn't work anymore Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Jun 1999 11:16:30 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a long absence, I was just about to get into my new joystick drivers when it now fails to compile. What's the recommended change? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 0:24:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id B389914DCC for ; Fri, 25 Jun 1999 00:24:21 -0700 (PDT) (envelope-from michaelc@tmbbwmc.bbn.hp.com) Received: from hpbbse.bbn.hp.com (root@hpbbse.bbn.hp.com [15.136.26.26]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id AAA26112 for ; Fri, 25 Jun 1999 00:24:10 -0700 (PDT) Received: from tmbbwmc.bbn.hp.com (michaelc@tmbbwmc.bbn.hp.com [15.138.27.161]) by hpbbse.bbn.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3) id IAA11275 for ; Fri, 25 Jun 1999 08:24:03 +0100 (MEZ) Received: from localhost (michaelc@localhost) by tmbbwmc.bbn.hp.com (8.8.6/8.8.6) with ESMTP id JAA16760 for ; Fri, 25 Jun 1999 09:23:51 +0200 (METDST) Date: Fri, 25 Jun 1999 09:23:51 +0200 (METDST) From: Michael Class To: freebsd-current@FreeBSD.ORG Subject: Re: New ATA stuff, questions and comment In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 23 Jun 1999, Doug wrote: > > > First a question, namely what is the current state of the ATA > > drivers in -current? Are they reliable (where "reliable" goes by -current > > terms obviously)? I finally am in a position to test them with a new > > workstation that has IDE disks, so I thought I'd give it a go. > I am using the new ATA-drivers for quite some time now. On a home-PC they work great. On my Laptop (Omnibook 5700) they only work if I change the code to not switch-on Generic DMA-Support. Basically I change the code in ata-dma.c::ata_dmainit at the very to NOT switch on generic DMA-mode even if the drive claims that it could do DMA. The Notebook has an "TOSHIBA MK2101MAN/B1.06 D" / piomode=4, dmamode=2, udmamode=1. The old wd-driver DMA did not work for this machine, but fortunately it was not switched on by default. This needs to be configurable before the the new ATA-drivers are made the default! Otherwise I am very happy with these drivers. Michael ___________________________________________________________________________ Michael Class E-Mail: michael_class@hp.com E-Business Solution Division Phone: +49 7031 14-3707 Fax: +49 7031 14-4196 ___________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 1: 5:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 912D914D33 for ; Fri, 25 Jun 1999 01:05:46 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA20018; Fri, 25 Jun 1999 10:05:33 +0200 (MET DST) Date: Fri, 25 Jun 1999 10:05:30 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.ORG Subject: Re: KLD cdev example doesn't work anymore In-Reply-To: <199906250316.LAA17664@ariadne.tensor.pgs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG find /usr/src -name \*.c | xargs grep DEV_DRIVER_MODULE and check the changes on that file. For your reference, the changes that have recently been made to ugen.c with respect to the cdevsw thingies: RCS file: /home/ncvs/src/sys/dev/usb/ugen.c,v retrieving revision 1.12 retrieving revision 1.16 diff -u -r1.12 -r1.16 --- ugen.c 1999/04/16 21:22:00 1.12 +++ ugen.c 1999/05/30 16:51:46 1.16 @@ -1,5 +1,5 @@ /* $NetBSD: ugen.c,v 1.11 1999/01/08 11:58:25 augustss Exp $ */ -/* $FreeBSD: src/sys/dev/usb/ugen.c,v 1.12 1999/04/16 21:22:00 peter Exp $* / +/* $FreeBSD: src/sys/dev/usb/ugen.c,v 1.16 1999/05/30 16:51:46 phk Exp $ * / /* * Copyright (c) 1998 The NetBSD Foundation, Inc. @@ -121,10 +121,25 @@ #define UGEN_CDEV_MAJOR 114 static struct cdevsw ugen_cdevsw = { - ugenopen, ugenclose, ugenread, ugenwrite, - ugenioctl, nostop, nullreset, nodevtotty, - ugenpoll, nommap, nostrat, - "ugen", NULL, -1 + /* open */ ugenopen, + /* close */ ugenclose, + /* read */ ugenread, + /* write */ ugenwrite, + /* ioctl */ ugenioctl, + /* stop */ nostop, + /* reset */ noreset, + /* devtotty */ nodevtotty, + /* poll */ ugenpoll, + /* mmap */ nommap, + /* strategy */ nostrategy, + /* name */ "ugen", + /* parms */ noparms, + /* maj */ UGEN_CDEV_MAJOR, + /* dump */ nodump, + /* psize */ nopsize, + /* flags */ 0, + /* maxio */ 0, + /* bmaj */ -1 }; #endif @@ -141,8 +156,8 @@ usbd_status ugen_set_interface __P((struct ugen_softc *, int, int)); int ugen_get_alt_index __P((struct ugen_softc *sc, int ifaceidx)); -#define UGENUNIT(n) (((n) >> 4) & 0xf) -#define UGENENDPOINT(n) ((n) & 0xf) +#define UGENUNIT(n) ((minor(n) >> 4) & 0xf) +#define UGENENDPOINT(n) (minor(n) & 0xf) USB_DECLARE_DRIVER(ugen); @@ -997,6 +1012,6 @@ return 0; } -CDEV_DRIVER_MODULE(ugen, uhub, ugen_driver, ugen_devclass, - UGEN_CDEV_MAJOR, ugen_cdevsw, usbd_driver_load, 0); +DEV_DRIVER_MODULE(ugen, uhub, ugen_driver, ugen_devclass, + UGEN_CDEV_MAJOR, NOMAJ, ugen_cdevsw, usbd_driver_load, 0); #endif Nick On Fri, 25 Jun 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > After a long absence, I was just about to get into my new joystick drivers > when it now fails to compile. What's the recommended change? > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 1:12:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 91FE114D33 for ; Fri, 25 Jun 1999 01:12:14 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA29199; Fri, 25 Jun 1999 10:10:56 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906250810.KAA29199@freebsd.dk> Subject: Re: New ATA stuff, questions and comment In-Reply-To: from Michael Class at "Jun 25, 1999 9:23:51 am" To: michaelc@tmbbwmc.bbn.hp.com (Michael Class) Date: Fri, 25 Jun 1999 10:10:56 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Michael Class wrote: > > On Wed, 23 Jun 1999, Doug wrote: > > > > > First a question, namely what is the current state of the ATA > > > drivers in -current? Are they reliable (where "reliable" goes by -current > > > terms obviously)? I finally am in a position to test them with a new > > > workstation that has IDE disks, so I thought I'd give it a go. > > > > I am using the new ATA-drivers for quite some time now. On a home-PC > they work great. On my Laptop (Omnibook 5700) they only work if I > change the code to not switch-on Generic DMA-Support. Basically I > change the code in ata-dma.c::ata_dmainit at the very to NOT switch > on generic DMA-mode even if the drive claims that it could do DMA. > The Notebook has an > "TOSHIBA MK2101MAN/B1.06 D" / piomode=4, dmamode=2, udmamode=1. > > The old wd-driver DMA did not work for this machine, but fortunately > it was not switched on by default. This needs to be configurable before > the the new ATA-drivers are made the default! That an area that I havn't quite decided on yet, but I'm aware of the potential problems (in fact I chose the default to find out how severe a problem this might be). > Otherwise I am very happy with these drivers. Thanks! -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 1:15: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 4AFAF14D33 for ; Fri, 25 Jun 1999 01:15:02 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id BAA11748 for ; Fri, 25 Jun 1999 01:15:02 -0700 (PDT) Date: Fri, 25 Jun 1999 01:15:02 -0700 (PDT) From: Julian Elischer To: current@freebsd.org Subject: Re: Microsoft performance (was: ...) (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some interesting comments from an interesting source. BTW. I'd appreciate it if everyone noticed how friendly and helpful Linus is and Not find some thing to rag on linux about with this. The aim of this thread is to improve FreeBSD in any way we see as being a real improvement. Don't cc him back into the topic. I'm sure he has enough to worry about. This is FYI only ok? ---------- Forwarded message ---------- Date: Fri, 25 Jun 1999 00:51:10 -0700 (PDT) From: Linus Torvalds To: Sean Eric Fagan Cc: Julian Elischer Subject: Re: Microsoft performance (was: ...) On Thu, 24 Jun 1999, Sean Eric Fagan wrote: > > Not sure if you've seen this stuff before; thought you might find it > interesting if not. (This is not intended to be anything other than, "NT > performs surprisingly well" :).) Indeed (Julian cc'd). We had this taught to us the hard way with the mindcraft benchmark. NT scales VERY well for netbench. It became pretty obvious pretty quickly that it's one of their basic benchmarks, and it's what they have optimized NT and IIS for. Fair enough - netbench may not be the best benchmark out there, but there isn't anything better. Julian, feel free to forward my comments to anybody, for whatever they are worth. > Ok well here are some real numbers for you.. > Win NT 4processors 1GB ram + raid array + IIS > webbench... 4000 transactions per second... > > FreeBSD.. Identical hardware.. > 1450 transactions per seccond > Linux: 2000 per second > Solaris86 6000 per second The major problem with webbench is apache, although the OS _does_ matter. The webbench overhead is largely the socket timeouts and you have to do accept() right scalability-wise. I suspect NT just doesn't do the timewait stuff at all, but I could be wrong. We ended up doing the accept() thing in Linux (waking up just one thread), even though I personally think it doesn't have that big an impact in real life. It was easy enough to do. Once you get over that, the numbers seem to be just purely about scaling the fs and network, but I never got interested enough to check more into it. The netbench load was more interesting in that area, and we ended up having a benchmark that didn't have the apache overhead so it was a "purer" benchmark anyway. AND it was what NT did really well on, so.. The apache guys are definitely looking at a new threading model, you might try to approach Dean Gaudet and ask him what he's up to. That, together with the scalaibility stuff, should hopefully be enough. NT didn't do _that_ well on this one. And btw, if you're feeling bad about the numbers above: C'T in Germany did a similar kind of benchmark which was more UNIX-oriented, with perl CGI scripts etc, and NT did really badly on it. Another case of NT being optimized for one thing, and one thing only. Oh, except that if you do the "MS CGI" (whetever they call they built-in modules), NT actually does that pretty well - built in to IIS. So it's not even "dynamic content" - it's really about what _kind_ of CGI you do. > With Netbench: > NT blows us away. Netbench is the big thing for NT. And the numbers you quote are the "bad" NT numbers (ie bad enough that Linux actually was able to inch ahead of NT). The _good_ NT numbers are three times as good, but they are done with (a) NT running FATFS, (b) w98 clients exclusively. > (we're talking an order of magnitude faster) > I'm not going ot give real numbers as I don't have them readily at hand > but they are something like 12MB/Sec for FreeBSD vs 90 MB/sec for NT and > 120MB/sec for linux. Matt has some patches that raise the 12 to 35 and > kirk has some changes that may raise the numbers to 70 or more, > and John has some patches that may add more again, but it's all theory, > and some of the patches have had less results than we expected. Qutoe frankly, to get close to NT, you have to scale really well to four CPU's. We've had the core "deep SMP people" working on this for the last month, and we _finally_ have a system that seems to scale pretty well: well enough that we think we can beat the _good_ NT numbers too. Or at least come so close as to not matter any more. When I say scale really well, I mean it. You need to (a) make sure your disk never does anything at all, and (b) make sure that you get almost perfect scaling for cached reads and writes. That's what NT comes pretty close to doing, it seems. The new Linux code has a per-page lock on the page cache, and pretty much nothing else. And I don't think you can beat NT with anything less. > With Uniprocessor things are a lot more equal. > but we still suck on netbench. If you suck on netbench even on UP, the most likely reason is just that you're doing too much IO. You can make a noticeable portion of the load go away by trying to keep dirty state in memory, and making sure that unlink() removes the dirty state without ever writing it out. That doesn't get rid of the problem (the netbench load is large enough that it doesn't fit in 1GB - each part of it would fit, but if you actually do the clients concurrently their combined working set is more than you can cache). The way to cheat on netbench _seems_ to be to actually serialize the client accesses - doing a few clients at a time, and letting the clients remove their own crud and avoiding the writeouts because the files got unlinked. That's what it looked like from our analysis, anyway. That way you can cache the whole working set because you do it piece-meal. HOWEVER - NT doesn't actually seem to cheat that way, so we never pursued that as a venue either (I'd feel really bad if the only way I could beat NT was through cheating). I just thought I'd bring it up as an example of how bad a benchmark it really is. > This is due to the exact form of netbench which is exactly nonoptimal for > FreeBSD. netbench really is a horrible benchmark. I don't know what the FreeBSD tuning parameters are, but if you can avoid flushing dirty buffers that will help. Try it (it will make interactive performance suck, but hey, it's a benchmark, not real life). > Also becaosue of the GKL (Giant Kernel Lock) (see Solaris's results) That's the big one. We're seeing a factor of 2.5 on a four-way. It's not a four-time increase, but it seems to become memory bus limited at that point. I'll warn you: we were able to get rid of the big kernel lock around the filesystem reasonably quickly, but that was mainly because we had all the infrastructure in place (that's what Linux-2.2 was all about - in Linux-2.2 the kernel lock is still heavily used, but it's not really a fundamental requirement any more). Even so, it wasn't exactly painless. We had to change the page cache quite extensively, even though I originally tried to design the page cache exactly for something like this. The networking layer also needs to scale. I refused to put as much effort into that, because I don't think that 4 100Mbps ethernet cards are all that realistic - it's much more realistic to have a single gigabit card and a switch for this kind of server, so I feel that for the networking most of the scalability is in the end going to be limited by the IO. On the filesystem side, I decided that the cache really has to scale perfectly. > Basically there are some applications and benchmarks for which FreeBSD > will really suck. We're working on them but some things are just a result > of how we do things. > > So don't assume that NT figures must be bad.. > we have too many weaknesses in our own code to throw stones. I was certainyl surprised by how well NT does. NT does reasonably well in another area too: writing back data through a shared file mapping was one of the few benchmarks NT actually _won_ against both Solaris and Linux on lmbench. We fixed it in the meantime, but the point being that there _are_ things that NT does well. However, I still feel pretty confident in that the "NT does this really well" category does seem to be a matter of a few special things that they have worked on a lot rather than anything "good across the board due to a kick-ass design" kind of goodness. So I do feel pretty good, and I do believe that I'll be able to release a new version of Linux by the end of the year that actually outperforms NT on the things it seems to shine on. I'm waiting with interest to see what the next benchmark the MS people are going to find that they do better on. They've obviously started to look for benchmarks to do that they do well on.. > It'd be intersting to see how FreeBSD 1.1.5 would have performed on the > same tests. Sometimes we've gained in general performance but lost in > some specific cases. I don't think you'll find that you'd do very differently on either NetBench or WebBench, unless you've really been working on the parts that they test. But I'd be happy to share what we found out when we were trying to figure out exactly how NT was able to do so much better.. Linus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 2: 5:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9777815605 for ; Fri, 25 Jun 1999 02:04:55 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA29319 for current@freebsd.org; Fri, 25 Jun 1999 11:04:54 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906250904.LAA29319@freebsd.dk> Subject: UPDATE9: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Fri, 25 Jun 1999 11:04:54 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nine'th update to the new ATA/ATAPI driver: The atapi subsystem has gotten better error handeling and timeouts, it also tries a REQUEST SENSE command when devices returns errors, to give a little more info as to what went wrong. It might be a little verbose for now, but I'm interested in as much feedback on errors as possible, especially timeouts, as I'm a bit in doubt if I've chosen resonable default values everywhere. The disk driver has been changed a bit to prepare for tagged queing, which is next on my list. The disk driver has grown a dump routine, I got one implementation from Darrell Anderson which also did partial dumps (usefull on big memory machines) I left out the partial stuff for now, and changed the rest alot to fit into the new ad_request framework. Some minor cleanups and rearrangements as well. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. Especially the DMA support can hose your disk real bad if anything goes wrong, again you have been warned :) Notebook owners should be carefull that their machines dont suspend as this might cause trouble... But please tell me how it works for you! Enjoy! -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 3:32:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 05A721557A for ; Fri, 25 Jun 1999 03:32:39 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id NAA11962; Fri, 25 Jun 1999 13:32:14 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 280F31F6B; Fri, 25 Jun 1999 13:32:36 +0300 (EEST) Date: Fri, 25 Jun 1999 13:32:36 +0300 From: Vallo Kallaste To: JMS Internet Cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel Pro 100+ Server Adapter Message-ID: <19990625133236.B9981@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <4.1.19990624194249.00a674a0@mail.sirius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <4.1.19990624194249.00a674a0@mail.sirius.com>; from JMS Internet on Thu, Jun 24, 1999 at 07:42:59PM -0700 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 24, 1999 at 07:42:59PM -0700, JMS Internet wrote: > I recently purchased a Intel Pro 100+ Server Adapter > for my FreeBSD machine (3.1), but I can't find any information if it is > supported, > or not... I'm also not sure which driver I would use for it.. Intel's > site, and the FreeBSD It's probably an 82559 chip based card. The management features aren't supported I guess but otherwise works well with fxp driver. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 4: 4:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 08DEA15662 for ; Fri, 25 Jun 1999 04:04:25 -0700 (PDT) (envelope-from fanf@demon.net) Received: by noc.demon.net; id MAA10278; Fri, 25 Jun 1999 12:04:24 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma010255; Fri, 25 Jun 99 12:04:09 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10xTm8-00015z-00; Fri, 25 Jun 1999 12:04:04 +0100 To: current@freebsd.org From: Tony Finch Subject: Re: FreeBSD on Merced In-Reply-To: <930242270.19444.219@excite.com> Message-Id: Date: Fri, 25 Jun 1999 12:04:04 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG john_wilson100@excite.com wrote: > >Are there any plans to port FreeBSD to the IA-64 architecture when it >comes out? The docs have recently been released > http://developer.intel.com/design/ia64/architecture.htm >so I was wondering if anyone had a chance to look at the stuff. When I looked a couple of weeks ago they had not yet released docs on the OS parts of the processor -- memory management, privileged modes, etc. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Winner, International Obfuscated C Code Competition 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 5:59:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 4334314C09 for ; Fri, 25 Jun 1999 05:59:22 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id IAA19498; Fri, 25 Jun 1999 08:59:22 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA11800; Fri, 25 Jun 1999 08:58:51 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id IAA49901; Fri, 25 Jun 1999 08:58:51 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199906251258.IAA49901@bb01f39.unx.sas.com> Subject: Re: a few comments on make release In-Reply-To: From George Michaelson at "Jun 25, 1999 10: 6:22 am" To: freebsd-current@freebsd.org Date: Fri, 25 Jun 1999 08:58:51 -0400 (EDT) Cc: ggm@dstc.edu.au (George Michaelson) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1) a cross-reference to http://www.freebsd.org/FAQ/FAQ243.html#246 > in the docs in /usr/src/release is useful! > > how about adding one to the Makefile > > 2) you can't always do a make release without 1:1 agreement between > your runtime state and the CVS and /usr/src repositaries being used > to do make release > > as an example, the re-integration of vinum exposed a Make failure > copying nonexistant vinum.ko into the release build. > > re-cvsupping, and then make buildworld/installworld before > make release should fix it. > > 3) now that CDburners are 10 a penny, pointers to how to cut the outcomes > of make release to CD (even if pitifully simple) would be useful. Assuming you are doing a make release, how about: #!/bin/sh -e export SNAP=3.2-RELEASE export SNAP=4.0-19990622-SNAP export RUN_MAKECDFS=YES cd /cdwork && rm -rf disc1 cd /pub/FreeBSD/${SNAP}/cdrom && \ tar -cf - disc1 | (cd /cdwork && tar -xvf -) cd /cdwork/disc1 && mkdir XF86333 cd /pub/FreeBSD/${SNAP}/XF86333 && \ tar -cf - . | (cd /cdwork/disc1/XF86333 && tar -xvf -) if [ ${RUN_MAKECDFS} = "YES" ]; then # # Create a bootable cdrom containing the distribution # cd /cdwork && rm -f cd1.image sh /usr/share/examples/worm/makecdfs.sh \ -b "${SNAP}" /cdwork/disc1 /cdwork/cd1.image \ "${SNAP} (c) FreeBSD" fi # # Burn it # #cd /cdwork && cdrecord dev=6,0 speed=4 -v -prcap -dummy cd1.image > > cheers > -George > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ------------------------------ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 9:22:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9E8A814F22; Fri, 25 Jun 1999 09:22:29 -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 JAA05132; Fri, 25 Jun 1999 09:22:28 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA39467; Fri, 25 Jun 1999 09:22:28 -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 Date: Fri, 25 Jun 1999 09:22:28 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: archie@freebsd.org Subject: traceroute breakage in -current Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed that traceroute in -current is starting its probes with port 1 instead of 33435 as it is supposed to do: tcpdump: listening on fxp0 09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1] 09:05:03.532569 206.213.73.12.38947 > 204.216.27.21.2: udp 12 [ttl 1] 09:05:03.533400 206.213.73.12.38947 > 204.216.27.21.3: udp 12 [ttl 1] 09:05:03.534319 206.213.73.12.38947 > 204.216.27.21.4: udp 12 09:05:03.559521 206.213.73.12.38947 > 204.216.27.21.5: udp 12 09:05:03.581135 206.213.73.12.38947 > 204.216.27.21.6: udp 12 09:05:03.603108 206.213.73.12.38947 > 204.216.27.21.7: udp 12 09:05:03.628822 206.213.73.12.38947 > 204.216.27.21.8: udp 12 09:05:03.650996 206.213.73.12.38947 > 204.216.27.21.9: udp 12 09:05:03.673285 206.213.73.12.38947 > 204.216.27.21.10: udp 12 It broke in revision 1.9 of "src/contrib/traceroute/traceroute.c". John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 9:40:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id C95C915656; Fri, 25 Jun 1999 09:40:47 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id KAA01742; Fri, 25 Jun 1999 10:40:44 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199906251640.KAA01742@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.org, tech-kern@FreeBSD.org, tech@openbsd.org Subject: Changing the semantics of splsoftclock() Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Jun 1999 10:40:44 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've come across several instances where I need to fiddle with state that is also touched by a timeout handler. From a naming standpoint, splsoftclock() sounds like the correct spl routine to use for protecting these activities. Unfortunately this only holds true if splsoftclock() is used in a process context where the fact that it may actually lower the ipl to softclock is not an issue. As it currently stands, in most cases you can rely on the fact that any spl level will also block callouts, but this seems risky. What I'd like to see happen is for either the semantics of splsoftclock() to change, or to have a new spl introduced (splcallout()??). The hope is to provide a consistent interface across all *BSDs which is why I've addressed this to all of the *BSD projects. I look forward to you input on this proposal. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 9:52:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 415461578B; Fri, 25 Jun 1999 09:52:14 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id KAA01780; Fri, 25 Jun 1999 10:52:12 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199906251652.KAA01780@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 Cc: current@FreeBSD.org, tech-kern@FreeBSD.org, tech@openbsd.org Subject: Re: Changing the semantics of splsoftclock() In-reply-to: Your message of "Fri, 25 Jun 1999 10:40:44 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Jun 1999 10:52:11 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've come across several instances where I need to fiddle with state that is also touched by a timeout handler. From a naming standpoint, splsoftclock() sounds like the correct spl routine to use for protecting these activities. Unfortunately this only holds true if splsoftclock() is used in a process context where the fact that it may actually lower the ipl to softclock is not an issue. As it currently stands, in most cases you can rely on the fact that any spl level will also block callouts, but this seems risky. What I'd like to see happen is for either the semantics of splsoftclock() to change, or to have a new spl introduced (splcallout()??). The hope is to provide a consistent interface across all *BSDs which is why I've addressed this to all of the *BSD projects. I look forward to you input on this proposal. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 9:53:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 80F6415746 for ; Fri, 25 Jun 1999 09:53:31 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id KAA01796; Fri, 25 Jun 1999 10:53:25 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199906251653.KAA01796@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.org, tech-kern@NetBSD.org, tech@openbsd.org Subject: Changing the semantics of splsoftclock() Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Jun 1999 10:53:25 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Sorry for the duplicate message for some of you. I botched the headers on the original mail. ] I've come across several instances where I need to fiddle with state that is also touched by a timeout handler. From a naming standpoint, splsoftclock() sounds like the correct spl routine to use for protecting these activities. Unfortunately this only holds true if splsoftclock() is used in a process context where the fact that it may actually lower the ipl to softclock is not an issue. As it currently stands, in most cases you can rely on the fact that any spl level will also block callouts, but this seems risky. What I'd like to see happen is for either the semantics of splsoftclock() to change, or to have a new spl introduced (splcallout()??). The hope is to provide a consistent interface across all *BSDs which is why I've addressed this to all of the *BSD projects. I look forward to you input on this proposal. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 10:17:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8B4CF14D09; Fri, 25 Jun 1999 10:17:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA27119; Fri, 25 Jun 1999 10:17:32 -0700 Date: Fri, 25 Jun 1999 10:15:55 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: current@FreeBSD.ORG, tech-kern@FreeBSD.ORG, tech@openbsd.org Subject: Re: Changing the semantics of splsoftclock() In-Reply-To: <199906251640.KAA01742@caspian.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why have splr semantics? That is, it raises to splsoftclock if current priority is lower, else doesn't fiddle with it. On Fri, 25 Jun 1999, Justin T. Gibbs wrote: > I've come across several instances where I need to fiddle with state that > is also touched by a timeout handler. From a naming standpoint, > splsoftclock() sounds like the correct spl routine to use for protecting > these activities. Unfortunately this only holds true if splsoftclock() > is used in a process context where the fact that it may actually lower > the ipl to softclock is not an issue. As it currently stands, in most > cases you can rely on the fact that any spl level will also block callouts, > but this seems risky. What I'd like to see happen is for either the > semantics of splsoftclock() to change, or to have a new spl introduced > (splcallout()??). The hope is to provide a consistent interface across > all *BSDs which is why I've addressed this to all of the *BSD projects. > I look forward to you input on this proposal. > > -- > Justin > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 10:28:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (Postfix) with ESMTP id B8A16155B8 for ; Fri, 25 Jun 1999 10:28:16 -0700 (PDT) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id KAA01378; Fri, 25 Jun 1999 10:28:02 -0700 Date: Fri, 25 Jun 1999 10:28:02 -0700 (PDT) From: Neal Westfall To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE9: ATA/ATAPI driver new version available. In-Reply-To: <199906250904.LAA29319@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trying the updated driver, I notice that the first time I try to mount the cdrom drive, it hangs, I hit ^C and get this error: atapi_error: PREVENT_ALLOW - timeout error = 00 After that, I can mount it fine. This system is all SCSI except for the cdrom, which is a generic 6x IDE cdrom drive. Here is the relevant probes (dmesg | grep ata): ata-pci0: at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ata_command: timeout waiting for interrupt On Fri, 25 Jun 1999, Soren Schmidt wrote: > Nine'th update to the new ATA/ATAPI driver: > -- Neal Westfall | mailto:nwestfal@odc.net | http://www.odc.net/~nwestfal "What is today a matter of academic speculation begins tomorrow to move armies and pull down empires. In that second stage, it has gone too far to be combatted; the time to stop it was when it was still a matter of impassionate debate." -- J. Gresham Machen, "Christianity and Culture" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 10:28:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.harrisburgacademy.org (2093702.harrisburgacademy.org [209.3.70.2]) by hub.freebsd.org (Postfix) with ESMTP id BE90A155EF for ; Fri, 25 Jun 1999 10:28:01 -0700 (PDT) (envelope-from i.think@harrisburgacademy.org) Received: from nemox.looksharp.net ([199.224.85.244]) by www.harrisburgacademy.org (Netscape Messaging Server 3.5) with ESMTP id 348 for ; Fri, 25 Jun 1999 13:10:03 -0400 Message-ID: <3773B99C.F470D1CF@nemox.looksharp.net> Date: Fri, 25 Jun 1999 13:17:17 -0400 From: NemoX X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: accessing CD using new ATA drivers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the device node that is used to access the cdrom in ATA? /dev/acd0c doesnt seem to work, although that is the one specified in dmesg acd0: CDROM drive at ata0 as slave acd0: drive speed 4125KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked -- DISCLAIMER: Anyone sending me unsolicited commercial electronic mail will be charged a $100 fee for time spent reading it. Do NOT send this type of electronic mail to me. In reading this, you automatically agree to be subjected to these terms: US Code Title 47, Sec.227(a)(2)(B), "The term 'telephone facsimile machine' means equipment which has the capacity to transcribe text or images (or both) from an electronic signal received over a regular telephone line onto paper." By Sec.227(b)(3)(C) it is unlawful "to use any telephone facsimile machine, computer, or other device to send an unsolicited advertisement to a telephone facsimile machine." By Sec.227(b)(3)(C), a violation of Sec.227(b)(3)(C) is punishable by "an action to recover for actual monetary loss from such a violation, or to receive $500 in damages for each such violation, whichever is greater To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 10:31:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 4E15415011 for ; Fri, 25 Jun 1999 10:31:25 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id LAA01902; Fri, 25 Jun 1999 11:31:20 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199906251731.LAA01902@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: "Justin T. Gibbs" , current@FreeBSD.ORG, tech-kern@NetBSD.ORG Subject: Re: Changing the semantics of splsoftclock() In-reply-to: Your message of "Fri, 25 Jun 1999 10:15:55 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Jun 1999 11:31:20 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ I've dropped tech@openbsd.org based on a request from Theo since he cannot post back to some of these lists. ] >Why have splr semantics? That is, it raises to splsoftclock if current >priority is lower, else doesn't fiddle with it. This is what I meant to suggest, but if this is not doable, create a new spl. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 10:32:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9A38E15011 for ; Fri, 25 Jun 1999 10:32:49 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id TAA30325; Fri, 25 Jun 1999 19:32:44 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199906251732.TAA30325@freebsd.dk> Subject: Re: UPDATE9: ATA/ATAPI driver new version available. In-Reply-To: from Neal Westfall at "Jun 25, 1999 10:28: 2 am" To: nwestfal@Vorlon.odc.net (Neal Westfall) Date: Fri, 25 Jun 1999 19:32:44 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Neal Westfall wrote: > Trying the updated driver, I notice that the first time I try > to mount the cdrom drive, it hangs, I hit ^C and get this > error: > > atapi_error: PREVENT_ALLOW - timeout error = 00 > > After that, I can mount it fine. This system is all SCSI except > for the cdrom, which is a generic 6x IDE cdrom drive. Hmm, that is a little wierd since: > Here is the relevant probes (dmesg | grep ata): > > ata-pci0: at device 1.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked > ata_command: timeout waiting for interrupt It also failed here in the probe, hmm... Does it work reliably ever after then ?? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 10:40:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (Postfix) with ESMTP id 86C4E15553 for ; Fri, 25 Jun 1999 10:40:49 -0700 (PDT) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id KAA01587; Fri, 25 Jun 1999 10:40:41 -0700 Date: Fri, 25 Jun 1999 10:40:40 -0700 (PDT) From: Neal Westfall To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE9: ATA/ATAPI driver new version available. In-Reply-To: <199906251732.TAA30325@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Jun 1999, Soren Schmidt wrote: > > atapi_error: PREVENT_ALLOW - timeout error = 00 > > > > After that, I can mount it fine. This system is all SCSI except > > for the cdrom, which is a generic 6x IDE cdrom drive. > > Hmm, that is a little wierd since: > > > Here is the relevant probes (dmesg | grep ata): > > > > ata-pci0: at device 1.1 on pci0 > > ata-pci0: Busmastering DMA supported > > ata0 at 0x01f0 irq 14 on ata-pci0 > > acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master > > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked > > ata_command: timeout waiting for interrupt > > It also failed here in the probe, hmm... > > Does it work reliably ever after then ?? Seems to. I was able to tar off a directory on the cdrom to the hard drive with no errors at all. Neal -- Neal Westfall | mailto:nwestfal@odc.net | http://www.odc.net/~nwestfal "What is today a matter of academic speculation begins tomorrow to move armies and pull down empires. In that second stage, it has gone too far to be combatted; the time to stop it was when it was still a matter of impassionate debate." -- J. Gresham Machen, "Christianity and Culture" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 11: 0:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (Postfix) with ESMTP id 9D662155A5 for ; Fri, 25 Jun 1999 11:00:29 -0700 (PDT) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id LAA01936; Fri, 25 Jun 1999 11:00:21 -0700 Date: Fri, 25 Jun 1999 11:00:20 -0700 (PDT) From: Neal Westfall To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE9: ATA/ATAPI driver new version available. In-Reply-To: <199906251732.TAA30325@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the complete output of dmesg in case it is helpful: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #106: Fri Jun 25 10:00:44 PDT 1999 root@Millennium.home.lan:/usr/src/sys/compile/MILLENNIUM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199309909 Hz CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xf9ff real memory = 134217728 (131072K bytes) avail memory = 127590400 (124600K bytes) Preloaded elf kernel "kernel" at 0xc02ea000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: OPT0931 [0x3109143e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] AD_WAIT_INIT FAILED 1002 0xff mss_attach 1 at 0x530 irq 10 dma 3:5 flags 0x15 pcm1 (OPTi931 sn 0xffffffff) at 0x530-0x537 irq 10 drq 3 flags 0x15 on isa npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 isab0: at device 1.0 on pci0 ata-pci0: at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 de0: irq 9 at device 10.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:36:73:56 vga-pci0: irq 12 at device 12.0 on pci0 ncr0: irq 15 at device 13.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: W83877F chipset (NIBBLE-only) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE/ECP/ECP_RLE Probing for PnP devices on ppbus0: ppbus0: PJL,MLC,PCL,PCLXL plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master acd0: drive speed 1367KB/sec, 120KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked de0: enabling 100baseTX port ata_command: timeout waiting for interrupt Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 2014MB (4124736 512 byte sectors: 255H 63S/T 256C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) atapi_error: PREVENT_ALLOW - timeout error = 00 cd9660: RockRidge Extension cd9660: RockRidge Extension cd9660: RockRidge Extension The atapi_error was when I tried to mount it the first time after boot, and then I mounted/unmounted it 3 times with no problem. Neal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 11: 4:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id B0ED8157DB for ; Fri, 25 Jun 1999 11:04:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id LAA54757; Fri, 25 Jun 1999 11:03:58 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 25 Jun 1999 11:03:57 -0700 (PDT) From: Doug White To: "Stephen J. Roznowski" Cc: nick.hibma@jrc.it, freebsd-current@FreeBSD.ORG Subject: Re: place of logfile for cron (PR 7682) In-Reply-To: <199906250204.WAA09632@istari.home.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Jun 1999, Stephen J. Roznowski wrote: > On 24 Jun, Nick Hibma wrote: > > > > The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log. > > The FreeBSD style is to put those things in /var/log (/var/log/cron). > > > > Anyone any opinions on this? Which scripts depend on that location? > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=7682 > > I agree with you. I submitted a similiar PR in January: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=9292 > > Whatever the decision, if your PR is closed, this one should be also. Don't forget to update newsyslog.conf since newsyslog babysits the cron log. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 11:38:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 83FBE14E75 for ; Fri, 25 Jun 1999 11:38:49 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA51503 for ; Fri, 25 Jun 1999 14:38:37 -0400 (EDT) Date: Fri, 25 Jun 1999 14:38:37 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: ctm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm working on restoring ctm finally (now the disk is working, and the extra room is terrific!) I am going to do things manually for a short while, so the interval of things is going to be unpredictable, but I'd consider it a favor if, when you get a ctm, you email me directly. Keep the ctm stuff off this list as much as possible, please. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 12: 7:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 6EC2B15095 for ; Fri, 25 Jun 1999 12:07:38 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA21389 for ; Fri, 25 Jun 1999 12:07:37 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 25 Jun 1999 12:07:36 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: freebsd-current@freebsd.org Subject: 'make all' in /sys/i386/boot fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was working on my com console stuff and when I went into /sys/i386/boot and did a 'make all install clean' to rebuild my boot blocks (after changing /etc/make.conf) it fails due to an error in the netboot sub directory. I don't need netboot so I just deleted it temporarily in the makefile, but I thought that y'all would want to know. If I get no comments on this I'll file a PR. 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-current" in the body of the message From owner-freebsd-current Fri Jun 25 13:13:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 43ECD15095 for ; Fri, 25 Jun 1999 13:13:21 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA03515 for ; Fri, 25 Jun 1999 13:13:21 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 25 Jun 1999 13:13:20 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: freebsd-current@freebsd.org Subject: boot -P AND autoboot possible? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I set up a serial console on my -current box and putting "-P" in /boot.config worked just fine, but I'd really like to use the new loader and such, plus according to the man page for loader /boot.config is deprecated. The only problem is I couldn't figure out where exactly this option should go. I tried a lot of things, none of which worked. In an ideal world what I'd like to have is the autoboot prompt with a delay, and then boot -P. Is this even possible? And is there any move to improving the documentation for the new loader stuff, or is it still in transition? I can submit patches for the man page(s) if I can get a grip on what's happening where (and when). :-/ What I'd really like to see is a chronological listing, like: First, foo happens Here are the options for "foo," they go in the "foo.conf" file Next, bar happens Here are the options for "bar," they go in the "bar.conf" file, but can be overriden with the "bar.rc" file... Etc. The current man pages come close to this, but I still get lost going back and forth between the various pages. Any comments, pointers to docs, etc. welcome. Thanks, 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-current" in the body of the message From owner-freebsd-current Fri Jun 25 15: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9FDD91559F for ; Fri, 25 Jun 1999 15:02:35 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA28284 for ; Fri, 25 Jun 1999 15:02:47 -0700 Date: Fri, 25 Jun 1999 15:01:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: NT vs Linux benchmark saga continues (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It'd be interesting to see where FreeBSD stacks up.... ---------- Forwarded message ---------- Date: 25 Jun 1999 17:00:02 -0400 From: Ramana Juvvadi To: linux-kernel@vger.rutgers.edu Subject: NT vs Linux benchmark saga continues http://www.zdnet.com/pcweek/stories/news/0,4153,1015266,00.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 15: 4:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 0967B14F2F for ; Fri, 25 Jun 1999 15:04:36 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id IAA26548; Sat, 26 Jun 1999 08:04:31 +1000 (EST) To: "John W. DeBoskey" Cc: freebsd-current@freebsd.org Subject: Re: a few comments on make release In-reply-to: Your message of "Fri, 25 Jun 1999 08:58:51 -0400." <199906251258.IAA49901@bb01f39.unx.sas.com> Date: Sat, 26 Jun 1999 08:04:31 +1000 Message-ID: <11897.930348271@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cd image making code removed] Bewdiful. just what the docter ordered. thanks! -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 15: 6:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id E8B9315153; Fri, 25 Jun 1999 15:06:28 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id WAA11861; Fri, 25 Jun 1999 22:05:58 GMT Message-ID: <3773FCA9.2B9408C6@tdx.co.uk> Date: Fri, 25 Jun 1999 23:03:21 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: archie@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: traceroute breakage in -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > I just noticed that traceroute in -current is starting its probes > with port 1 instead of 33435 as it is supposed to do: > > tcpdump: listening on fxp0 > 09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1] > > It broke in revision 1.9 of "src/contrib/traceroute/traceroute.c". Thanks! - I thought I was going mad! - I've been out the office recently, so I've not had time to chase it up, but I noticed _exacltly_ the same thing... This results in my -current machine not being able to traceroute through our firewall, whereas the 2.2.X / 3.X boxes can... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 15: 9:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id D050015153 for ; Fri, 25 Jun 1999 15:09:10 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id PAA46881; Fri, 25 Jun 1999 15:08:30 -0700 (PDT) From: Archie Cobbs Message-Id: <199906252208.PAA46881@bubba.whistle.com> Subject: Re: traceroute breakage in -current In-Reply-To: <3773FCA9.2B9408C6@tdx.co.uk> from Karl Pielorz at "Jun 25, 99 11:03:21 pm" To: kpielorz@tdx.co.uk (Karl Pielorz) Date: Fri, 25 Jun 1999 15:08:29 -0700 (PDT) Cc: jdp@polstra.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Pielorz writes: > > I just noticed that traceroute in -current is starting its probes > > with port 1 instead of 33435 as it is supposed to do: > > > > tcpdump: listening on fxp0 > > 09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1] > > > > It broke in revision 1.9 of "src/contrib/traceroute/traceroute.c". > > Thanks! - I thought I was going mad! - I've been out the office recently, so > I've not had time to chase it up, but I noticed _exacltly_ the same thing... > This results in my -current machine not being able to traceroute through our > firewall, whereas the 2.2.X / 3.X boxes can... I just fixed this, so see if it works for you now. Sorry about that. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 15:28:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 930A21559E for ; Fri, 25 Jun 1999 15:28:17 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA03303; Sat, 26 Jun 1999 08:28:15 +1000 Date: Sat, 26 Jun 1999 08:28:15 +1000 From: Bruce Evans Message-Id: <199906252228.IAA03303@godzilla.zeta.org.au> To: gibbs@caspian.plutotech.com, mjacob@feral.com Subject: Re: Changing the semantics of splsoftclock() Cc: current@FreeBSD.ORG, gibbs@plutotech.com, tech-kern@NetBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>Why have splr semantics? That is, it raises to splsoftclock if current >>priority is lower, else doesn't fiddle with it. splsoftclock() has always had spllower() semantics, and its main users (kern_clock.c and kern_time.c) depend on this. FreeBSD has a precedent of not changing poor spl names because the change would be confusing: splnet() should be named splsoftnet() and splimp() should be named splnet() as in NetBSD. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 15:31:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CBAAD15716 for ; Fri, 25 Jun 1999 15:31:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA28427; Fri, 25 Jun 1999 15:31:30 -0700 Date: Fri, 25 Jun 1999 15:29:51 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bruce Evans Cc: current@FreeBSD.ORG, tech-kern@NetBSD.ORG, tech@openbsd.org Subject: Re: Changing the semantics of splsoftclock() In-Reply-To: <199906252228.IAA03303@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>Why have splr semantics? That is, it raises to splsoftclock if current > >>priority is lower, else doesn't fiddle with it. > > splsoftclock() has always had spllower() semantics, and its main users > (kern_clock.c and kern_time.c) depend on this. Okay. Then Justin's suggestion of splcallout with splr semantics makes sense? > > FreeBSD has a precedent of not changing poor spl names because the change > would be confusing: splnet() should be named splsoftnet() and splimp() > should be named splnet() as in NetBSD. I'm not sure what this means. I guess the gist is "don't change splsoftclock". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 16:51:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id ECB6E14DFA for ; Fri, 25 Jun 1999 16:51:35 -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 QAA00646; Fri, 25 Jun 1999 16:39:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906252339.QAA00646@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Cc: freebsd-current@freebsd.org Subject: Re: 'make all' in /sys/i386/boot fails In-reply-to: Your message of "Fri, 25 Jun 1999 12:07:36 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Jun 1999 16:39:05 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was working on my com console stuff and when I went into > /sys/i386/boot and did a 'make all install clean' to rebuild my boot > blocks (after changing /etc/make.conf) it fails due to an error in the > netboot sub directory. I don't need netboot so I just deleted it > temporarily in the makefile, but I thought that y'all would want to know. > If I get no comments on this I'll file a PR. sys/i386/boot is deprecated. -- \\ 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-current" in the body of the message From owner-freebsd-current Fri Jun 25 17:47:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from Tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (Postfix) with ESMTP id 386F014D3D for ; Fri, 25 Jun 1999 17:46:58 -0700 (PDT) (envelope-from bruceb@panther.austx.tandem.com) Received: from fedex.austx.tandem.com (fedex.austx.tandem.com [131.124.250.27]) by Tandem.com (8.9.3/2.0.1) with ESMTP id RAA06171 for ; Fri, 25 Jun 1999 17:46:53 -0700 (PDT) Received: from panther.austx.tandem.com (panther.austx.tandem.com [131.124.4.106]) by fedex.austx.tandem.com (8.9.0/8.9.0) with ESMTP id TAA21584 for ; Fri, 25 Jun 1999 19:46:52 -0500 (CDT) Received: (from bruceb@localhost) by panther.austx.tandem.com (8.8.5/8.7.1) id TAA17216 for freebsd-current@freebsd.org; Fri, 25 Jun 1999 19:46:14 -0500 (CDT) From: Bruce Burden Message-Id: <199906260046.TAA17216@panther.austx.tandem.com> Subject: .: Out of file descriptors ?? To: freebsd-current@freebsd.org Date: Fri, 25 Jun 1999 19:46:13 -0500 (CDT) Reply-To: bruceb@austx.tandem.com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I did a cvsup on the night of June 24/25, got the world built, installed, /etc updated, the kernel config file updated, built the kernel, updated it, and when I attempt to boot, I get the following error: .: Out of file descriptors This is shortly after the "nmging root on da1s1a" message comes out. /root is at 31%, and that after I went in and cleaned out some things (34% down to 31%), /var is in a seperate partition. Okay, I am confused. What is going on? How do I correct this situation? BTW, the system comes up in single user, so I can poke around, mount / on /dev/sd1s1a, so its not like /root is hosed. Is there some "secret" filesystem I am not aware of that might be full? If it matters (it didn't seem to) I built GENERIC in the /sys/ i386/conf directory, same error message happens. And, my last cvsup was 7 February, but I was runnnig ELF with the updated boot blocks. At least, I think I was... Thanks, Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 17:50:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id D27F115274 for ; Fri, 25 Jun 1999 17:50:47 -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 RAA00994; Fri, 25 Jun 1999 17:34:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906260034.RAA00994@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: bruceb@austx.tandem.com Cc: freebsd-current@freebsd.org Subject: Re: .: Out of file descriptors ?? In-reply-to: Your message of "Fri, 25 Jun 1999 19:46:13 CDT." <199906260046.TAA17216@panther.austx.tandem.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Jun 1999 17:34:52 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hi all, > > I did a cvsup on the night of June 24/25, got the world built, > installed, /etc updated, the kernel config file updated, built > the kernel, updated it, and when I attempt to boot, I get the > following error: > > .: Out of file descriptors You copied /etc/defaults/rc.conf to /etc/rc.conf, in spite of the clear warning in this file not to do that. Don't do that. -- \\ 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-current" in the body of the message From owner-freebsd-current Fri Jun 25 17:59:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id D5BC3154E1 for ; Fri, 25 Jun 1999 17:59:07 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id TAA18314; Fri, 25 Jun 1999 19:59:04 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <009201bebf6f$161061c0$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: , References: <199906260046.TAA17216@panther.austx.tandem.com> Subject: Re: Out of file descriptors ?? Date: Fri, 25 Jun 1999 19:59:03 -0500 Organization: West Bend Internet 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.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Bruce Burden > I did a cvsup on the night of June 24/25, got the world built, > installed, /etc updated, the kernel config file updated, built > the kernel, updated it, and when I attempt to boot, I get the > following error: > > .: Out of file descriptors > Check the bottom of your /etc/rc.conf file for: for i in ${rc_conf_files}; do if [ -f $i ]; then . $i fi done What is happening is /etc/defaults/rc.conf pulls in /etc/rc.conf, which then pulls in /etc/rc.conf .... repeat until we run out of file descriptors. You need to remove the above code from the /etc/rc.conf file. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 18:46:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id AD24814DAE for ; Fri, 25 Jun 1999 18:46:33 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id SAA01197; Fri, 25 Jun 1999 18:46:05 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 25 Jun 1999 18:46:05 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: 'make all' in /sys/i386/boot fails In-Reply-To: <199906252339.QAA00646@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Jun 1999, Mike Smith wrote: > > I was working on my com console stuff and when I went into > > /sys/i386/boot and did a 'make all install clean' to rebuild my boot > > blocks (after changing /etc/make.conf) it fails due to an error in the > > netboot sub directory. I don't need netboot so I just deleted it > > temporarily in the makefile, but I thought that y'all would want to know. > > If I get no comments on this I'll file a PR. > > sys/i386/boot is deprecated. Ok, well actually that could explain why it didn't work then. :) Where would I go if I wanted to rebuild my boot blocks to make the com console run at a different speed, or is this something I could set with one of the voluminous conf files in /boot, or?? Thanks, 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-current" in the body of the message From owner-freebsd-current Fri Jun 25 22:15:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id D6C55154FE for ; Fri, 25 Jun 1999 22:15:34 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10xkoE-000CvT-00; Sat, 26 Jun 1999 07:15:22 +0200 From: Sheldon Hearn To: Doug Cc: freebsd-current@FreeBSD.ORG Subject: Re: boot -P AND autoboot possible? In-reply-to: Your message of "Fri, 25 Jun 1999 13:13:20 MST." Date: Sat, 26 Jun 1999 07:15:21 +0200 Message-ID: <49690.930374121@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Jun 1999 13:13:20 MST, Doug wrote: > I can submit patches for the man page(s) if I can get a grip on what's > happening where (and when). :-/ What I'd really like to see is a > chronological listing, like: I think you're reading the wrong manpage. I've just had a look at loader(8) and can't really see what you'd want to improve. Can you confirm that your loader.8 DESCRIPTION starts with "The program called loader is the third stage of FreeBSD's three stage bootstrap. It is a BTX client linked statically to libstand(3) and usually located in the directory /boot." If so, then did you try the autoboot_delay option? Have you noticed the loader.conf(5) manpage? I'm pretty sure Mr Sobral's done a fairly good job with the documentation for the new boot loader. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 22:17:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E4F381546F for ; Fri, 25 Jun 1999 22:17:11 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10xkpc-000CwR-00; Sat, 26 Jun 1999 07:16:48 +0200 From: Sheldon Hearn To: Doug Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: 'make all' in /sys/i386/boot fails In-reply-to: Your message of "Fri, 25 Jun 1999 18:46:05 MST." Date: Sat, 26 Jun 1999 07:16:47 +0200 Message-ID: <49750.930374207@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Jun 1999 18:46:05 MST, Doug wrote: > Where would I go if I wanted to rebuild my boot blocks to make the > com console run at a different speed, or is this something I could set > with one of the voluminous conf files in /boot, or?? Try src/sys/boot ? Tip for the future: When you next make world, copy the output to a file so that you can grep it to find out where stuff is installed out of: make world 2>&1 | tee /some/place/make_world.log Or whatever. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 25 23:35: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-44.ppp.wenet.net [206.15.85.44]) by hub.freebsd.org (Postfix) with ESMTP id 18F6B1537B for ; Fri, 25 Jun 1999 23:35:03 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id XAA00710 for ; Fri, 25 Jun 1999 23:35:05 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 25 Jun 1999 23:35:04 -0700 (PDT) From: Alex Zepeda To: current Subject: gdb no longer works? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried numerous times (updating the kernel, buildworld, etc) to get gdb to work, but so far it seems like ELF coredumps are broken (course this could be a C++ issue too): zippy:~#gdb `which konqueror` konqueror.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... Core was generated by `konqueror'. Program terminated with signal 11, Segmentation fault. Register eax not found in core file. (gdb) - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 1: 5:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 8347A14C95 for ; Sat, 26 Jun 1999 01:05:43 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id BAA03271; Sat, 26 Jun 1999 01:05:30 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <377489CB.65817350@gorean.org> Date: Sat, 26 Jun 1999 01:05:31 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: 'make all' in /sys/i386/boot fails References: <49750.930374207@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Fri, 25 Jun 1999 18:46:05 MST, Doug wrote: > > > Where would I go if I wanted to rebuild my boot blocks to make the > > com console run at a different speed, or is this something I could set > > with one of the voluminous conf files in /boot, or?? > > Try src/sys/boot ? Well that certainly looks like the right answer. Are you uncertain about it, or just being rhetorical? Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 1: 9:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 217BE14C95 for ; Sat, 26 Jun 1999 01:09:48 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10xnWK-000Ese-00; Sat, 26 Jun 1999 10:09:04 +0200 From: Sheldon Hearn To: Doug Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: 'make all' in /sys/i386/boot fails In-reply-to: Your message of "Sat, 26 Jun 1999 01:05:31 MST." <377489CB.65817350@gorean.org> Date: Sat, 26 Jun 1999 10:09:04 +0200 Message-ID: <57203.930384544@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Jun 1999 01:05:31 MST, Doug wrote: > Well that certainly looks like the right answer. Are you > uncertain about it, or just being rhetorical? The expanded version was Try src/sys/boot, which is where I found what looked very much like the new boot loader. I've now checked and it's _definitely_ src/sys/boot . Have fun. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 1:15:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcsext.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id CA7461524D for ; Sat, 26 Jun 1999 01:15:06 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1474 bytes) by hcsext.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 26 Jun 1999 10:14:32 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m10xnbX-0000fgC; Sat, 26 Jun 99 10:14 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: NT vs Linux benchmark saga continues (fwd) In-Reply-To: from Matthew Jacob at "Jun 25, 99 03:01:07 pm" To: mjacob@feral.com Date: Sat, 26 Jun 1999 10:14:27 +0200 (METDST) Cc: freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 618 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And to follow up on this topic: the german magazine c't has an article in their current issue, where they compare a real-world setup measuring web-server performance for NT an Linux both for an SMP and non-SMP setup. Linux was - depending on the setup and application - a bit to much faster ... hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 2:20:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 9551814F88 for ; Sat, 26 Jun 1999 02:20:14 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id CAA03694; Sat, 26 Jun 1999 02:20:06 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37749B46.E2CB5F82@gorean.org> Date: Sat, 26 Jun 1999 02:20:06 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: boot -P AND autoboot possible? References: <49690.930374121@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Fri, 25 Jun 1999 13:13:20 MST, Doug wrote: > > > I can submit patches for the man page(s) if I can get a grip on what's > > happening where (and when). :-/ What I'd really like to see is a > > chronological listing, like: > > I think you're reading the wrong manpage. I've just had a look at > loader(8) and can't really see what you'd want to improve. Can you > confirm that your loader.8 DESCRIPTION starts with > > "The program called loader is the third stage of FreeBSD's > three stage bootstrap. Yes, that's the one, but as you point out here we're already talking about the third stage. The problem is (as I mentioned in my request) /boot.config bypasses this stage. Various parts of the new loader are well documented, but there is no overall picture of how the various parts fit together. In any case, /sys/boot/README does a pretty good job of explaining, better than the man pages IMO. After reading it several times and a lot of experimentation, it turns out that I want to put the 'boot -P' command in /boot/loader.rc. If I include an autoboot statement, the 'boot -P' command is ignored, so it looks like there is no way to do what I want to do. Note to the boot developers, please consider this a feature request to add the functionality to both autoboot, and boot with flags (like -P). Also, the autoboot prompt message requires "quotes" around it. This is not indicated in /boot/loader.help, and the loader man page does not indicate the ability to specify the message at all. HTH, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 2:22:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (unknown [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 711F714F88 for ; Sat, 26 Jun 1999 02:22:36 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id JAA22376 for ; Sat, 26 Jun 1999 09:21:59 GMT Date: Sat, 26 Jun 1999 09:21:59 +0000 (GMT) From: Ben Rosengart To: freebsd-current@FreeBSD.ORG Subject: Re: Out of file descriptors ?? In-Reply-To: <009201bebf6f$161061c0$8dfee0d1@westbend.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Jun 1999, Scot W. Hetzel wrote: > What is happening is /etc/defaults/rc.conf pulls in /etc/rc.conf, which then > pulls in /etc/rc.conf .... repeat until we run out of file descriptors. I am not fond of the new defaults/rc.conf system. Used to be when I wanted to modify something in rc.conf, I opened it up and changed the value. Now I have to extract a line from defaults/rc.conf, put it in rc.conf, and change it -- unless I don't understand the new setup correctly. That makes more work for me, not less. What's the idea here? -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 2:45:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id F1C2414DE1 for ; Sat, 26 Jun 1999 02:45:43 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-161.skylink.it [194.185.55.161]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id LAA23296 for ; Sat, 26 Jun 1999 11:45:04 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id LAA00532 for ; Sat, 26 Jun 1999 11:42:35 +0200 (CEST) Date: Sat, 26 Jun 1999 11:42:35 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: FreeBSD current mailing list Subject: Re: place of logfile for cron (PR 7682) - move it? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that no one really has any objections to moving the log file. These would the locations to change(find | grep /var/log) src/usr.sbin/cron/cron/config.h src/usr.sbin/cron/doc/CHANGES (src/usr.sbin/cron/doc/CHANGES.FreeBSD a la xntpd?) src/etc/Makefile src/etc/newsyslog.conf src/etc/syslog.conf Plus a line in Updating. Anything I forgot? Nick On Thu, 24 Jun 1999, Nick Hibma wrote: > > The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log. > The FreeBSD style is to put those things in /var/log (/var/log/cron). > > Anyone any opinions on this? Which scripts depend on that location? > > Nick > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=7682 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 3: 1:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 427E614DDF for ; Sat, 26 Jun 1999 03:01:29 -0700 (PDT) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id TAA25161; Sat, 26 Jun 1999 19:31:04 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990626193104:34751=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: Date: Sat, 26 Jun 1999 19:31:04 +0930 (CST) From: "Daniel J. O'Connor" To: Ben Rosengart Subject: Re: Out of file descriptors ?? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990626193104:34751=_ Content-Type: text/plain; charset=us-ascii On 26-Jun-99 Ben Rosengart wrote: > rc.conf, and change it -- unless I don't understand the new setup > correctly. That makes more work for me, not less. What's the idea > here? When you upgrade and use mergemaster its a lot less work.. The new defaults for the upgrade take place automatically and your old settings are left alone. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990626193104:34751=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN3Sk4Gj0TqzKxF7VAQGryQP+PYtt+TwuyGDcMXl11fv6TZwj956THJ7R TcihBhkKkcdsTqX2CDwn4jDi/3qvI2LiEsKP5VLRnQdzTiD/nhCPSLxaHA2ETq0J 4N5M4c9VmCKqQLT58SsYIfquGkfBvWdYOd92V/u96rfeKqNY9czbeJZlvvXCTZ65 Evq5Kno6miY= =yeHS -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990626193104:34751=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 3:15:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 613AB14DDF for ; Sat, 26 Jun 1999 03:15:26 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10xpUT-000GDe-00; Sat, 26 Jun 1999 12:15:17 +0200 From: Sheldon Hearn To: Ben Rosengart Cc: freebsd-current@FreeBSD.ORG Subject: Re: Out of file descriptors ?? In-reply-to: Your message of "Sat, 26 Jun 1999 09:21:59 GMT." Date: Sat, 26 Jun 1999 12:15:17 +0200 Message-ID: <62349.930392117@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Jun 1999 09:21:59 GMT, Ben Rosengart wrote: > I am not fond of the new defaults/rc.conf system. Your objection is far too late, I'm afraid. The change makes staying STABLE and staying CURRENT much easier than it was before and has met with resounding approval, although it took a few die-hards a while to see the wisdom of it. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 6:36: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 9F00914EE9 for ; Sat, 26 Jun 1999 06:35:56 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: from scones.sup.scc.nl (i025.ztm.euronet.nl [194.134.112.26]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id PAA06047 from for ; Sat, 26 Jun 1999 15:35:52 +0200 (MET DST) Received: (from daemon@localhost) by scones.sup.scc.nl (8.9.3/8.9.3) id PAA53480 for current@FreeBSD.ORG; Sat, 26 Jun 1999 15:27:46 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by scones.sup.scc.nl with netnews for current@FreeBSD.ORG (current@FreeBSD.ORG) To: current@FreeBSD.ORG Date: Sat, 26 Jun 1999 15:27:43 +0200 From: Marcel Moolenaar Message-ID: <3774D54F.74B6F2C4@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19990624100825.G417@freebie.lemis.com>, <19990624104502.N417@freebie.lemis.com> Subject: Re: ktrace causes kernel panic Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: [snip] > >>> Using a recent (few days) -current I had a process lock up on me > >>> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > >>> while. When I issued a 'ktrace -C' in another screen, everything froze and > >>> the kernel panic'ed. I dropped to the debugger on the console and it was > >>> definintely ktrace that caused the panic. > >> [snip] > Not much. You'll need to get a dump. I got spontaneous reboots on -stable as well. That was just before my vacation. I'll try to dig into it mysel, aAs soon as I recovered from my vacation :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 6:42: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id E1F4B14EE9 for ; Sat, 26 Jun 1999 06:41:45 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id NAA07489 for ; Sat, 26 Jun 1999 13:41:42 GMT Message-ID: <3774D7F8.C6375580@tdx.co.uk> Date: Sat, 26 Jun 1999 14:39:04 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: -current breakage? (11.00 bst, 26/6/1999) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just tried building the world three times, cvsup'd at around 11.00 bst, and again at 12.00 and 13.00 - they all break at the point below... Any suggestions? :) - I was running "make buildworld -j8 | tee /var/tmp/mw.out". Each time I carefully blow away /usr/obj before re-running... -Kp " /usr/src/lib/libcam/../../sys/sys/buf.h: In function `BUF_LOCK': /usr/src/lib/libcam/../../sys/sys/buf.h: In function `BUF_LOCK': In file included from /usr/src/lib/libcam/../../sys/cam/scsi/scsi_sa.c:44: /usr/src/lib/libcam/../../sys/sys/buf.h:260: `curproc' undeclared (first use in this function) /usr/src/lib/libcam/../../sys/sys/buf.h:260: (Each undeclared identifier is reported only once /usr/src/lib/libcam/../../sys/sys/buf.h:260: for each function it appears in.) /usr/src/lib/libcam/../../sys/sys/buf.h: In function `BUF_TIMELOCK': /usr/src/lib/libcam/../../sys/sys/buf.h:274: `curproc' undeclared (first use in this function) /usr/src/lib/libcam/../../sys/sys/buf.h: In function `BUF_LOCK': In file included from /usr/src/lib/libcam/../../sys/cam/scsi/scsi_sa.c:44: /usr/src/lib/libcam/../../sys/sys/buf.h:260: `curproc' undeclared (first use in this function) /usr/src/lib/libcam/../../sys/sys/buf.h:260: (Each undeclared identifier is reported only once /usr/src/lib/libcam/../../sys/sys/buf.h:260: for each function it appears in.) In file included from /usr/src/lib/libcam/../../sys/cam/scsi/scsi_sa.c:44: /usr/src/lib/libcam/../../sys/sys/buf.h:260: `curproc' undeclared (first use in this function) /usr/src/lib/libcam/../../sys/sys/buf.h:260: (Each undeclared identifier is reported only once /usr/src/lib/libcam/../../sys/sys/buf.h:260: for each function it appears in.) /usr/src/lib/libcam/../../sys/sys/buf.h: In function `BUF_TIMELOCK': /usr/src/lib/libcam/../../sys/sys/buf.h:274: `curproc' undeclared (first use in this function) /usr/src/lib/libcam/../../sys/sys/buf.h: In function `BUF_TIMELOCK': /usr/src/lib/libcam/../../sys/sys/buf.h:274: `curproc' undeclared (first use in this function) cc -fpic -DPIC -O -pipe -I/usr/src/lib/libcam -I/usr/src/lib/libcam/../../sys -I/usr/obj/usr/src/tmp/usr/include -c /us r/src/lib/libcam/../../sys/cam/cam.c -o cam.So *** Error code 1 *** Error code 1 *** Error code 1 3 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 7:11:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from fasterix.frmug.org (d066.paris-81.cybercable.fr [212.198.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 4F08814D5C for ; Sat, 26 Jun 1999 07:11:47 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.3/8.9.3/pb-19990315) id QAA10039 for freebsd-current@freebsd.org; Sat, 26 Jun 1999 16:11:44 +0200 (CEST) Message-ID: <19990626161143.A9799@fasterix.frmug.fr.net> Date: Sat, 26 Jun 1999 16:11:43 +0200 From: Pierre Beyssac To: freebsd-current@freebsd.org Subject: kernel profiling Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.92.8i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just curious: would it be easily doable to profile the kernel by sampling the program counter, à la profil(2) but for kernel mode? Has anyone attempted to write this? -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 7:15:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 70FF914D5E; Sat, 26 Jun 1999 07:15:47 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-165.skylink.it [194.185.55.165]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id QAA28271; Sat, 26 Jun 1999 16:15:07 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id QAA01231; Sat, 26 Jun 1999 16:11:29 +0200 (CEST) Date: Sat, 26 Jun 1999 16:11:28 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing list , FreeBSD Hardware Mailing list Subject: USB project status Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Project status of the USB project: Currently under development: Rewrite of uhub driver to take full advantage of the newbus architecture. It compiles but has not been tested yet. Rewrite of umass driver to take full advantage of CAM and its 'actions', using callbacks for USB transfers (msmith's idea). This will reduce the time required to boot. (see http://www.etla.net/~n_hibma/usb/usb.pl#UMASSDriver) Support for 3Com modem model 5605 (Voice Faxmodem Pro) and for 3Com ISDN TA (provided by http://www.3com.com/) (Communications Class, Abstract Control Model (AT commandset)) (see http://www.etla.net/~n_hibma/usb/usb.pl#UCDCDriver) Support for the Y-E data floppy disk drives (drive provided by http://www.yedata.co.jp/) (Mass Storage Class, UFI/CBI Subclass) (see http://www.etla.net/~n_hibma/usb/usb.pl#UMASSDriver) Support for the Imation Superdisk LS-120 drives (Mass Storage Class, 8070i/CBI (IDE/ATAPI ?) Subclass) (see http://www.etla.net/~n_hibma/usb/usb.pl#UMASSDriver) Support for 3.2-STABLE users. To be developed: Support for Digi 2/4/8 port serial adapter AcelePort (might be provided by Digi) (proprietary interface) Bulk transfers on OHCI controllers All the while: More work on UHCI and OHCI to make transfers and transfer cancelling more reliable usbdi.h interface needs to be looked at and made consistent Header file needs rearranging, but also the set of functions in usbdi.c is incomplete. Further away: Support for scanners derived from SCSI scanners (HP) Support for isochroneous transfers on USB bus (needed for audio and video support) Support for audio devices Support for video devices Support for joysticks, gamepads and the likes Cheers, Nick Hibma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 8: 9:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from gate.keisu.t.u-tokyo.ac.jp (ns06.t.u-tokyo.ac.jp [133.11.68.1]) by hub.freebsd.org (Postfix) with SMTP id 8652F14C97 for ; Sat, 26 Jun 1999 08:09:11 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: (qmail 94192 invoked from network); 26 Jun 1999 15:09:11 -0000 Received: from sylph.sat.t.u-tokyo.ac.jp (10.6.1.20) by ns06.t.u-tokyo.ac.jp with SMTP; 26 Jun 1999 15:09:11 -0000 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by sylph.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id C580D2DAA9; Sun, 27 Jun 1999 00:09:10 +0900 (JST) Received: from ett.sat.t.u-tokyo.ac.jp by ett.sat.t.u-tokyo.ac.jp (8.9.3/sat-V0.6) id AAA45845; Sun, 27 Jun 1999 00:09:09 +0900 (JST) Date: Sun, 27 Jun 1999 00:09:08 +0900 Message-ID: <14196.60692.776168.25222H@ett.sat.t.u-tokyo.ac.jp> From: Hidetoshi Shimokawa To: pb@fasterix.freenix.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel profiling In-Reply-To: In your message of "Sat, 26 Jun 1999 16:11:43 +0200" <19990626161143.A9799@fasterix.frmug.fr.net> References: <19990626161143.A9799@fasterix.frmug.fr.net> User-Agent: Wanderlust/1.0.0 (Kokomo) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/21.2 (beta13) (Demeter) (i386-unknown-freebsd3.1) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX wrote: > > Just curious: would it be easily doable to profile the kernel by > sampling the program counter, la profil(2) but for kernel mode? > Has anyone attempted to write this? You can enable kernel profiling by configure kernel with `-p' or '-pp' option. See config(8) and kgmon(8) for detail. I have a patch for FreeBSD/alpha to support kernel profiling. -- /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 8:15:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 752E014DDF for ; Sat, 26 Jun 1999 08:15:15 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id QAA59676; Sat, 26 Jun 1999 16:17:21 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 26 Jun 1999 16:17:21 +0100 (BST) From: Doug Rabson To: Hidetoshi Shimokawa Cc: pb@fasterix.freenix.org, freebsd-current@freebsd.org Subject: Re: kernel profiling In-Reply-To: <14196.60692.776168.25222H@ett.sat.t.u-tokyo.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999, Hidetoshi Shimokawa wrote: > At Sat, 26 Jun 1999 16:11:43 +0200, > Pierre Beyssac wrote: > > > > Just curious: would it be easily doable to profile the kernel by > > sampling the program counter, la profil(2) but for kernel mode? > > Has anyone attempted to write this? > > You can enable kernel profiling by configure kernel with `-p' or '-pp' > option. See config(8) and kgmon(8) for detail. > > I have a patch for FreeBSD/alpha to support kernel profiling. Another excellent alternative for kernel profiling is iprobe. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 8:35:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from meer.meer.net (meer.meer.net [140.174.164.2]) by hub.freebsd.org (Postfix) with ESMTP id D6FAB14BE6 for ; Sat, 26 Jun 1999 08:35:12 -0700 (PDT) (envelope-from gnn@punk.neville-neil.com) Received: from punk.meer.net (punk.neville-neil.com [209.157.132.82]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id IAA18690 for ; Sat, 26 Jun 1999 08:35:11 -0700 (PDT) Received: from punk (localhost.meer.net [127.0.0.1]) by punk.meer.net (8.9.2/8.9.2) with ESMTP id IAA13137 for ; Sat, 26 Jun 1999 08:34:01 -0700 (PDT) (envelope-from gnn@punk.neville-neil.com) Message-Id: <199906261534.IAA13137@punk.meer.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Who leads networking? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Jun 1999 08:34:01 -0700 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey Folks, I'm new to contributing to FreeBSD but not to working with kernels etc. I'm thinking of adding a new framing type to PPP which is described in the latest Transactions on Networking. Who do I talk to about this kind of stuff? Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 8:41:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.mindspring.com (smtp2.mindspring.com [207.69.200.32]) by hub.freebsd.org (Postfix) with ESMTP id 6245D14BE6 for ; Sat, 26 Jun 1999 08:41:27 -0700 (PDT) (envelope-from brdean@mindspring.com) Received: from vger.foo.com (user-2ivf0b9.dialup.mindspring.com [165.247.129.105]) by smtp2.mindspring.com (8.8.5/8.8.5) with ESMTP id LAA11851 for ; Sat, 26 Jun 1999 11:41:24 -0400 (EDT) Received: (from bsd@localhost) by vger.foo.com (8.9.3/8.9.3) id LAA16019; Sat, 26 Jun 1999 11:41:27 -0400 (EDT) (envelope-from bsd) From: Brian Dean Message-Id: <199906261541.LAA16019@vger.foo.com> Subject: kernel panic w/regard to setting io permissions bitmap To: freebsd-current@freebsd.org Date: Sat, 26 Jun 1999 11:41:26 -0400 (EDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm chasing down a panic that occurs when you call 'i386_set_ioperm()' in -current (19990625-SNAP). This call worked correctly in the 19990426-SNAP. I first noticed the problem with the 6/10 snap and it's still with us as of the 6/25 snap. The panic occurs at 'swtch_com+0x6e: ltr %si'. At the time, %si is 0x20, which indexes to what appears to be a busy tss (type=01011b) with a limit of 0x67. That instruction generates a general protection fault with an error code of 0. The current process was Idle. After piecing together the base address from the descriptor (which should point to the tss), and examining its contents, it seems as though the tss is not valid, i.e., it is composed of all zeros except for esp0 and ss0 (which appear to have reasonable values) and for the io map base address, which is 0x0068 which would seem to indicate that this tss does not have an io permission bitmap. If this is correct and I didn't mess something up when piecing all this together by hand, that would explain the GP(0) fault because the segment registers were zero, which would point them to an invalid GDT entry. Perhaps someone could reproduce this and double check me? Also ... I think I could analyze this better if I could break into the debugger and set a break point *before* the panic, and start tracing at the i386_set_ioperm() routine and follow what happens from there. Is there a function call that I can insert at the appropriate place to force dropping into the kernel debugger? I can't remote debug from my second machine right now because they are running kernels that are a few months apart, and I can't upgrade my other system at the moment. Could someone point me in the right direction in this regard (dropping to the debugger before the panic)? Thanks, -Brian -- Brian Dean brdean@mindspring.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 8:57:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id ED8F214D2D for ; Sat, 26 Jun 1999 08:57:27 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id LAA58145; Sat, 26 Jun 1999 11:57:17 -0400 (EDT) (envelope-from mi) Message-Id: <199906261557.LAA58145@misha.cisco.com> Subject: Re: place of logfile for cron (PR 7682) - move it? In-Reply-To: from Nick Hibma at "Jun 26, 1999 11:42:35 am" To: Nick Hibma Date: Sat, 26 Jun 1999 11:57:17 -0400 (EDT) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma once wrote: > It seems that no one really has any objections to moving the log file. > > These would the locations to change(find | grep /var/log) > > src/usr.sbin/cron/cron/config.h > src/usr.sbin/cron/doc/CHANGES > (src/usr.sbin/cron/doc/CHANGES.FreeBSD a la xntpd?) > src/etc/Makefile > src/etc/newsyslog.conf > src/etc/syslog.conf I'd, probably, put a symlink from the old location to the new one... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 9: 1:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id A4FE914D2D for ; Sat, 26 Jun 1999 09:01:36 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id SAA01004; Sat, 26 Jun 1999 18:01:55 +0200 (CEST) To: Doug Rabson Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel profiling References: Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 26 Jun 1999 18:01:49 +0200 In-Reply-To: Doug Rabson's message of "Sat, 26 Jun 1999 16:17:21 +0100 (BST)" Message-ID: <5l3dzfdk7m.fsf@assaris.sics.se> Lines: 6 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson writes: > Another excellent alternative for kernel profiling is iprobe. Can we get a pointer? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 9: 4:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id CB68214D2D for ; Sat, 26 Jun 1999 09:04:08 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA21072; Sat, 26 Jun 1999 18:02:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Rabson Cc: Hidetoshi Shimokawa , pb@fasterix.freenix.org, freebsd-current@FreeBSD.ORG Subject: Re: kernel profiling In-reply-to: Your message of "Sat, 26 Jun 1999 16:17:21 BST." Date: Sat, 26 Jun 1999 18:02:18 +0200 Message-ID: <21070.930412938@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Do ug Rabson writes: >> You can enable kernel profiling by configure kernel with `-p' or '-pp' >> option. See config(8) and kgmon(8) for detail. >> >> I have a patch for FreeBSD/alpha to support kernel profiling. > >Another excellent alternative for kernel profiling is iprobe. Not to mention compiling with "-g -a" and using kernbb to get Basic Block profiling. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 9: 7:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9C01814D71 for ; Sat, 26 Jun 1999 09:07:08 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id RAA61945; Sat, 26 Jun 1999 17:09:41 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 26 Jun 1999 17:09:40 +0100 (BST) From: Doug Rabson To: Assar Westerlund Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel profiling In-Reply-To: <5l3dzfdk7m.fsf@assaris.sics.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Jun 1999, Assar Westerlund wrote: > Doug Rabson writes: > > Another excellent alternative for kernel profiling is iprobe. > > Can we get a pointer? There is a nice tutorial at http://www.cs.duke.edu/ari/iprobe.html. This tool is alpha specific though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 9:12:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 691CB14E73 for ; Sat, 26 Jun 1999 09:12:31 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id RAA61957; Sat, 26 Jun 1999 17:11:13 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 26 Jun 1999 17:11:13 +0100 (BST) From: Doug Rabson To: Poul-Henning Kamp Cc: Hidetoshi Shimokawa , pb@fasterix.freenix.org, freebsd-current@FreeBSD.ORG Subject: Re: kernel profiling In-Reply-To: <21070.930412938@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Jun 1999, Poul-Henning Kamp wrote: > In message , Do > ug Rabson writes: > > >> You can enable kernel profiling by configure kernel with `-p' or '-pp' > >> option. See config(8) and kgmon(8) for detail. > >> > >> I have a patch for FreeBSD/alpha to support kernel profiling. > > > >Another excellent alternative for kernel profiling is iprobe. > > Not to mention compiling with "-g -a" and using kernbb to get Basic > Block profiling. I have not tried that. Iprobe is a nice low-overhead flat profiler which can correlate time spent in both the kernel and user-mode processes. If you don't need call-graph information and are using an alpha, it is an excellent tool. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 9:27:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from meer.meer.net (meer.meer.net [140.174.164.2]) by hub.freebsd.org (Postfix) with ESMTP id 9557614F32 for ; Sat, 26 Jun 1999 09:27:48 -0700 (PDT) (envelope-from gnn@punk.neville-neil.com) Received: from punk.meer.net (punk.neville-neil.com [209.157.132.82]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id JAA21200 for ; Sat, 26 Jun 1999 09:27:45 -0700 (PDT) Received: from punk (localhost.meer.net [127.0.0.1]) by punk.meer.net (8.9.2/8.9.2) with ESMTP id JAA13664 for ; Sat, 26 Jun 1999 09:26:29 -0700 (PDT) (envelope-from gnn@punk.neville-neil.com) Message-Id: <199906261626.JAA13664@punk.meer.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org Subject: Building -current with 3.1? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Jun 1999 09:26:28 -0700 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Folks, I've been getting the src-sys stuff via CVS and now want to build it. Can this be done with just the 3.1 tools (right off the CD) or do I need the compilers etc. as well? I get the following when doing a make in src/sys: ===> boot/i386/boot2 cc -elf -I/usr/local/FreeBSD-current/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -Os -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c boot2.c cc1: Invalid option `-Os' Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 10:32:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (Postfix) with SMTP id D568014FFA for ; Sat, 26 Jun 1999 10:32:28 -0700 (PDT) (envelope-from herbelot@cybercable.fr) Received: (qmail 18004 invoked from network); 26 Jun 1999 17:29:48 -0000 Received: from d106.paris-26.cybercable.fr (HELO cybercable.fr) ([212.198.26.106]) (envelope-sender ) by bouvreuil.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 26 Jun 1999 17:29:48 -0000 Message-ID: <37750E00.C226194B@cybercable.fr> Date: Sat, 26 Jun 1999 19:29:36 +0200 From: Thierry Herbelot Organization: Les barbus =?iso-8859-1?Q?associ=E9s?=, Paris, France X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "George V. Neville-Neil" Cc: freebsd-current@freebsd.org Subject: Re: Building -current with 3.1? References: <199906261626.JAA13664@punk.meer.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, The standard compiler has changed between 3.x and -Current (gcc2.7.2.1 => egcs) - so don't even think of compiling code from -Current with Stable tools. You may want to try some "make upgrade" to upgrade all of your OS from 3.X to 4.0 (then you will use the -Current sources for your kernel). I would rather suggest installing a minimal -Current snapshot and then using your -Current source tree. TfH "George V. Neville-Neil" wrote: > > Hi Folks, > > I've been getting the src-sys stuff via CVS and now want to build it. Can > this > be done with just the 3.1 tools (right off the CD) or do I need the compilers > etc. as well? > I get the following when doing a make in src/sys: > > ===> boot/i386/boot2 > cc -elf -I/usr/local/FreeBSD-current/src/sys/boot/i386/boot2/../btx/lib -I. > -fno-builtin -Os -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd > -Wall -Waggregate-return -Wbad-function-cast -Wcast-align > -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith > -Wshadow -Wstrict-prototypes -Wwrite-strings -c boot2.c > cc1: Invalid option `-Os' > > Thanks, > George > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 12:55: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from meer.meer.net (meer.meer.net [140.174.164.2]) by hub.freebsd.org (Postfix) with ESMTP id 06D8C15000 for ; Sat, 26 Jun 1999 12:54:57 -0700 (PDT) (envelope-from gnn@punk.neville-neil.com) Received: from punk.meer.net (punk.neville-neil.com [209.157.132.82]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id MAA03087; Sat, 26 Jun 1999 12:54:54 -0700 (PDT) Received: from punk (localhost.meer.net [127.0.0.1]) by punk.meer.net (8.9.2/8.9.2) with ESMTP id MAA14718; Sat, 26 Jun 1999 12:53:32 -0700 (PDT) (envelope-from gnn@punk.neville-neil.com) Message-Id: <199906261953.MAA14718@punk.meer.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Thierry Herbelot Cc: freebsd-current@freebsd.org Subject: Re: Building -current with 3.1? In-Reply-To: Your message of "Sat, 26 Jun 1999 19:29:36 +0200." <37750E00.C226194B@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Jun 1999 12:53:31 -0700 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The standard compiler has changed between 3.x and -Current (gcc2.7.2.1 > => egcs) - so don't even think of compiling code from -Current with > Stable tools. > > You may want to try some "make upgrade" to upgrade all of your OS from > 3.X to 4.0 (then you will use the -Current sources for your kernel). > > I would rather suggest installing a minimal -Current snapshot and then > using your -Current source tree. > OK, thanks. What I think I'll do (unless someone tells me otherwise) is move to -stable (which is off of RELENG_3 right?) and work from there. My machine to mess with is also my email server and I don't know that -current is the best idea on that. Later, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 12:58: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 7C2E215000 for ; Sat, 26 Jun 1999 12:58:05 -0700 (PDT) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1002) id 79E8E759; Sat, 26 Jun 1999 12:57:56 -0700 (PDT) Date: Sat, 26 Jun 1999 12:57:56 -0700 From: Chris Piazza To: "George V. Neville-Neil" Cc: Thierry Herbelot , freebsd-current@FreeBSD.ORG Subject: Re: Building -current with 3.1? Message-ID: <19990626125756.A11033@norn.ca.eu.org> References: <37750E00.C226194B@cybercable.fr> <199906261953.MAA14718@punk.meer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199906261953.MAA14718@punk.meer.net>; from George V. Neville-Neil on Sat, Jun 26, 1999 at 12:53:31PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 26, 1999 at 12:53:31PM -0700, George V. Neville-Neil wrote: > > The standard compiler has changed between 3.x and -Current (gcc2.7.2.1 > > => egcs) - so don't even think of compiling code from -Current with > > Stable tools. > > > > You may want to try some "make upgrade" to upgrade all of your OS from > > 3.X to 4.0 (then you will use the -Current sources for your kernel). > > > > I would rather suggest installing a minimal -Current snapshot and then > > using your -Current source tree. > > > > OK, thanks. > > What I think I'll do (unless someone tells me otherwise) is move to -stable > (which is off of RELENG_3 right?) and work from there. My machine to mess > with is also my email server and I don't know that -current is the best idea > on that. Just to clarify don't "make upgrade" unless you're going from a.out -> elf. (2.2 -> 3.x generally). Do a normal make world depite what was said above. -Chris -- cpiazza@home.net cpiazza@FreeBSD.org "Life is divided into the horrible and the miserable." -Woody Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 13:50:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from tbsd.org (dns-gw.dns.za.net [209.212.114.217]) by hub.freebsd.org (Postfix) with ESMTP id ADF6715104 for ; Sat, 26 Jun 1999 13:50:08 -0700 (PDT) (envelope-from lists@tbsd.org) Received: from tbsd.org (tbsd.org [206.49.228.7]) by tbsd.org (8.9.3/8.9.1) with ESMTP id WAA02347 for ; Sat, 26 Jun 1999 22:50:31 +0200 (SAST) (envelope-from lists@tbsd.org) Date: Sat, 26 Jun 1999 22:50:31 +0200 (SAST) From: FreeBSD mailing lists To: current@freebsd.org Subject: Ports problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just wondered if it was a problem with my installation or in general, but is anyone else here having problems with ports being dependant on glib12.2 and ports installing glib12.3 instead? I notice I cant install a LARGE number of the ports because of this problem, any suggestions? Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 13:56:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (c1-63-dbn.dial-up.net [196.34.155.63]) by hub.freebsd.org (Postfix) with ESMTP id 7161D14D4E for ; Sat, 26 Jun 1999 13:56:23 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA10146; Sat, 26 Jun 1999 22:55:23 +0200 (SAST) From: Robert Nordier Message-Id: <199906262055.WAA10146@ceia.nordier.com> Subject: Re: boot -P AND autoboot possible? In-Reply-To: <37749B46.E2CB5F82@gorean.org> from Doug at "Jun 26, 1999 02:20:06 am" To: Doug@gorean.org (Doug) Date: Sat, 26 Jun 1999 22:55:17 +0200 (SAST) Cc: sheldonh@uunet.co.za (Sheldon Hearn), freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I can submit patches for the man page(s) if I can get a grip on what's > > > happening where (and when). :-/ What I'd really like to see is a > > > chronological listing, like: > > > > I think you're reading the wrong manpage. I've just had a look at > > loader(8) and can't really see what you'd want to improve. Can you > > confirm that your loader.8 DESCRIPTION starts with > > > > "The program called loader is the third stage of FreeBSD's > > three stage bootstrap. > > Yes, that's the one, but as you point out here we're already talking about > the third stage. The problem is (as I mentioned in my request) /boot.config > bypasses this stage. Various parts of the new loader are well documented, > but there is no overall picture of how the various parts fit together. The proper place for -P is /boot.config. I'm not sure where you got the impression that "/boot.config necessarily bypasses loader", but this isn't the case. The boot(8) man page reads: By default, a three-stage bootstrap is employed, and control is automatically passed from the boot blocks (bootstrap stages one and two) to a separate third-stage bootstrap program, loader. This third stage provides more sophisticated control over the booting process than it is possible to achieve in the boot blocks, which are constrained by occupying limited fixed space on a given disk or slice. However, it is possible to dispense with the third stage altogether, either by specifying a kernel name in the boot block parameter file, /boot.config, or by hitting a key during a brief pause (while one of the characters -, \, |, or / is displayed) before loader is invoked. Booting will also be attempted at stage two, if the third stage cannot be loaded. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 14:11:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id F40DA14C17 for ; Sat, 26 Jun 1999 14:11:43 -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 OAA13116; Sat, 26 Jun 1999 14:11:43 -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 OAA45089; Sat, 26 Jun 1999 14:11:42 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 26 Jun 1999 14:11:42 -0700 (PDT) Message-Id: <199906262111.OAA45089@vashon.polstra.com> To: gnn@neville-neil.com Subject: Re: Who leads networking? In-Reply-To: <199906261534.IAA13137@punk.meer.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199906261534.IAA13137@punk.meer.net>, George V. Neville-Neil wrote: > > I'm new to contributing to FreeBSD but not to working with kernels > etc. I'm thinking of adding a new framing type to PPP which is described in > the latest Transactions on Networking. Who do I talk to about this kind > of stuff? If you want the person specifically in charge of something, see . For networking it's Garrett Wollman . The current@freebsd.org is also a good place to propose changes like the one you mentioned. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 14:13:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (c1-63-dbn.dial-up.net [196.34.155.63]) by hub.freebsd.org (Postfix) with ESMTP id 85FDF14C17 for ; Sat, 26 Jun 1999 14:13:45 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA10488; Sat, 26 Jun 1999 23:11:58 +0200 (SAST) From: Robert Nordier Message-Id: <199906262111.XAA10488@ceia.nordier.com> Subject: Re: 'make all' in /sys/i386/boot fails In-Reply-To: <49750.930374207@axl.noc.iafrica.com> from Sheldon Hearn at "Jun 26, 1999 07:16:47 am" To: sheldonh@uunet.co.za (Sheldon Hearn), Doug@gorean.org (Doug) Date: Sat, 26 Jun 1999 23:11:56 +0200 (SAST) Cc: mike@smith.net.au (Mike Smith), freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Where would I go if I wanted to rebuild my boot blocks to make the > > com console run at a different speed, or is this something I could set > > with one of the voluminous conf files in /boot, or?? > > Try src/sys/boot ? That's the right place to go for the rebuild, but the setting is in /etc/make.conf (BOOT_COMCONSOLE_SPEED). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 15:24:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id ECE5314C2E for ; Sat, 26 Jun 1999 15:24:13 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id SAA10414; Sat, 26 Jun 1999 18:24:00 -0400 (EDT) (envelope-from wollman) Date: Sat, 26 Jun 1999 18:24:00 -0400 (EDT) From: Garrett Wollman Message-Id: <199906262224.SAA10414@khavrinen.lcs.mit.edu> To: gnn@neville-neil.com Cc: current@freebsd.org Subject: Re: Who leads networking? In-Reply-To: <199906262111.OAA45089@vashon.polstra.com> References: <199906261534.IAA13137@punk.meer.net> <199906262111.OAA45089@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > If you want the person specifically in charge of something, see > . For networking it's > Garrett Wollman . And in the particular case of PPP, I defer to its maintainer, . -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 15:30:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 59FC7152D5 for ; Sat, 26 Jun 1999 15:30:07 -0700 (PDT) (envelope-from Spud@netvision.net.il) Received: from RAS1-p15.hfa.netvision.net.il (RAS1-p15.hfa.netvision.net.il [62.0.145.15]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id BAA11940 for ; Sun, 27 Jun 1999 01:30:05 +0300 (IDT) Date: Sun, 27 Jun 1999 01:30:38 +0300 (IDT) From: Tomer Weller X-Sender: Spud@Tomer.DrugsAreGood.org To: current@FreeBSD.Org Subject: COMMENTs ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just cvsupping, why are all the ports getting a COMMENT file ? the DESCR file is not enough anymore ? ====================================== Tomer Weller spud@i.am wellers@netvision.net.il "Drugs are good, and if you do'em pepole think that you're cool", NoFX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 15:34:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from mtiwmhc06.worldnet.att.net (mtiwmhc06.worldnet.att.net [204.127.131.41]) by hub.freebsd.org (Postfix) with ESMTP id E57C714F14 for ; Sat, 26 Jun 1999 15:34:13 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp ([12.77.176.235]) by mtiwmhc06.worldnet.att.net (InterMail v03.02.07.07 118-134) with ESMTP id <19990626223412.YIPE22412@earth.fxp>; Sat, 26 Jun 1999 22:34:12 +0000 Date: Sat, 26 Jun 1999 18:34:11 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Tomer Weller Cc: current@FreeBSD.ORG Subject: Re: COMMENTs ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999, Tomer Weller wrote: > just cvsupping, why are all the ports getting a COMMENT file ? the DESCR > file is not enough anymore ? > COMMENT and DESCR have always been there; see: http://www.freebsd.org/handbook/porting.html ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 19: 9:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles527.castles.com [208.214.165.91]) by hub.freebsd.org (Postfix) with ESMTP id 04A42150DA for ; Sat, 26 Jun 1999 19:09:26 -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 QAA00428; Sat, 26 Jun 1999 16:21:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906262321.QAA00428@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ben Rosengart Cc: freebsd-current@freebsd.org Subject: Re: Out of file descriptors ?? In-reply-to: Your message of "Sat, 26 Jun 1999 09:21:59 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Jun 1999 16:21:09 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 25 Jun 1999, Scot W. Hetzel wrote: > > > What is happening is /etc/defaults/rc.conf pulls in /etc/rc.conf, which then > > pulls in /etc/rc.conf .... repeat until we run out of file descriptors. > > I am not fond of the new defaults/rc.conf system. Used to be when I > wanted to modify something in rc.conf, I opened it up and changed the > value. Now I have to extract a line from defaults/rc.conf, put it in > rc.conf, and change it -- unless I don't understand the new setup > correctly. That makes more work for me, not less. What's the idea > here? Separation between the default initialisation values for parameters, and the actual values of parameters that specifically apply to your system. With only one file, you have no way of adding new (default) parameter values without forcing the user to manually merge the two. The minor extra amount of work in the short term is greatly offset in the long term. Try merging your local changes from a 2.2.x rc.conf with a new 3.x vintage rc.conf to see what I mean. -- \\ 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-current" in the body of the message From owner-freebsd-current Sat Jun 26 19: 9:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles527.castles.com [208.214.165.91]) by hub.freebsd.org (Postfix) with ESMTP id A168214EBB for ; Sat, 26 Jun 1999 19:09:40 -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 PAA00302; Sat, 26 Jun 1999 15:51:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906262251.PAA00302@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Cc: Mike Smith , freebsd-current@freebsd.org Subject: Re: 'make all' in /sys/i386/boot fails In-reply-to: Your message of "Fri, 25 Jun 1999 18:46:05 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Jun 1999 15:51:51 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > sys/i386/boot is deprecated. > > Ok, well actually that could explain why it didn't work then. :) > Where would I go if I wanted to rebuild my boot blocks to make the > com console run at a different speed, or is this something I could set > with one of the voluminous conf files in /boot, or?? /sys/boot -- \\ 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-current" in the body of the message From owner-freebsd-current Sat Jun 26 19:26:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 39EC014BEB for ; Sat, 26 Jun 1999 19:26:19 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA10366; Sun, 27 Jun 1999 12:26:11 +1000 Date: Sun, 27 Jun 1999 12:26:11 +1000 From: Bruce Evans Message-Id: <199906270226.MAA10366@godzilla.zeta.org.au> To: brdean@mindspring.com, freebsd-current@FreeBSD.ORG Subject: Re: kernel panic w/regard to setting io permissions bitmap Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The panic occurs at 'swtch_com+0x6e: ltr %si'. At the time, %si is >0x20, which indexes to what appears to be a busy tss (type=01011b) >with a limit of 0x67. That instruction generates a general protection >fault with an error code of 0. The current process was Idle. >... >Perhaps someone could reproduce this and double check me? Same here. I think it is missing at least enlargement of the limit of 0x67. >Also ... I think I could analyze this better if I could break into the >debugger and set a break point *before* the panic, and start tracing >at the i386_set_ioperm() routine and follow what happens from there. >Is there a function call that I can insert at the appropriate place to >force dropping into the kernel debugger? Just set a breakpoint: Ctrl-SysReq enter ddb b i386_set_ioperm set breakpoint c leave ddb Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 19:42:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from bsd1.gccs.com.au (gw-telstra.gccs.com.au [203.17.152.1]) by hub.freebsd.org (Postfix) with ESMTP id DE23A14C18 for ; Sat, 26 Jun 1999 19:42:21 -0700 (PDT) (envelope-from starr3@gccs.com.au) Received: from lb50x (lb50x.gccs.com.au [203.17.152.10]) by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id MAA62812; Sun, 27 Jun 1999 12:41:03 +1000 (EST) Message-ID: <00be01bec046$acf71430$0a9811cb@gccs.com.au> From: "Harry Starr" To: "Alex Zepeda" , "current" References: Subject: Re: gdb no longer works? Date: Sun, 27 Jun 1999 12:41:03 +1000 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has been happening to me, as well! gdb takes a sig 11 and dies on coredumps on my -current as well. Can't even get to a (gdb) prompt! Also, gcore is busted! Barfs on a line from /proc/${PID}/map It appears that the format of /map lines has changed, and the scanf is failing... ----- Original Message ----- From: Alex Zepeda To: current Sent: Saturday, June 26, 1999 4:35 PM Subject: gdb no longer works? > I've tried numerous times (updating the kernel, buildworld, etc) to get > gdb to work, but so far it seems like ELF coredumps are broken (course > this could be a C++ issue too): > > zippy:~#gdb `which konqueror` konqueror.core > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > Core was generated by `konqueror'. > Program terminated with signal 11, Segmentation fault. > > Register eax not found in core file. > (gdb) > > > - alex > > I thought felt your touch > In my car, on my clutch > But I guess it's just someone who felt a lot like I remember you. > - Translator > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 20:15:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp13.bellglobal.com (smtp13.bellglobal.com [204.101.251.52]) by hub.freebsd.org (Postfix) with ESMTP id AE32714CF0 for ; Sat, 26 Jun 1999 20:15:21 -0700 (PDT) (envelope-from vanderh@ecf.toronto.edu) Received: from localhost.nowhere (ppp18389.on.bellglobal.com [206.172.130.69]) by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id XAA23257; Sat, 26 Jun 1999 23:16:37 -0400 (EDT) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id XAA64910; Sat, 26 Jun 1999 23:15:38 -0400 (EDT) (envelope-from tim) Date: Sat, 26 Jun 1999 23:15:38 -0400 From: Tim Vanderhoek To: "Chris D. Faulhaber" Cc: Tomer Weller , current@FreeBSD.ORG Subject: Re: COMMENTs ? Message-ID: <19990626231538.B64234@mad> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Chris D. Faulhaber on Sat, Jun 26, 1999 at 06:34:11PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 26, 1999 at 06:34:11PM -0400, Chris D. Faulhaber wrote: > On Sun, 27 Jun 1999, Tomer Weller wrote: > > > just cvsupping, why are all the ports getting a COMMENT file ? the DESCR > > file is not enough anymore ? > > COMMENT and DESCR have always been there; see: > http://www.freebsd.org/handbook/porting.html You will notice that the COMMENT file is getting updated on approximately 65% of the ports, though. It's always existed, it just rarely got changed until a recent massive change that hit a lot of them. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 21:24:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C4B5F14C20 for ; Sat, 26 Jun 1999 21:24:33 -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 WAA88475; Sat, 26 Jun 1999 22:24:25 -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 WAA08307; Sat, 26 Jun 1999 22:22:29 -0600 (MDT) Message-Id: <199906270422.WAA08307@harmony.village.org> Subject: General feeling on merging APIs... To: current@FreeBSD.org, tech-kern@netbsd.org, tech@openbsd.org Date: Sat, 26 Jun 1999 22:22:29 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906251653.KAA01796@caspian.plutotech.com> "Justin T. Gibbs" writes: : The hope is to provide a consistent interface across : all *BSDs which is why I've addressed this to all of the *BSD projects. More generally, I'd like to identify areas where the kernel APIs of the various projects have diverged and see what, if anything, can be done about them. I'd also like to get commitment from the various controlling bodies of the *BSD projects to a statement something along the lines of: We support the identification of API differences between the various BSDs. We generally support the idea of merging the APIs, but reserve the right to veto anything too radical. I've been trying to put together some compatibility shims for newconfig drivers in FreeBSD's new-bus world and have run accross a number of minor differences that would be trivial to fix. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 22:26:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 9FFFD14A2F for ; Sat, 26 Jun 1999 22:26:43 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 3D12D75; Sun, 27 Jun 1999 13:26:42 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: mjacob@feral.com, current@FreeBSD.ORG, gibbs@plutotech.com, tech-kern@NetBSD.ORG Subject: Re: Changing the semantics of splsoftclock() In-reply-to: Your message of "Sat, 26 Jun 1999 08:28:15 +1000." <199906252228.IAA03303@godzilla.zeta.org.au> Date: Sun, 27 Jun 1999 13:26:42 +0800 From: Peter Wemm Message-Id: <19990627052642.3D12D75@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >>Why have splr semantics? That is, it raises to splsoftclock if current > >>priority is lower, else doesn't fiddle with it. > > splsoftclock() has always had spllower() semantics, and its main users > (kern_clock.c and kern_time.c) depend on this. > > FreeBSD has a precedent of not changing poor spl names because the change > would be confusing: splnet() should be named splsoftnet() and splimp() > should be named splnet() as in NetBSD. I would like to correct this, it is a source of problems when dealing with NetBSD code. It would be a relatively harmless change for us since it's failure mode is fairly benign. Old code calling splnet() that gets missed will still work, just it will block more than is strictly required. splimp() callers will get found quickly since they'll be an undefined reference. However, it would make backporting drivers from -current to 3.x a bit of a problem.. > Bruce Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 26 23:18:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 4985214EE0 for ; Sat, 26 Jun 1999 23:18:52 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA26124; Sun, 27 Jun 1999 16:18:46 +1000 Date: Sun, 27 Jun 1999 16:18:46 +1000 From: Bruce Evans Message-Id: <199906270618.QAA26124@godzilla.zeta.org.au> To: bde@zeta.org.au, brdean@mindspring.com, freebsd-current@FreeBSD.ORG Subject: Re: kernel panic w/regard to setting io permissions bitmap Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>The panic occurs at 'swtch_com+0x6e: ltr %si'. At the time, %si is >>0x20, which indexes to what appears to be a busy tss (type=01011b) >>with a limit of 0x67. That instruction generates a general protection >>fault with an error code of 0. The current process was Idle. The busy tss seems to be the only problem. The busy bit in the tss descriptor should be clear when the ltr instruction is executed, because the descriptor has just been copied from an image whose busy bit is clear. This was broken in rev.1.332 of machdep.c by moving the initialisation of common_tssd to after the first ltr instruction, so that the busy bit in common_tssd is set. Bruce diff -c2 machdep.c~ machdep.c *** machdep.c~ Sat Jun 26 21:41:33 1999 --- machdep.c Sun Jun 27 15:52:07 1999 *************** *** 1643,1651 **** common_tss.tss_ss0 = GSEL(GDATA_SEL, SEL_KPL) ; common_tss.tss_ioopt = (sizeof common_tss) << 16; - gsel_tss = GSEL(GPROC0_SEL, SEL_KPL); - ltr(gsel_tss); - private_tss = 0; tss_gdt = &gdt[GPROC0_SEL].sd; common_tssd = *tss_gdt; dblfault_tss.tss_esp = dblfault_tss.tss_esp0 = dblfault_tss.tss_esp1 = --- 1643,1651 ---- common_tss.tss_ss0 = GSEL(GDATA_SEL, SEL_KPL) ; common_tss.tss_ioopt = (sizeof common_tss) << 16; tss_gdt = &gdt[GPROC0_SEL].sd; common_tssd = *tss_gdt; + private_tss = 0; + gsel_tss = GSEL(GPROC0_SEL, SEL_KPL); + ltr(gsel_tss); dblfault_tss.tss_esp = dblfault_tss.tss_esp0 = dblfault_tss.tss_esp1 = To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message